Show Navigation | Hide Navigation

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

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

Related Topics

Creates a temporary feature layer using routes and route events.

When the temporary layer is used (displayed on a map, or used by another geoprocessing tool), dynamic segmentation is performed.

Usage tips

Temporary layers are stored in memory and can be used as input to other geoprocessing functions in your current ArcCatalog or ArcMap session.
In ArcMap, temporary feature layers can be added to the focus map's table of contents if you have indicated that you want to add results of geoprocessing operations to the display.
Once you exit ArcCatalog or ArcMap, temporary feature layers are removed from memory. To persist a temporary layer on disk, use Save To Layer File.
Temporary feature layers created in ArcCatalog cannot be used in ArcMap (and vice versa).
The input table can be any type of table ArcGIS supports.
Use Make Feature Layer on the routes and/or Make Table View on the events prior to Make Route Event Layer to reduce the number of routes and events that will be processed.
Not all types of tables have an ObjectID field. When such tables are used by Make Route Event Layer, the resulting layer will not be selectable and cannot be used effectively by certain geoprocessing operations. Consider using Make Query Table prior to Make Route Event Layer to add a virtual ObjectID field.
Learn more about dynamic segmentation.
The following environments affect this tool: configKeyword, scratchWorkspace, and workspace.

Command line syntax
An overview of the Command Line window
MakeRouteEventLayer_lr <in_routes> <route_id_field> <in_table> <in_event_properties> <out_layer> {offset_field} {NO_ERROR_FIELD | ERROR_FIELD} {NO_ANGLE_FIELD | ANGLE_FIELD} {NORMAL | TANGENT} {ANGLE | COMPLEMENT} {LEFT | RIGHT} {POINT | MULTIPOINT}

Parameter	Explanation	Data Type
<in_routes>	The route features upon which events will be located.	Feature Layer
<route_id_field>	The field containing values that uniquely identify each route.	Field
<in_table>	The table whose rows will be located along routes.	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 is required when the event type is POINT or LINE. To-Measure Field — A field containing measure values. This field must be numeric and is required when the event type is LINE.	Route Measure Event Properties
<out_layer>	The layer to be created. This layer is stored in memory, so a path is not necessary.	Feature Layer
{offset_field}	The field containing values used to offset events from their underlying route. This field must be numeric.	Field
{NO_ERROR_FIELD \| ERROR_FIELD}	Specifies whether a field named LOC_ERROR will be added to the temporary layer that is created. NO_ERROR_FIELD — Do not add a field to store locating errors. This is the default. ERROR_FIELD — Add a field to store locating errors.	Boolean
{NO_ANGLE_FIELD \| ANGLE_FIELD}	Specifies whether a field named LOC_ANGLE will be added to the temporary layer that is created. This parameter is only valid when the event type is POINT. NO_ANGLE_FIELD — Do not add a field to store locating angles. This is the default. ANGLE_FIELD — Add a field to store locating angles.	Boolean
{NORMAL \| TANGENT}	Specifies the type of locating angle that will be calculated. This parameter is only valid if ANGLE_FIELD has been specified. NORMAL — The normal (perpendicular) angle will be calculated. This is the default. TANGENT — The tangent angle will be calculated.	String
{ANGLE \| COMPLEMENT}	Specifies whether the complement of the locating angle will be calculated. This parameter is only valid if ANGLE_FIELD has been specified. ANGLE — Do not write the complement of the angle. Write only the calculated angle. This is the default. COMPLEMENT — Write the complement of the angle.	Boolean
{LEFT \| RIGHT}	Specifies the side on which the route events with a positive offset are displayed. This parameter is only valid if an offset field has been specified. LEFT — Events with a positive offset will be displayed to the left of the route. The side of the route is determined by the measures and not necessarily the digitized direction. This is the default. RIGHT — Events with a positive offset will be displayed to the right of the route. The side of the route is determined by the digitized direction.	Boolean
{POINT \| MULTIPOINT}	Specifies whether point events will be treated as point features or multipoint features. POINT — Point events will be treated as point features. This is the default. MULTIPOINT — Point events will be treated as multipoint features.	Boolean

Data types for geoprocessing tool parameters

Command line example

Workspace D:\Data\pitt_county
MakeRouteEventLayer_lr route_hwy.shp rkey accident.dbf "rkey POINT mile" accident_events # ERROR_FIELD ANGLE_FIELD

Workspace D:\Data\pitt_county\pitt.mdb
MakeRouteEventLayer_lr roads\hwy rkey pavecond "rkey LINE fmp tmp" pave_events # ERROR_FIELD

Workspace D:\Data\pitt_county\pitt.gdb
MakeRouteEventLayer_lr roads\hwy rkey pavecond "rkey LINE fmp tmp" pave_events # ERROR_FIELD

Workspace "Database Connections\Connection to Jerry.sde"
MakeRouteEventLayer_lr gdb.roads\gdb.hwy rkey gdb.accident "rkey POINT mile" accident_events2

Scripting syntax
About getting started with writing geoprocessing scripts
MakeRouteEventLayer_lr (in_routes, route_id_field, in_table, in_event_properties, out_layer, offset_field, add_error_field, add_angle_field, angle_type, complement_angle, offset_direction, point_event_type)

