UNCLASSIFIED
Error Conditions
This section describes each of the
error messages that can be generated by the GEOTRANS application. Errors are
grouped into four types.
Initialization Error Messages
Coordinate Conversion
Error Messages
User-Defined Ellipsoid & Datum Error
Messages
File Processing Error
Messages
Initialization Error
Messages
Initialization error messages are
returned by the MSP Coordinate Conversion Service when it is unable to
initialize properly.
The Initialization error messages
are:
 - Error initializing
     MSP Coordinate Conversion Service: Unable to locate ellipsoid data file: ellips.dat!
- Error initializing
     MSP Coordinate Conversion Service: Ellipsoid table is full!
- Error initializing
     MSP Coordinate Conversion Service: Invalid ellipsoid code!
- Error initializing
     MSP Coordinate Conversion Service: Unable to locate datum data files:
     3_param.dat, 7_param.dat!
- Error initializing
     MSP Coordinate Conversion Service: Datum table is full!
- Error initializing
     MSP Coordinate Conversion Service: Unable to read datum file!
- Error initializing
     MSP Coordinate Conversion Service: Unable to locate geoid
     data
     files:
     egm84.grd, egm96.grd!
- Error initializing
     MSP Coordinate Conversion Service: Unable to read geoid
     file!
Typically, multiple initialization
error messages are generated.  After each
of these messages have been acknowledged, a Failed to create empty document
dialog box will appear. 
Initialization failure most often
occurs as a result of the application software being unable to open or read one
or more of five key data files:
1)      ellips.dat  containing ellipsoid parameter values,
2)      3_param.dat
 containing datum parameter values for datums that
are specified only by their displacement relative to WGS84,
3)      7_param.dat
 containing datum parameter values for datums that
are specified in terms of displacement, rotation, and scale differences
relative to WGS84,
4)      egm96.grd
 containing geoid separation values for Earth
Gravity Model 1996,
5)      egm84.grd
 containing geoid separation values for Earth
Gravity Model 1984.
These data files are normally located
in the /data subdirectory, and the GEOTRANS software looks for them there by
default. As an alternative, you can define the environment variable CCS_DATA,
and place the files in the directory identified by this variable.
Coordinate Conversion
Error Messages
Coordinate conversion error messages
are displayed by the GEOTRANS software when a parameter or coordinate value is
invalid relative to a particular coordinate system or map projection. In some
cases, all of the individual parameter or coordinate values may be valid, but
the combination is not. It may also be possible for the input coordinates to be
invalid relative to the output coordinate system or map projection after being
converted. When any of these errors are detected during interactive operations,
a message box is displayed, identifying either the input or the output
coordinate system or map projection, and the parameter or coordinate value, or
values, which are invalid. When any of these errors are detected during file
processing, the same message is written to the output coordinate file in the
form of a comment.
Each message includes a prefix that
indicates whether the problem is in the input or output portion of the
conversion process, and the coordinate reference frame involved. For example,
if the error occurred in a conversion from UTM to geodetic coordinates, the
prefix might read "Input UTM Coordinates:"
The Coordinate Conversion warning
messages are:
 - Latitude is too far from Central
      Meridian, distortion may be significant  This warning
     indicates that the input coordinates are located too far from the central
     meridian of either the input or output projection, as indicated in the
     message prefix. The conversion is performed, but you should recheck the
     input coordinates and the Central Meridian
     parameter value.
- Location is not within valid domain for current datum
      This warning indicates that the input coordinates are not located in the
     part of the world addressed by the current input or output datum, as
     indicated in the message prefix. The conversion is performed, but you
     should recheck the input coordinates and the input and output datum
     selections.
The Coordinate Conversion error
messages are:
 - 1st and 2nd Standard Parallels
     cannot both be zero  the 1st and 2nd Standard
     Parallel parameter values are both zero (i.e., the equator), and so do not
     define a valid projection cone.
 - Central Meridian out of range  the Central
      Meridian parameter value for the input or output projection,
     as indicated in the message prefix, is outside the valid range for
     longitude values, which is from -180° to +360°.
 - Easting/X out of range  the Easting/X coordinate
     value is not valid for the input or output projection, as indicated by the
     message prefix. The value is too far from the False Easting parameter
     value for the projection.
 - Easting/Northing too far from center of projection-
     the combination of the Easting/X and Northing/Y coordinate values denote a
     point that is located too far from the center of the current input or
     output projection, as indicated by the message prefix.
 - Invalid Standard Parallel  the Standard Parallel
     parameter value is not valid for the Equidistant Cylindrical projection.
 - Invalid 1st Standard Parallel  the 1st Standard
     Parallel parameter value is not valid for the currently specified Albers
     Equal Area Conic or Lambert Conformal Conic projection. The valid range is
     from -90° to +90°, but does not include the poles themselves.
 - Invalid 2nd Standard Parallel  the 2nd Standard
     Parallel parameter value is not valid for the currently specified Albers
     Equal Area Conic or Lambert Conformal Conic projection. The valid range is
     from -90° to +90°, but does not include the poles themselves.
 - Invalid British National Grid Coordinate String  the
     input British National Grid coordinate string does not contain a valid
     British National Grid coordinate value. The British National Grid coordinate
     string may contain invalid characters or may not be formatted correctly
 - Invalid GEOREF Coordinate String  the input GEOREF
     coordinate string does not contain a valid GEOREF coordinate value.
