Storing measure value as integer

MasaoMatsuokaDev

AEGIST Guide book 2019 (page 45) says this about storing measure values as integer. I have a few questions about this recommendation.

To eliminate the problems caused by decimal measurements within the digital computing environment the Guidebook has adopted a standard LRM measure unit of M (the Greek letter mu), which is equivalent to 0.001 mile. This standard will restrict measure values to whole integer numbers. It is a simple matter to convert to decimal values by dividing a value by 1,000 at the time of publication, for those users who need this format. Some GIS platforms currently use this convention by internally converting measure values to integers.

 Questions:

1. Does Roads and Highways support this or doing this internally?

2. Do any DOTs actually store like this in Roads and Highways?

3. What is the recommendation in the context of Roads and Highways?

Thank you.

Masao Matsuoka (WSDOT)

Masao

MasaoMatsuokaDev

Thanks for the detailed information.

In one of the articles Feature class basics—ArcGIS Pro | Documentation, it says "ArcGIS records coordinates using integer numbers and can handle locations with high precision." Are the M values stored in the same way as well? My understanding is ArcGIS internally store coordinate values as integer to avoid the floating point number issue. However, as you pointed out the calibration point store measure values as double. So I guess it won't help. So the answer to my original question is "No". Roads and Highways does not support AEGIST recommendation. I also read in another article there is a way to set the tolerance to something like 0.001 miles, but that is not recommended as it might introduce non-monotonic measures. The best we can do is to set measure to something like 0.0010000. However the value is stored as double so it might end up to be something like 0.0009876. So we need to round it before presenting to users. Am I understanding this correctly?

Thanks

Masao