Latest Contributions by AmitHazra

Hello Masao It sounds like you are using the out of the box Location Referencing tools to create and configure the LRS and network for your Roads and Highways Pro data model. When you use the Create LRS and Create LRS Network GP tools the R&H Pro model is created assuming you are going to be leveraging the “Autogenerated Route ID” network Route ID configuration. That configuration requires a “Route Name” field that is synonymous with a unique ID that is more human-readable than a GUID. This Route Name concept is configured more commonly with our Pipeline Referencing users but since we are actively trying to align the development of the enterprise LRS product users will begin to see additional enhanced functionality blended from the surface transportation and pipeline industries. If you intend to use these creation/configuration tools to start your data model and you wish to use a Single-Field Route Id or a concatenated Multi-Field Route ID then you’ll want to add the fields you need to your network feature class and then run the Modify LRS Network GP so you can change the “Route ID Field Configuration” parameter to your liking. Alternatively, you can reference our information model definitions and choose to model your entire LRS ahead of configuring it. In this case, you'll use the Create LRS From Existing Dataset and Create LRS Network from Existing Dataset GP tools.   -amit@esri Esri LRS Transportation Team ... View more

Hello Courtney The object relationship and editing scenarios you're describing between centerlines, routes, and events is one of the primary reasons for why we built ArcGIS Roads and Highways. In the Roads and Highways data model, centerlines form the foundation for route geometry. Roads and Highways tools are utilized to build and maintain routes upon the centerlines, and event feature classes are maintained on the routes the events are characterizing. You can read more about the information model in our LRS data modeling document. The solution incorporates advanced rules to manage the relationship of centerlines to routes and automates the update of event measures and shapes based on configurable location event rules called "behaviors". In addition to these fundamental desktop editing capabilities and automated rules, Roads and Highways provides a rich Server-based solution including a JavaScript REST API to develop web-based apps on.  If you'd like to talk more about bringing enterprise LRS capabilities to your organization please reach out to us anytime, Amit@esri Esri LRS Transportation Team ... View more

Hello Saranya This is the expected ArcGIS Desktop (ArcMap) output for publishing the GenerateReport geoprocessing tool for Roadway Reporter. Now that the tool has been run you're ready to publish it as a GP service and subsequently configure the Roadway Reporter app. Refer to our deployment resource documentation for further information: Publishing the Generate Report tool to a service—ArcGIS Roads and Highways Server | Documentation for ArcGIS Enterprise  -amit@esri Esri LRS Transportation Team ... View more

A note about the comments regarding removing centerline geometry duplication in Roads and Highways as it relates to route concurrency (overlapping route geometry) and route dominance. Although my reply does not necessarily address the original GeoNet question, I do want to bring to the community’s attention the relative importance in de-duplicating centerlines in Roads and Highways for ALRS networks where route dominance is configured. For this example, I present to you four routes where the concurrency rules are set such that the greater, alphanumeric Route ID is the dominance rule. Example 1: Routes “zRoad” and “aRoad” are concurrent. Each route has its own centerlines and those centerlines overlap in the highlighted region below (not de-duplicated): Here is the corresponding centerline sequence table for Example 1: Example 2: Routes “xRoad” and “bRoad” are concurrent. Each route shares the middle centerline where they overlap in the highlighted region below (de-duplicated): Here is the corresponding centerline sequence table for Example 2. Note the yellow highlighted records represent the concurrent centerline segment: Now, suppose we need to run the Calculate Route Concurrencies GP tool to calculate and report the concurrent route segments within the LRS Network and determine what routes are dominant for a given section of roadway. Here is what the output of the GP tool should look like for Example 2: In this example, the GP tool traverses the centerline sequence table to determine routes in networks that share centerline sections and based on the configured network concurrency rules determines what the dominant route is along the concurrent section (re: DominantFlag). However, without de-duplicating centerlines for Example 1, the output result from the geoprocessing produces an empty recordset: Finally, running the Remove Centerline Geometry Duplication utility on the ALRS and then re-running Calculate Route Concurrencies GP yields this result for Example 1 and Example 2: The moral of the story here is that no matter why or when you introduced centerline geometry duplication into your ALRS, if you have overlapping/concurrent route definitions you really need to be cognizant that route dominance depends of keeping your centerline sequence table nice and tidy. Hope that helps!   amit@esri roads and highways team ... View more

