To navigate to the Concurrent Locations window, follow the steps below:
- Select System from the top banner menu
- Select LRS/GIS
- Select Linear Network Tools
- Select Geometry
- Select Concurrent Locations
Concurrent Locations are when two or multiple routes share the same roadbed. In the example below, Route 053-SR-0001-00 between Milepoint 5.2 and 14.83, and Route 053-SR-0520-00 between Milepoint 0 and 9.66 share the same roadbed. 
In the window, the system will show the data like this:
Two tables are used to define concurrency in AgileAssets system.
Dominant Location (CONCURRENT_LOCATION_DOM)
This data is displayed at the upper pane at the window. This table stores the set of locations within the network that are dominated by another route. This table lists each dominant location (using their LOC_IDENT values) and its subordinate locations.
This table lists the locations of roadway segments that dominate other route names within the system. For example, if two different routes share the same physical roadbed this table contains the location reference (LOC_IDENT) and unique identifier (DOM_LOCATION_ID) for the primary route location. The primary key of the table is the DOM_LOCATION_ID column (a unique integer linked to the S_CONCURRENT_LOCATION_DOM sequence in the database). Subordinate locations all refer to their appropriate dominant location by this field. The LOC_IDENT column refers to the actual location information associated with each dominant location stored in the SETUP_LOC_IDENT table. The table's structure is shown below.
Column Name | Pk | Null? | Data Type | Comment |
|---|---|---|---|---|
DOM_LOCATION_ID | Y | N | INTEGER | Unique Integer for each location in the network that dominates any other route |
LOC_IDENT | N | INTEGER | The location reference for each dominant location (FK to SETUP_LOC_IDENT) | |
USER_UPDATE | Y | VARCHAR2 (16 Char) | Last User to Edit record | |
DATE_UPDATE | Y | DATE | Last edit date | |
COMMENT_STR | Y | VARCHAR2 (300 Char) | Comments | |
COMMENT_ID | Y | INTEGER | Attachment Record ID |
CONCURRENT_LOCATION_DOM Sample Data
Subordinate Location (CONCURRENT_LOCATION_SUB)
This data is displayed at the upper pane at the window. This table stores the set of locations within the network that are dominated by another route. This table lists each location (LOC_IDENT) and the location that it is dominated by (DOM_LOCATION_ID) which is a foreign key to the CONCURRENT_LOC_DOM table. The structure is shown below.
Column Name | Pk | Null? | Data Type | Comment |
|---|---|---|---|---|
DOM_LOCATION_ID | N | INTEGER | Link to the dominating location | |
LOC_IDENT | N | INTEGER | Location referenced for the subordinate location | |
USER_UPDATE | Y | VARCHAR2 (16 Char) | Last user edit | |
DATE_UPDATE | Y | DATE | Date last edited | |
COMMENT_STR | Y | VARCHAR2 (300 Char) | Comment Text | |
COMMENT_ID | Y | INTEGER | Attachment Record ID | |
SAME_DIRECTION | Y | NUMBER (1) | 1 indicates the subordinate location follows the same direction as the dominant, 0 indicates the directions are reversed |
CONCURRENT_LOCATION_SUB Sample Data
Note: In AgileAssets system, data are never stored on the subordinate locations. Any data entered using a subordinate location will be automatically converted to its corresponding dominant location.
Furthermore, system does not allow an event to cross the boundary on the subordinate location, because it cannot be properly converted to a dominant location.
