Support of units

It is unlikely that you will encounter the following under typical usage of the B2W Track Quantity Request integration, as it uses standardized units that the Siteworks software recognizes. This is only necessary if B2W Track is configured with custom unit values. For the Quantity Request integration to correctly operate, the unit confirmation must be correct for the type of measurement (line, area, volume) so that the Siteworkssoftware can recognize the type of measurement requested.

The software has a built-in list of standard units and their conversion factors. However, you might need to add a new unit type for it to correctly recognize either a new unit type or a different definition for an existing unit. For example, CUYD, CY, and YD^3 all represent Cubic Yards, but the software may not correctly recognize the YD^3 measurement sent from B2W Track as a volume request. If this happens, the software incorrectly displays a length, area, or volume measurement as a point request. In this case, you will need to add a YD^3 definition to a LocalUnits.txt file in the Siteworks Diagnostic Data folder.

Adding new units

To add new units to Siteworks to use with the B2W Track Quantity Request integration integration, create a new text file called “LocalUnits.txt” and save it in the Trimble Siteworks Diagnostic Data folder:

  • Windows: C:\Trimble Synchronizer Data\<PC>\Trimble Siteworks Diagnostic Data

  • Android: Internal Storage/TrimbleSync/Siteworks/Trimble Siteworks Diagnostic Data

New unit definitions are added one per row, using the following rules:

  • Each unit line must have the three comma-separated elements: <name>,<type>,<SI unit multiplier>.

  • Spaces and capitalization in the unit name are ignored.

  • <type> must be "length","area", or "volume".

  • <SI unit multiplier> is the conversion factor used to convert from metric or SI units to the desired value.

  • All internal measurements in the Siteworks software are performed in metric and then multiplied by this factor.

    For example, to define a linear foot, the entry would be: lf,length,3.28084 (where 3.28084 is the meter-to-foot conversion factor).

  • Double forward slashes “//” indicates a comment in the file; any text after "//" on a line is ignored.

When a new unit is added to the LocalUnits.txt file, it is included in Siteworks' built-in list. If a unit is already in the Siteworks built-in list and then added to the LocalUnits.txt file with a different conversion factor, the conversion factor in the built-in list is updated to the new factor from the text file. Although the values are in the Siteworks built-in list and the LocalUnits.txt is no longer required, the build-in values are overwritten and reset when the Siteworks software is reinstalled or updated.

The unit values and conversion factors that are in the Siteworks built-in list are in the following table. Any units not in this must be manually added to a LocalUnits.txt file. The sample text below can be copied into the LocalUnits.txt file and modified as needed:


cuyd,volume,1.30795
C.Y.,volume,1.30795
sqyd,area,1.1959
s.y.,area,1.1959
lnft,length,3.28084
l.f.,length,3.28084

Length units

Area units

Volume units

m,length,1.0

m2,area,1.0

m3,volume,1.0

ft,length,3.28084

sqft,area,10.7639

cuft,volume,35.31467

k,length,0.001

Square ft,area,10.7639

cubicft,volume,35.31467

lf,length,3.28084

acre,area,0.000247105

cf,volume,35.31467

lm,length,0.000621371

ha,area,0.0001

cy,volume,1.30795

lkm,length,0.001

sf,area,10.7639

gal,volume,264.172

mile,length,0.000621371

sy,area,1.1959

l,volume,1000.0

yard,length,1.0936

syin,area,1.1959

 

ym,length,1.0936

 

 

km,length,0.001