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”). IMX extension is usually used for report files on import from DXF format.
In table 62-1 a list of messages about errors and other messages placed by the system in report file is given. These messages also contain information about results of performing import operations.
Message | Explanation |
Total features:… | Total number of features in DXF file. |
Total imported features:… | Number of features in DXF file imported to the map. |
Total completed features:… | Number of features of DXF file for which the operation of completion has been performed. |
Total rejected features:… | Number of features of DXF file which were not imported due to the presence of errors in their structure. |
For link with table… at field… records adding is impossible – error of adding record | Import mode with linking and adding records is set, but the table doesn't have a record with the value corresponding to the value in the link group of the feature being loaded. When adding a record a conflict arises which reason is the presence of not-emptiness attribute of other table fields. The feature is loaded. |
For link with table… at field… at feature type… first found record is used | One of the import modes with linking is set. Link field in the table does not have the attribute of uniqueness, link mode of feature type with the table is unique. In this case a situation is possible when while loading a feature several table records having a suitable value in the link field are found. Linking will be performed only with one of them. Generally speaking such a situation should be examined as an error of designing GDB structure. |
For link with table… at field… - error of linking with record | One of the import modes with linking is set. An error occurred during linking. The feature is loaded. |
Line: … | The line number of beginning of description of DXF file feature to which the message given in next report lines belongs. This message with indication of line number precedes all messages enumerated below. |
cannot complete the feature | It is impossible to perform completion operation for the feature. The feature is not loaded. |
polygon is not simple Start of first segment:… End of first segment:… Start of second segment:… End of second segment:… | Polygon boundary has self-intersections. Coordinates of intersecting boundary segments are indicated. The feature is not loaded. |
polygon is not simple after completing Start of first segment:… End of first segment:… Start of second segment:… End of second segment:… | The polygon formed after completion has a boundary with 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. The feature is not loaded. |
data are absent | There is not enough data describing the feature. The feature is not loaded. |
too few vertices | Polyline or polygon describing the feature does not contain sufficient number of points. The feature is not loaded. |
incorrect feature size or incorrect feature coordinates | Feature sizes in DXF file do not correspond to those admissible in ObjectLand. The feature is not loaded. |
extra group value is absent | One of the import modes with linking is set, but DXF file being loaded has no group with the code specified for extra group in import settings. The feature is loaded. |
cannot convert extra group value | The value in the extra group of the feature of DXF file being loaded consists not only of digits, though link field is integer. The feature is loaded. |
it is impossible to link the feature – record is absent | Import mode with linking and diagnostics is set, but the table has no record with the value corresponding to the value in extra group of the feature being loaded. The feature is loaded. |
Table 62-1. Messages in report file on import from DXF file
 |  |