- Invalid GARS Coordinate String  the input GARS
     coordinate string does not contain a valid GARS coordinate value.
 - Invalid MGRS Coordinate String  the input MGRS
     coordinate string does not contain a valid MGRS coordinate value. The MGRS
     string may not be formatted correctly, or the zone letter, zone number,
     100,000m square designation, and easting/northing values specified by the
     string may not be consistent with one another.
- Invalid USNG Coordinate String  the input USNG
     coordinate string does not contain a valid USNG coordinate value. The USNG
     string may not be formatted correctly, or the zone letter, zone number,
     100,000m square designation, and easting/northing values specified by the
     string may not be consistent with one another.
 - Invalid Zone  the UTM zone number specified does not
     have a valid value. The valid range for UTM zone numbers is from 1 to 60.
 - Invalid Zone Override  the UTM zone number specified
     in the Set Zone field is too far from the 'natural' UTM zone of the input
     coordinates. The specified zone must be adjacent to the 'natural' zone of
     the input coordinates.
 - Latitude out of range  the Latitude coordinate value
     is not valid for the input or output projection, as indicated by the
     message prefix. Depending on the projection, this may mean that the
     latitude value is too close to a pole or the equator, or is outside the
     valid range for latitude values, which is from -90° to +90°.
 - Latitude 1 out of range  the Latitude 1 parameter
     value for the input or output Oblique Mercator projection is not valid.
     Latitude 1 is outside the valid range for the first latitude values, which
     is from -90° to +90°, not including the poles.
 - Latitude 1 and Latitude 2 cannot be equal  Latitude
     1 and Latitude 2 parameter values are the same. 
 - The latitude part of the GEOREF string is greater
     than 60  the latitude portion of a GEOREF string must have a value in the
     range from 0000 to 5999.
 - Latitude 2 out of range  the Latitude 2 parameter
     value for the input or output Oblique Mercator projection is not valid.
     Latitude 2 is outside the valid range for the second latitude values,
     which is from -90° to +90°, not including the poles.
 - Longitude out of range  the Longitude coordinate
     value is not valid for the input or output projection, as indicated by the
     message prefix. This means that the longitude value is outside the valid
     range for longitude values, which is from -180° to +360°.
 - Longitude 1 out of range  the Longitude 1 parameter
     value for the input or output Oblique Mercator projection is not valid.
     Longitude 1 is outside the valid range for latitude values, which is from
     -180° to +360°.
 - Longitude 2 out of range  the Longitude 2 parameter
     value for the input or output Oblique Mercator projection is not valid.
     Longitude 2 is outside the valid range for latitude values, which is from
     -180° to +360°.
 - The longitude part of the GEOREF string is greater
     than 60  the longitude portion of a GEOREF string must have a value in
     the range from 0000 to 5999.
 - Northing/Y out of range  the Northing/Y coordinate
     value is not valid for the input or output projection, as indicated by the
     message prefix. The value is too far from the False Northing parameter
     value for the projection.
 - Origin Latitude (or Latitude of True Scale) out of
     range  the Origin Latitude (or Latitude of True Scale) parameter value
     for the input or output projection, or Local
     Cartesian coordinate system, as indicated in the message prefix, is not
     valid. Depending on the projection, this may mean that the Origin Latitude
     is too close to a pole or the equator, or is outside the valid range for
     latitude values, which is from -90° to +90°.
 - Origin Longitude (or Longitude Down from Pole) out of
     range  the Origin Longitude (or Longitude Down from Pole) parameter value
     for the input or output projection, or Local Cartesian coordinate system,
     as indicated in the message prefix, is not valid. This means that the
     Origin Longitude value is outside the valid range for longitude values,
     which is from -180° to +360°.
 - Point 1 and Point 2 cannot be in different
     hemispheres  Latitude 1 and Latitude 2 parameter values are in opposite
     hemispheres. 
 - Scale Factor out of range  the Scale Factor
     parameter value is not valid (i.e., either too large or too small) for the
     input or output projection, as indicated by the message prefix.
 - Standard Parallels cannot be equal and opposite
     latitudes  the 1st and 2nd Standard Parallel
     parameter values denote the same latitude, but in opposite hemispheres.
     This would cause the projection cone to become a cylinder, and is not
     allowed.
 - Coordinates are outside valid area  the specified
     British National Grid coordinate string is outside the valid conversion
     area.
 - Ellipsoid must be Airy  the specified ellipsoid for
     a British National Grid coordinate string must be Airy.
 - Ellipsoid must be International  the specified
     ellipsoid for New Zealand Map Grid coordinates must be International.
