Skip to end of metadata
Go to start of metadata

NET_EXT_ROUTES

This table contains one record for every route in the LRS. This is the precursor for SETUP_NETWORK_LINES described in Section 8.3.1.

Data Structure:

Column

Data Type

Description

NET_EXT_SYSTEM_ID

NUMBER(38,0)

From the value for Net_Ext_System_ID field of the Net_Ext_Systems table (should always be 1)

NET_ROUTE_NAME

VARCHAR2(100 CHAR)

This is the route name based on the base LRM

SHAPE

GEOMETRY

XYZM geometry, can be multipart geometry in the case of physical gaps in the route. The Ms should be based on the base LRM.

NET_OFFSET_FROM

NUMBER(22,3)

The measure at the start of the route to 3 decimal places based on the base LRM.

NET_OFFSET_TO

NUMBER(22,3)

The measure at the end of the route to 3 decimal places based on the base LRM.

TEMPO_EFF_BIRTH_DATE

DATE

The date of the last edit to this route

TEMPO_EFF_DEATH_DATE

DATE

Should be null since all of these routes should be active, but use if you want to retire a route

IS_MODIFIED

NUMBER(38,0)

This field indicates whether this route has been updated during the LRS Gateway.


Out of the box, a standard import using shape file has been configured that matches NET_EXT_ROUTES structure. The shape file needs to have the following specification:

Shape File Header

Data Type

Description

FIG


Not mapped

GEOM

Shape

Map to SHAPE field. Need to be ESPG:4326 projection.

OBJECTID


Not mapped

SYSTEM_ID

Integer

Should always be 1. Mapped to NET_EXT_SYSTEM_ID.

ROUTE_NAME

String

Mapped to NET_ROUTE_NAME

MEAS_FROM

Number

Mapped to NET_OFFSET_FROM

MEAS_TO

Number

Mapped to NET_OFFSET_TO

DATE_FROM

Date

Mapped to TEMPO_EFF_BIRTH_DATE

DATE_TO

Date

Mapped to TEMPO_EFF_DEATH_DATE

MODIFIED

Number

Should always be 1 for initial LRS population. Mapped to IS_MODIFIED.

NET_EXT_CONCURRENCY

This table correlates dominant and subordinate routes. For subordinate routes that are in the opposite direction of the dominant route, make the dominant "from" measure greater than the dominant "to" measure. It has one record for each subordinate segment in the entire LRS. There can be multiple subordinate sections tied to the same dominant section. This is the precursor for the two CURRENT_LOCATION_SUB and CURRENT_LOCATION_DOM tables described in Section 8.3.2.

Data Structure:

Column

Data Type

Description

NET_EXT_SYSTEM_ID

NUMBER(38,0)

From the value for Net_Ext_System_ID field of the Net_Ext_Systems table (should always be 1)

NET_DOM_ROUTE_NAME

VARCHAR2(100 CHAR)

The name of the dominant route based on the base LRM.

NET_DOM_OFFSET_FROM

NUMBER(22,3)

The measure on the dominant route at the start of the concurrency to 3 decimal places based on the base LRM. If it is an opposite direction concurrency, the values in the NET_DOM_OFFSET_FROM and the NET_DOM_OFFSET_TO fields are reversed.

NET_DOM_OFFSET_TO

NUMBER(22,3)

The measure on the dominant route at the end of the concurrency to 3 decimal places based on the base LRM. If it is an opposite direction concurrency, the values in the NET_DOM_OFFSET_FROM and the NET_DOM_OFFSET_TO fields are reversed.

NET_SUB_ROUTE_NAME

VARCHAR2(100 CHAR)

The name of a subordinate route based on the base LRM.

NET_SUB_OFFSET_FROM

NUMBER(22,3)

The measure on the subordinate route at the start of the concurrency to 3 decimal places based on the base LRM.

NET_SUB_OFFSET_TO

NUMBER(22,3)

The measure on the subordinate route at the end of the concurrency to 3 decimal places based on the base LRM.

ERROR_TEXT

VARCHAR2(4000 CHAR)

Null


Out of the box, a standard import using csv file has been configured that matches NET_EXT_CONCURRENCY structure. The csv needs to have the following specification:

