What’s Enhanced<\/strong><\/h2>\nBatch Trace<\/strong><\/p>\nTwo new capabilities were added to the Batch Trace tool.<\/p>\n
\n- Historical Date Field – A new parameter was added to use a date from the starting points to run two traces per set of starting points.\u00a0 If a date is specified, the trace is run against the current moment and at the time specified in this date field.\u00a0 This will allow you to compare the outputs between the two moments and determine if a change as occurred.\u00a0 This new parameter can help you run traces by section to determine is a section changed and if it needs to be updated in an ADMS.<\/li>\n
- Stats Table – The output folder parameter is now optional regardless of your result type.\u00a0 If the output folder is specified, a new geodatabase with a stats table is created.\u00a0 This provides information about when a trace was run.\u00a0 This can be used to update the starting points history field with the moment the trace was run at.<\/li>\n<\/ul>\n
Subnetwork Aggregator<\/strong><\/p>\nOne new option was added to this tool.<\/p>\n
\n- Calculate Asset Summary – Option to calculate and store asset counts per subnetwork. If checked, an AssetSummary table is created in the output geodatabase.<\/li>\n<\/ul>\n
Change GDB Spatial Reference<\/strong><\/p>\nChanging the spatial reference of a geodatabase with a Linear Referencing controller dataset is now supported.<\/p>\n
Adjust Data Sources<\/strong><\/p>\nIf the maps have a selection set, it is now cleared.\u00a0 Maps store selection sets by ObjectID.\u00a0 When moving maps between data sources, there is no guarantee that ObjectIDs are the same for a row.\u00a0 If selection sets are maintained, it could end up selected the incorrect rows.<\/p>\n
"}],"short_description":"An update to a toolset to assist working with the utility network and their maps.","flexible_content":[{"acf_fc_layout":"content","content":"