LRS Core Data Elements
Routes
Routes are typically unbroken geometries. In our example to the right, 16th street will be unbroken from beginning to end. The only exception would be if there is real-world interruption, like a park or a lake or something similar to that.
| FIELD | DESCRIPTION | DATA TYPE | EXAMPLE |
|---|---|---|---|
| FROMDATE | Active/start date of a route record | Date | 9/1/2018 |
| TODATE | Retired date of a route record | Date | 9/1/2018 |
| ROUTEID* | Unique ID of a route (a linear LRS feature) | Text | 11001402 |
| ROUTENAME+ | Name of a route in the LRS. Concatenated from StreetName + StreetType + Quadrant | Text | 14th ST NW |
| STREETNAME | Street name of this route (if RoadType = Street or Alley) | Text | 14th |
| STREETTYPE | Street type of this route (if RoadType = Street) | Text | ST |
| QUADRANT | Quadrant of this route segment (if RoadType = Street or Alley) | Short integer | NW |
| ROADTYPE | Type of roadway (see domain lookup table) | Short Integer | 1 (Street) |
* Indicates a Key ID
+ Indicates a Calculated Field
WE ARE NO LONGER MAINTAINING A LISTING OF STREET CODE (STCODE) OR STREET IDS (STREETID)
ROADTYPE codes
| Code | Description |
|---|---|
| 1 | Street |
| 2 | Service Road |
| 3 | Ramp |
| 4 | Alley |
| 5 | Driveway |
| 6 | Trail |
| 7 | Walkways |
How is a RouteID Created?
Our route identifiers are mostly random, 8 or 9 character values which represent the unique route feature within a given quadrant.
First Digit = RoadType Code
1 = Street
2 = Service Road
3 = Ramp
4 = Alley
5 = Driveway
6 = Trail
Second Digit = Quadrant code:
1 – NW
2 – NE
3 – SE
4 – SW
5 - Boundary
- Remaining 6 digits = Script-generated, randomized and unique numbers