csv File Header

Data Type

Description

NET_EXT_SYSTEM_ID

Integer

Should always be 1.

NET_DOM_ROUTE_NAME

String

Map to NET_DOM_ROUTE_NAME

NET_DOM_OFFSET_FROM

Number

Map to NET_DOM_OFFSET_FROM

NET_DOM_OFFSET_TO

Number

Map to NET_DOM_OFFSET_TO

NET_SUB_ROUTE_NAME

String

Map to NET_SUB_ROUTE_NAME

NET_SUB_OFFSET_FROM

Number

Map to NET_SUB_OFFSET_FROM

NET_SUB_OFFSET_TO

Number

Map to NET_SUB_OFFSET_TO

ERROR_TEXT

String

Map to ERROR_TEXT. Empty for initial data load.

NET_EXT_GAPS

This table describes gaps in routes. It has one record for each gap in the LRS. This is the precursor for NETWORK_GAPS described in Section 8.3.3.

Data Structure:

Field

Data Type

Description

NET_EXT_SYSTEM_ID

NUMBER(38,0)

From the value for Net_Ext_System_ID field of the Net_Ext_Systems table (should always be 1)

NET_ROUTE_NAME

VARCHAR2(100 CHAR)

This is the route name based on the base LRM

NET_OFFSET_FROM

NUMBER(22,3)

The measure at the start of the gap to 3 decimal places based on the base LRM.

NET_OFFSET_TO

NUMBER(22,3)

The measure at the end of the gap to 3 decimal places based on the base LRM.

ERROR_TEXT

VARCHAR2(4000 CHAR)

Null

ALLOW_SPANNING

NUMBER(1,0)

0 for "physical" gaps (where there is a geographical distance between the start and the end of the gap), 1 for "measure" gaps (where there is no geographical distance between the start and the end of the gap).

Out of the box, a standard import using csv file has been configured that matches NET_EXT_GAPS table structure. The csv needs to have the following specification:

csv File Header

Data Type

Description

NET_EXT_SYSTEM_ID

Integer

Should always be 1.

NET_ROUTE_NAME

String

Map to NET_ROUTE_NAME

NET_OFFSET_FROM

Number

Map to NET_OFFSET_FROM

NET_OFFSET_TO

Number

Map to NET_OFFSET_TO

ERROR_TEXT

String

Map to ERROR_TEXT. Empty for initial data load.

ALLOW_SPANNING

Number

0 for "physical" gaps (cases where there is a geographical distance between the start and the end of the gap), 1 for "measure" gaps (cases where there is no geographical distance between the start and the end of the gap). Map to ALLOW_SPANNING

NET_EXT_LRMS

This table correlates alternate LRMS to the base LRM. The LRMs are defined in the Setup_Loc_Ref and Setup_Loc_Ref_Columns tables. It contains one record for each alt LRM segment in the LRS. This is the precursor for the Base/Alt LRM mapping.
Out of the box, no Alt LRM has been configured. Therefore, no standard import is configured on to this buffer table.

Data Structure:

Field

Data Type

Description

NET_EXT_SYSTEM_ID

NUMBER(38,0)

From the value for Net_Ext_System_ID field of the Net_Ext_Systems table (should always be 1)

NET_LRM_ID

NUMBER(38,0)

This comes from the Net_LRM_ID field of the Setup_Loc_Ref table for LRMs where Is_Basic_Loc_Ref is 0.

NET_LRM_LOCATION

VARCHAR2(100 CHAR)

The name(s) of the alt LRM route. The route name fields are laid out in the Setup_Loc_Ref_Column table. They are listed in the Column_ID field where Loc_Ref_ID matches the LRM in question from the Setup_Loc_Ref table and the value of Loc_Ref_Column_Type_ID is 1. If multiple fields are used, they should be concatenated with "*;" as the delimeter. The order of the fields in the concatenation is determined by the Net_Order_ID field in the Setup_Loc_Ref_Column table.

NET_LRM_OFFSET_FROM

NUMBER(22,3)

The measure on the alt LRM route at the start of the segment to 3 decimal places.

NET_LRM_OFFSET_TO

NUMBER(22,3)

