Help

Detect Non-Monotonic Routes

Summary

Checks routes for nonmonotonic calibration of the m-values on vertices. Non-Monotonic calibration occurs when a route does not contain either strictly increasing or strictly decreasing m-values on its vertices.

Usage

  • If two consecutive vertices have the same m-value, then it is considered nonmonotonic calibration.

  • If there is no polyline between two consecutive vertices with the same m-value, then the tool will output a record without a shape.

  • The output feature class contains the paths between nonmonotonic vertices.

  • The output feature class contains the following fields: NetworkName, RouteID, FromMeasure, ToMeasure, FromDate, and ToDate.

Syntax

DetectNonMonotonicRoutes_roads (in_network, out_feature, in_monotonicity_type, in_from_date_field, in_to_date_field, in_route_id_field)
ParameterExplanationData Type
in_network

The network containing the routes to be validated.

Feature Layer
out_feature

Feature class containing polylines for nonmonotonic paths.

Feature Class
in_monotonicity_type

Type of monotonicity checked on the routes.

  • ANY —Output will contain polylines for any m-values that are neither strictly increasing nor strictly decreasing.
  • STRICTLY_INCREASING —Output will contain polylines for any m-values that are not strictly increasing.
  • STRICTLY_DECREASING —Output will contain polylines for any m-values that are not strictly decreasing.
String
in_from_date_field

The attribute/field of the input Network Layer containing the From Date of the route.

Date Field
in_to_date_field

The attribute/field of the input Network Layer containing the To Date of the route.

Date Field
in_route_id_field

The attribute/field of the input Network Layer containing the Route ID field.

Field

Code sample

DetectNonMonotonicRoutes example (Python window)

The following Python window script demonstrates how to use the DetectNonMonotonicRoutes function in immediate mode.

# tool variables
inNetwork="MileMarker"
outFeatures="NonMonotonic_Output"
monoType="STRICTLY_DECREASING"
fromDateField="FROM_DATE"
toDateField="TO_DATE"
routeIdField="ROUTE_ID"

# set current workspace
arcpy.env.workspace="C:/data/Outputs.gdb"

# execute the tool
arcpy.DetectNonMonotonicRoutes_roads(inNetwork, outFeatures, monoType, fromDateField, toDateField, routeIdField)
DetectNonMonotonicRoutes example (stand-alone Python script)

The following Python window script demonstrates how to use the DetectNonMonotonicRoutes function in stand-alone Python script.

# Name: Detect Non-Monotonic Routes_Example.py
# Description: Convert Roads and Highways Network Layer to Feature Layer and Detect Non-Monotonic Routes in a file geodatabase
# Requires: Esri Roads and Highways Solution

# Import arcpy module
import arcpy

# Check out any necessary licenses
arcpy.CheckOutExtension("Highways")

# Local variables
network = "C:/Data/NY_Data.gdb/LRSN_MilePoint"
nonMonotonicOutput = "C:/Data/Outputs.gdb/NonMonotonic_Output"

# Process: Detect Non-monotonic Routes
arcpy.env.overwriteOutput = 1
arcpy.DetectNonMonotonicRoutes_roads(network, nonMonotonicOutput, "Any", "From_Date", "To_Date", "Route_Id")

Environments

This tool does not use any geoprocessing environments

Licensing information

  • ArcGIS Desktop Basic: Requires Roads and Highways
  • ArcGIS Desktop Standard: Requires Roads and Highways
  • ArcGIS Desktop Advanced: Requires Roads and Highways

Related topics