19 datasets found
  1. a

    Municipal Boundaries

    • gisdata-slco.opendata.arcgis.com
    • opendata.utah.gov
    • +1more
    Updated Jan 7, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Salt Lake County (2017). Municipal Boundaries [Dataset]. https://gisdata-slco.opendata.arcgis.com/datasets/municipal-boundaries
    Explore at:
    Dataset updated
    Jan 7, 2017
    Dataset authored and provided by
    Salt Lake County
    Area covered
    Description

    Salt Lake County Municipal Boundaries, including Cities, Metro Townships and Unincorporated areas.Source:Salt Lake County Surveyor's Office

  2. d

    EnviroAtlas - Salt Lake City, UT - EnviroAtlas Community Boundary

    • catalog.data.gov
    Updated Apr 11, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Environmental Protection Agency, Office of Research and Development-Sustainable and Healthy Communities Research Program, EnviroAtlas (Point of Contact) (2025). EnviroAtlas - Salt Lake City, UT - EnviroAtlas Community Boundary [Dataset]. https://catalog.data.gov/dataset/enviroatlas-salt-lake-city-ut-enviroatlas-community-boundary5
    Explore at:
    Dataset updated
    Apr 11, 2025
    Dataset provided by
    U.S. Environmental Protection Agency, Office of Research and Development-Sustainable and Healthy Communities Research Program, EnviroAtlas (Point of Contact)
    Area covered
    Utah, Salt Lake City
    Description

    This EnviroAtlas dataset shows the Salt Lake City, UT EnviroAtlas community boundary. It represents the outside edge of all the block groups included in the EnviroAtlas Community. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

  3. a

    Utah Municipal Boundaries Cartography

    • hub.arcgis.com
    • opendata.utah.gov
    • +2more
    Updated Dec 31, 2010
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah Automated Geographic Reference Center (AGRC) (2010). Utah Municipal Boundaries Cartography [Dataset]. https://hub.arcgis.com/datasets/utah::utah-municipal-boundaries-cartography/about
    Explore at:
    Dataset updated
    Dec 31, 2010
    Dataset authored and provided by
    Utah Automated Geographic Reference Center (AGRC)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    These data were created for mapping usage, areas have been trimmed to the high water mark of Great Salt Lake and Utah Lake. Creates a clearer visual picture of the municipalities.

    Current thru June 30, 2017

  4. T

    Utah ZIP Code Areas

    • opendata.utah.gov
    csv, xlsx, xml
    Updated Mar 20, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2020). Utah ZIP Code Areas [Dataset]. https://opendata.utah.gov/dataset/Utah-ZIP-Code-Areas/u55x-3pbz
    Explore at:
    csv, xml, xlsxAvailable download formats
    Dataset updated
    Mar 20, 2020
    Area covered
    Utah
    Description

    This dataset represents an ongoing effort to approximate the geographic extents of 5 digit zip codes. The dataset was produced using a combination of methods and is based on several sets of source data. Methods include: 1) using local zip code polygon data obtained from counties and cities contained within these counties; 2) Identifying place locations (city, town, places) from the postal service website and address information system (AIS) and as a last result, building theissen polygons around usps places in unpopulated areas; and 3) editing line work using the 2000 Census TIGER line file's zip code attributes. In addition, AGRC has used the locations of mailing addresses known to be valid to fine tune this dataset.


    Updates:
    • Split the 84095 (South Jordan) zip code along the Bangerter Hwy to create the new zip code 84009 (South Jordan), July 2015
    • The 84747 (Loa) and 84716 (Boulder) zip code boundaries were adjusted to follow the address grid quadrant boundaries, January 2015
    • Improvements were made to 84773 (Teasdale) and 84775 (Torrey), January 2015
    • Improvements were made to the 84321, 84341 (Logan), 84302 (Brigham City), and 84307 (Corinne) zip code boundaries, November 2014
    • Improvements were made to the 84010 (Bountiful) and 84054 (North Salt Lake) zip code boundary, May 2014
    • The 84764 (Bryce Canyon City), 84766 (Tropic), 84718 (Cannonville), and 84759 (Panguitch) zip code boundaries were adjusted to follow the address grid guadrant boundaries, May 2014
    • Minor updates to St. George and Washington zip codes (84770, 84780, 84790), February 2013
    • Minor updates to Salt Lake City zip codes (84112, 84113) and Park City zip codes (84060, 84098), January 2013
    • Minor updates to Salt Lake City zip codes (84101, 84102, 84103, 84104, 84105, 84108, 84111, 84116, 84150), July 2012
    • Minor updates to West Valley City zip codes (84119, 84120), July 2012
    • Taylorsville zip code (84129) Update, July 2011
    • Minor updates July 2014, January 2011; June, November, December 2010

  5. c

    Salt Lake City Geodata - Datasets - CivicData.com

    • civicdata.com
    Updated Aug 28, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). Salt Lake City Geodata - Datasets - CivicData.com [Dataset]. https://civicdata.com/dataset/salt-lake-city-geodata
    Explore at:
    Dataset updated
    Aug 28, 2024
    License

    U.S. Government Workshttps://www.usa.gov/government-works
    License information was derived automatically

    Area covered
    Salt Lake City
    Description

    City Council Boundaries

  6. TIGER/Line Shapefile, 2022, County, Salt Lake County, UT, Topological Faces...

    • catalog.data.gov
    Updated Jan 28, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Spatial Data Collection and Products Branch (Point of Contact) (2024). TIGER/Line Shapefile, 2022, County, Salt Lake County, UT, Topological Faces (Polygons With All Geocodes) [Dataset]. https://catalog.data.gov/dataset/tiger-line-shapefile-2022-county-salt-lake-county-ut-topological-faces-polygons-with-all-geocod
    Explore at:
    Dataset updated
    Jan 28, 2024
    Dataset provided by
    United States Census Bureauhttp://census.gov/
    Area covered
    Salt Lake County, Utah
    Description

    The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

  7. a

    City Councils

    • gis-slcgov.opendata.arcgis.com
    Updated Oct 29, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Salt Lake City (2020). City Councils [Dataset]. https://gis-slcgov.opendata.arcgis.com/datasets/city-councils-1
    Explore at:
    Dataset updated
    Oct 29, 2020
    Dataset authored and provided by
    Salt Lake City
    Area covered
    Description

    This layer depicts boundaries for City Council districts in Salt Lake City, Utah.

  8. u

    Utah Address System Quadrants

    • opendata.gis.utah.gov
    • hub.arcgis.com
    • +1more
    Updated Aug 10, 2016
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah Automated Geographic Reference Center (AGRC) (2016). Utah Address System Quadrants [Dataset]. https://opendata.gis.utah.gov/datasets/utah-address-system-quadrants/api
    Explore at:
    Dataset updated
    Aug 10, 2016
    Dataset authored and provided by
    Utah Automated Geographic Reference Center (AGRC)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    Last update: April 4, 2023Added the Mammoth address system in Juab county. Additional minor edits to account for annexations in Utah (Springville, Lehi) and Box Elder (Willard, Garland) counties, April 2023.Added several address grids in Beaver county (Elk Meadows, Ponderosa, Greenville, Adamsville, Sulphurdale). Made major updates to grids in Utah, Cache, Tooele, and Box Elder Counties. Renamed 'NSL' to 'North Salt Lake' and 'East Carbon City' to 'East Carbon', December 2022. Minor adjustment to quadrants in Bluff.Added Rocky Ridge address grid in northern Juab county, August 2022.Updates were made near Elsinore/Central Valley/Monroe corners due to recent Elsinore annexation and inputs from Sevier County, September 2021.Improvements were made to Brigham City, Millville, Logan, and Providence, February 2016.Improvements were made to the Heber, Hyde Park, Logan, and Woodland address system boundaries; updated the American Fork, Fielding, Payson, and Saratoga Springs address system boundaries to reflect recent annexations, January 2016Improvements were made to the Hyde Park and Logan address system boundary, November 2015Improvements were made to the Hyrum and Logan address system boundary, November 2015Updated the American Fork address system boundary to reflect recent annexations, October 2015Improvements were made to the Brigham City, Fishlake, Fremont, Garland, Loa, Lyman, Mantua, Tremonton, and Willard address system boundaries; updated the Lehi and Santa Clara address system boundaries to reflect recent annexations, August 2015Improvements were made to the Price and Wellington address system boundaries; updated the Lehi and Provo address system boundaries to reflect recent annexations, July 2015Improvements were made to the Layton and HAFB address system boundaries; updated the Provo and Spanish Fork address system boundaries to reflect recent annexations, June 2015Updated address system boundaries to reflect annexations in Lehi, Lewiston, and Snowville, May 2015Improvements were made to the Orderville address system boundary to match the municipal boundary, February 2015Updated address system boundaries to match annexations in American Fork, Farmington, Elk Ridge, Grantsville, Lehi, Mendon, Mount Pleasant, Payson, Provo, Spanish Fork, and Washington, January 2015 Improvements were made to the Elmo and Cleveland address system boundaries, December 2014Improvements were made to the Wellington address system boundaries, July 2014Improvements were made to the NSL (North Salt Lake) and Bountiful address system boundaries, June 2014.Changed address system name East Carbon-Sunnyside to East Carbon City, May 2014Updated address system boundaries to match annexations in northern Utah County; misc improvements in Davis County; adjusted Laketown/Garden City boundary, April 2014Merged East Carbon and Sunnyside to create the East Carbon-Sunnyside address system, February 2014.Improvements were made to the Iron County address system quadrant boundaries and topological errors were corrected statewide, January 2014. Improvements were made to Garfield County and Washington County address system quadrant boundaries, August 2013.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/location/address-data/

  9. n

    National GACC Boundaries - Dataset - CKAN

    • nationaldataplatform.org
    Updated Feb 28, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). National GACC Boundaries - Dataset - CKAN [Dataset]. https://nationaldataplatform.org/catalog/dataset/national-gacc-boundaries1
    Explore at:
    Dataset updated
    Feb 28, 2024
    Description

    The physical location of an interagency, regional operation center for the effective coordination, mobilization and demobilization of emergency management resources. A coordination center serves federal, state and local wildland fire agencies through logistical coordination of resources throughout the geographic area, and with other geographic areas, as well. Listings of geographic coordination centers and their respective geographic coordinating areas can be found within the National Interagency Mobilization Guide.9/6/2022 - 9/26/2022 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southern California and Great Basin in the state of Nevada, specifically between Queen Valley and Mono Valley, . The team making the changes are led by James Tomaselli, Gina Dingman, and Ian Mills. Changes proposed will be put into effect for the 2023 calendar year, and will also impact alignments of Initial Attack Frequency Zones and Dispatch boundaries in the area described. Initial edits provided by Daniel Yarborough. Final edits by JKuenzi, USFS. A description of the change is as follows: The northwest end of changes start approximately 1 mile west of Mt Olsen and approximately 0.5 mile south of the Virginia Lakes area.Head northwest passing on the northeast side of Red Lake and the south side of Big Virginia Lake to follow HWY 395 North east to CA 270.East through Bodie to the CA/NV state line.Follows the CA/NV State Line south to HWY CA 167/NV 359.East on NV359 to where the HWY intersects the corner of FS/BLM land.Follows the FS/BLM boundary to the east and then south where it ties into the current GACC boundary. 1/3/2022 - Tabular changes in accordance with data shown in WFMI (Wildland Fire Management Information) Application. Edits by JKuenzi, USFS. GACCLocation Field for Alaska Interagency Coordination Center modified from "Fairbanks, AK" to "Fairbanks, AK (Fort Wainwright,AK)".GACCLocation Field for Great Basin Coordination Center changed from "Boise, ID" to "Salt Lake City, UT". 3/24/2021 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southwestern and Southern GACCs proposed and implemented. The interagency team making the change are led by Kenan Jaycox, Calvin Miller, and Dana (Nancy) Ellsworth, but also include: Elliott Herrera, David Sosa, Tiffany Fralie, Chris Adamcik, Jonathan Nash, Tammy Milton, Juan Ortiz, Cathy Peterson, and Kim Albracht, among others. Portions of Texas, formerly under Southwestern GACC direction were moved to the Southern GACC with a few exceptions that will remain part of the Southwestern GACC, including:Kiowa/Rita Blanca National Grasslands. Black Kettle National Grasslands, including Lake Martin, and Lake McClellan. Guadalupe Mountains National Park. Fort Bliss Military Reservation and McGregor Range. All changes proposed for implementation starting 1/10/2022. Current changes to be released in January 2022. Edits by JKuenzi, USFS. See also data sets for Dispatch Areas, and Initial Attack Frequency Zones Federal for related changes.

  10. a

    Boundary

    • azgeo-open-data-agic.hub.arcgis.com
    Updated Sep 17, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    AZGeo ArcGIS Online (AGO) (2025). Boundary [Dataset]. https://azgeo-open-data-agic.hub.arcgis.com/datasets/azgeo::boundary
    Explore at:
    Dataset updated
    Sep 17, 2025
    Dataset authored and provided by
    AZGeo ArcGIS Online (AGO)
    Area covered
    Description

    The National Agriculture Imagery Program (NAIP) is a federal program which acquires aerial imagery during the agricultural growing seasons in the continental U.S. A primary goal of the NAIP program is to make digital ortho photography available to governmental agencies and the public within a year of acquisition. NAIP projects are contracted each year based upon available funding and the FSA imagery acquisition cycle. Beginning in 2003, NAIP was acquired on a 5-year cycle. 2008 was a transition year, and a three-year cycle began in 2009. Use the following link for an interactive status map of NAIP acquisitions from 2002 - 2023: https://www.fsa.usda.gov/programs-and-services/aerial-photography/imagery-programs/naip-imagery/NAIP is administered by the USDA's Farm Service Agency (FSA) through the Aerial Photography Field Office in Salt Lake City. This "leaf-on" imagery is used as a base layer for GIS programs in FSA's County Service Centers, and is used to maintain the Common Land Unit (CLU) boundaries.

  11. T

    Utah Address System Quadrants

    • opendata.utah.gov
    csv, xlsx, xml
    Updated Mar 20, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2020). Utah Address System Quadrants [Dataset]. https://opendata.utah.gov/dataset/Utah-Address-System-Quadrants/2vp2-yxpf
    Explore at:
    csv, xlsx, xmlAvailable download formats
    Dataset updated
    Mar 20, 2020
    Area covered
    Utah
    Description

    Improvements were made to Brigham City, Millville, Logan, and Providence, February 2016.Improvements were made to the Heber, Hyde Park, Logan, and Woodland address system boundaries; updated the American Fork, Fielding, Payson, and Saratoga Springs address system boundaries to reflect recent annexations, January 2016Improvements were made to the Hyde Park and Logan address system boundary, November 2015Improvements were made to the Hyrum and Logan address system boundary, November 2015Updated the American Fork address system boundary to reflect recent annexations, October 2015Improvements were made to the Brigham City, Fishlake, Fremont, Garland, Loa, Lyman, Mantua, Tremonton, and Willard address system boundaries; updated the Lehi and Santa Clara address system boundaries to reflect recent annexations, August 2015Improvements were made to the Price and Wellington address system boundaries; updated the Lehi and Provo address system boundaries to reflect recent annexations, July 2015Improvements were made to the Layton and HAFB address system boundaries; updated the Provo and Spanish Fork address system boundaries to reflect recent annexations, June 2015Updated address system boundaries to reflect annexations in Lehi, Lewiston, and Snowville, May 2015Improvements were made to the Orderville address system boundary to match the municipal boundary, February 2015Updated address system boundaries to match annexations in American Fork, Farmington, Elk Ridge, Grantsville, Lehi, Mendon, Mount Pleasant, Payson, Provo, Spanish Fork, and Washington, January 2015 Improvements were made to the Elmo and Cleveland address system boundaries, December 2014Improvements were made to the Wellington address system boundaries, July 2014Improvements were made to the NSL (North Salt Lake) and Bountiful address system boundaries, June 2014.Changed address system name East Carbon-Sunnyside to East Carbon City, May 2014Updated address system boundaries to match annexations in northern Utah County; misc improvements in Davis County; adjusted Laketown/Garden City boundary, April 2014Merged East Carbon and Sunnyside to create the East Carbon-Sunnyside address system, February 2014.Improvements were made to the Iron County address system quadrant boundaries and topological errors were corrected statewide, January 2014. Improvements were made to Garfield County and Washington County address system quadrant boundaries, August 2013.

  12. g

    EnviroAtlas - Salt Lake City, UT - Proximity to Parks | gimi9.com

    • gimi9.com
    Updated Dec 3, 2013
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2013). EnviroAtlas - Salt Lake City, UT - Proximity to Parks | gimi9.com [Dataset]. https://gimi9.com/dataset/data-gov_enviroatlas-salt-lake-city-ut-proximity-to-parks5
    Explore at:
    Dataset updated
    Dec 3, 2013
    License

    CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
    License information was derived automatically

    Area covered
    Utah, Salt Lake City
    Description

    This EnviroAtlas dataset shows the approximate walking distance from a park entrance at any given location within the EnviroAtlas community boundary. The zones are estimated in 1/4 km intervals up to 1km then in 1km intervals up to 5km. Park entrances were included in this analysis if they were within 5km of the community boundary. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

  13. u

    Population Projections (TAZ) - RTP 2023

    • data.wfrc.utah.gov
    Updated May 17, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Wasatch Front Regional Council (2024). Population Projections (TAZ) - RTP 2023 [Dataset]. https://data.wfrc.utah.gov/datasets/b22aac2dbb994a949665cb3a3fb078c1
    Explore at:
    Dataset updated
    May 17, 2024
    Dataset authored and provided by
    Wasatch Front Regional Council
    Description

    Every four years, the Wasatch Front’s two metropolitan planning organizations (MPOs), Wasatch Front Regional Council (WFRC) and Mountainland Association of Governments (MAG), collaborate to update a set of annual small area -- traffic analysis zone and ‘city area’, see descriptions below) -- population and employment projections for the Salt Lake City-West Valley City (WFRC), Ogden-Layton (WFRC), and Provo-Orem (MAG) urbanized areas.

    These projections are primarily developed for the purpose of informing long-range transportation infrastructure and services planning done as part of the 4 year Regional Transportation Plan update cycle, as well as Utah’s Unified Transportation Plan, 2023-2050. Accordingly, the foundation for these projections is largely data describing existing conditions for a 2019 base year, the first year of the latest RTP process. The projections are included in the official travel models, which are publicly released at the conclusion of the RTP process.

    Projections within the Wasatch Front urban area ( SUBAREAID = 1) were produced with using the Real Estate Market Model as described below. Socioeconomic forecasts produced for Cache MPO (Cache County, SUBAREAID = 2), Dixie MPO (Washington County, SUBAREAID = 3), Summit County (SUBAREAID = 4), and UDOT (other areas of the state, SUBAREAID = 0) all adhere to the University of Utah Gardner Policy Institute's county-level projection controls, but other modeling methods are used to arrive at the TAZ-level forecasts for these areas.

    As these projections may be a valuable input to other analyses, this dataset is made available here as a public service for informational purposes only. It is solely the responsibility of the end user to determine the appropriate use of this dataset for other purposes.

    Wasatch Front Real Estate Market Model (REMM) Projections

    WFRC and MAG have developed a spatial statistical model using the UrbanSim modeling platform to assist in producing these annual projections. This model is called the Real Estate Market Model, or REMM for short. REMM is used for the urban portion of Weber, Davis, Salt Lake, and Utah counties. REMM relies on extensive inputs to simulate future development activity across the greater urbanized region. Key inputs to REMM include:

    Demographic data from the decennial census
    County-level population and employment projections -- used as REMM control totals -- are produced by the University of Utah’s Kem C. Gardner Policy Institute (GPI) funded by the Utah State Legislature
    Current employment locational patterns derived from the Utah Department of Workforce Services
    Land use visioning exercises and feedback, especially in regard to planned urban and local center development, with city and county elected officials and staff
    Current land use and valuation GIS-based parcel data stewarded by County Assessors
    Traffic patterns and transit service from the regional Travel Demand Model that together form the landscape of regional accessibility to workplaces and other destinations
    Calibration of model variables to balance the fit of current conditions and dynamics at the county and regional level
    

    ‘Traffic Analysis Zone’ Projections

    The annual projections are forecasted for each of the Wasatch Front’s 3,546 Traffic Analysis Zone (TAZ) geographic units. TAZ boundaries are set along roads, streams, and other physical features and average about 600 acres (0.94 square miles). TAZ sizes vary, with some TAZs in the densest areas representing only a single city block (25 acres).

    ‘City Area’ Projections

    The TAZ-level output from the model is also available for ‘city areas’ that sum the projections for the TAZ geographies that roughly align with each city’s current boundary. As TAZs do not align perfectly with current city boundaries, the ‘city area’ summaries are not projections specific to a current or future city boundary, but the ‘city area’ summaries may be suitable surrogates or starting points upon which to base city-specific projections.

    Summary Variables in the Datasets

    Annual projection counts are available for the following variables (please read Key Exclusions note below):

    Demographics

    Household Population Count (excludes persons living in group quarters) 
    Household Count (excludes group quarters) 
    

    Employment

    Typical Job Count (includes job types that exhibit typical commuting and other travel/vehicle use patterns)
    Retail Job Count (retail, food service, hotels, etc)
    Office Job Count (office, health care, government, education, etc)
    Industrial Job Count (manufacturing, wholesale, transport, etc)
    Non-Typical Job Count* (includes agriculture, construction, mining, and home-based jobs) This can be calculated by subtracting Typical Job Count from All Employment Count 
    All Employment Count* (all jobs, this sums jobs from typical and non-typical sectors).
    
    • These variables includes REMM’s attempt to estimate construction jobs in areas that experience new and re-development activity. Areas may see short-term fluctuations in Non-Typical and All Employment counts due to the temporary location of construction jobs.

    Key Exclusions from TAZ and ‘City Area’ Projections

    As the primary purpose for the development of these population and employment projections is to model future travel in the region, REMM-based projections do not include population or households that reside in group quarters (prisons, senior centers, dormitories, etc), as residents of these facilities typically have a very low impact on regional travel. USTM-based projections also excludes group quarter populations. Group quarters population estimates are available at the county-level from GPI and at various sub-county geographies from the Census Bureau.

    Statewide Projections

    Population and employment projections for the Wasatch Front area can be combined with those developed by Dixie MPO (St. George area), Cache MPO (Logan area), and the Utah Department of Transportation (for the remainder of the state) into one database for use in the Utah Statewide Travel Model (USTM). While projections for the areas outside of the Wasatch Front use different forecasting methods, they contain the same summary-level population and employment projections making similar TAZ and ‘City Area’ data available statewide. WFRC plans, in the near future, to add additional areas to these projections datasets by including the projections from the USTM model.

  14. a

    Office Jobs Projections (TAZ) - RTP 2019

    • data-wfrc.opendata.arcgis.com
    • data.wfrc.utah.gov
    Updated Apr 17, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Wasatch Front Regional Council (2019). Office Jobs Projections (TAZ) - RTP 2019 [Dataset]. https://data-wfrc.opendata.arcgis.com/items/5c60a8d187cf41ff8fb7fb6e658875da
    Explore at:
    Dataset updated
    Apr 17, 2019
    Dataset authored and provided by
    Wasatch Front Regional Council
    License

    CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
    License information was derived automatically

    Area covered
    Description

    Important Dataset Update 6/24/2020:Summit and Wasatch Counties updated.Important Dataset Update 6/12/2020:MAG area updated.Important Dataset Update 7/15/2019: This dataset now includes projections for all populated statewide traffic analysis zones (TAZs). Projections within the Wasatch Front urban area ( SUBAREAID = 1) were produced with using the Real Estate Market Model as described below. Socioeconomic forecasts produced for Cache MPO (Cache County, SUBAREAID = 2), Dixie MPO (Washington County, SUBAREAID = 3), Summit County (SUBAREAID = 4), and UDOT (other areas of the state, SUBAREAID = 0) all adhere to the University of Utah Gardner Policy Institute's county-level projection controls, but other modeling methods are used to arrive at the TAZ-level forecasts for these areas.As with any dataset that presents projections into the future, it is important to have a full understanding of the data before using it. Before using this data, you are strongly encouraged to read the metadata description below and direct any questions or feedback about this data to analytics@wfrc.org. Every four years, the Wasatch Front’s two metropolitan planning organizations (MPOs), Wasatch Front Regional Council (WFRC) and Mountainland Association of Governments (MAG), collaborate to update a set of annual small area -- traffic analysis zone and ‘city area’, see descriptions below) -- population and employment projections for the Salt Lake City-West Valley City (WFRC), Ogden-Layton (WFRC), and Provo-Orem (MAG) urbanized areas. These projections are primarily developed for the purpose of informing long-range transportation infrastructure and services planning done as part of the 4 year Regional Transportation Plan update cycle, as well as Utah’s Unified Transportation Plan, 2019-2050. Accordingly, the foundation for these projections is largely data describing existing conditions for a 2015 base year, the first year of the latest RTP process. The projections are included in the official travel models, which are publicly released at the conclusion of the RTP process. As these projections may be a valuable input to other analyses, this dataset is made available at http://data.wfrc.org/search?q=projections as a public service for informational purposes only. It is solely the responsibility of the end user to determine the appropriate use of this dataset for other purposes. Wasatch Front Real Estate Market Model (REMM) ProjectionsWFRC and MAG have developed a spatial statistical model using the UrbanSim modeling platform to assist in producing these annual projections. This model is called the Real Estate Market Model, or REMM for short. REMM is used for the urban portion of Weber, Davis, Salt Lake, and Utah counties. REMM relies on extensive inputs to simulate future development activity across the greater urbanized region. Key inputs to REMM include:Demographic data from the decennial census;County-level population and employment projections -- used as REMM control totals -- are produced by the University of Utah’s Kem C. Gardner Policy Institute (GPI) funded by the Utah State Legislature;Current employment locational patterns derived from the Utah Department of Workforce Services; Land use visioning exercises and feedback, especially in regard to planned urban and local center development, with city and county elected officials and staff;Current land use and valuation GIS-based parcel data stewarded by County Assessors;Traffic patterns and transit service from the regional Travel Demand Model that together form the landscape of regional accessibility to workplaces and other destinations; andCalibration of model variables to balance the fit of current conditions and dynamics at the county and regional level.‘Traffic Analysis Zone’ ProjectionsThe annual projections are forecasted for each of the Wasatch Front’s 2,800+ Traffic Analysis Zone (TAZ) geographic units. TAZ boundaries are set along roads, streams, and other physical features and average about 600 acres (0.94 square miles). TAZ sizes vary, with some TAZs in the densest areas representing only a single city block (25 acres). ‘City Area’ ProjectionsThe TAZ-level output from the model is also available for ‘city areas’ that sum the projections for the TAZ geographies that roughly align with each city’s current boundary. As TAZs do not align perfectly with current city boundaries, the ‘city area’ summaries are not projections specific to a current or future city boundary, but the ‘city area’ summaries may be suitable surrogates or starting points upon which to base city-specific projections.Summary Variables in the DatasetsAnnual projection counts are available for the following variables (please read Key Exclusions note below):DemographicsHousehold Population Count (excludes persons living in group quarters)Household Count (excludes group quarters)EmploymentTypical Job Count (includes job types that exhibit typical commuting and other travel/vehicle use patterns)Retail Job Count (retail, food service, hotels, etc)Office Job Count (office, health care, government, education, etc)Industrial Job Count (manufacturing, wholesale, transport, etc)Non-Typical Job Count* (includes agriculture, construction, mining, and home-based jobs) This can be calculated by subtracting Typical Job Count from All Employment Count.All Employment Count* (all jobs, this sums jobs from typical and non-typical sectors).* These variable includes REMM’s attempt to estimate construction jobs in areas that experience new and re-development activity. Areas may see short-term fluctuations in Non-Typical and All Employment counts due to the temporary location of construction jobs.Population and employment projections for the Wasatch Front area can be combined with those developed by Dixie MPO (St. George area), Cache MPO (Logan area), and the Utah Department of Transportation (for the remainder of the state) into one database for use in the Utah Statewide Travel Model (USTM). While projections for the areas outside of the Wasatch Front use different forecasting methods, they contain the same summary-level population and employment projections making similar TAZ and ‘City Area’ data available statewide. WFRC plans, in the near future, to add additional areas to these projections datasets by including the projections from the USTM model.Key Exclusions from TAZ and ‘City Area’ ProjectionsAs the primary purpose for the development of these population and employment projections is to model future travel in the region, REMM-based projections do not include population or households that reside in group quarters (prisons, senior centers, dormitories, etc), as residents of these facilities typically have a very low impact on regional travel. USTM-based projections also excludes group quarter populations. Group quarters population estimates are available at the county-level from GPI and at various sub-county geographies from the Census Bureau.

  15. d

    National Assessment of Oil and Gas Project - Eastern Great Basin Province...

    • catalog.data.gov
    • data.usgs.gov
    • +1more
    Updated Oct 1, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey (2025). National Assessment of Oil and Gas Project - Eastern Great Basin Province (019) Boundary [Dataset]. https://catalog.data.gov/dataset/national-assessment-of-oil-and-gas-project-eastern-great-basin-province-019-boundary
    Explore at:
    Dataset updated
    Oct 1, 2025
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Description

    The USGS Central Region Energy Team assesses oil and gas resources of the United States. The onshore and State water areas of the United States comprise 71 provinces. Within these provinces, Total Petroleum Systems are defined and Assessment Units are defined and assessed. Each of these provinces is defined geologically, and most province boundaries are defined by major geologic changes. The Eastern Great Basin Province is located in western Utah, eastern Nevada, southern Idaho, and the northwest corner of Arizona, encompassing all or parts of Mohave County in Arizona, Power, Bannock, Cassia, Oneida, and Franklin Counties in Idaho, Elko, Eureka, Lander, White Pine, Nye, Lincoln, and Clark Counties in Nevada, and Cache, Box Elder, Weber, Davis, Tooele, Salt Lake, Wasatch, Utah, Juab, Sanpete, Millard, Sevier, Beaver, Piute, Iron, and Washington Counties in Utah. The main population centers within the study area are Henderson and Las Vegas, Nevada.; Provo and Salt Lake City, Utah. The main highways, I-80, U.S. 6 and U.S. 50, generally traverse the area from east to west; I-15 travels northeast/southwest on the eastern portion of Eastern Great Basin from Salt Lake City, Utah to Las Vegas, Nevada. The Sevier River, Humboldt River, and Colorado River and their tributaries drain the area. The province boundary was drawn to include the geologic structures generally considered to be in or bounding the eastern portion of the Great Basin.

  16. Dispatch Boundaries Email 20230412

    • nifc.hub.arcgis.com
    Updated May 4, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Interagency Fire Center (2023). Dispatch Boundaries Email 20230412 [Dataset]. https://nifc.hub.arcgis.com/maps/nifc::dispatch-boundaries-email-20230412
    Explore at:
    Dataset updated
    May 4, 2023
    Dataset authored and provided by
    National Interagency Fire Centerhttps://www.nifc.gov/
    Area covered
    Description

    The physical location covered by an interagency, dispatch center for the effective coordination, mobilization and demobilization of emergency management resources. A dispatch center actively supports incidents within its boundaries and the resources assigned to those incidents.07/28/2025 - Updated email for USIDCIC from SM.FS.idcic@usda.gov to idcic@firenet.gov; edited by JHobson01/23/2025 - Updated email for USCAANCC to firenet email; edited by KJHansen6/27/2023 - Tabular changes only. Edits by JHobson, NPS. For Taos Interagency Dispatch Center, change Email from pdl_r3_Taos_Dispatch_Center@fs.fed.us to nmtdc@firenet.gov. For Santa Fe Interagency Dispatch Center, change Email from nmsfc01dispatch@fs.fed.us to nmsfc@firenet.gov.For Missoula Interagency Dispatch Center, change Email from sm.fs.mtmdc@firenet.gov to mtmdc@firenet.gov.Albuquerque Interagency Dispatch Center, change Email from nmabc01.dispatch@usda.gov to nmabc@firenet.gov. 3/31/2023 - 4/4/2023 - Tabular changes only. DispLocation and GACCUnitID updated using Unit IDx information current as of 4/3/2023. Edits by JKuenzi, USFS. Text changes to table include:For GACCUnitID, change USNWCC to USORNWC.For GACCUnitID, change USUTGBCC to USUTGBC.For USAZPHC, change DispLocation from Phoenix, AZ, to Mesa, AZ.For USORCOC, change DispLocation from Prineville,OR, to Redmond, OR.For USOREIC, change DispLocation from Eugene, OR, to Springfield, OR.For USPRCIC, change DispLocation from Boqueron, PR, to Palmer de Rio, PR.For USUTNUC, change DispLocation from Salt Lake City, UT, to Draper, UT.For USVAVIC, change DispLocation from Roanoke, VA, to Charlottesville, VA.For USWYTDC, change DispLocation from Moose, WY, to Bondurant, WY.3/23/2023-3/24/2023 - Tabular changes only. ContactPhone updated using Unit IDx information current as of 3/24/2023. Text changes per Official Unit IDs list "Unit Idx Name" field supplied by Kara Stringer (Combined Dispatch Centers 03222023.xlsx), co-lead for NWCG Unit ID Committee. Edits by JKuenzi, USFS. Changes include:GACCName from "Southwest Coordination Center" to "Southwest Area Coordination Center"GACCName from "Southern California Geographic Area Coordination Center" to "Southern California Coordination Center"DispUnitID from USCAMRNC to USCAMRCCDispName from "Angeles Emergency Communication Center" to "Angeles Communication Center"DispName from "Bitterroot Interagency Dispatch Center" to "Bitterroot Dispatch Center"DispName from "Blue Mountain Interagency Communication Center" to "Blue Mountains Interagency Dispatch Center"DispName from "Boise Dispatch Center" to "Boise Interagency Dispatch Center"DispName from "Coeur d'Alene Interagency Dispatch Center" to "Coeur d'Alene Dispatch Center"DispName from "Dillon Interagency Dispatch Center" to "Dillon Dispatch Center"DispName from "Florida Interagency Dispatch Center" to "Florida Interagency Coordination Center"DispName from "Fort Belknap Dispatch" to "Fort Belknap Agency Dispatch Center"DispName from "Grass Valley Emergency Comm Center" to 'Grass Valley Interagency Emergency Command Center"DispName from "Great Falls Interagency Dispatch Center" to "Great Falls Dispatch Center"DispName from "Howard Forest Command Center" to "Howard Forest Emergency Command Center"DispName from "Illinois Interagency Dispatch Center" to "Illinois Interagency Coordination Center"DispName from "Kern County Fire Department Emergency Communication Center" to "Kern County Emergency Command Center"DispName from "Las Vegas Interagency Communication Center" to "Las Vegas Interagency Dispatch Center"DispName from "Los Padres Communications Center" to "Los Padres Communication Center"DispName from "Madera-Mariposa-Merced Emergency Command Center" to "Madera-Mariposa-Merced Command Center"DispName from "Mat-Su/Southwest Area Forestry Dispatch" to "Mat-Su/Southwest Area Dispatch"DispName from "Mid-Atlantic Coordination Center" to "Mid-Atlantic Interagency Coordination Center"DispName from "Missouri-Iowa Interagency Fire Center to Missouri-Iowa Interagency Dispatch Center"DispName from "North Dakota Interagency Dispatch Center" to "North Dakota Dispatch Center"DispName from "Owens Valley Interagency Communications Center" to "Owens Valley Interagency Command Center"DispName from "Plumas Emergency Communications Center" to "Plumas Emergency Communication Center"DispName from "Rocky Boy's Dispatch" to "Rocky Boy's Agency Dispatch Center"DispName from "Roseburg Interagency Coordination Center" to "Roseburg Interagency Communication Center"DispName from "San Benito-Monterey Emergency Command Center" to "San Benito Monterey Emergency Command Center"DispName from "Santa Clara Command Center" to "Santa Clara Emergency Command Center'DispName from "South Central Interagency Dispatch Center" to "South Idaho Interagency Dispatch Center"DispName from "Tuolumne Calaveras Command Center" to "Tuolumne Calaveras Emergency Command Center"DispName from "Valdez-Copper River Area Forestry Dispatch" to "Valdez-Copper River Area Dispatch"DispName from 'Woodacre Emergency Command Center" to "Woodacre Headquarters Emergency Command Center"DispName from "Yakima Agency Dispatch Center" to "Yakama Agency Dispatch Center"DispName from "Yreka Interagency Dispatch Center" to "Yreka Interagency Command Center"DispName from "Uinta Basin Interagency Fire Center" to "Uintah Basin Interagency Fire Center"DispName from "Wisconsin Interagency Dispatch Center (federal) /Wisconsin State Dispatch Center (state)" to "Wisconsin Interagency Dispatch Center"DispName from "Michigan Interagency Dispatch Center (federal) /Michigan State Dispatch Center (state)" to "Michigan Interagency Dispatch Center"DispName from "Fresno-Sierra Emergency Command Center" to "Sierra Interagency Communication Center"DispName from "Perris Emergency Command Center" to "Riverside Emergency Command Center"DispName from "Red Bluff Emergency Command Center" to "Tehama Glenn Emergency Command Center"DispName from "Visalia Emergency Command Center" to "Tulare Emergency Command Center"DispName from "Orville Emergency Command Center" to "Butte Emergency Command Center"DispName from "Saint Helena Emergency Command Center" to "Lake Napa Command Center" 1/11/2023 - Tabular and geospatial changes. USMTBFAC (Blackfeet Reservation) merged into USMTGDC (Great Falls Interagency Dispatch Center). USMTBFAC remains as 4th Tier Dispatch. USMTFHA (Flathead Reservation) merged into USMTMDC (Missoula Interagency Dispatch Center). USMTFHA remains as 4th Tier Dispatch. Changes made by Kat Sorenson, R1 Asst Aircraft Coordinator, and Kara Stringer, IRWIN Business Lead. Edits by JKuenzi.1/10/2023 - Tabular and geospatial changes. Two islands on west edge of John Day Dispatch area (USORJDCC) absorbed into USORCOC Dispatch per direction from Kaleigh Johnson (Asst Ctr Mgr), Jada Altman (Central Oregon Center Mgr), and Jerry Messinger (Air Tactical Group Supervisor). Update made to Dispatch and Initial Attack Frequency Zone boundaries. Edits by JKuenzi,11/08/2022 - Tabular and geospatial changes. Update made to Dispatch and Initial Attack Frequency Zone boundaries between Miles City Interagency Dispatch Center (USMTMCC) and Billings Interagency Dispatch Center (USMTBDC), along Big Horn and Rosebud County line near Little Wolf Mountains, per Kat Sorenson, R1 Asst Aircraft Coordinator, and Kelsey Pluhar, DNRC Asst. Center Manager at Miles City Interagency Dispatch Center. Area in Big Horn County is dispatched by MTMCC. Edits by JKuenzi,09/06/2022-09/26/2022 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southern California and Great Basin in the state of Nevada. Boundary modified between CAOVCC (Owens Valley Interagency Communications Center) and NVSFC (Sierra Front Interagency Dispatch Center), specifically between Queen Valley and Mono Valley. The team making the change is made up of Southern Calif (JTomaselli) and Great Basin (GDingman) GACCs, with input from Ian Mills and Lance Rosen (BLM). Changes proposed will be put into effect for the 2023 calendar year, and will also impact alignments of Initial Attack Frequency Zone boundaries and GACC boundaries in the area described. Initial edits provided by Ian Mills and Daniel Yarborough. Final edits by JKuenzi, USFS.A description of the change is as follows: The northwest end of changes start approximately 1 mile west of Mt Olsen and approximately 0.5 mile south of the Virginia Lakes area. Head northwest passing on the northeast side of Red Lake and the south side of Big Virginia Lake to follow HWY 395 North east to CA 270. East through Bodie to the CA/NV state line. Follows the CA/NV State Line south to HWY CA 167/NV 359. East on NV359 to where the HWY intersects the corner of FS/BLM land. Follows the FS/BLM boundary to the east and then south where it ties into the current GACC boundary.09/22/2022 - Tabular changes only. The DispLocation value of "Prineville, OR", was updated to "Redmond, OR", and the ContactPhone value was updated for Central Oregon Interagency Dispatch Ctr (USORCOC) per direction from Desraye Assali, Supervisory GIS Specialist in Region 6. The original correction had been made 9/30/2020, in the National Dispatch Office Location dataset, but had been missed in the National Dispatch Boundary dataset. Edits by JKuenzi, USFS.09/07/2022 - 09/08/2022 - Tabular and geospatial changes. Multiple boundaries modified in Northern Rockies GACC to bring lines closer in accordance with State boundaries. Information provided by Don Copple, State Fire Planning & Intelligence Program Manager for Montana Dept of Natural Resources & Conservation (DNRC), Kathy Pipkin, Northern Rockies GACC Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi, USFS. The following changes were made:Boundary changes made to the following: Bitterroot Interagency Dispatch Ctr (USMTBDC), Dillon Interagency Dispatch Ctr (USMTDDC), Flathead Dispatch (USMTFHA), Great Falls Interagency Dispatch Ctr

  17. n

    Data from: National Agriculture Imagery Program (NAIP)

    • cmr.earthdata.nasa.gov
    • data.nasa.gov
    • +2more
    Updated Jan 29, 2016
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2016). National Agriculture Imagery Program (NAIP) [Dataset]. https://cmr.earthdata.nasa.gov/search/concepts/C1220567672-USGS_LTA.html
    Explore at:
    Dataset updated
    Jan 29, 2016
    Time period covered
    Jan 1, 1970 - Present
    Area covered
    Earth
    Description

    The National Agriculture Imagery Program (NAIP) acquires aerial imagery during the agricultural growing seasons in the continental U.S. A primary goal of the NAIP program is to make digital ortho photography available to governmental agencies and the public within a year of acquisition.

    NAIP is administered by the USDA's Farm Service Agency (FSA) through the Aerial Photography Field Office in Salt Lake City. This "leaf-on" imagery is used as a base layer for GIS programs in FSA's County Service Centers, and is used to maintain the Common Land Unit (CLU) boundaries.

  18. u

    Office Jobs Projections (City Area) - RTP 2019

    • data.wfrc.utah.gov
    • data-wfrc.opendata.arcgis.com
    Updated Apr 17, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Wasatch Front Regional Council (2019). Office Jobs Projections (City Area) - RTP 2019 [Dataset]. https://data.wfrc.utah.gov/datasets/office-jobs-projections-city-area-rtp-2019
    Explore at:
    Dataset updated
    Apr 17, 2019
    Dataset authored and provided by
    Wasatch Front Regional Council
    License

    CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
    License information was derived automatically

    Area covered
    Description

    Important Dataset Update 6/24/2020:Summit and Wasatch Counties updated.Important Dataset Update 6/12/2020:MAG area updated.Important Dataset Update 7/15/2019: This dataset now includes projections for all populated statewide traffic analysis zones (TAZs). Projections within the Wasatch Front urban area ( SUBAREAID = 1) were produced with using the Real Estate Market Model as described below. Socioeconomic forecasts produced for Cache MPO (Cache County, SUBAREAID = 2), Dixie MPO (Washington County, SUBAREAID = 3), Summit County (SUBAREAID = 4), and UDOT (other areas of the state, SUBAREAID = 0) all adhere to the University of Utah Gardner Policy Institute's county-level projection controls, but other modeling methods are used to arrive at the TAZ-level forecasts for these areas.As with any dataset that presents projections into the future, it is important to have a full understanding of the data before using it. Before using this data, you are strongly encouraged to read the metadata description below and direct any questions or feedback about this data to analytics@wfrc.org. Every four years, the Wasatch Front’s two metropolitan planning organizations (MPOs), Wasatch Front Regional Council (WFRC) and Mountainland Association of Governments (MAG), collaborate to update a set of annual small area -- traffic analysis zone and ‘city area’, see descriptions below) -- population and employment projections for the Salt Lake City-West Valley City (WFRC), Ogden-Layton (WFRC), and Provo-Orem (MAG) urbanized areas. These projections are primarily developed for the purpose of informing long-range transportation infrastructure and services planning done as part of the 4 year Regional Transportation Plan update cycle, as well as Utah’s Unified Transportation Plan, 2019-2050. Accordingly, the foundation for these projections is largely data describing existing conditions for a 2015 base year, the first year of the latest RTP process. The projections are included in the official travel models, which are publicly released at the conclusion of the RTP process. As these projections may be a valuable input to other analyses, this dataset is made available at http://data.wfrc.org/search?q=projections as a public service for informational purposes only. It is solely the responsibility of the end user to determine the appropriate use of this dataset for other purposes. Wasatch Front Real Estate Market Model (REMM) ProjectionsWFRC and MAG have developed a spatial statistical model using the UrbanSim modeling platform to assist in producing these annual projections. This model is called the Real Estate Market Model, or REMM for short. REMM is used for the urban portion of Weber, Davis, Salt Lake, and Utah counties. REMM relies on extensive inputs to simulate future development activity across the greater urbanized region. Key inputs to REMM include:Demographic data from the decennial census;County-level population and employment projections -- used as REMM control totals -- are produced by the University of Utah’s Kem C. Gardner Policy Institute (GPI) funded by the Utah State Legislature;Current employment locational patterns derived from the Utah Department of Workforce Services; Land use visioning exercises and feedback, especially in regard to planned urban and local center development, with city and county elected officials and staff;Current land use and valuation GIS-based parcel data stewarded by County Assessors;Traffic patterns and transit service from the regional Travel Demand Model that together form the landscape of regional accessibility to workplaces and other destinations; andCalibration of model variables to balance the fit of current conditions and dynamics at the county and regional level.‘Traffic Analysis Zone’ ProjectionsThe annual projections are forecasted for each of the Wasatch Front’s 2,800+ Traffic Analysis Zone (TAZ) geographic units. TAZ boundaries are set along roads, streams, and other physical features and average about 600 acres (0.94 square miles). TAZ sizes vary, with some TAZs in the densest areas representing only a single city block (25 acres). ‘City Area’ ProjectionsThe TAZ-level output from the model is also available for ‘city areas’ that sum the projections for the TAZ geographies that roughly align with each city’s current boundary. As TAZs do not align perfectly with current city boundaries, the ‘city area’ summaries are not projections specific to a current or future city boundary, but the ‘city area’ summaries may be suitable surrogates or starting points upon which to base city-specific projections.Summary Variables in the DatasetsAnnual projection counts are available for the following variables (please read Key Exclusions note below):DemographicsHousehold Population Count (excludes persons living in group quarters)Household Count (excludes group quarters)EmploymentTypical Job Count (includes job types that exhibit typical commuting and other travel/vehicle use patterns)Retail Job Count (retail, food service, hotels, etc)Office Job Count (office, health care, government, education, etc)Industrial Job Count (manufacturing, wholesale, transport, etc)Non-Typical Job Count* (includes agriculture, construction, mining, and home-based jobs) This can be calculated by subtracting Typical Job Count from All Employment Count.All Employment Count* (all jobs, this sums jobs from typical and non-typical sectors).* These variable includes REMM’s attempt to estimate construction jobs in areas that experience new and re-development activity. Areas may see short-term fluctuations in Non-Typical and All Employment counts due to the temporary location of construction jobs.Population and employment projections for the Wasatch Front area can be combined with those developed by Dixie MPO (St. George area), Cache MPO (Logan area), and the Utah Department of Transportation (for the remainder of the state) into one database for use in the Utah Statewide Travel Model (USTM). While projections for the areas outside of the Wasatch Front use different forecasting methods, they contain the same summary-level population and employment projections making similar TAZ and ‘City Area’ data available statewide. WFRC plans, in the near future, to add additional areas to these projections datasets by including the projections from the USTM model.Key Exclusions from TAZ and ‘City Area’ ProjectionsAs the primary purpose for the development of these population and employment projections is to model future travel in the region, REMM-based projections do not include population or households that reside in group quarters (prisons, senior centers, dormitories, etc), as residents of these facilities typically have a very low impact on regional travel. USTM-based projections also excludes group quarter populations. Group quarters population estimates are available at the county-level from GPI and at various sub-county geographies from the Census Bureau.

  19. National Geographic Area Coordination Centers (GACC)

    • gis-calema.opendata.arcgis.com
    • hub.arcgis.com
    Updated Jul 22, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    CA Governor's Office of Emergency Services (2023). National Geographic Area Coordination Centers (GACC) [Dataset]. https://gis-calema.opendata.arcgis.com/items/0d6cf94fbcce4808951e3cb360d7462b
    Explore at:
    Dataset updated
    Jul 22, 2023
    Dataset provided by
    California Governor's Office of Emergency Services
    Authors
    CA Governor's Office of Emergency Services
    Area covered
    Description

    The physical location of an interagency, regional operation center for the effective coordination, mobilization and demobilization of emergency management resources. A coordination center serves federal, state and local wildland fire agencies through logistical coordination of resources throughout the geographic area, and with other geographic areas, as well. Listings of geographic coordination centers and their respective geographic coordinating areas can be found within the National Interagency Mobilization Guide.3/23/2023 - Tabular changes only. Name changes per Official Unit IDs list "Unit Idx Name" field supplied by Kara Stringer (Combined Dispatch Centers 03222023.xlsx), co-lead for NWCG Unit ID Committee. Edits by JKuenzi, USFS. Changes include:From "Southwest Coordination Center" to "Southwest Area Coordination Center"From "Southern California Geographic Area Coordination Center" to "Southern California Coordination Center" 9/6/2022 - 9/26/2022 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southern California and Great Basin in the state of Nevada, specifically between Queen Valley and Mono Valley, . The team making the changes are led by James Tomaselli, Gina Dingman, and Ian Mills. Changes proposed will be put into effect for the 2023 calendar year, and will also impact alignments of Initial Attack Frequency Zones and Dispatch boundaries in the area described. Initial edits provided by Daniel Yarborough. Final edits by JKuenzi, USFS. A description of the change is as follows: The northwest end of changes start approximately 1 mile west of Mt Olsen and approximately 0.5 mile south of the Virginia Lakes area.Head northwest passing on the northeast side of Red Lake and the south side of Big Virginia Lake to follow HWY 395 North east to CA 270.East through Bodie to the CA/NV state line.Follows the CA/NV State Line south to HWY CA 167/NV 359.East on NV359 to where the HWY intersects the corner of FS/BLM land.Follows the FS/BLM boundary to the east and then south where it ties into the current GACC boundary. 1/3/2022 - Tabular changes in accordance with data shown in WFMI (Wildland Fire Management Information) Application. Edits by JKuenzi, USFS. GACCLocation Field for Alaska Interagency Coordination Center modified from "Fairbanks, AK" to "Fairbanks, AK (Fort Wainwright,AK)".GACCLocation Field for Great Basin Coordination Center changed from "Boise, ID" to "Salt Lake City, UT". 3/24/2021 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southwestern and Southern GACCs proposed and implemented. The interagency team making the change are led by Kenan Jaycox, Calvin Miller, and Dana (Nancy) Ellsworth, but also include: Elliott Herrera, David Sosa, Tiffany Fralie, Chris Adamcik, Jonathan Nash, Tammy Milton, Juan Ortiz, Cathy Peterson, and Kim Albracht, among others. Portions of Texas, formerly under Southwestern GACC direction were moved to the Southern GACC with a few exceptions that will remain part of the Southwestern GACC, including:Kiowa/Rita Blanca National Grasslands. Black Kettle National Grasslands, including Lake Martin, and Lake McClellan. Guadalupe Mountains National Park. Fort Bliss Military Reservation and McGregor Range. All changes proposed for implementation starting 1/10/2022. Current changes to be released in January 2022. Edits by JKuenzi, USFS. See also data sets for Dispatch Areas, and Initial Attack Frequency Zones Federal for related changes.

  20. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Salt Lake County (2017). Municipal Boundaries [Dataset]. https://gisdata-slco.opendata.arcgis.com/datasets/municipal-boundaries

Municipal Boundaries

Explore at:
2 scholarly articles cite this dataset (View in Google Scholar)
Dataset updated
Jan 7, 2017
Dataset authored and provided by
Salt Lake County
Area covered
Description

Salt Lake County Municipal Boundaries, including Cities, Metro Townships and Unincorporated areas.Source:Salt Lake County Surveyor's Office

Search
Clear search
Close search
Google apps
Main menu