Share
 
 

About Importing Point Files That Contain User-defined Properties

Import point files using point file formats that contain user-defined properties.

When you import an ASCII point file, user-defined attributes described in the point file format are mapped to the user-defined properties in the survey database. If a matching property does not exist then it is created.

The user-defined attribute data for the points is stored as extended data using the same attribute data system as the LandXML extended properties. These properties are managed on the Survey tab in the Manage Extended Data collection in a survey database.

In the Manage Extended Properties dialog box, on the Survey Points node there is a new right-click menu option to Insert Into Drawing. When you use this option it forces the creation of the Survey-defined extended properties in the current drawing.

When new attributes are created in the survey database during an ASCII point file import, the data type of the drawing side attribute is replicated in the survey database, for example, Station would map to Station. Also, when attributes are mapped back to the drawing, the data type is preserved.

Limitations

  • Enumeration type attributes are not recognized by survey and are ignored during the attribute creation and data mapping process.
  • Attributes that are displayed on the Survey tab in Toolspace are formatted using the units and the display format that is defined in the survey database and user settings. The attribute units and display are not based on the current Drawing Settings.
  • Attributes that are initially created in a drawing and then added to the survey database during import do not map back to the same drawing side attribute when you add survey data to the drawing. Survey creates a new survey specific attribute definition in the drawing. For example: a string attribute "Address" that is created in the drawing would round trip back to the drawing as "Point.Address" within the Survey User-defined classification.
  • User-defined Property support is only available for ASCII point file import using external point files and the Point File Formats. User-defined Properties are not supported when you import points directly from a drawing or from field book files.

Was this information helpful?