Flat attribute file exporter for TGO


Download the zip file of the flatattr system (220Kb).

Flatattr.dll is a plug in exporter for Trimble Geomatics Office.

Version 2 provides a number of functions depending on how it is configured using cfg_flat.exe, which is included in the zip file. The system can be configured to flatten a TGO attribute file, with or without attribute names, or to just remove lieca style codes.


Cfg_Flat is used to configure the behaviour of the flatattr.dll. Hopefully it is reasonably obvious to use.

  • Output Flat Attribute
      Outputs a file with all the attributes on a single line. Normally this is on. The only   time it makes sense for it not to be on is with Leica codes.
  • Output Attribute Names:
      If the attribute is Type with a value of Concrete. Then with output Attribute names Type, Concrete would be output. If it is unchecked then just Concrete would be output
  • Output as Decimal Degrees
      Selecting this option will create a file of the format
       Pt, Local Lat, Local Long, Elevation, codes.
      The Lat and Longs are in decimal degrees, always with a sign
  • Remove leading number from code (Leica Codes)
      Eg. if the code entered is 103 CP, then CP will be written to the file.
  • FBK will write a Softdesk FBK format file, in this case the Field Separator will be set to be a space.
    Sfotdesk field book format is space delimited with NE SS at the start and “” around the code and attributes.

Flattening the attribute file

When installed in TGO (recommend to be installed in the Survey) tab of the file export feature of Trimble Geomatics Office, a new format call Flat Attribute File is added to the system.

When the all attribute formats are used in TGO you get a file that has one line for each attribute an example of this is

1999-5174, 5036505.664, 379826.099, 29.190, CB, STRUCTID, J1190-C001
1999-5174, 5036505.664, 379826.099, 29.190, CB, HOUSE_NO, 0
1999-5174, 5036505.664, 379826.099, 29.190, CB, STREET_NAME, JEANNE D'ARC
1999-5174, 5036505.664, 379826.099, 29.190, CB, STRUC_TYP, CB
1999-5174, 5036505.664, 379826.099, 29.190, CB, BASIN_ID, CGW071

For a number of applications this is what is wanted for other applications it would be easier to have this all on the same lines. Flatattr provide this ability.

In the above example the output line would be

1999-5174, 5036505.664, 379826.099, 29.190, CB, STRUCTID, J1190-C001, HOUSE_NO, 0,STREET_NAME, JEANNE D'ARC,STRUC_TYP, CB,BASIN_ID, CGW071

Note: That this would be on a single line.

The system can be configured to not output the attribute names, which would give the following output, again all on one line

1999-5174, 5036505.664, 379826.099, 29.190, CB, J1190-C001, 0, JEANNE D'ARC,CB,CGW071

Note on codes:

    The file format has the code output, not the attribute name. These means that if attributes are added or deleted in the office then the attributes that are output will be inconsistent with the attribute type indicated by the code field. Normally these will be the same.

    The reason for this is two fold.

      1: It means that you get codes for points without attributes
      2: It allows outputting of points with two attributes as a single point

    This is easy to change if desired



If the file is sorted in point number order and you have a duplicate points (Same Pt name, Cords and code) then the attributes from both points will be combined. This creates a super point with all the attributes.

For this to work the file needs to be in point number order, although generally you should just add multiple attributes to the point.

If you have duplicate points in the database then it is possible that this could occur when it is not desired, it is best remove points with identical names and coordinates before exporting.



    Today Survey Controller and the SDR33 both support the uploading of code information, they do not support uploading of the description of the feature code. This means that users of numeric feature coding systems do not have the ability have a text description of the code displayed.

    To work around this limitation the normal solution is to add the text discription of the numeric code as part of the code. For example if code 100 is a control point (CP) then the feature code library would be 100 CP.

    When the leica code processing option is enabled then when this code is exported just the numeric vaue would be output. In the above case the output code would be 100. If the code is not of this format then it is output unchanged


    When leica codes are enabled with flat attribute files then the code and attribute values have this processing applied to them. This seems to be the desired normally. Again this can easily be changed if needed