Show Navigation | Hide Navigation

You are here:
Geoprocessing tool reference > Linear Referencing toolbox > Tools

Transform Route Events (Linear Referencing)
Release 9.2 Last modified November 9, 2006	Print all topics in : "Tools"

Related Topics

Transforms the measures of events from one route reference to another and writes them to a new event table.

Usage tips

Transforming events allows you to use the events from one route reference with another route reference having different route identifiers and/or measures.
Any whole or partial event that intersects a target route is written to the new event table.
The output event type (POINT or LINE) must match the input event type.
The best results will be achieved when the source routes and the target routes closely overlay. Do not use a large cluster tolerance to try and overcome discrepancies between the source and target routes because it can lead to unexpected results.
Use Make Table View prior to Transform Route Events to effectively reduce the number of events that will be processed.
The output table can be displayed in ArcMap using Make Route Event Layer or the Add Route Events dialog box.
Learn more about transforming event measures
The following environments affect this tool: configKeyword, scratchWorkspace, and workspace.

Command line syntax
An overview of the Command Line window
TransformRouteEvents_lr <in_table> <in_event_properties> <in_routes> <route_id_field> <target_routes> <target_route_id_field> <out_table> <out_event_properties> <cluster_tolerance> {FIELDS | NO_FIELDS}

Parameter	Explanation	Data Type
<in_table>	The input event table.	Table View
<in_event_properties>	Parameter consisting of the route location fields and the type of events in the input event table. Route Identifier Field — The field containing values that indicate which route each event is along. This field can be numeric or character. Event Type — The type of events in the input event table (POINT or LINE). POINT — Point events occur at a precise location along a route. Only a from-measure field must be specified. LINE — Line events define a portion of a route. Both from- and to-measure fields must be specified. From-Measure Field — A field containing measure values. This field must be numeric, and it is required when the event type is POINT or LINE. To-Measure Field — A field containing measure values. This field must be numeric, and it is required when the event type is LINE.	Route Measure Event Properties
<in_routes>	The input route features.	Feature Layer
<route_id_field>	The field containing values that uniquely identifies each input route.	Field
<target_routes>	The route features to which the input events will be transformed.	Feature Layer
<target_route_id_field>	The field containing values that uniquely identifies each target route.	Field
<out_table>	The table to be created.	Table
<out_event_properties>	Parameter consisting of the route location fields and the type of events that will be written to the output event table. Route Identifier Field — The field that will contain values that indicate which route each event is along. Event Type — The type of events the output event table will contain (POINT or LINE). POINT — Point events occur at a precise location along a route. Only a from-measure field must be specified. LINE — Line events define a portion of a route. Both from- and to-measure fields must be specified. From-Measure Field — A field that will contain measure values. Required when the event type is POINT or LINE. To-Measure Field — A field that will contain measure values. Required when the event type is LINE.	Route Measure Event Properties
<cluster_tolerance>	The maximum tolerated distance between the input events and the target routes.	Linear unit
{FIELDS \| NO_FIELDS}	Specifies whether the output event table will contain route location fields plus all the attributes from the input events. FIELDS — The output event table will contain route location fields plus all the attributes from the input events. This is the default. NO_FIELDS — The output event table will only contain route location fields plus the ObjectID field from the input events.	Boolean

Data types for geoprocessing tool parameters

Command line example

Workspace "C:\Data"
TransformRouteEvents_lr pavement.dbf "route1 LINE begin_mp end_mp" hwy.shp route1 hwy_new.shp route1 trans_out1.dbf "route1 LINE fmp tmp" "0.1 meters"

Workspace "C:\Data\pitt.mdb"
TransformRouteEvents_lr accident "route1 POINT measure" roads\hwy route1 roads\hwy_new route1 trans_out2 "route1 POINT mp" "0.1 meters"

Workspace "C:\Data\pitt.gdb"
TransformRouteEvents_lr accident "route1 POINT measure" roads\hwy route1 roads\hwy_new route1 trans_out2 "route1 POINT mp" "0.1 meters"

Workspace "Database Connections\Connection to Jerry.sde"
TransformRouteEvents_lr gdb.accident "route1 POINT measure" gdb.hwy route1 gdb.hwy_new route1 trans_out3 "route1 POINT mp" "0.1 meters"

Scripting syntax
About getting started with writing geoprocessing scripts
TransformRouteEvents_lr (in_table, in_event_properties, in_routes, route_id_field, target_routes, target_route_id_field, out_table, out_event_properties, cluster_tolerance, in_fields)

