Description: GIS representation of the UDOT Route System (main routes, ramps and collectors). Routes are represented as PolylineM features where the m coordinate is in miles. PolylineMs have been calibrated at end points and also some intermediate points as described in the UDOT linear referencing system (LRS) route descriptions for state route junctions, interstate bridge deck (begin and end) and other miscellaneous features.Updated: April 13, 2016
Description: GIS representation of the UDOT Route System (main routes, ramps and collectors). Routes are represented as PolylineM features where the m coordinate is in miles. PolylineMs have been calibrated at end points and also some intermediate points as described in the UDOT linear referencing system (LRS) route descriptions for state route junctions, interstate bridge deck (begin and end) and other miscellaneous features.Updated: April 13, 2016
Description: GIS representation of the UDOT Route System (main routes, ramps and collectors). Routes are represented as PolylineM features where the m coordinate is in miles. PolylineMs have been calibrated at end points and also some intermediate points as described in the UDOT linear referencing system (LRS) route descriptions for state route junctions, interstate bridge deck (begin and end) and other miscellaneous features.Updated: April 13, 2016
Description: GIS representation of the UDOT Route System (main routes, ramps and collectors). Routes are represented as PolylineM features where the m coordinate is in miles. PolylineMs have been calibrated at end points and also some intermediate points as described in the UDOT linear referencing system (LRS) route descriptions for state route junctions, interstate bridge deck (begin and end) and other miscellaneous features.Updated: April 13, 2016
Description: Boundaries.Counties is a multi-purpose statewide dataset of county boundaries for cartography and approximate boundary identification. Includes July 2012 major update of Millard and Juab counties. The county boundaries dataset has also been adjusted to the updated Geographic Coordinate Database from BLM (CadSNDIv2, June, 2014). Boundaries.Counties boundaries are maintained by AGRC with the help of many state, county, and local entities. Changes and updates are through certification by the Lt. Governor’s Office sent in by County Recorders office. Data developed with coordinate geometry (COGO) from original legal descriptions in the Utah State Code (17-50-201 (Repealed 1/1/03)). When necessary the data was adjusted to conform to known physical features and updated surveys submitted to Lt. Governor’s Office. This dataset does not represent exact legal boundaries, but, rather a set of boundaries used for the administrative purposes that conforms to logical and administrative rules. Update done T12N R2W Sc 23 Box Elder & Cache Counties April 3, 2017.
Description: Boundaries.Counties is a multi-purpose statewide dataset of county boundaries for cartography and approximate boundary identification. Includes July 2012 major update of Millard and Juab counties. The county boundaries dataset has also been adjusted to the updated Geographic Coordinate Database from BLM (CadSNDIv2, June, 2014). Boundaries.Counties boundaries are maintained by AGRC with the help of many state, county, and local entities. Changes and updates are through certification by the Lt. Governor’s Office sent in by County Recorders office. Data developed with coordinate geometry (COGO) from original legal descriptions in the Utah State Code (17-50-201 (Repealed 1/1/03)). When necessary the data was adjusted to conform to known physical features and updated surveys submitted to Lt. Governor’s Office. This dataset does not represent exact legal boundaries, but, rather a set of boundaries used for the administrative purposes that conforms to logical and administrative rules. Update done T12N R2W Sc 23 Box Elder & Cache Counties April 3, 2017.
Description: Boundaries.Counties is a multi-purpose statewide dataset of county boundaries for cartography and approximate boundary identification. Includes July 2012 major update of Millard and Juab counties. The county boundaries dataset has also been adjusted to the updated Geographic Coordinate Database from BLM (CadSNDIv2, June, 2014). Boundaries.Counties boundaries are maintained by AGRC with the help of many state, county, and local entities. Changes and updates are through certification by the Lt. Governor’s Office sent in by County Recorders office. Data developed with coordinate geometry (COGO) from original legal descriptions in the Utah State Code (17-50-201 (Repealed 1/1/03)). When necessary the data was adjusted to conform to known physical features and updated surveys submitted to Lt. Governor’s Office. This dataset does not represent exact legal boundaries, but, rather a set of boundaries used for the administrative purposes that conforms to logical and administrative rules. Update done T12N R2W Sc 23 Box Elder & Cache Counties April 3, 2017.
XMin: NaN
YMin: NaN
XMax: NaN
YMax: NaN
Spatial Reference: PROJCS["PG-881",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",640826.69833225],PARAMETER["False_Northing",281653.39566425],PARAMETER["Central_Meridian",-111.5],PARAMETER["Standard_Parallel_1",40.716667],PARAMETER["Standard_Parallel_2",41.783333],PARAMETER["Scale_Factor",1.0002499556],PARAMETER["Latitude_Of_Origin",40.3333333333333],UNIT["Foot_US",0.3048006096012192]]
Description: "Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.Last Update: Dec., 2016