NYSDOT has seen a number of very small overlaps generated by the concurrency API and the Calculate Route Concurrencies (CRC) tool. We have not been able to uncover an underlying cause in the ALRS network that explain these overlap anomalies.
A discrepancy between the measure field definition and the LRS Network Resolution and Tolerance Properties was recently pointed out to us. All of our ALRS network and event feature classes have measure fields defined as Double 38,8. However, our ALRS network measure precision is set to 7 as shown below.
I'm trying to figure out if this precision discrepancy between the field definition and the ALRS has the potential to cause the (apparently invalid) route concurrency results.