The measure on the alt LRM route at the end of the segment to 3 decimal places.

NET_ROUTE_NAME

VARCHAR2(100 CHAR)

This is the route name based on the base LRM

NET_OFFSET_FROM

NUMBER(22,3)

The measure on the base LRM route at the start of the segment to 3 decimal places.

NET_OFFSET_TO

NUMBER(22,3)

The measure on the base LRM route at the end of the segment to 3 decimal places.

ERROR_TEXT

VARCHAR2(4000 CHAR)

Null

NET_EXT_LOCATIONS_U_OUT

This table contains Events that were modified due to an LRS edit. Deletions are in a separate table. Events that were neither modified nor deleted should not be included. It contains at least one record for each modified event. It should contain 1 record for each piece of a split event.
Because this buffer table is only used during LRS update (usually through an LRS interface). When the LRS is being initially populated, then this buffer table should be empty. Therefore, no standard import is configured on this table out of the box.

Data Structure:

Field

Data Type

Description

NET_EXT_SYSTEM_ID

NUMBER(38,0)

From the value for Net_Ext_System_ID field of the Net_Ext_Systems table (should always be 1)

LOC_IDENT

VARCHAR2(100 CHAR)

This is the unique identifier for the Event. It comes from Setup_Loc_Ident.

SUB_LOC_IDENT

NUMBER(38,0)

For all point events the value will be 1. For linear events that don't split the value will also be 1. For linear events that do split each piece will have a separate record in this table. The values for this field for those records will range from 1 to n for each of the n pieces that the event is split into. Any other attributes associated with the location will follow the Split rule defined in Section 2.2. [Note: the order that these values are assigned does not matter. They just need to be unique within records that have the same value of loc_ident.]

NET_ROUTE_NAME

VARCHAR2(100 CHAR)

This is the route name for the event based on the base LRM

LANE_DIR

NUMBER(38,0)

This is a code list value for the carriageway designation. Just copy over what was in the input event table.

LANE_ID

NUMBER(38,0)

This is a code list value for the lane designation. Just copy over what was in the input event table.

NET_OFFSET_FROM

NUMBER(22,3)

The measure at the start of the event to 3 decimal places based on the base LRM.

NET_OFFSET_TO

NUMBER(22,3)

The measure at the end of the event to 3 decimal places based on the base LRM. For point events it is the same value as in NET_OFFSET_FROM.

ERROR_TEXT

VARCHAR2(4000 CHAR)

Null (used by LRS Gateway and the Roads & Highways Interface)

NET_LRS_TRANSACTION_ID

NUMBER(38,0)

Null (used only with Network Manager)

DATE_EFFECTIVE

DATE

This is the real-world date associated with the LRS edit that caused the Event to be updated.

MOD_STATUS

VARCHAR2(2 BYTE)

The value of this field is always either U or D. Most records will have the value of U. Events that are split in such a way that a piece of the event is deleted will have a value of D on the piece that is deleted. Example: An original event that went from 1 to 10 is on a route where a section was deleted from 6 to 10. For this we should have 2 records in this table. One that goes from 0 to 6 and has a Mod_Status value of U and another that goes from 6 to 10 that has a Mod_Status value of D.

NET_EXT_LOCATIONS_D_OUT

This table contains Events that were deleted due to an LRS edit. It contains one record for each completely deleted event. Partially deleted events are handled via the NET_EXT_LOCATIONS_U_OUT table.

Because this buffer table is only used during LRS update (usually through an LRS interface). When the LRS is being initially populated, then this buffer table should be empty. Therefore, no standard import is configured on this table out of the box.

Data Structure:

Field

Data Type

Description

NET_EXT_SYSTEM_ID

NUMBER(38,0)

From the value for Net_Ext_System_ID field of the Net_Ext_Systems table (should always be 1)

LOC_IDENT

VARCHAR2(100 CHAR)

This is the unique identifier for the Event. It will be one of the fields in the table of events that AgileAsssets will need to supply to you as input.

DATE_EFFECTIVE

DATE

This is the real-world date associated with the LRS edit that caused the Event to be deleted.

Because this buffer table is only used when there is LRS update (usually through an LRS interface), no standard import is configured on this table out of the box.

  • No labels