At this step it is required to enter a name of report file on import (see chapter 61 “General characteristic of import/export operations”, subsection “Report file”). IMM extension is usually used for report files on import from MIF format.
In table 64-2 a list of messages about errors and other messages placed by the system in report file is given. These messages contain information about results of performing import operations.
Message | Explanation |
Total features: … | Total number of ObjectLand features for import from MIF file. |
Total imported features: … | Number of features successfully imported to the map. |
Total imported records: … | Number of records of MID file imported to GDB tables. |
Total linked features: … | Number of features for which links with imported table records were set. |
Total rejected features: … | Number of features of MIF file which were not imported due to the presence of errors in their structure. |
Line: … | The line number of beginning of description of the feature in MIF file to which the message given in next report lines belongs. If the message is connected with the error in attributive data about the feature, the number of the corresponding line in MID file is also given after the number of MIF file line. This message precedes all messages enumerated below with indication of line number. |
polygon is not simple | Polygon boundary has self-intersections. Coordinates of intersecting boundary segments are indicated. The feature is not loaded. |
text is absent | String value of the text feature is empty. |
too few vertices | Polyline or polygon describing the feature does not contain sufficient number of points. The feature is not loaded. |
Illegal feature format | Displayed in import of text features with inadmissible parameter values. The feature is not loaded. |
Coordinates of point (line, area) feature are absent | Coordinates of the corresponding feature are not specified in MIF file. The feature is not loaded. |
Number of line (area) feature sections is absent | The number of sections (polylines or polygons) constituting the feature in MIF file is not specified. The feature is not loaded. |
Illegal number of feature sections | The number of sections (polylines or polygons) of the feature does not correspond to the number of section descriptions. The feature is not loaded. |
Number of feature vertices is absent | No number of vertices is indicated for the feature in MIF file. The feature is not loaded. |
Illegal number of feature vertices | The number of vertices of the feature specified in MIF file does not correspond to the real number of described vertices. The feature is not loaded. |
incorrect feature size | Feature sizes in MIF file do not correspond to those admissible in ObjectLand. The feature is not loaded. |
Cannot convert integer (real) number | Incorrect format of number specifying some parameter in MIF file. The feature is not loaded. |
error of adding feature | An error of performing the operation of adding a feature (for example, as a result of breaking GDB structure). The feature is not loaded. |
Inappropriate data format | Record field in MID file contains the value inadmissible for the field of the present type. |
error of loading record. <error description> (<error code>) Field: <name of field with which error is connected> | When importing a record from MID file an error was found (for example, breaking properties of uniqueness or non-emptiness of field values). The record is not loaded. |
error of linking with record | An error when trying to link imported record of MID file with feature (for example, as a result of breaking GDB structure). The record is loaded but not linked. |
Table 64-2. Messages in report file on import from MIF file
 |  |
