Make Traversal (Production Mapping)

Summary

Combines existing line features into a single route feature class using feature attributes, attributes from joined tables, or a combination thereof.

Usage

Syntax

MakeTraversal_production (in_line_features, in_dissolve_field, out_feature_class, out_roadway_identifier, {in_use_dissolve_field}, {in_separation_character}, {out_from_measure}, {out_to_measure}, {in_allow_multipart_features}, {in_measure_source}, {in_from_measure}, {in_to_measure}, {in_calibration_point_feature}, {in_calibration_identifier_field}, {in_measure_field}, {in_search_radius})
ParameterExplanationData Type
in_line_features

The feature layer or path to the feature class that contains the linear features you want to merge.

Feature Layer
in_dissolve_field
[in_dissolve_field,...]

The fields in the line feature class whose values determine whether or not line features are going to be merged. Examples of these fields could include RouteName, RouteNumber, and Direction, for example, I-10-WB.

Field
out_feature_class

The path to and name of the new feature class that will contain the merged features.

Feature Class
out_roadway_identifier

The field in the output feature class that will contain the route identifiers. If in_use_dissolve_field is TRUE, the dissolve field values are used as the route identifier. If in_use_dissolve_field is FALSE, a unique number value is used as the route identifier.

String
in_use_dissolve_field
(Optional)

Indicates whether or not the dissolve field values will be used as the route identifiers.

  • USE_DISSOLVEThe dissolve field values are used as the route identifiers. If there is more than one dissolve field selected, the values are separated using the separation character indicated in in_separation_char. This is the default value.If no separation character has been specified, the values are concatenated.
  • NO_DISSOLVEThe dissolve field values are not used as the route identifier. Instead, they are unique numeric values.
Boolean
in_separation_character
(Optional)

The character(s) you want to use to separate concatenated values for the route identifier when more than one dissolve field is specified.

If no separation character is specified, the values are concatenated.

If the in_use_dissolve_field value is NO_DISSOLVE, this value is ignored.

String
out_from_measure
(Optional)

The name of the field that is going to contain the from-measure values for the merged features. The default value is F_Meas.

String
out_to_measure
(Optional)

The name of the field that is going to contain the to-measure values for the merged features. The default value is T_Meas.

String
in_allow_multipart_features
(Optional)

Indicates whether or not multipart features can be created when features are merged based on their dissolve field values.

  • DISALLOW_MULTIPART_FEATFeatures will only be merged based on the dissolve fields if they are not going to create multipart geometries.
  • ALLOW_MULTIPART_FEATFeatures can be merged based on dissolve fields, even if they are going to create multipart geometries.
Boolean
in_measure_source
(Optional)

Specifies how route measures will be obtained for the merged features.

  • LENGTHThe geometric length of the input features will be used to accumulate the measures. This is the default.
  • ONE_FIELDThe value stored in the field specified in the in_from_measure parameter will be used to accumulate the measures.
  • TWO_FIELDSThe values stored in fields specified for the in_from_measure and in_to_measure parameters will be used to set the measures.
  • CALIBRATIONThe values from a calibration points feature class will be used to accumulate the measures.
String
in_from_measure
(Optional)

The field that contains the starting measure values. This parameter is required if you choose ONE_FIELD or TWO_FIELDS for the in_measure_source parameter.

The field you choose is from the input feature class and must be numeric.

Field
in_to_measure
(Optional)

The field that contains the ending measure values. This parameter is required if you choose TWO_FIELDS for the in_measure_source parameter.

The field you choose is from the input feature class and must be numeric.

Field
in_calibration_point_feature
(Optional)

The feature layer or path to the point feature class that contains calibration points that will be used to determine the length of merged line features. This parameter is required if you choose CALIBRATION for the in_measure_source parameter.

Feature Layer
in_calibration_identifier_field
(Optional)

The field within the calibration point feature class that contains the calibration point identifiers. The values in this field match those that are created in the out_roadway_identifier parameter.

This parameter is required if you choose CALIBRATION for the in_measure_source parameter.

Field
in_measure_field
(Optional)

The field in the calibration point feature class that contains the measure values. This field must be numeric.

This parameter is required if you choose CALIBRATION for the in_measure_source parameter.

Field
in_search_radius
(Optional)

The amount of space that can exist between the calibration point and the route. If the distance between the calibration point and the line is further than the specified value, the calibration point is not used to determine the measure value.

Linear Unit

Code Sample

MakeTraversal (Python window)

The following Python window example demonstrates how to use the MakeTraversal function with production mapping sample data. The code creates a feature layer from the RoadL feature class. The code then creates a route from this feature layer by dissolving on the name field. Output is written to the file geodatabase. Use this code from ArcMap or ArcCatalog with the Production Mapping extension enabled.

import arcpy
arcpy.MakeFeatureLayer_management(r'C:\data\SoCal.gdb\SoCal\RoadL',"RoadL","nam <> 'UNK'")
arcpy.ImportToolbox(r'C:\Program Files\ArcGIS\Desktop10.0\ArcToolbox\Toolboxes\Production Mapping Tools.tbx')
arcpy.MakeTraversal_production("RoadL","nam","c:/data/traverse.gdb/RoadLTraverse","RoadID","USE_DISSOLVE")

Environments

Related Topics

Licensing Information

ArcView: No
ArcEditor: Requires Production Mapping
ArcInfo: Requires Production Mapping

5/4/2011