See the description of the indicated
coordinate reference frame, and/or the description(s) of the indicated
parameter or coordinate field(s) for more information on the valid ranges and
valid combinations of map projection parameter and coordinate values.
It is possible for the MSP Coordinate
Conversion Application to output error messages other than those listed above.
However, these error messages should never appear under normal circumstances, and
indicate that the software is in an invalid internal state.
User-Defined Ellipsoid & Datum
Error Messages
User-defined datum error messages may
be generated when you use the Create... or Delete... commands in the Datum
menu. When creating a new user-defined datum, if the code specified for the new
datum is already in use, or if any of the parameters for the new datum are not
value, an error message box will be displayed after the OK button is clicked.
Once the error message is acknowledged, the message box disappears and you are
returned to the Create Datum dialog box, where you may either correct the
invalid inputs, or cancel the operation.
When deleting a user-defined datum,
if the code specified for the datum to be deleted is not user-defined, an error
message box will be displayed after the OK button is clicked. Once the error
message is acknowledged, the message box disappears and you are returned to the
Delete Datum dialog box, where you may either select another datum, or cancel
the operation.
The user-defined datum error messages
are:
 - 3-parameter datum table is full  the 3-parameter
     datum table has run out of available space. No more new datums can be created until the Datum module is
     modified to allocate additional space.
- 7-parameter datum table is full  the 7-parameter
     datum table has run out of available space. No more new datums can be
     created until the Datum module is modified to allocate additional space.
- Error returned by Ellipsoid module  the most likely
     cause for this message is that the ellipsoid specified for the new
     user-defined datum is invalid. Select another ellipsoid.
 - Invalid local datum domain of validity  the
     specified latitude and longitude values do not form a valid bounding
     geodetic rectangle. The southernmost latitude is greater than the
     northernmost latitude, and/or the westernmost longitude is greater than
     the easternmost longitude. The bounding rectangle cannot cross the ±180°
     line.
 - Latitude out of range  one or both of the latitude
     values specified for the domain of validity of the new datum is not valid.
 - Longitude out of range  one or both of the longitude
     values specified for the domain of validity of the new datum is not valid.
 - Specified code not user defined  the specified datum
     is not a user-defined datum. 
 - Specified code already in use- the code specified for
     the new user-defined datum is already in use for an existing datum. Choose
     a different code for the new datum.
 - Standard error values must be positive,
     or -1 if unknown  one or more of the datum shift standard error
     values is negative, but is not -1. Correct the standard error value(s).
User-defined ellipsoid error messages
may be generated when you use the Create... command in the Ellipsoid menu. When
creating a user-defined ellipsoid, if the code specified for the new
user-defined ellipsoid is already in use, or if the ellipsoid axis values are
not valid, an error message box will be displayed after the OK button is
clicked. Once the error message is acknowledged, the message box disappears and
you are returned to the Create Ellipsoid dialog box, where you may either
correct the invalid inputs, or cancel the operation.
When deleting a user-defined
ellipsoid, if the code specified for the ellipsoid to be deleted is not
user-defined, an error message box will be displayed after the OK button is
clicked. Once the error message is acknowledged, the message box disappears and
you are returned to the Delete Ellipsoid dialog box, where you may either
select another ellipsoid, or cancel the operation.
The user-defined ellipsoid error
messages are:
 - Ellipsoid flattening must be between 250 and 350 
     self-explanatory. Correct the flattening value.
 - Ellipsoid is in use by a datum  the user-defined
     ellipsoid is in use by a user-defined datum and can not be deleted. You
     must delete all user-defined datums that use the
     ellipsoid before it can be deleted.
 - Ellipsoid semi-major axis must be greater than zero 
     self-explanatory. Correct the semi-major axis value.
 - Ellipsoid table is full  the ellipsoid table has run
     out of available space. No more user-defined ellipsoids can be created
     until the Ellipsoid module is modified to allocate additional space.
 - Specified code already in use  the code specified
     for the new ellipsoid is already in use for an existing ellipsoid. Choose
     a different code for the new ellipsoid.
 - Specified code not user defined  the specified
     ellipsoid is not a user-defined ellipsoid.
