Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Last Update: 02/09/2022</SPAN></P><P><SPAN>This trails map layer represents off-road recreational trail features and important road connections that augment Utah’s recreational trail network. This map layer features many of Utah’s recreational trails but is not yet complete. Currently, the trails information primary depicts trails used by hiking and mountain biker users. It began with map data purchased from a private entity (Orbital View, Inc), for which full rights were purchased by the GOED Office of Outdoor Recreation in July 2014. Since the original purchase, subsequent substantive updates have included: 2014 Revisions from National Park service; 2015 additions from Emery County; June 2016 additions from Cache County US Forest Service Geodata Hub (all forests except Sawtooth in NW Box Elder County), and Mountainland Association of Governments (Utah and Wasatch counties). Significant updates were made in 2018 as part of the multimodal project. These included pathways and off-road bike trails in the project area. Additional trails can be submitted to Utah UGRC for inclusion in this map layer.</SPAN></P><P><SPAN>Note: Presently, the planned approach for on street bicycle lanes and routes is to incorporate them in the the statewide roads GIS layer using left and right side attributes. On street bike infrastructure is not expected to be represented in this map layer.</SPAN></P><P><SPAN>More information about this layer can be found here: https://gis.utah.gov/data/recreation/trails/</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>SGID10.LOCATION.Buildings was derived from building footprints generated by Microsoft for all 50 States https://github.com/Microsoft/USBuildingFootprints In some cases the pixel prediction algorithm used by Microsoft identified and created building footprints where no buildings existed. To flag potential errors, building footprints within 750 meters of known populated areas (SGID10.DEMOGRAPHIC.PopBlockAreas2010_Approx) and within 500 meters of an address point (SGID10.LOCATION.AddressPoints) were selected and indentified as being a likely structure, footprints falling outside these areas were identified as possible buildings in the 'TYPE' field. In addition, attributes were added for address, city, county, and zip where possible. </SPAN></P></DIV></DIV></DIV>
Copyright Text: This data is created and licensed by Microsoft under the Open Data Commons Open Database License (ODbL) https://opendatacommons.org/licenses/odbl/. Schema and attributes provided by the AGRC.
Color: [78, 78, 78, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Century Gothic Font Style: normal Font Weight: bold Font Decoration: none
Description: Boundaries.Municipalities is a multi-purpose statewide dataset of municipal boundaries for cartography and approximate boundary identification. Boundaries.Municipalities 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 City and County Recorders offices. Boundary updates are occasionally accepted from local GIS departments when older (pre 2007) relevant boundary change information was not received through required channels. All features are adjusted to the current Geographic Coordinate Database (GCDB) points. Data developed with coordinate geometry (COGO) from legal descriptions were used. When necessary the data was adjusted to conform to known physical features. 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 (e.g. no two cities or redevelopment areas may cover the same geographic extent). Data is current thru July 1,2018.
Color: [52, 52, 52, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Myriad Pro Cond Font Style: normal Font Weight: normal Font Decoration: none
Description: The statewide roads dataset is maintained by AGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. AGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. AGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is AGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/
ONEWAY
(
type: esriFieldTypeString, alias: ONEWAY, length: 1
, Coded Values:
[0: 0 Two way]
, [1: 1 One way Direction of Arc]
, [2: 2 One way Opposite Direction of Arc]
)
DOT_CLASS
(
type: esriFieldTypeString, alias: DOTRoadFundingClass, length: 1
, Coded Values:
[A: Class A - State ]
, [B: Class B - County ]
, [C: Class C - Municipality]
, ...3 more...
)
Description: The statewide roads dataset is maintained by AGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. AGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. AGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is AGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/
ONEWAY
(
type: esriFieldTypeString, alias: ONEWAY, length: 1
, Coded Values:
[0: 0 Two way]
, [1: 1 One way Direction of Arc]
, [2: 2 One way Opposite Direction of Arc]
)
DOT_CLASS
(
type: esriFieldTypeString, alias: DOTRoadFundingClass, length: 1
, Coded Values:
[A: Class A - State ]
, [B: Class B - County ]
, [C: Class C - Municipality]
, ...3 more...
)
Description: The statewide roads dataset is maintained by AGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. AGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. AGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is AGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/
ONEWAY
(
type: esriFieldTypeString, alias: ONEWAY, length: 1
, Coded Values:
[0: 0 Two way]
, [1: 1 One way Direction of Arc]
, [2: 2 One way Opposite Direction of Arc]
)
DOT_CLASS
(
type: esriFieldTypeString, alias: DOTRoadFundingClass, length: 1
, Coded Values:
[A: Class A - State ]
, [B: Class B - County ]
, [C: Class C - Municipality]
, ...3 more...
)
Description: The statewide roads dataset is maintained by AGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. AGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. AGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is AGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/
ONEWAY
(
type: esriFieldTypeString, alias: ONEWAY, length: 1
, Coded Values:
[0: 0 Two way]
, [1: 1 One way Direction of Arc]
, [2: 2 One way Opposite Direction of Arc]
)
DOT_CLASS
(
type: esriFieldTypeString, alias: DOTRoadFundingClass, length: 1
, Coded Values:
[A: Class A - State ]
, [B: Class B - County ]
, [C: Class C - Municipality]
, ...3 more...
)
Description: The statewide roads dataset is maintained by AGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. AGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. AGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is AGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/
ONEWAY
(
type: esriFieldTypeString, alias: ONEWAY, length: 1
, Coded Values:
[0: 0 Two way]
, [1: 1 One way Direction of Arc]
, [2: 2 One way Opposite Direction of Arc]
)
DOT_CLASS
(
type: esriFieldTypeString, alias: DOTRoadFundingClass, length: 1
, Coded Values:
[A: Class A - State ]
, [B: Class B - County ]
, [C: Class C - Municipality]
, ...3 more...
)
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The most comprehensive wetland classification system for the state of Utah is the National Wetland Inventory (NWI). While the NWI is the most complete and accessible classification system, the 366 unique wetland type identifiers in the state are often difficult to interpret and have little relevance to natural resource managers. Consequently, NWI data are often overlooked as a viable wetland spatial data source, which often restricts opportunity for interagency cooperation as agencies develop their own wetland GIS datasets and workflows. Agencies benefitted from a simplified functional reclassification of NWI data provided by the Utah Geological Survey in 2014 to the AGRC for distribution to the public. In the subsequent two years, legacy data was added, NWI revised the database schema, and areas were remapped to current conditions and mapping standards. The Utah Geological Survey (UGS) reclassified the2016 version in an effort to provide GIS data users with the most current data with a universal schema across the state. The reclassification scheme was based on the hydrogeomorphic (HGM) approach, modified from the 2014 reclassification and focused largely on landscape position (geomorphology), hydrodynamic, and ecologic characteristics.</SPAN></P></DIV></DIV></DIV>
Copyright Text: Emerson and Sempler, 2017, Utah Wetland Functional Classification: Version 1, Utah Geological Survey