The ArcGIS Pro 3.6 and ArcGIS Enterprise 12.0 releases bring new capabilities and quality of use improvements to ArcGIS Roads and Highways and ArcGIS Pipeline Referencing users. These enhancements are designed to streamline compliance reporting workflows, simplify the data loading process, and save time for common workflows.
ArcGIS Pro capabilities
The following capabilities have been added to ArcGIS Pro.
New Data Products toolset
The Data Products toolset contains three new geoprocessing tools that allow you to create data products without an LRS data template:
In contrast with the template-based approach in previous releases, you can create data products by directly running the tools above. You can incorporate these tools into existing Python scripts or ModelBuilder models to create custom data products for your organization. For those already familiar with creating data products, you can quickly generate feature counts, length summaries, and route logs without needing to first create a template.
Learn more about creating data products with and without a template
Generate LRS Data Product multi-date support
The Generate LRS Data Product tool supports multiple Effective Date values, allowing you to compare changes in length or feature count over time. For example, you can compare the change in DOT Class mileage year over year along a pipeline or the amount of pavement that changes from fair to poor condition along a road each year.
Relaxed requirements for data loading
In this release of ArcGIS Pro, data loading has fewer restrictions.
Append events even if there are conflict prevention locks and optional mapping of date fields
Bulk loading event data when conflict prevention is enabled is now more flexible. If you need to bulk load events using the Append Events tool, but route locks are impeding the workflow, you can check the Append even if there are conflict prevention locks parameter to override these locks and proceed with loading events.
After running the tool with this parameter checked, any events that are appended onto routes or events that are locked will receive the location error value of No Error: Conflict Prevention Bypassed on those appended records.
Bypassing conflict prevention locks may result in data corruption or unexpected behavior, so it is recommended that you create a database backup before running the tool with this parameter checked.
Additionally, the mapping of the FromDate and ToDate fields in the tool is now optional, so you can bulk load events from vendors that do not record or account for the time during data collection. If you decide not to include the ToDate field, or both the FromDate and ToDate fields, remove the fields from the fields list in the Field Map parameter. The appended events will inherit the To Date (or From and To Date) value of the route they’re appended onto.
Generate intersections even if there are conflict prevention locks
Similar to the Append Events tool, the Generate Intersections tool has been enhanced with a new parameter called Generate intersections even if there are conflict prevention locks. This parameter allows users to generate or update intersections without locking intersecting routes to the route that was edited and to minimize disruption to other LRS data editors who need to make edits to intersecting routes.
Users can also bypass conflict prevention locks when generating or updating intersections as part of the Process Edits tool. To do so, check the Generate intersections even if there are conflict prevention locks box in the Location Referencing options.
The Append Routes tool allows partial loading of routes
In previous releases, when bulk loading routes using the Append Routes tool, one problematic source route would result in the tool failing and not appending any routes. In this release, that is no longer the case. When the Allow partial loading of routes parameter is checked, valid routes will be loaded even if some routes fail validation. The tool outputs a feature class of routes that failed validation, along with messages explaining how to correct them.
Performance improvement in the Overlay Events tool
When running the Overlay Events tool with data from a feature service, the dynamic segmentation process is performed asynchronously with the new Overlay Events REST operation. This new implementation yields significant performance gains, which should result in faster completion time and reduced timeouts.
Address Data Management integration
If you use the combined Roads and Highways and Address Data Management solution deployment pattern, the LRS Hierarchy pane now displays the Address Schema node that contains the address range and site address point feature classes.
By right-clicking each entity and viewing its properties, you can verify which feature class and fields are configured with the Address Data Management solution. This gives you better visibility into what gets updated during LRS editing operations, helping you track changes, design editing workflows, and coordinate QC efforts more effectively.
ArcGIS Utility Network integration
If you use the combined Pipeline Referencing and ArcGIS Utility Network deployment pattern, the LRS Schema node in the LRS Hierarchy pane now has a clear label when a utility network is integrated with the LRS.
Also, in the Centerline properties, you can verify which fields are configured with a utility network. This capability allows you to ensure the relevant fields are configured correctly before you start editing.
ArcGIS Enterprise capabilities
The following capabilities are included in ArcGIS Enterprise.
Express mode support for Location Referencing widgets in Experience Builder
All Location Referencing widgets now support express mode. In express mode, Location Referencing widgets are set up automatically using the web map in the Map widget. Any changes to the web map will immediately update the Location Referencing widgets.
When you configure an app in express mode, all Location Referencing widgets are automatically configured with the Interact with a Map widget setting.
Dynamic Segmentation widget enhancements
The following updates have been made to the Dynamic Segmentation widget.
Search by route ID or route name
Searching for routes by route ID or route name is now built into the Dynamic Segmentation widget. This means you no longer need to rely on data actions. You can run dynamic segmentation directly within the same widget, without switching back and forth between different widgets.
Interact with the map
Also included in this release is the ability to synchronize between the map and the straight line diagram (SLD).
When the Map Interact button 
is enabled, navigating within the map will update the SLD, and vice versa. You can use other map layers as guideposts as you navigate to different locations along the route and view the SLD for those areas in context.
View-only dynamic segmentation table and SLD
Data administrators can now configure view-only access to the dynamic segmentation table and the SLD. To do this, turn the Allow editing setting off. This allows administrators to confidently deploy the SLD in applications for noneditors, such as project planners, knowing that data won’t be accidentally edited or changed.
User interface enhancements
The SLD view now shows more layers with less scrolling. This is helpful if your SLD contains many event layers and you want to compare how these events interact or overlap. Also, the SLD’s scale bar now shows 10 tick marks instead of 8, allowing you to be more precise when navigating along a route.
The Add Line Event and Add Point Event widgets support appending to a primary route
Route concurrency occurs when two or more routes overlap geographically and share the same centerline. In this release, the Add Line Event and Add Point Event widgets support automatically adding events to the primary (dominant) route in the network when route concurrency exists. By checking the Add event to dominant route parameter, any events appended will be placed on the primary route. Even if the route and measure information entered for the input event would otherwise locate it on a subordinate route, the tool will automatically assign it to the primary route. This enhancement streamlines data entry and improves data integrity for event editors because they can enter route and event information directly from source documents without having to translate the data beforehand.
_______________________________________________________________________
Try these new features and let us know what you think!