Parameter	Explanation	Data Type
in_table (Required)	The input event table.	Table View
in_event_properties (Required)	Parameter consisting of the route location fields and the type of events in the input event table. Route Identifier Field — The field containing values that indicate which route each event is along. This field can be numeric or character. Event Type — The type of events in the input event table (POINT or LINE). POINT — Point events occur at a precise location along a route. Only a from-measure field must be specified. LINE — Line events define a portion of a route. Both from- and to-measure fields must be specified. From-Measure Field — A field containing measure values. This field must be numeric, and it is required when the event type is POINT or LINE. To-Measure Field — A field containing measure values. This field must be numeric, and it is required when the event type is LINE.	Route Measure Event Properties
in_routes (Required)	The input route features.	Feature Layer
route_id_field (Required)	The field containing values that uniquely identifies each input route.	Field
target_routes (Required)	The route features to which the input events will be transformed.	Feature Layer
target_route_id_field (Required)	The field containing values that uniquely identifies each target route.	Field
out_table (Required)	The table to be created.	Table
out_event_properties (Required)	Parameter consisting of the route location fields and the type of events that will be written to the output event table. Route Identifier Field — The field that will contain values that indicate which route each event is along. Event Type — The type of events the output event table will contain (POINT or LINE). POINT — Point events occur at a precise location along a route. Only a from-measure field must be specified. LINE — Line events define a portion of a route. Both from- and to-measure fields must be specified. From-Measure Field — A field that will contain measure values. Required when the event type is POINT or LINE. To-Measure Field — A field that will contain measure values. Required when the event type is LINE.	Route Measure Event Properties
cluster_tolerance (Required)	The maximum tolerated distance between the input events and the target routes.	Linear unit
in_fields (Optional)	Specifies whether the output event table will contain route location fields plus all the attributes from the input events. FIELDS — The output event table will contain route location fields plus all the attributes from the input events. This is the default. NO_FIELDS — The output event table will only contain route location fields plus the ObjectID field from the input events.	Boolean

Data types for geoprocessing tool parameters

Script example

# Example 1:
# Transform line events (input table is dBASE)

import arcgisscripting, constants
gp = arcgisscripting.create()
try:
    gp.Workspace = "C:/Data"
    in_tbl = "pavement.dbf"
    in_props = "route1 LINE begin_mp end_mp"
    in_rt = "hwy.shp"
    in_rid = "route1" 
    target_rt = "hwy_new.shp"
    target_rid = "route1" 
    out_tbl = "trans_out1.dbf"
    out_props = "route1 LINE fmp tmp"
    tol = "0.1 meters"  
    gp.TransformRouteEvents_lr(in_tbl, in_props, in_rt, in_rid, target_rt, target_rid, out_tbl, out_props, tol)
except:
    print gp.GetMessages(2)


# Example 2:
#   Transform point events (input table is in a file geodatabase)

import arcgisscripting, constants
gp = arcgisscripting.create()
try:
    gp.Workspace = "C:/Data/pitt.gdb"
    in_tbl = "accident"
    in_props = "route1 POINT measure"
    in_rt = "roads/hwy"               # hwy exists in the roads feature dataset 
    in_rid = "route1" 
    target_rt = "roads/hwy_new"       # hwy_new exists in the roads feature dataset 
    target_rid = "route1" 
    out_tbl = "trans_out2"
    out_props = "route1 POINT mp"
    tol = "0.1 meters"  
    gp.TransformRouteEvents_lr(in_tbl, in_props, in_rt, in_rid, target_rt, target_rid, out_tbl, out_props, tol)
except:
    print gp.GetMessages(2)    


# Example 3:
#   Transform point events (input table is in a personal geodatabase)

import arcgisscripting, constants
gp = arcgisscripting.create()
try:
    gp.Workspace = "C:/Data/pitt.mdb"
    in_tbl = "accident"
    in_props = "route1 POINT measure"
    in_rt = "roads/hwy"               # hwy exists in the roads feature dataset 
    in_rid = "route1" 
    target_rt = "roads/hwy_new"       # hwy_new exists in the roads feature dataset 
    target_rid = "route1" 
    out_tbl = "trans_out2"
    out_props = "route1 POINT mp"
    tol = "0.1 meters"  
    gp.TransformRouteEvents_lr(in_tbl, in_props, in_rt, in_rid, target_rt, target_rid, out_tbl, out_props, tol)
except:
    print gp.GetMessages(2)


# Example 4:
#   Transform point events (input table is in an enterprise geodatabase)
import arcgisscripting, constants
gp = arcgisscripting.create()
try:
    wkspc = "Database Connections/Connection to Jerry.sde"
    gp.Workspace = wkspc 
    in_tbl = gp.QualifyTableName("accident", wkspc) 
    in_props = "route1 POINT measure"
    in_rt = gp.QualifyTableName("hwy", wkspc) 
    in_rid = "route1" 
    target_rt = gp.QualifyTableName("hwy_new", wkspc) 
    target_rid = "route1" 
    out_tbl = "trans_out3"
    out_props = "route1 POINT mp"
    tol = "0.1 meters"  
    gp.TransformRouteEvents_lr(in_tbl, in_props, in_rt, in_rid, target_rt, target_rid, out_tbl, out_props, tol)
except:
    print gp.GetMessages(2)

Transform Route Events (Linear Referencing)

Command line example

Script example