Hello Christoper If I'm interpreting your post correctly it sounds like you have a GIS feature class representing your bike path extents but the features do not have LRS route and measure information associated to them. I'm assuming these features may or may not be coincident with your network geometry. I'm assuming you'd like to derive route and measure information for each feature and then use Location Referencing Append Events GP to bulk load the paths rather than simply using Event Editor. I would suggest as a first pass looking at the core Linear Referencing tool called Locate Features Along Routes. The output from this tool is a table that provides the relative route and measure information for your spatial features. Be cautious when using this tool on linear data as the algorithm to convert lines to linear events uses a cluster tolerance which can sometimes yield unsatisfactory results. There are other more workflow-centric and custom GP-based patterns but I'd be curious to know whether this tool gets you a good part of the way on your migration. -Amit@esri Roads and Highways team  ... View more

Hello Ana, Although there seems to be some ambiguity in our docs, the redline feature class should not be M or Z enabled if you choose to use route redlining in the Roads and Highways Event Editor. To resolve your issue you could create a new redline feature class and replace the old one. In order to make this GDB feature class swap you'll want to be sure there are no services running that contain the current redline. Thanks, Amit@esri Roads and Highways Practice ... View more

Hello Joseph,   Assuming you are using ArcGIS Desktop 10.5.1 or later there is a COTS-based workflow to bring your routes back from retirement. This workflow assumes you want/need to preserve all timeslices for the route in question and that you may have custom/intermediate calibration points. The process is simpler if you are reloading a route using geometric length or do not have intermediate calibration.   For the route in question, clear the TVD (temporal view date) for the network and calibration point feature classes. Select the route and calibration features for all time slices of the route in question. Export those route and calibration point feature classes to a file geodatabase. In the exported route and calibration point feature classes, carefully edit the To Dates for the records you retired back to <null>. Using the Roads and Highways Load Routes tool, use the edited route feature class to reload the route in question. Once the routes are loaded, you'll be prompted to choose a calibration method. If you have no custom/intermediate calibration you could simply choose from the source route measures or geometric length. If you have custom/intermediate then it does not matter what you choose as you'll need to apply an additional workflow to bring that calibration back. Optionally, choose to remove centerline duplication at the end of the calibration process Prior to opening an ArcMap Edit session, open the Roads and Highways Advanced Editing options and check the option to "not apply event behaviors to manual calibration point changes". Add the exported and edited calibration point feature class to the map. With the TVD still cleared, open an edit session and select all the calibration points for the route in question. Delete those points. Select and copy/paste the exported calibration points for the route in question into the R&H calibration point feature class. Apply edits and save/close your edit session. Be sure your events’ temporal dates match the routes as you wish. You may also wish to test this workflow in a version or file GDB export to be sure it yields the results you desire. -Amit@esri Roads and Highways team ... View more

Hello James A common pattern among our enterprise-scale Event Editor deployments is to create business-unit and task specific configurations for editing events. In a practical sense, this means that for each configuration of Event Editor you'll publish one LRS-enabled service with only the event layers required by the end users' maintenance needs and then should they wish to have additional LRS event layers or other reference data layers (e.g. polygon boundaries etc) in their configuration you'll simply publish those layers as map services without LRS capability enabled. From your Portal you'll then manage access to those web layers through group sharing at the service, webmap, and app item level. Each Event Editor configuration will have a default webmap with the one LRS-enabled service and then you can also add in any number of reference map layers so long as they are not LRS-enabled. Hope that helps. If you have any other implementation questions please do not hesitate to ask. Amit@esri ... View more

Hello Kyle, Cross-validation checks already exist in Data Reviewer for ArcGIS Pro as Event on Event checks. Check this out: https://pro.arcgis.com/en/pro-app/help/data/validating-data/event-on-event.htm. Thanks! Amit@esri ... View more

Hello Colin - Export Network is expecting up to 9 arguments: When you open the parentheses on the tool it should look similar to: -Amit@Esri ... View more

Hello Dustin Good question. I suspect you've either built your own Geometry to Measure widget or you are using a derivative of our Github sample. If your LRS network has overlapping route geometries and you've configured ALRS network concurrency rules then you'll need to reference the Network Layer Concurrencies operation in our REST API. Thanks, Amit@esri ... View more

Hello Anna- I'm sorry you are having issues getting answers to your query. But don't give up! This community is primarily devoted to the Esri Roads and Highways LRS product. Since I understand you are trying to integrate highway network data into an Esri Network dataset may I suggest you try to post your question into our Network Analyst Community GeoNet Network Analyst as you may increase the awareness of your issue with specialized users and Esri staff of that product. Good luck! Amit@EsriTransportation ... View more

Hi Justin - Interesting find. Can you validate whether the spatial parameters for the GP environment using Create Routes matches your ALRS?  ... View more