File
Processing Error Messages
File processing error messages are
generated when the header of an input coordinate file does not have the proper
format, or when a particular set of coordinates in the body of an input
coordinate file cannot be read successfully, or contains an illegal value. When
an error is detected in the header of an input coordinate file, a message box
is displayed, and file processing is aborted. When an error is detected in the
body of an input coordinate file, a message is written to the output coordinate
file in the form of a comment.
The File Processing input coordinate
file header error messages are:
 - Input file error opening file  the file designated
     by the specified path and file name could not be opened, probably because
     it does not exist. Recheck the file and directory/folder names, and try
     again.
 - Input file error in keyword  a line in the input
     coordinate file header does not start with a recognizable keyword.
 - Input file error in coordinate type  a line in the
     input coordinate file header starting with the keyword 'COORDINATES' or
     'PROJECTION' did not contain a valid value.
 - Input file error in datum  a line in the input
     coordinate file header starting with the keyword 'DATUM' did not contain a
     valid datum code.
 - Input file error in Central Meridian  a line in the
     input coordinate file header starting with the keyword 'CENTRAL MERIDIAN'
     did not contain a legal value, or contained a value outside the valid
     range for a longitude (-180° to +360°).
 - Input file error in Origin Latitude  a line in the
     input coordinate file header starting with the keyword 'ORIGIN LATITUDE'
     did not contain a legal value, or contained a value outside the valid
     range for a latitude (-90° to +90°).
 - Input file error in Origin Longitude  a line in the
     input coordinate file header starting with the keyword 'ORIGIN LONGITUDE'
     did not contain a legal value, or contained a value outside the valid
     range for a longitude (-180° to +360°).
 - Input file error in Origin Height  a line in the
     input coordinate file header starting with the keyword 'ORIGIN HEIGHT' did
     not contain a legal value.
 - Input file error in Standard Parallel  a line in the
     input coordinate file header starting with the keyword 'STANDARD PARALLEL'
     did not contain a legal value, or contained a value outside the valid
     range for a latitude (-90° to +90°).
 - Input file error in Standard Parallel 1  a line in
     the input coordinate file header starting with the keyword 'STANDARD
     PARALLEL 1' did not contain a legal value, or contained a value outside
     the valid range for a latitude (-90° to +90°).
 - Input file error in Standard Parallel 2  a line in
     the input coordinate file header starting with the keyword 'STANDARD
     PARALLEL 2' did not contain a legal value, or contained a value outside
     the valid range for a latitude (-90° to +90°).
 - Input file error in Latitude 1  a line in the input coordinate
     file header starting with the keyword 'LATITUDE ONE' did not contain a
     legal value, or contained a value outside the valid range for the first
     latitude (-89° to +89°, excluding the equator).
 - Input file error in Longitude 1  a line in the input
     coordinate file header starting with the keyword 'LONGITUDE ONE' did not
     contain a legal value, or contained a value outside the valid range for a
     longitude (-180° to +360°).
 - Input file error in Latitude 2  a line in the input
     coordinate file header starting with the keyword 'LATITUDE TWO' did not
     contain a legal value, or contained a value outside the valid range for
     the second latitude (-89° to +89°).
 - Input file error in Longitude 2  a line in the input
     coordinate file header starting with the keyword 'LONGITUDE TWO' did not
     contain a legal value, or contained a value outside the valid range for a
     longitude (-180° to +360°).
 - Input file error in False Easting  a line in the
     input coordinate file header starting with the keyword 'FALSE EASTING' did
     not contain a legal value.
 - Input file error in False Northing  a line in the
     input coordinate file header starting with the keyword 'FALSE NORTHING'
     did not contain a legal value.
 - Input file error in Scale Factor  a line in the
     input coordinate file header starting with the keyword 'SCALE FACTOR' did
     not contain a legal value.
 - Input file unknown error  the input coordinate file
     header could not be parsed successfully. Check to make sure that the
     specified file was actually a valid coordinate file.
Unless otherwise indicated above, you
should examine the header of the input coordinate file, and use a text editor
to correct the error. See the description of the indicated field for
information on the valid ranges of map projection parameter and coordinate
values.
The File Processing input coordinate
file body error messages are:
 - Error reading coordinates from input file  the line
     containing a set of coordinates was not formatted properly, or contained
     one or more illegal coordinate values.
In addition, any of the coordinate
conversion error messages contained in the previous section can occur during
file processing. These messages are written to the output coordinate file in
the form of comments. The File Processing dialog box displays the number of
such errors in the file when file processing is complete. Examine the line in
the input coordinate file which corresponds to the line containing the error
message in the output coordinate file (there is a one-to-one correspondence),
and correct the contents of the input coordinate file using a text editor. See
the descriptions of the coordinate systems, and the coordinate field
descriptions, for information on the valid formats and ranges of coordinate
values.
UNCLASSIFIED