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.

FIELDDESCRIPTIONDATA TYPEEXAMPLE
FROMDATE

Active/start date of a route record

Date9/1/2018
TODATERetired date of a route recordDate9/1/2018
ROUTEID*Unique ID of a route (a linear LRS feature)Text11001402
ROUTENAME+Name of a route in the LRS. Concatenated from StreetName + StreetType + QuadrantText14th ST NW
STREETNAMEStreet name of this route (if RoadType = Street or Alley)Text14th
STREETTYPEStreet type of this route (if RoadType = Street)TextST
QUADRANTQuadrant of this route segment (if RoadType = Street or Alley)Short integerNW
ROADTYPEType of roadway (see domain lookup table)Short Integer1 (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

CodeDescription
1Street
2Service Road
3Ramp
4Alley
5

Driveway

6Trail
7Walkways



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