Résumé
Helps generate and update LRS intersection point features.
Utilisation
This tool only works with ArcGIS for Desktop Advanced.
Turn on Editor Tracking for the network and the intersecting layers. Editor tracking in conjunction with the Start Time parameter makes it possible to only update intersections that have changed since the Start Time provided by the user. Doing so may result in faster performance. For more information on the Editor Tracking tool, see Enable Editor Tracking.
Intersection Layeris a point feature class that stores the LRS intersections data. This feature class gets updated as the result of running this tool.
Network Layeris the polyline feature class that stores the LRS network data. You can select routes from this feature class for which the intersections will be updated. Definition filters on the network layer are also considered when selecting the routes for updating the intersections.
The route selection or definition filters are only considered if a Network Layer is selected in the tool.
The Start Time is used to only update intersections for routes and interesting features that have been edited since this time. This option is only available for the datasets with Editor Tracking enabled. If Editor Tracking is not enabled in any of the intersecting layers, then the intersections are updated for all the routes present in the dataset.
If the Lock Routes option is checked, then routes for which intersections are being calculated will be locked. If not checked, no routes will be locked in support of calculating intersections. This option is only possible for data available in an enterprise geodatabase.
If the Lock Routes option is checked, then routes for which intersections are being calculated should be available for locking by the current user in the current version.
With the Lock Routes option unchecked, you can periodically calculate the intersections in a publication dataset without the need to lock routes to calculate them.
If the Lock Routes option is unchecked and the routes aren't locked during intersection calculation, then you would be responsible for reconciling any intersection conflicts with the parent version, which can be achieved by accepting (reconciling) route changes in the edit version from the parent and recalculating intersections using the Update Intersection Points tool.
The Lock Routes option also allows you to calculate intersections in the Lock Root version after posting so that intersections are always calculated with the most recent routes without the need to lock routes or the need to calculate intersections in edit versions that are the children of Lock Root. For more information on the Lock Root version, see Conflict prevention in Roads and Highways for Desktop.
If the Lock Intersecting Routes option is checked, then all routes that intersect with routes for which intersections are being calculated will be locked. If not checked, they will not be locked. This option is disabled unless the Lock Routes option is checked. This option is only possible for data available in an enterprise geodatabase.
If the Lock Intersecting Routes option is checked, then routes for which intersections are being calculated including their intersecting routes should be available for locking by the current user in the current version.
If the Lock Intersecting Routes option is unchecked, then you have the option of not locking the routes that are intersecting with the routes for which intersections are being calculated. This would reduce the number of locks needed to calculate intersections.
If the Lock Intersecting Routes option is unchecked, then the intersecting routes aren't locked during the calculation. You would be responsible for reconciling any intersection conflicts with the parent version, which can be achieved by accepting (reconciling) route changes in the edit version from the parent and recalculating intersections using the Update Intersection Points tool.
If the Only calculate intersections for routes edited by me in current version option is checked, then only routes edited by the present user in the current version, as identified by ArcGIS editor tracking, will have intersections updated. For a dataset available in a file geodatabase, the intersections are updated for routes that are edited by the current windows user. Editor tracking must be enabled for the network feature class to make use of this functionality.
The routes to be processed for updating the intersections are chosen on the basis of the Route selection AND Route definition query AND Date selection AND the option of Only calculating intersections for routes edited by me in the current version. In other words, if you have provided all the above four options, then only the routes which fulfil all those conditions will be processed for updating the intersections. Additionally if the Lock Routes and the Lock Intersecting Routes options are also checked, then the selected routes should be available for locking for successfully running the tool.
If Editor Tracking is not enabled in an enterprise geodatabase, then all routes edited in the selected version are processed if the Only calculate intersections for routes edited by me in current version option is checked.
The following types of intersection points are not updated using this tool:
- Points that are not part of the intersecting layers
- Points that are added manually to the LRS intersection class
- Points that are copied to the LRS intersection class
- Points that are merged or appended to the LRS intersection class
When intersections are updated, the following situations can occur:
- New intersections are created - New intersections can be created due to edit activities such as Create Route, Realign Route, Extend Route, Reassign Route, Cartographic Realignment, Addition or edits of Non-LRS features such as railroads and political boundaries, and so on.
- Present intersections are retired - An intersection is retired with its To Date populated with the route's edit date due to Realign Route, Retire Route, Reassign Route, and so on.
- Present intersections are moved - Intersections are moved due to Cartographic Realignment or edits of Non-LRS features. In such cases, that intersection's location is changed and the shape (point location) for the intersection is updated, maintaining the intersection ID. The intersections are not retired in this case. If a feature intersects a route in multiple locations and the intersection locations change, the original intersection closest to the new location determines where the intersection is moved.
- Present intersections are deleted - Intersections are deleted due to Cartographic Realignment or edits of Non-LRS features. This occurs when the routes do not intersect the features anymore in any time range.
The following table shows the various scenarios when updating the intersections:
Edit Activity Route and Route Intersection Route and Non-LRS layer intersection Route Edits
Retires the present intersections and/or creates new intersections
Retires the present intersections and/or creates new intersections
Cartographic Realignment: Intersecting as a result
Moves the present intersections and/or creates new intersections
Moves the present intersections
Cartographic Realignment: Not intersecting anymore
Deletes the present intersections
Deletes the present intersections
Non-LRS feature edited: Intersecting as a result
N/A
Moves the present intersections
Non-LRS feature edited: Not intersecting anymore
N/A
Deletes the present intersections
- When conflict prevention is enabled
If a message appears that is related to acquiring locks, the need to reconcile, or not being able to acquire locks, and so on, then Roads and Highways conflict prevention is enabled. For more information about these messages, see Conflict prevention in Roads and Highways for Desktop.
- If conflict prevention has been enabled and an intersecting polygon feature such as a county boundary has been edited, you will be prompted to acquire locks for all the routes that intersect that polygon's boundary.
- If you are working in the lock root version, all the locks acquired by the tool to update the intersections will be released automatically.
- If you are working in a child version, all the locks acquired by the tool to update the intersections will remain.
Syntaxe
UpdateIntersectionPoints_roads (in_intersection_layer, {in_network}, {in_start_time}, {in_lock_routes}, {in_lock_intersecting_routes}, {in_only_calculate_intersections_for_routes_edited_by_me_in_current_version})
Paramètre | Explication | Type de données |
in_intersection_layer | The LRS intersection feature class that needs to be updated. | Feature Layer |
in_network (Facultatif) | The polyline feature class that stores the LRS network data. You can select routes from this feature class for which the intersections will be updated. Definition filters on the network layer are also considered when selecting the routes for updating the intersections. | Feature Layer |
in_start_time (Facultatif) | This value is used to only update intersections for routes and interesting features that have been edited since this time for those layers that have editor tracking turned on. | Date |
in_lock_routes (Facultatif) | Routes for which intersections are being calculated will be locked. | Boolean |
in_lock_intersecting_routes (Facultatif) | All routes that intersect with routes for which intersections are being calculated will be locked. | Boolean |
in_only_calculate_intersections_for_routes_edited_by_me_in_current_version (Facultatif) | Only routes edited by the present user as indicated in the ArcGIS editor tracking will have the intersections calculated for the current version of the data. | Boolean |
Exemple de code
UpdateIntersectionPoints example 1 (Python window)
The following Python window script demonstrates how to use the UpdateIntersectionPoints tool in ArcMap.
# tool variables
in_intersection_layer="Intersections"
in_network="MilePoint"
in_start_time="01/01/2012"
in_lock_routes="LOCK_ROUTES"
in_lock_intersecting_routes="LOCK_INTERSECTING_ROUTES"
in_only_calculate_intersections_for_routes_edited_by_me_in_current_version="ONLY_CALCULATE_INTERSECTIONS_FOR_ROUTES_EDITED_BY_ME_IN_CURRENT_VERSION"
# set current workspace
arcpy.env.workspace="C:/data/Outputs.gdb"
# execute the tool with all options
arcpy.UpdateIntersectionPoints_roads ("Intersections", "Milepoint", "01/01/2012", "LOCK_ROUTES", "LOCK_INTERSECTING_ROUTES", "ONLY_CALCULATE_INTERSECTIONS_FOR_ROUTES_EDITED_BY_ME_IN_CURRENT_VERSION")
UpdateIntersectionPoints example 2 (stand-alone script)
The following Python window script demonstrates how to use the UpdateIntersectionPoints tool in a stand-alone Python script.
# Name: UpdateIntersections_PyWin.py
# Description: Updates LRS intersection points
# Requirements: Esri Roads and Highways solution
# Import arcpy module
import arcpy
# Check out any necessary licenses
arcpy.CheckOutExtension("Highways")
# Local variables
IntersectionPointLayer = r"C:\RH\DOT.sde\rht2.RH.LRSI_Route_Intersections"
NetworkLayer = r"C:\RH\DOT.sde\rht2.RH.LRSN_MilePoint"
StartDate = "4/5/2016"
LockRoutes = "LOCK_ROUTES"
LockIntersectingRoutes = "LOCK_INTERSECTING_ROUTES"
OnlyUseRoutesEditedbyMeInCurrentVersion = "ONLY_CALCULATE_INTERSECTIONS_FOR_ROUTES_EDITED_BY_ME_IN_CURRENT_VERSION"
# Process: Update Intersection Points
arcpy.UpdateIntersectionPoints_roads(IntersectionPointLayer, NetworkLayer, StartDate,LockRoutes, LockIntersectingRoutes, OnlyUseRoutesEditedbyMeInCurrentVersion)
Environnements
Cet outil n'utilise aucun environnement de géotraitement
Informations de licence
- ArcGIS for Desktop Basic: Non
- ArcGIS for Desktop Standard: Non
- ArcGIS for Desktop Advanced: Requiert Roads and Highways