Developers

Coordinate Systems

As of Veta 5.2, only data using select map projections (coordinate systems) can be shown on a map, regardless of the file format. Files using other projections will be shown, but without a map.

  • WGS84
  • State Plane
  • UTM
  • Minnesota County
  • Oregon Coordinate Reference System

Tagged Data File Format

Currently, each manufacturer uses a different file format. This requires Veta to have support for each format and to maintain it in the future. To eliminate this, a new standard file format was developed in conjunction with manufacturers. Veta 5.2 has partial support for the format, with additional functionality implemented in future versions.

Data Headers

Supported blocks

  • data-lot-name
  • gridding-height
  • gridding-process
  • gridding-width
  • machine-id
  • machine-name
  • machine-type
  • spatial-reference-authority
  • spatial-reference-id

Notes

gridding-process: Both gridded and ungridded are supported. gridded is only supported with “All Passes”. What Veta refers to as “Final Coverage” is not supported.

machine-type: The following types are supported:

  • compactor
  • paving thermal profiler
  • laser test roller

Data Sources

Supported non-array blocks:

  • footprint-perpendicular
  • footprint-parallel
  • index
  • offset-perpendicular
  • offset-parallel
  • measurement-name
  • recording-interval: Only continuous is supported.

Supported array blocks:

  • adjusted-deflection
  • easting
  • gps-quality
  • icmv
  • icmv-compaction-mode
  • icmv-vibration-amplitude
  • icmv-vibration-frequency
  • machine-speed
  • northing
  • relative-direction
  • surface-temperature
  • timestamp

Notes

footprint-perpendicular, footprint-parallel: Veta 5.2 will use the same footprint for all data sources in a file, as is done for current file formats. Different footprints are not be feasible for Veta 5.2, but may be in the future. The footprint will be chosen from a prioritized list based on the machine type:

  • compactor
    The last two sources in the list would not normally have a footprint. However, for a compactor that is only recording position and no other data, the first two sources do not apply.

    1. icmv
    2. surface-temperature
    3. machine-speed
    4. northing
  • paving thermal profiler
    1. First surface-temperature
  • laser test roller
    1. First adjusted-deflection

recording-interval: Only continuous is supported.

measurement-name: Required when using ICMV data. Because Veta’s map legends are currenly pre-defined, ICMV names must match the following values, although this may change in the future.

  • Caterpillar CMV
  • CCV
  • Dynapac CMV
  • Dynapac E-VIB1
  • Dynapac E-VIB2
  • EDV
  • EVIB
  • HMV
  • MCI
  • Trimble CMV
  • Volvo CMV

Quality

Veta uses the term “invalid” to denote measurements that will be ignored. Floating point measurements can and should be marked as invalid by “NaN” values (not a number) as defined by IEEE 754. It is recommended to use this method when possible to reduce file size. For non-floating point measurements or when this method is not desirable, additional blocks are provided:

  • quality (array)
  • threshold-minimum
  • threshold-minimum-comparison
  • threshold-maximum
  • threshold-maximum-comparison

The thresholds apply to the quality, not the actual measurement value, for more flexibility. The quality can be used as a simple flag (0 or 1), a measured value, or a calculated method. The source does not matter; it is only used in relation to the thresholds.

Because GPS measurements already have a quality flag, the gps-quality block is provided.

Veta supports the following quality methods:

  • gps-quality
  • NaN
  • quality array for Single and Double arrays. For other data types, quality will be ignored and the filtering can be done manually in Veta.

Lookup Tables

Supported lookup tables:

  • Compaction mode
  • Machine gear direction

Measurement Units

All units listed in the specification are recognized.

Verification

We offer an application that will read a TDS file and create a text version. The application targets Microsoft .NET Core 2.0, and should run on any operating system that has support for 2.0 (Windows, Linux, MacOS).

TDS Verifier 1.0 – June 12, 2018

Files representing 2 of the 3 examples in the specification are included, along with the text output created by the application.

Usage options:

  • dotnet “TDS Verifier.dll” input-directory
  • dotnet “TDS Verifier.dll” input-file
  • dotnet “TDS Verifier.dll” input-file output-directory
  • dotnet “TDS Verifier.dll” input-file output-file