--------------------------------------------------------------------------------
LKPOPNREAD, Look up file 'file-spec' opened for reading.
Explanation: The specified POLMERGE look-up file has been opened successfully.
User action: None.
LSTOPNOUT, /LIST list file 'file-spec' opened for output.
Explanation: The specified listing file has been opened successfully.
User action: None.
--------------------------------------------------------------------------------
ACIGN, AC of type other than 4 or 5 ignored in feature 'number'.
Explanation: The input file contains an AC of type other than the left right codes 4 or 5. It is not copied to the output file.
User action: Check that useful information held in these codes is not being lost. In general polygon data should not contain ACs which do not represent left right codes.
MISSAC, Missing Left or Right AC entry in NF 'number'.
Explanation: A feature was present in the input file with no AC 4 or 5 left right codes. This message is only output when the /ACCHECK qualifier is present.
User action: Check the input file and correct using LITES2. If polygon merging is to occur regardless of left right coding then /NOACCHECK should be specified.
MULTAC4, multiple AC 4 codes - only first is output in feature with FSN 'number'.
Explanation: A feature in the input file has more than one AC 4 code. POLMERGE only reads one AC 4 per feature. Any subsequent ones are ignored and not output to the merged file.
User action: Check that no useful information is held in the secondary ACs which would be lost after POLMERGE processing.
MULTAC5, multiple AC 5 codes - only first is output in feature with FSN 'number'.
Explanation: A feature in the input file has more than one AC 5 code. POLMERGE only reads one AC 5 per feature. Any subsequent ones are ignored and not output to the merged file.
User action: Check that no useful information is held in the secondary ACs which would be lost after POLMERGE processing.
PHANNOMOTH, Phantom neighbour for polygon number 'number' has no mother polygon, and will be eliminated.
Explanation: The phantom neighbour for an isolated polygon which is being eliminated has no mother polygon, and will be eliminated regardless of specified elimination basis.
User action: Check the input .IFJ file if the resulting .IFF has an error.
TOOMNYBOUNDS, too many common boundaries between polygons starting with FSN 'number' and 'number'
Explanation: The number of common boundaries between two polygons to be merged has exceeded the current limit. Processing continues but the polygon is not merged.
User action: The specified FSNs will allow the polygon boundary to be identified using LITES2. It is not envisaged that this boundary limit will be exceeded and so Laser-Scan should be notified if this message occurs.
TOOMNYNEIGH, too many neighbours in polygon with first FSN 'number' - not merged.
Explanation: The limits for the number of neighbours a polygon may have for merging to occur has been exceeded. Processing continues but the polygon is not merged.
User action: The specified FSNs will allow the polygon to be identified using LITES2. Generally the polygon will be fairly large. It is not envisaged that this boundary limit will be exceeded and so Laser-Scan should be notified if this message occurs.
--------------------------------------------------------------------------------
ACINCON, polygon labels in AC texts inconsistent in feature with FSN %N (%N).
Explanation: If the /ACCHECK qualifier is present, this message is output for those polygons formed with inconsistent labels in the text fields of their AC 4 or 5 codes. POLMERGE processing stops after the consistency checking stage.
User action: Correct the input file using LITES2. If polygon merging is to occur regardless of the left right coding then specify /NOACCEHCK.
CLINIFF, error closing input IFF file 'file-spec'.
Explanation: POLMERGE has failed to close the input IFF file.
User action: Supplementary messages which follow this message should help to identify the cause of the failure.
CLLIST, error closing list file 'file-spec'.
Explanation: POLMERGE has failed to close the listing file specified with the /LIST qualifier.
User action: Supplementary messages which follow this message should help to identify the cause of the failure.
CLLOOKUP, error closing lookup file 'file-spec'.
Explanation: POLMERGE has failed to close the lookup file selected with the /LOOKUP qualifier.
User action: Supplementary messages which follow this message should help to identify the cause of the failure.
CLOUTIFF, error closing output IFF file 'file-spec'.
Explanation: POLMERGE has failed to close the output IFF file.
User action: Supplementary messages which follow this message should help to identify the cause of the failure.
INVALELIMTOL, 'tolerance' is an invalid eliminate tolerance - must be positive.
Explanation: One of the eliminate tolerances specified with the /AREA or /RATIO qualifiers is negative.
User action: Correct the tolerance values on the command line.
INVALMERTOL, 'tolerance' is an invalid merge tolerance - must be positive.
Explanation: One of the merge tolerances specified with the /AREA or /RATIO qualifiers is negative.
User action: Correct the tolerance values on the command line.
OPLIST, error opening /OUTPUT list file 'file-spec' for output.
Explanation: POLMERGE is unable to open the file specified by the /LIST qualifier.
User action: Supplementary messages which follow this message should help to identify the cause of the failure.
OPLOOKUP, error opening /LOOKUP file 'file-spec' for reading.
Explanation: POLMERGE is unable to open the file specified by the /LOOKUP qualifier.
User action: Supplementary messages which follow this message should help to identify the cause of the failure.
TOOMNYCODES, too many primary or secondary codes in lookup file.
Explanation: The limit of the number of primary or secondary codes which may be specified in the lookup file has been exceeded.
User action: If possible, remove the number of non-essential codes in the lookup file. If the number of codes required are still greater then the maximum permitted, then please consult Laser-Scan.
UNEXPEOF, unexpected end of IFF file 'file-spec'.
Explanation: The specified input IFF file was corrupt and did not have an IFF EJ entry.
User action: Use IMEND to correctly terminate the file. If the segment file is bad, re-run ILINK/STRUCTURE on the repaired IFF file before using POLMERGE. If the problem persists try reading the suspect file into LITES2 (and then exiting to create a new version of the file) before retrying ILINK and POLMERGE. If the problem still persists then consult Laser-Scan.
--------------------------------------------------------------------------------
INTRNLERR, internal consistency error 'number' detected in routine 'routine-name' - please submit an SPR.
Explanation: POLMERGE has detected a sever error in the named routine.
User action: Please report the problem to Laser-Scan. Include the input file and run information in a Software Performance Report (SPR).
LOST, failed to locate IFF entry at recorded address - position lost.
Explanation: POLMERGE has attempted to locate an entry in one of the input IFF files which no longer appear to exist. This is an unrecoverable error and POLMERGE is consequently lost.
User action: Try reading the input files into LITES2. If this succeeds than the problem lies within POLMERGE. Please make a copy of the input IFF files and report the problem to Laser-Scan.
UNEXPENTJP, unexpected entry 'entry' found while patching JP entries after NF 'feature number'.
Explanation: POLMERGE was unable to patch a JP entry while updating a file.
User action: Please make a copy of the input IFF files and report the problem to Laser-Scan.
--------------------------------------------------------------------------------