11. Error and Warning messages

Extensive data checking is performed when reading the input data and also during further program flow. Logical and formal errors are immediately notified. One must differentiate between fatal mistakes which are marked by an "S", "D", "F" or "P" and comments and warning messages which are marked by an "C" or "W". At a fatal message the program will be stopped after the next processing step. Though C- and W-messages indicate a possible error the program continues as normal. The messages generally are of the format

        *** Cxxx Message

with        *** :stars as markers
        C :        classification:
                C    comments
                W    warning messages
                S    software protection or license errors (fatal)
                D    capacity / dimension problems (fatal)
                F    fatal data errors
                P    unexpected events / program errors (fatal)
        xxx :        error number
        Message:    short explanation text

Errors which may have been detected when reading the input data from GEO INPUT file will be printed immediately after the corresponding input line.

An explanation for each error number is given below, together with suggestions for avoiding or eliminating the errors. The checks mentioned here do not refer to errors in measurements.

In order to provide a fast user support an on-line data communication and eMail service have been established.

The following error explanations may refer to the remarks for special cases at the end of this chapter.

C101	Camera <val> not in use. Statement ignored Camera <val> has not been allocated to any photo and therefore is not necessary for the calculation.
C102	Camera number in image data corrected to trace number
C103	Inversion and data snooping suppressed because of warning W225
C104	Inversion and data snooping suppressed because redundant additional parameters were eliminated after last iteration Eliminate from input all additional parameters which have been recognised as redundant and start the program again for further iterations.
C105	More then <val> identical points. Listing aborted
C106	Only one block. No transformation
C107	Pass no. <val> not in list. Statement ignored
C108	Photo no. <val> not found. Statement ignored
C109	Photo no. <val> not in list. Statement ignored Photo <val> is not contained in the block. The approximate values of the orientation will not be required.
C110	Point <val> inactive. Line ignored The indicated point was skipped by the user or the point name is out of selected range.
C111	Unused point <val> ignored
W201	<val> points in block lost
W202	<val> transformation points lost
W203	Block is not oriented by control points Reference to a possibly defective system. The seven datum parameters (3 translations, 3 rotations, scale) are not totally defined by the control points. If no other observations add to datum definition, as for example image orientations, zenith distances, height differences, azimuth, stereo basis or distances, a defective normal-equation system can be expected. See Section 2.4. A free network adjustment should possibly be used.
W204	Camera number <val> in image data does not fit with trace number <val>
W205	Geometry not sufficient for block transformation
W206	Indefinite column no. <val>. Diag. element= <val> The unknown no. <val> cannot be estimated. The normal-equation matrix is unconditioned. See also W222. <val> was computed as diagonal element.
W207	Statement "<str>" is empty The preceding input statement <val> is used for definition of standard deviations. It does not include values, and therefore subsequent corresponding measurements cannot be considered in the adjustment.
W208	Max. no. of iterations reached, but after last iteration redundant additional parameters have been eliminated. More iterations necessary Eliminate from input all additional parameters which have been recognised as redundant and start the program again for further iterations.
W209	Max. no. of iterations reached, but the values in solution vector are greater than the selected criterion of termination. More iterations necessary Whether the criteria to terminate iterations or the maximum number of iterations was too small (see PARM statement). Note the printed largest value in the solution vector and, if necessary, start the program anew for further iterations.
W210	Not all input statements processed (in SKIP)
W211	No known point in model <val>/<val>
W212	No observations for unknown no. <val> No observations exist for unknown no. <val>. A defective system will be indicated and further explanation will be given..
W214	Not enough transformation points. <val> blocks not transformed
W215	Error <val> in photo sequence reordering
W216	Not enough points to transform block <val> into block <val>
W218	Photo no. <val> not oriented
W220	Position of G-matrix not efficient
W221	Problem to compute initial coord.s for point <val> <str>
W222	There are <val> unconditioned unknowns The normal-equation matrix is unconditioned with a system defect <val>. The following lines contain exact information on the unknowns in question. The approximations to these unknowns computed by the program or those indicated by the user are assumed. The program does not differentiate between configuration defects and datum defects (see Section 2.4).
W224	Vector ex and delta for camera <val> missing. Zero substituted Camera <val> is included in a stereo metric camera condition. BINGO introduces the additional unknowns e' (eccentricity vector) for each camera in question. Approximate values (empty ECES and ECCA statement) or better, measured values or calibration values with appropriate standard deviations (ECES and ECCA statement), should be introduced. The program sets all values to zero.
W225	l(T)Pl - n(T)x < 0.0 : <val>Divergence? vTPv is calculated by means of lTPl - nTx for estimation of s0. This calculation yields the negative value <val>. This error can be caused by very unrealistic approximations to the unknowns (far beyond the linear range), or it may occur during divergence in the iteration process.
W226	Only <val> points in photo <val>
W227	No known point in model. Model rejected
W228	Optimisation rejected. Photo <val> not indexed
W229	Zero arguments in function riwinb
W230	<val> Points have been skipped during block transformation
W231	<val> statement ignored. Data already in project file
W232	Photo <val> has no connections
W233	No points inside range <val> to <val>. Statement ignored')
W234	Point <val> to be skipped not found in photo data
W235	Largest photo coordinate is <val>. Check your measurement unit
W236	<val> points have been skiped from ITERA file because of format errors
W237	Ending line missing in photo coordinate file
W238	"FILE GPS" statement should contain two standard deviation values - one value for xy, and one for z - or none. First standard deviation value used for x/y, second for z'
W239	"FILE IMU" statement should contain four standard deviation values: 1st for x/y, 2nd for z, 3rd for phi/omega, and 4th for kappa - or none. All values ignored. 1.0 substituted.
W240	Data not in ascending order of GPS time in line <val>
W241	Focal length of camera <val> is unknown parameter. No standard deviation defined
W242	Principal point of camera <val> is unknown parameter. No standard deviation defined
W243	Data line <val> contains tabulator characters. This might lead to unexpected results
W245	Double GPS position data for photo <val>
W246	All radial distortion values have the same sign (+ or -). I.e.: High correlation with focal length')
W247	Largest image radius is <val>. Radial distortion values go up to r= <val> <val> value(s) ignored.
W248	Not enough radial distortion values. Largest image radius is <val> Distortion values go only up to r=<val>
S301	CmStick module not found
S302	Insufficient license for BINGO-SPOT. Call for an upgrade
S303	Insufficient license for Windows NT version. Call for an upgrade
S304	License key mismatch
S309	<str> not licensed in this program version. Ask your supplier for an upgrade
D401	In photo <val> more than <val> points found The number <val> of measurements per photo has been exceeded in photo <val>. Possibly the last lines (point no < 0) of the photo are missing or have not been placed correctly in the input data file.
D402	More than <val> skipped photo measurements. Not all data stored
D403	No. of blocks exceeds limit of <val>
D404	Not all <val> transformation points used. Max= <val>
D405	Not enough memory for factorisation One of the installation parameters has an incorrect value; or: see remark A-2.
D406	Not enough memory for sorting The memory is not large enough for sorting the photo measurements. Either the data include a point which appears in an exceptionally large number of photos or in all, or a photo contains too many measurements.
D407	Not enough memory to test add. par. <val> <val> The required core memory space exceeds capacity <val>. Not all additional parameters can be checked simultaneously. At first only include a few additional parameters in the adjustment until the program has eliminated the additional parameters for these cameras. Then eliminate those parameters from input which have been deleted by the program, and add the additional parameters for the next camera, etc.
D408	Only three groups permitted The program BINGO processes up to three GRUP statements. Thus, up to four point-groups with different weights can be established. Combine the points so that only three GRUP statements are necessary.
D409	Point no. <val> in <val> photos found. Max= <val> <val> photo measurements are available for point <val>. The capacity of BINGO permits processing of <val> photo measurements per point. Reduce the number of photo measurements for this point. Take care to adopt the most favourable intersections
D410	Too many GPS files. Max= <val>
D411	Too many SKIP statements. Line ignored
D412	Too many additional parameters. Max= <val> The number of additional parameters exceeds the capacity of <val> additional parameters per camera.
D413	Too many ambiguity parameters or too many shift and drift parameters
D414	Too many blocks for matrix N The normal-equation matrix contains many unknowns and a great number of elements, or the sequence of unknowns is unfavourable. The necessary capacity is indicated above in line ‘PROFILE OF NORMAL EQUATION MATRIX N’. Matrix N is written on disk block by block. The number of blocks exceeds the capacity of BINGO. Divide the block.
D415	Too many distortion values
D416	Too many links. Max= <val>
D417	Too many photo station data. Max= <val> The available capacity of <val> photo stations is already exhausted.
D418	Too many photos or ranges selected
D419	Too many photos. Max= <val> <val> photos at most can be processed in BINGO. The allocated IMAGE COORDINATE file contains more than <val> photos. This exceeds the capacity. Subdivide the block.
D420	Too many points in block
D421	Too many points. Max= <val> points at most can be processed in BINGO. This capacity has been exceeded.
D422	Too many satellite passes. Max= <val>
D423	Too many sets of directions. Max= <val> The number of sets of directions exceeds the capacity of <val> sets.
D424	Too many stereometric camera conditions. Max= <val> The available capacity of <val> stereometric-camera conditions is already exhausted.
D425	Too many survey measurements. Max= <val> The number of survey measurements (DIFF, DISH, DIS3, ZEDI, AZIM, and SEDI statements and GPS data) exceeds the capacity of <val> measured values.
D426	Too many transf. points
D427	Too many unknowns <val> <val> The number of <val> unknowns exceeds the capacity of <val> unknowns. Divide the block.
D428	Too many scanner images. Max= <val>
D429	Too many control points. Max= <val>
D430	Not enough room to store satellite data
D431	Too many SKIP/UNSK/RENU statements. Max= <val>
D432	Too many cameras. Max = <val>
F501	(Pll / n-u) < 0. MXIT=-1 substituted A negative value results when the product is divided by the redundancy of the block (number of observations minus number of unknowns). This error may result from very unrealistic approximations to the unknowns. Therefore, the MXIT parameter (maximum number of iterations) is set to -1. Then no adjustment is carried out. The list of residuals thus indicates the compatibility to the approximations to the unknowns. See also remark A.
F502	A CONT statement must not contain blank control point elements
F503	A CORD statement must not contain blank coordinates
F504	There are <val> points with incomplete approximate coordinates No approximate coordinates can be computed for point <val> because the point has not been measured in at least two photos or, the photo base is to small or, the rays from the photo measurements do not intersect because they are parallel. Enter approximate coordinates for this point via the CORD statement. If this message appears during adjustment of a survey network (no photo measurements), the CORD statement for this point has been forgotten.
F505	Block has only <val> points For performing a bundle block adjustment at least three points are necessary. Possibly the data files have not been correctly allocated.
F506	Camera constant for camera <val> missing No camera constant has been entered for camera <val>.
F507	Maximum number of <val> cameras exceeded: <val>
F508	Characteristic <val> for unknowns is invalid In the preceding input statement an invalid characteristic <val> for control of unknowns for a camera has been read in. The following values are valid: Zero to four.
F509	Correction of camera name not possible
F511	Double LINE no. <val> in line <val>
F512	Double event no. <val> in line <val>
F513	Double input statement for camera <val> The data in the preceding input statement for camera <val> have been read in before.
F514	Double input statement for pass <val>
F515	Double input statement for photo <val> Either a photo <val> has been allocated to a photo station more than once (ISTA), or the approximate orientations for photo <val> have been read in repeatedly (ORIT, ORIA).
F516	Double input statement for point <val> Control point <val> has been read-in before.
F518	Error in pre-adjustment of object points
F519	File <str> not found
F520	File name "<str>"in project file longer than 64 characters
F521	File name too long
F522	Format error no. <val> reading line no. <val> <val>
F523	Format error no. <val> in line <val>
F525	G-matrix element no. <val> not negative definite
F526	GEO INPUT file and ITERA file not existing
F527	IMAGE COORDINATE file not existing
F528	Identical points in input statement Station and target point in the preceding input statement have identical point names.
F529	Identical points: <val> <val> <val> Points <val> and <val> are to be linked by means of a measurement of type <val>. The coordinates, however, are identical, so that no differential quotient can be computed. Check the approximations to the coordinates for these points and, if necessary, enter more realistic values by means of a CORD statement.
F530	Illegal character in column <val> in line <val>
F531	Illegal character in position <val>
F532	Illegal data in position <val>
F533	Illegal data input for selected free network type. The problem occurs with data type "<str>"
F534	Illegal data length in column <val> in line <val>
F535	Illegal data length in position <val>
F536	Illegal data type for <str>-value in line <val>
F537	Illegal data type for LINE number in line <val>
F538	Illegal data type for ambiguity counter in line <val>
F539	Illegal data type for coefficient in line <val>
F540	Illegal data type for event number in line <val>
F542	Illegal data type for precision in line <val>
F543	Illegal data type for reference time in line <val>
F545	Illegal data type for time in line <val>
F546	Illegal data type in position <val>
F547	Illegal data type
F548	Illegal event number: <val>
F549	Illegal factor <val> The indicated factor in the GRUP statement must be positive.
F550	Illegal image dimension for scanner data
F551	Illegal input statement "<str>" in line= <val> The input statement < str > contained in file ITERA has not been defined and is therefore illegal.
F552	Illegal input statement: <str> Input statement < str > is undefined and thus illegal.
F553	Illegal no. for add. parameter: <val> <val> is an illegal parameter number. Only parameters 1 to 38 are defined.
F554	Illegal photo number: <val>
F555	Missing or illegal point name <val>
F556	Illegal polynome code
F557	Illegal value for standard deviation A negative standard deviation has been indicated in the preceding input statement. This is illegal.
F558	Inconsistent use of camera numbers for photo <val>
F559	Inhomogeneous GPS file types
F560	LINE no. <val> in line <val> exceeds range 1 to 999000
F561	Link from event <val> to photo <val> not satisfied
F562	Linked photo <val> in line <val> has no orientation
F563	Linked photo <val> in line <val> is not type aerial
F564	Minimum number of photos is TWO
F565	Missing number behind colon
F566	Multiple use of event number <val>
F568	No input data. No processing The allocated data file of photo coordinates is empty, or a wrong data file has been allocated.
F569	No pass data for scene <val>
F570	No points found. No processing The input contains no points or measurement elements. Probably an empty or a wrong input data file has been allocated.
F571	No. of add. parameter twice: <val> The additional parameter <val> has been read in previously for this camera.
F572	No. of station point for set of directions missing The first statement must contain the station name for the set of directions. The subsequent SEDI statements, which are allocated to this set of directions, must not contain the station name but only the target point names. The sequence of input statements (SEDI) for a set of directions must not be interrupted by other input statements.
F573	Not enough data in FILE statement
F574	Not enough data in GTRA statement
F575	Not enough data in LINE statement in line <val>
F576	Not enough data in line <val>
F577	Not enough data
F578	Not enough datum reference points for free network adjustment
F579	Not enough points for adjustment Less than two points are active in the block. Adjustment is impossible.
F580	Error creating file <str>
F581	Format mismatch for input data <str> in line <str>
F582	Orientation data for photo <val> missing The approximate parameters of outer orientation are missing for photo <val> (ORIT or ORIA statement).
F583	Orientation elements missing for Pass <val>
F584	Photo no. <val>not in list One of the photos <val> or <val> indicated in the stereo metric-camera condition, or the photo <val> indicated for the camera station, is not included in the list of image names.
F585	No data for photo <val> Photo <val> is indicated in the list of image names. For this photo no photo coordinates are available yet.
F586	Point <val> not included in NES A valid point could not be included in the normal-equation system (NES). See also remark A. ◆    Either you have made a typing error during input of point names, ◆    or the data contain two independent networks. In that case the network must be linked by at least one observation, or two separate blocks must be produced, and separate computations must be carried out, ◆    or the sequence of data is so unfavourable that the program could not find an appropriate sorting system. Try to avoid the error by changing the input sequence of the survey measurements.
F588	Polynom coefficients missing for pass <val>
F589	Error reading file <str>
F590	Error deleting file <str>
F591	Requested project file not existing
F592	Scanner data not found
F593	Set of directions no. <val> incomplete Set of directions no. <val> contains only one direction.
F594	For stereometric camera conditions all photos have to be of the same type (all aerial or all terrestrial) <val> <val>
F595	Stereometric camera condition with one camera illegal In the preceding stereo metric-camera condition the same camera name has been indicated for both the left and the right photo. This is not permitted.
F597	System not redundant <val> <val> <val> <val> The block contains more unknowns than observations. The rank defect amounts to <val>.
F598	Error renaming file <str>
F599	Point <val> in plane of photo <val>. Measurement ignored The differential quotients for the collinearity equation of point <val> in photo <val> cannot be computed as the approximations to the point lies behind the plane of the photo. Check the approximations and, if necessary, enter more realistic values for photo orientation or the point coordinates (CORD statement).
F600	Unknown name in FILE statement: "<str>"
F601	Upper range limit below lower range limit
F602	Value for angle invalid The angular value on the preceding input statement is larger than 400 gon and therefore invalid.
F603	Illegal data type in line <val>
F605	Not enough data in line <val>
F606	Error opening file <str>
F607	Error in command line parameters "<str>"
F609	Illegal name <str> in line <val>. Length exceeds 15 characters Maximum length of point, photo or camera name is 15 characters.
F610	Camera name missing in <str> statement
F611	Way point ID <val> found, but not in file <str>
F612	Way point ID <val> not found in file <str>
F613	Double scan line ID <val> in lines <val> and <val>
F614	Incorrect way point sequence in LINE <val> points <val> / <val> / <val>
F615	Double way point ID <val> in lines <val> and <val>
F616	Cannot open JAS camera data for camera <val>
F617	Point <val> in image <val> outside time range of waypoints <val> and <val>
F618	No options allowed for way point files
F619	Error reading camera definition file <str>
F620	Inconsistent use of sensor types for camera <val>
F621	Sensor type for camera <val> already defined
F622	Program stops because of divergence
F623	SET number <val> not allowed for this camera type
F624	Inhomogeneous number of radial groups in GRUP <val>Y and RAWE <val>
F625	Not enough data in DORI statement
F626	Illegal key in DORI statement <val>
F627	Photo <val> not found in list
F628	Illegal data type in DORI statement: <val>
F629	Not enough data in EDIS statement
F630	Illegal data type in EDIS statement: <val>
P801	Address missing in subr CHECK See remark A.
F624	Inhomogeneous number of radial groups in GRUP <val>Y and RAWE <val>
P803	BINGO/ITER2 configuration error See remark A.
P804	BINGO/ITER3 configuration error See remark A.
P805	BINGO/TEZUP configuration error See remark A.
P806	Dimension error in VRDRU See remark A.
P807	Error <val> in subr SELLI See remark A.
P808	Error in record length <val> <val> An error has occurred during calculation of record length for output of matrices C or N-1, or an installation parameter has been set incorrectly. See also remark A.
P809	G-matrix position error See remark A.
P810	Header not found in subr GETTP See remark A.
P811	Illegal record no. in subr NOLES See remark A.
P812	Illegal value for ISZK used. ISZK= <val> See remark A.
P813	Logical error in reorder See remark A.
P814	No. of points do not fit in subr MODOR. Model <val>/<val>: <val> <val> <val> See remark A.
P815	Not all right-hand sides computed. <val> <val> See remark A.
P816	Pass not addressed in subr MODMA See remark A.
P817	Photo not addressed in subr MODMA See remark A.
P818	Point <val> not found in block <val> See remark A.
P819	RELAX configuration error <val> See remark A.
P820	Sorting error <val> <val> <val> <val> Your data set contains probably two independant blocks An error has occurred during sorting of the photo measurements for point <val>. Act according to remark A.
P821	Too many right-hand sides: <val> <val> See remark A.
P822	Unexpected return code from PCMOV in subr MODMA See remark A.
P823	Point sorting error in subr SELLI See remark A.
P824	Unexpected event "<str1>" trapped by BINGO exception handler in modul <str2> Execution terminated The BINGO exception handler has been called by the system because of the exception error <str1>. Please check your data. Act according to remark A.
P825	JAS data sorting error in module <str>
P826	JAS data time assignment error <val> in module <str>