OpenRoads Designer Tip: Downsizing Survey Field Codes

Many survey field code lists can be overwhelming and exhausting. Having a field code for every single item isn’t always necessary when using OpenRoads Designer to process your collected data.

For example, is a field code needed for each type of fence? A code for chain link fence, another code for wood fence, another code for plastic fence… While some will argue that we need to be able to use the different field codes to display different line styles, colors, levels, and more, in reality we do not need multiple field codes to control what is displayed in a DGN file.

For the fence type example, one field code could be used for all fences with survey attributes used during the field data collection. Fences can be coded as 251 with either an attribute for Chain Link, Wood, or Plastic.

OpenRoads can then read the attributes and determine which line style, level, and color to use for the fence line. This reduces the number of field codes required for all the fence types. The same technique can be applied to Trees, Found Monuments, Manholes, and other items.

Chris McNulty

Chris is a Senior Consultant at EnvisionCAD and provides expertise and training in MicroStation.

Tags: , , ,

Leave a Reply

Your email address will not be published. Required fields are marked *