Latest Contributions by NathanEasley

Hi Jesse, I'd recommend opening up a support case with Esri Technical Support on this issue, especially since you're able to consistently reproduce the results you're seeing. Nathan Esri Roads and Highways team ... View more

Hi Preston, Everything looks correct there.  I would suggest opening a support case with Esri Support.  They can assist you with troubleshooting the issue. Nathan Esri Roads and Highways team ... View more

Hi Preston, A few quick questions that might help narrow down what's going on. 1. Can you confirm the events that don't appear in event editor are in fact registered as events in the same LRS as the events that do appear? 2. In the MXD you used to publish the service, were the events within group layers? Nathan Esri Roads and Highways team ... View more

Hi Amelia, Thanks for the additional information about related workflows.  The Apply Edits REST endpoint that is used in Add Linear Events and when updating events in the event attribute table is only able to merge with one adjacent event currently (not both like in the case you mentioned originally). We could add support to merge with all adjacent events, however, the downside to adding this support is performance of the endpoint will be slowed down.  Because this endpoint is utilized for the majority of operations in Event Editor, the performance impact would be seen throughout, even if there is no merging that would take place. We're open to making this change to the endpoint, however, the trade off would be decreased performance throughout the application. As I mentioned, the Merge Events widget can be used to merge adjacent events, either in place of Add Linear Events/event attribute table editing, or as a step after using those tools. I'm happy to discuss this point at the next RHUG meeting to get an idea of the rest of the communities thoughts about whether the trade off in performance is worth adding this support. Nathan Esri Roads and Highways team ... View more

Hi Amelia, For workflows like these where you'd like to merge more than 2 events, you should use the merge events widget in Event Editor (https://enterprise.arcgis.com/en/roads-highways/latest/event-editor/merging-events.htm).  It will allow you to change attributes and merge more 2 or more adjacent events together in one operation. Nathan Esri Roads and Highways team ... View more

Hi Preston, Are you able to consistently reproduce this or has it only happened once?  If it happens consistently, I would open a support case with Esri Customer Care to have them investigate. Nathan Esri Roads and Highways team ... View more

Hi Peter, In order to remove a centerline, you need to remove any route associated with it.  In the Roads and Highways information model, the centerlines provide the geometry for routes.  If you just deleted the centerline, you could have routes with incorrect geometry (due to missing centerlines) and even have calibration points no longer located on the route (which would result in no or incorrect calibration).  Because the centerlines are the building blocks for the routes, in order to remove a centerline, you must also remove any dependent routes that use that centerline for their geometry. As mentioned in previous posts, there are a few different ways to remove the centerline.  I would encourage you to choose the method that best aligns with your business processes to complete the removal of the erroneous centerline. Thanks, Nathan ... View more

Hi Peter, There is a geoprocessing tool within the Roads and Highways toolbox to handle this exact case you're mentioning above.  The delete routes tool will make sure that all records related to the route/centerline combination you want to delete are removed correctly (http://desktop.arcgis.com/en/arcmap/latest/tools/location-referencing-roads-toolbox/delete-routes.htm) from the geodatabase.  I would encourage you to use this tool to complete your workflow.  Just select the route (or routes) that are associated with the centerline you want to remove from the system and make sure to check the delete associated centerlines option in the tool. Good luck. Nathan Esri Roads and Highways team ... View more

Hi Michael, You're correct that the error code 4 is related to the route either not being calibrated in a portion or not aligning with the centerline.  I have a few suggestions below to take a closer look at the routes in the concurrent section to determine if either of these conditions are present. To determine if there is any portion of any of the routes in the concurrent section that don't have calibration you can do the following: Use the routes tab in the layer properties to turn on the symbology to show routes that have unpopulated (NaN) M values at any location (http://desktop.arcgis.com/en/arcmap/latest/manage-data/linear-referencing/displaying-route-measure-anomalies.htm) or you can look for M values that are NaN for each of the routes that are concurrent using the Sketch Properties (http://desktop.arcgis.com/en/arcmap/latest/extensions/3d-analyst/using-the-edit-sketch-properties-window.htm). If you don't see any NaN values in any of the concurrent routes, you'll need to look at the centerlines that compose the concurrent routes to ensure they're geometries are shared.  You can do this by using the Select by Location tool (http://desktop.arcgis.com/en/arcmap/latest/map/working-with-layers/using-select-by-location.htm) or by manually inspecting the features to ensure they're sharing the same shape (you'll need to by very closely zoomed in since the centerline and route being more than the XY tolerance apart will trigger this error code 4). If everything looks as expected after looking at these routes, I would encourage you to log a support case and work with an analyst to further investigate what caused this error code to appear. Nathan Esri Roads and Highways Product Team ... View more