It is not the intent that all stewards will change theirĬurrent data management process to match this standard, but rather that stewards will evaluate their current This data model is meant to suggest 'best practices'.
The UNIQUE_ID field is static and is UGRC's current, ad hoc solution to a persistent UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then Placename/Area, based on current SGID polygon boundaries. UGRC spatially assigns fields in the section titled Section titled Addressing is primarily maintained by the local stewards, where as the section titledĭOT/FHWA is primarily maintained by UDOT. Model spreadsheet and the corresponding tabs for update notes and coded value domains.
To see specific information about the data model including field names and descriptions, data types, coded valueĭomains, and data model updates, see the data Transportation.Roads utilizes a data model based on Next-Generation 911 standards and the Federal HighwayĪdministration's All Roads Network Of Linear-referenced Data (ARNOLD) reporting requirements for state DOTs. Us know where we have gaps or inaccurate information. Wasatch Front), as well as improvements in the statewide bike data. Recent collaborative efforts between UGRC, UDOT, and WFRC have led to significant enhancements in the bikeĪnd pedestrian data in both the Roads and Trails-and-Pathways layers. This layer also plays an important role in active transportation Linear referencing system (LRS) as well as UGRC's network analysis datasets. Location. This dataset is also used as the base geometry for deriving the GIS-representation of UDOT’s highway Transportation.Roads is a multi-purpose statewide roads dataset for cartography, routing, and range based-address