Parameter	Explanation	Data Type
in_routes (Required)	The route features upon which events will be located.	Feature Layer
route_id_field (Required)	The field containing values that uniquely identify each route.	Field
in_table (Required)	The table whose rows will be located along routes.	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 is required when the event type is POINT or LINE. To-Measure Field — A field containing measure values. This field must be numeric and is required when the event type is LINE.	Route Measure Event Properties
out_layer (Required)	The layer to be created. This layer is stored in memory, so a path is not necessary.	Feature Layer
offset_field (Optional)	The field containing values used to offset events from their underlying route. This field must be numeric.	Field
add_error_field (Optional)	Specifies whether a field named LOC_ERROR will be added to the temporary layer that is created. NO_ERROR_FIELD — Do not add a field to store locating errors. This is the default. ERROR_FIELD — Add a field to store locating errors.	Boolean
add_angle_field (Optional)	Specifies whether a field named LOC_ANGLE will be added to the temporary layer that is created. This parameter is only valid when the event type is POINT. NO_ANGLE_FIELD — Do not add a field to store locating angles. This is the default. ANGLE_FIELD — Add a field to store locating angles.	Boolean
angle_type (Optional)	Specifies the type of locating angle that will be calculated. This parameter is only valid if ANGLE_FIELD has been specified. NORMAL — The normal (perpendicular) angle will be calculated. This is the default. TANGENT — The tangent angle will be calculated.	String
complement_angle (Optional)	Specifies whether the complement of the locating angle will be calculated. This parameter is only valid if ANGLE_FIELD has been specified. ANGLE — Do not write the complement of the angle. Write only the calculated angle. This is the default. COMPLEMENT — Write the complement of the angle.	Boolean
offset_direction (Optional)	Specifies the side on which the route events with a positive offset are displayed. This parameter is only valid if an offset field has been specified. LEFT — Events with a positive offset will be displayed to the left of the route. The side of the route is determined by the measures and not necessarily the digitized direction. This is the default. RIGHT — Events with a positive offset will be displayed to the right of the route. The side of the route is determined by the digitized direction.	Boolean
point_event_type (Optional)	Specifies whether point events will be treated as point features or multipoint features. POINT — Point events will be treated as point features. This is the default. MULTIPOINT — Point events will be treated as multipoint features.	Boolean

Data types for geoprocessing tool parameters

Script example

# Example 1:
#   Make a POINT event layer. Routes and events are in a shapefile workspace.
#   An error field and an angle field are added to the new layer. The new layer can be used
#   by other geoprocessing functions.

import arcgisscripting, constants
gp = arcgisscripting.create()
try:
    gp.Workspace = "D:/Data/pitt_county"
    rt = "route_hwy.shp"
    rid = "rkey" 
    tbl = "accident.dbf"
    props = "rkey POINT mile"
    lyr = "accident_events" 
    gp.MakeRouteEventLayer_lr (rt, rid, tbl, props, lyr, "#",  "ERROR_FIELD",  "ANGLE_FIELD") 
except:
    print gp.GetMessages(2)


# Example 2:
#   Make a LINE event layer. Routes and events are in a file geodatabase.
#   An error field is added to the new layer. The new layer can be used by other 
#   geoprocessing functions.

import arcgisscripting, constants
gp = arcgisscripting.create()
try:
    gp.Workspace = "D:/Data/pitt_county/pitt.gdb"
    rt = "roads/hwy"          # the 'hwy' feature class is in the 'roads' feature dataset
    rid = "rkey" 
    tbl = "pavecond"
    props = "rkey LINE fmp tmp"
    lyr = "pave_events" 
    gp.MakeRouteEventLayer_lr (rt, rid, tbl, props, lyr, "#",  "ERROR_FIELD")
except:
    print gp.GetMessages(2)


# Example 3:
#   Make a LINE event layer. Routes and events are in a personal geodatabase.
#   An error field is added to the new layer. The new layer can be used by other 
#   geoprocessing functions.

import arcgisscripting, constants
gp = arcgisscripting.create()
try:
    gp.Workspace = "D:/Data/pitt_county/pitt.mdb"
    rt = "roads/hwy"          # the 'hwy' feature class is in the 'roads' feature dataset
    rid = "rkey" 
    tbl = "pavecond"
    props = "rkey LINE fmp tmp"
    lyr = "pave_events" 
    gp.MakeRouteEventLayer_lr (rt, rid, tbl, props, lyr, "#",  "ERROR_FIELD")
except:
    print gp.GetMessages(2)


# Example 4:
#   Make a POINT event layer. Routes and events are in an enterprise geodatabase.
#   The new layer can be used by other geoprocessing functions.

import arcgisscripting, constants
gp = arcgisscripting.create()
try:
    wkspc = "Database Connections/Connection to Jerry.sde"
    gp.Workspace = wkspc 
    ds = gp.QualifyTableName("roads", wkspc)          # the 'roads' feature dataset
    fc = gp.QualifyTableName("hwy", wkspc)            # the 'hwy' feature class 
    rt = ds + "/" + fc #the 'hwy' feature class is in the 'roads' feature dataset
    rid = "rkey" 
    tbl = gp.QualifyTableName("accident", wkspc)
    props = "rkey POINT mile"
    lyr = "accident_events2" 
    gp.MakeRouteEventLayer_lr (rt, rid, tbl, props, lyr) 
except:
    print gp.GetMessages(2)

Make Route Event Layer (Linear Referencing)

Command line example

Script example