Hello Amit - Thank you very much for your investigation and workarounds.
1. Yes, after seeing the March RHUG presentation from Ohio DOT, I was attracted to the approach that Ethan Pointer used to assemble the LRS network from scratch and use the process to make “clean up” updates to the attribute tables and properties of the LRS feature classes. I also wanted to change the M tolerance (and corresponding resolution) in the ArcGIS Pro geodatabase from the R&H default to 0.0000001 Mile (US Survey). My thought was that as that as long at the M tolerance is set smaller than the default tolerance, it should be compatible with the rest of the LRS. Perhaps that is not the case. I understand that this reconfigured measure resolution should not have any impact inside the Roads and Highways ALRS which is controlled by the Measure Precision setting, but we believe the default measure tolerance is causing rounding discrepancies in the 7th decimal place in our downstream data mart which is not controlled by the ALRS measure precision functionality.
I am coming to the conclusion that I need to change my approach to migrating the geodatabase. We have done some work with Clive recently on our migration so we will continue to look at this. Based on your work around, it sounds like my measure tolerance should be OK if we straighten out some other things but I would like to confirm that.
2. “The LRSN_Milepoint network you configured is set to Autogenerated Route Id”. Good catch…this was not intended. Originally I was trying to use the “Create LRS Network from Existing Dataset” GP tool and had the Route ID Field Config set to “Single-Field Route ID”. An error from that tool related to an undefined M unit of measure had me resort to the “Create LRS Network” GP tool instead and that tool appears to have assigned “Autogenerated Route Id”. Good to know there is a “Modify LRS Network” tool that can change this.
Your post has me realizing how I could be tripping things up by using a combination of tools to establish the new LRS Feature Dataset in Pro. I have not yet tried to run “Modify LRS” because I have been focused on getting everything from the ArcMap ALRS into the file geodatabase first. As you and Clive have suggested, I will try the migration from the ArcMap ALRS next…once I make the attribute table and property changes. I’m learning a lot along the way.