Latest Contributions by NathanEasley

Hi Kevin, Answers to your 2 questions are below. I didn’t see more information on aligning the Measure Precision and Tolerance settings in the attached white paper.  Do you concur with the “if…then” statements above or is my brain playing tricks on me with a whole bunch of very small numbers? The M tolerance is the value that will be used to determine if two values are the same (within tolerance) or different (outside tolerance) within Roads and Highways when performing calculations.  The precision value within the LRS properties shows the decimal place where a significant (non-zero) value is present in the M tolerance.  In the example you showed, the M tolerance had 6 zeros before a significant digit was at the 7th place, so the precision is 7.  If the M tolerance had 2 zeros then a significant digit at the 3rd place, the precision would be 3. If we decide to update our ALRS to reset the measure tolerance, I understand that we need to start from scratch and reload the network and event feature classes into it.  Could you guide me to the best process/documentation to do that? It depends how you want to model the feature classes.  You can model them all yourself in advance then create the LRS within the geodatabase and associate those feature classes as Networks, Events, and Intersections in the LRS.  I'd recommend taking a look at this topic on tolerance and resolution in the LRS, if you're planning to go that route to understand the XYZM tolerance and resolution values for all those feature classes https://pro.arcgis.com/en/pro-app/latest/help/production/roads-highways/tolerance-and-resolution-settings-for-the-lrs.htm.  The other option is let the Roads and Highways configuration tools create the feature classes when you create the LRS, Networks, Events, and Intersections.  With this approach, you would need to add your business data fields after these tools run.  With both approaches, we'd recommend using a new geodatabase to ensure things like domains aren't duplicated between the old and the new LRS. Nathan ArcGIS Roads and Highways team ... View more

We would recommend keeping all parts of the Enterprise (Server, Portal, etc.) at the same version to avoid the types of issues it sounds like you're encountering with a mixed environment.  As you transition to Pro in the future, you'll need to keep your Pro and Enterprise versions in alignment https://enterprise.arcgis.com/en/roads-highways/latest/get-started/esri-roads-and-highways-for-server.htm#ESRI_SECTION1_4AFF4553FB7440A69D08F52B8F90D616 ... View more

The Edit Log is a table within the gdb that has your LRS.  You can query it the same way you would a regular gdb table.  The information about the edit does live in an XML blob so you would need to be able to convert that XML into something readable. The only warning with this approach is to make sure you don't add/update/delete any of the records in the table.  Treat it as read only to see route edits that have occurred within the LRS. ... View more

The queryEditLog endpoint only exists for the version of the REST API that comes with services published from Pro.  You can easily tell the difference by looking at the URL for LRSServer vs LRServer.  LRSServer is for ArcMap published services and LRServer is for Pro published services. Nathan Roads and Highways Product team ... View more

Hi Andrew, Take a look at the allowmerge parameter within the lrsApplyEdits operation (https://developers.arcgis.com/rest/services-reference/enterprise/apply-edits.htm).  It should make the type of merge you're asking about. Nathan ArcGIS Pipeline Referencing team ... View more

Hi Kevin, Not sure what happened with the link, but it should be working now. ... View more