100+ datasets found
  1. Hazardous Fuel Treatment Reduction: Polygon (Feature Layer)

    • catalog.data.gov
    • agdatacommons.nal.usda.gov
    • +5more
    Updated Jun 5, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2025). Hazardous Fuel Treatment Reduction: Polygon (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/hazardous-fuel-treatment-reduction-polygon-feature-layer-9c557
    Explore at:
    Dataset updated
    Jun 5, 2025
    Dataset provided by
    U.S. Department of Agriculture Forest Servicehttp://fs.fed.us/
    Description

    Note: This is a large dataset. To download, go to ArcGIS Open Data Set and click the download button, and under additional resources select the shapefile or geodatabase option. The Forest Service's Natural Resource Manager (NRM) Forest Activity Tracking System (FACTS) is the agency standard for managing information about activities related to fire/fuels, silviculture, and invasive species. FACTS is an activity tracking application for all levels of the Forest Service. The application allows tracking and monitoring of NEPA decisions as well as the ability to create and manage KV trust fund plans at the timber sale level. This application complements its companion NRM applications, which cover the spectrum of living and non-living natural resource information. This layer represents activities of hazardous fuel treatment reduction that are polygons. All accomplishments toward the unified hazardous fuels reduction target must meet the following definition: Vegetative manipulation designed to create and maintain resilient and sustainable landscapes, including burning, mechanical treatments, and/or other methods that reduce the quantity or change the arrangement of living or dead fuel so that the intensity, severity, or effects of wildland fire are reduced within acceptable ecological parameters and consistent with land management plan objectives, or activities that maintain desired fuel conditions. These conditions should be measurable or predictable using fire behavior prediction models or fire effects models. Go to this url for full metadata description: https://data.fs.usda.gov/geodata/edw/edw_resources/meta/S_USA.Activity_HazFuelTrt_PL.xml

  2. d

    GIS Data | Global Geospatial data | Postal/Administrative boundaries |...

    • datarade.ai
    .json, .xml
    Updated Mar 4, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    GeoPostcodes (2025). GIS Data | Global Geospatial data | Postal/Administrative boundaries | Countries, Regions, Cities, Suburbs, and more [Dataset]. https://datarade.ai/data-products/geopostcodes-gis-data-gesopatial-data-postal-administrati-geopostcodes
    Explore at:
    .json, .xmlAvailable download formats
    Dataset updated
    Mar 4, 2025
    Dataset authored and provided by
    GeoPostcodes
    Area covered
    United States
    Description

    Overview

    Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.

    Our self-hosted GIS data cover administrative and postal divisions with up to 6 precision levels: a zip code layer and up to 5 administrative levels. All levels follow a seamless hierarchical structure with no gaps or overlaps.

    The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.

    Use cases for the Global Boundaries Database (GIS data, Geospatial data)

    • In-depth spatial analysis

    • Clustering

    • Geofencing

    • Reverse Geocoding

    • Reporting and Business Intelligence (BI)

    Product Features

    • Coherence and precision at every level

    • Edge-matched polygons

    • High-precision shapes for spatial analysis

    • Fast-loading polygons for reporting and BI

    • Multi-language support

    For additional insights, you can combine the GIS data with:

    • Population data: Historical and future trends

    • UNLOCODE and IATA codes

    • Time zones and Daylight Saving Time (DST)

    Data export methodology

    Our geospatial data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson

    All GIS data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

    Why companies choose our map data

    • Precision at every level

    • Coverage of difficult geographies

    • No gaps, nor overlaps

    Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

  3. d

    Monarch Butterfly Habitat Restoration: Polygon (Feature Layer)

    • catalog.data.gov
    • agdatacommons.nal.usda.gov
    • +6more
    Updated Apr 21, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2025). Monarch Butterfly Habitat Restoration: Polygon (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/monarch-butterfly-habitat-restoration-polygon-feature-layer-90e3c
    Explore at:
    Dataset updated
    Apr 21, 2025
    Dataset provided by
    U.S. Forest Service
    Description

    Activities meeting the Monarch Butterfly Habitat Restoration initiative are a subset of activities that benefit native plants, and in doing so, benefit pollinators. Activities such as thinning, prescribed fire and other methods of fuel removal, treating invasive species and acres of native plantings can benefit Monarchs. Activities are self-reported by Forest Service Units and are reported when completed. This layer does not contain all activities that benefit Monarchs because this is a relatively new requirement for the program. The quality and comprehensiveness of this data will increase over time. Metadata

  4. Integrated Resource Restoration (IRR): Polygon (Feature Layer)

    • catalog.data.gov
    • datasets.ai
    • +7more
    Updated Apr 21, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2025). Integrated Resource Restoration (IRR): Polygon (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/integrated-resource-restoration-irr-polygon-feature-layer-224fd
    Explore at:
    Dataset updated
    Apr 21, 2025
    Dataset provided by
    U.S. Department of Agriculture Forest Servicehttp://fs.fed.us/
    Description

    Depicts the area of activities funded through the NFRR Budget Line Item and reported through the FACTS database. (The activities fall under number of acres treated annually to sustain or restore watershed function: acres of forestlands treated using timber sales, acres of forestland vegetation improved, acres of forestland vegetation established, acres of rangeland vegetation improved, acres treated for noxious weeds/invasive plants on NFS lands, and acres of hazardous fuels treated outside the wildland/urban interface (WUI) to reduce the risk of catastrophic wildland fire) and are self-reported by Forest Service Units. Metadata

  5. California Overlapping Cities and Counties and Identifiers with Coastal...

    • data.ca.gov
    • gis.data.ca.gov
    • +1more
    Updated Feb 20, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Technology (2025). California Overlapping Cities and Counties and Identifiers with Coastal Buffers [Dataset]. https://data.ca.gov/dataset/california-overlapping-cities-and-counties-and-identifiers-with-coastal-buffers
    Explore at:
    kml, gdb, zip, gpkg, xlsx, arcgis geoservices rest api, geojson, csv, txt, htmlAvailable download formats
    Dataset updated
    Feb 20, 2025
    Dataset authored and provided by
    California Department of Technologyhttp://cdt.ca.gov/
    Area covered
    California
    Description

    WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

    • Metadata is missing or incomplete for some layers at this time and will be continuously improved.
    • We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.
    This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.

    Purpose

    County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.

    Related Layers

    This dataset is part of a grouping of many datasets:

    1. Cities: Only the city boundaries and attributes, without any unincorporated areas
    2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
    3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
    4. Place Abbreviations
    5. Unincorporated Areas (Coming Soon)
    6. Census Designated Places (Coming Soon)
    7. Cartographic Coastline
    Working with Coastal Buffers
    The dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.

    Point of Contact

    California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

    Field and Abbreviation Definitions

    • COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
    • Place Name: CDTFA incorporated (city) or county name
    • County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
    • Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
    • GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
    • GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
    • Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
    • CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
    • Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
    • COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
    • GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

    Accuracy

    CDTFA"s source data notes the following about accuracy:

    City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated

  6. MDOT SHA Right-Of-Way (Polygons)

    • data.imap.maryland.gov
    • hub.arcgis.com
    • +1more
    Updated Apr 6, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    ArcGIS Online for Maryland (2022). MDOT SHA Right-Of-Way (Polygons) [Dataset]. https://data.imap.maryland.gov/datasets/mdot-sha-right-of-way-polygons
    Explore at:
    Dataset updated
    Apr 6, 2022
    Dataset provided by
    https://arcgis.com/
    Authors
    ArcGIS Online for Maryland
    Area covered
    Description

    This is a publicly available map image service with limited GIS attributes. A downloadable version of this data is now available through the MDOT GIS Open Data Portal: Download MDOT SHA Right-of-Way Polygons (Open Data Portal) The following related versions of this data are available here:MDOT SHA Right-of-Way (Secured)Line dataFull attribute tableAccessible to only MDOT employees and contractors upon requestMDOT SHA Right-of-Way (Map Image Service)Read-only map serviceLine dataLimited attributes (quality level)Accessible to publicMDOT SHA Right-of-Way data is a composite layer of PSD field-collected survey sources, PSD in-house computations, traced PSD hardcopy materials, and historical Maryland Department of Planning (MDP) parcel boundaries.This data product was intended to replace MDOT SHA Planning Level Right-of-Way (Tax Map Legacy), which is an increasingly obsolete legacy product for MDOT SHA Right-of-Way information that in some areas remains the most comprehensive. For continuity, many MDP parcel boundaries found in MDOT SHA Planning Level Right-of-Way (Tax Map Legacy) have been incorporated into MDOT SHA Right-of-Way data with an "Estimated" quality level. Please see below for a description of the primary attribute.-----------------------------------------------------The polygons in this layer are divided into 318 arbitrary grid zones across the State of Maryland. Updates to the parent ROW boundary line data set [MDOT SHA Right-of-Way (Secured)] are made by grid and reflected in this polygon layer.For more information or to report errors in this data, please contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

  7. m

    Parcel Polygons

    • gis.data.mass.gov
    • opendata.worcesterma.gov
    Updated Jul 26, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Worcester, MA (2024). Parcel Polygons [Dataset]. https://gis.data.mass.gov/datasets/worcesterma::parcel-polygons-1
    Explore at:
    Dataset updated
    Jul 26, 2024
    Dataset authored and provided by
    City of Worcester, MA
    Area covered
    Description

    This polygon layer complies with L3 of the MassGIS Digital Parcel Standard. Parcel editing is completed as needed based on information from the City of Worcester Assessor.More information: Visit the MassGIS Digital Parcel Standard to learn more.Informing Worcester is the City of Worcester's open data portal where interested parties can obtain public information at no cost.

  8. u

    GIS Clipping and Summarization Toolbox

    • data.nkn.uidaho.edu
    • verso.uidaho.edu
    Updated Dec 15, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Justin L. Welty; Michelle I. Jeffries; Robert S. Arkle; David S. Pilliod; Susan K. Kemp (2021). GIS Clipping and Summarization Toolbox [Dataset]. http://doi.org/10.5066/P99X8558
    Explore at:
    zip compressed directory(688 kilobytes)Available download formats
    Dataset updated
    Dec 15, 2021
    Dataset provided by
    USGS Public Project Explorer
    Authors
    Justin L. Welty; Michelle I. Jeffries; Robert S. Arkle; David S. Pilliod; Susan K. Kemp
    License

    https://creativecommons.org/licenses/publicdomain/https://creativecommons.org/licenses/publicdomain/

    https://spdx.org/licenses/CC-PDDChttps://spdx.org/licenses/CC-PDDC

    Description

    Geographic Information System (GIS) analyses are an essential part of natural resource management and research. Calculating and summarizing data within intersecting GIS layers is common practice for analysts and researchers. However, the various tools and steps required to complete this process are slow and tedious, requiring many tools iterating over hundreds, or even thousands of datasets. USGS scientists will combine a series of ArcGIS geoprocessing capabilities with custom scripts to create tools that will calculate, summarize, and organize large amounts of data that can span many temporal and spatial scales with minimal user input. The tools work with polygons, lines, points, and rasters to calculate relevant summary data and combine them into a single output table that can be easily incorporated into statistical analyses. These tools are useful for anyone interested in using an automated script to quickly compile summary information within all areas of interest in a GIS dataset

  9. Continent Polygons

    • figshare.com
    zip
    Updated Jun 24, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Stephanie Shepherd (2020). Continent Polygons [Dataset]. http://doi.org/10.6084/m9.figshare.12555170.v3
    Explore at:
    zipAvailable download formats
    Dataset updated
    Jun 24, 2020
    Dataset provided by
    Figsharehttp://figshare.com/
    figshare
    Authors
    Stephanie Shepherd
    License

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

    Description

    Shapefiles for each conttinent, subset of publicly available shapefile from ESRI.

  10. M

    Metro Regional Parcel Dataset - (Updated Quarterly)

    • gisdata.mn.gov
    ags_mapserver, fgdb +4
    Updated Apr 19, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MetroGIS (2025). Metro Regional Parcel Dataset - (Updated Quarterly) [Dataset]. https://gisdata.mn.gov/dataset/us-mn-state-metrogis-plan-regional-parcels
    Explore at:
    fgdb, gpkg, html, shp, jpeg, ags_mapserverAvailable download formats
    Dataset updated
    Apr 19, 2025
    Dataset provided by
    MetroGIS
    Description

    This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees.

    This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate system from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

    NOTICE: The standard set of attributes changed to the MN Parcel Data Transfer Standard on 1/1/2019.
    https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

    See section 5 of the metadata for an attribute summary.

    Detailed information about the attributes can be found in the Metro Regional Parcel Attributes document.

    The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

    The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

    In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

    This is a MetroGIS Regionally Endorsed dataset.

    Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

    Anoka = http://www.anokacounty.us/315/GIS
    Caver = http://www.co.carver.mn.us/GIS
    Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
    Hennepin = https://gis-hennepin.hub.arcgis.com/pages/open-data
    Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
    Scott = http://opendata.gis.co.scott.mn.us/
    Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

  11. USA Protected from Land Cover Conversion (Mature Support)

    • hub.arcgis.com
    • a-public-data-collection-for-nepa-sandbox.hub.arcgis.com
    Updated Jan 31, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Esri (2017). USA Protected from Land Cover Conversion (Mature Support) [Dataset]. https://hub.arcgis.com/datasets/be68f60ca82944348fb030ca7b028cba
    Explore at:
    Dataset updated
    Jan 31, 2017
    Dataset authored and provided by
    Esrihttp://esri.com/
    Area covered
    Description

    Important Note: This item is in mature support as of June 2024 and will be retired in December 2026. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. Areas protected from conversion include areas that are permanently protected and managed for biodiversity such as Wilderness Areas and National Parks. In addition to protected lands, portions of areas protected from conversion includes multiple-use lands that are subject to extractive uses such as mining, logging, and off-highway vehicle use. These areas are managed to maintain a mostly undeveloped landscape including many areas managed by the Bureau of Land Management and US Forest Service.The Protected Areas Database of the United States classifies lands into four GAP Status classes. This layer displays lands managed for biodiversity conservation (GAP Status 1 and 2) and multiple-use lands (GAP Status 3). Dataset SummaryPhenomenon Mapped: Protected and multiple-use lands (GAP Status 1, 2, and 3)Units: MetersCell Size: 30.92208102 metersSource Type: ThematicPixel Type: 8-bit unsigned integerData Coordinate System: WGS 1984Mosaic Projection: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, the US Virgin Islands, Guam, Northern Mariana Islands and American Samoa.Source: USGS National Gap Analysis Program PAD-US version 3.0Publication Date: July 2022ArcGIS Server URL: https://landscape10.arcgis.com/arcgis/This layer displays protected areas from the Protected Areas Database of the United States version 3.0 created by the USGS National Gap Analysis Program. This layer displays areas managed for biodiversity where natural disturbances are allowed to proceed or are mimicked by management (GAP Status 1), areas managed for biodiversity where natural disturbance is suppressed (GAP Status 2), and multiple-use lands where extract activities are allowed (GAP Status 3). The source data for this layer are available here. A feature layer published from this dataset is also available.The polygon vector layer was converted to raster layers using the Polygon to Raster Tool using the National Elevation Dataset 1 arc second product as a snap raster.The service behind this layer was published with 8 functions allowing the user to select different views of the service. Other layers created from this service using functions include:USA Protected AreasUSA Unprotected AreasUSA Protected Areas - Gap Status 1-4USA Protected Areas - Gap Status 1USA Protected Areas - Gap Status 2USA Protected Areas - Gap Status 3USA Protected Areas - Gap Status 4What can you do with this layer? This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "Protected from Land Cover Conversion" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "Protected from Land Cover Conversion" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

  12. c

    California City Boundaries and Identifiers

    • gis.data.ca.gov
    • data.ca.gov
    • +1more
    Updated Sep 16, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Technology (2024). California City Boundaries and Identifiers [Dataset]. https://gis.data.ca.gov/datasets/california-city-boundaries-and-identifiers
    Explore at:
    Dataset updated
    Sep 16, 2024
    Dataset authored and provided by
    California Department of Technology
    License

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

    Area covered
    Description

    WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCity boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal Buffers (this dataset)Counties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing excludes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCDTFA_CITY: CDTFA incorporated city nameCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections. Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor.CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information.CDTFA's source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San

  13. d

    High-Resolution QuickBird Imagery and Related GIS Layers for Barrow, Alaska,...

    • catalog.data.gov
    • datasets.ai
    • +4more
    Updated Apr 11, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    NSIDC (2025). High-Resolution QuickBird Imagery and Related GIS Layers for Barrow, Alaska, USA, Version 1 [Dataset]. https://catalog.data.gov/dataset/high-resolution-quickbird-imagery-and-related-gis-layers-for-barrow-alaska-usa-version-1
    Explore at:
    Dataset updated
    Apr 11, 2025
    Dataset provided by
    NSIDC
    Area covered
    Utqiagvik, Alaska, United States
    Description

    This data set contains high-resolution QuickBird imagery and geospatial data for the entire Barrow QuickBird image area (156.15° W - 157.07° W, 71.15° N - 71.41° N) and Barrow B4 Quadrangle (156.29° W - 156.89° W, 71.25° N - 71.40° N), for use in Geographic Information Systems (GIS) and remote sensing software. The original QuickBird data sets were acquired by DigitalGlobe from 1 to 2 August 2002, and consist of orthorectified satellite imagery. Federal Geographic Data Committee (FGDC)-compliant metadata for all value-added data sets are provided in text, HTML, and XML formats. Accessory layers include: 1:250,000- and 1:63,360-scale USGS Digital Raster Graphic (DRG) mosaic images (GeoTIFF format); 1:250,000- and 1:63,360-scale USGS quadrangle index maps (ESRI Shapefile format); an index map for the 62 QuickBird tiles (ESRI Shapefile format); and a simple polygon layer of the extent of the Barrow QuickBird image area and the Barrow B4 quadrangle area (ESRI Shapefile format). Unmodified QuickBird data comprise 62 data tiles in Universal Transverse Mercator (UTM) Zone 4 in GeoTIFF format. Standard release files describing the QuickBird data are included, along with the DigitalGlobe license agreement and product handbooks. The baseline geospatial data support education, outreach, and multi-disciplinary research of environmental change in Barrow, which is an area of focused scientific interest. Data are provided on four DVDs. This product is available only to investigators funded specifically from the National Science Foundation (NSF), Office of Polar Programs (OPP), Arctic Sciences Section. An NSF OPP award number must be provided when ordering this data.

  14. NZ Coastlines and Islands Polygons (Topo 1:50k)

    • data.linz.govt.nz
    • geodata.nz
    csv, dwg, geodatabase +6
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Land Information New Zealand, NZ Coastlines and Islands Polygons (Topo 1:50k) [Dataset]. https://data.linz.govt.nz/layer/51153-nz-coastlines-and-islands-polygons-topo-150k/
    Explore at:
    mapinfo mif, mapinfo tab, kml, pdf, geodatabase, csv, dwg, geopackage / sqlite, shapefileAvailable download formats
    Dataset authored and provided by
    Land Information New Zealandhttps://www.linz.govt.nz/
    License

    https://data.linz.govt.nz/license/attribution-4-0-international/https://data.linz.govt.nz/license/attribution-4-0-international/

    Area covered
    New Zealand,
    Description

    This provides a polygon coastline and islands layer which is based on the Topo50 products. It is a combination of the following layers:

    This topographic coastline is the line forming the boundary between the land and sea, defined by mean high water.

    Islands from the NZ Island Polygons layer that lie within the NZ Coastline and Chatham Islands areas (i.e. islands in lakes, rivers and estuaries) have been removed.

    The GIS workflow to create the layer is:

    1. NZ Coastlines were converted from a polyline to a polygon using a polyline to polygon tool.
    2. The resulting coastal polygon was then used as an input into an erase tool and run against the NZ Island Polygon layer to remove all islands lying within the NZ Mainland and Stewart Island.
    3. This was then merged with the NZ Chatham Is island polygons (Topo, 1:50k) that have had the islands within the main island polygon removed, NZ Auckland Is Island Polygons (Topo, 1:50k), NZ Campbell Is / Motu Ihupuku Island, NZ Antipodes Is Island Polygons (Topo, 1:25k), NZ Kermadec Is Island Polygons (Topo, 1:25k), NZ Bounty Is Island Polygons (Topo, 1:25k) and NZ Snares Is / Tini Heke Island Polygons (Topo, 1:25k) layers using a merge tool.

    For more detailed description of each layer refer to the layer urls above.

    APIs and web services This dataset is available via ArcGIS Online and ArcGIS REST services, as well as our standard APIs. LDS APIs and OGC web services ArcGIS Online map services ArcGIS REST API

  15. G

    Surficial Geology of Alberta: Ungeneralized Digital Mosaic (GIS data,...

    • open.canada.ca
    • open.alberta.ca
    • +1more
    html, xml, zip
    Updated Dec 6, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Government of Alberta (2024). Surficial Geology of Alberta: Ungeneralized Digital Mosaic (GIS data, polygon features) [Dataset]. https://open.canada.ca/data/dataset/b4e65c24-a4cb-4abe-8a2b-4fa320082447
    Explore at:
    html, xml, zipAvailable download formats
    Dataset updated
    Dec 6, 2024
    Dataset provided by
    Government of Alberta
    License

    Open Government Licence - Canada 2.0https://open.canada.ca/en/open-government-licence-canada
    License information was derived automatically

    Area covered
    Alberta
    Description

    This GIS dataset is a compilation of existing surficial map information for Alberta tiled into one layer. It was an interim product to produce the generalized polygon dataset (Alberta Geological Survey DIG 2013-0002), which is suitable for presentation and use at 1:1,000,000 scale. We prepared the data by appending existing GIS datasets of each surficial map of Alberta into one provincial layer with a standard attribute table. Data sources included published Alberta Geological Survey and Geological Survey of Canada maps, one master's thesis, and ecological (biophysical) land-classification maps of the mountain parks. When possible, we transferred all of the legend data from each map source into the standard schema. As part of our 1:1,000,000-scale map project, we completed mapping the unmapped areas of Alberta at roughly 500,000 to 1,000,000 scale. This dataset includes those previously unpublished data. With this dataset users can, for the first time, view the surficial geology of different map areas done at different scales and map projections by different geologists according to different legends in one GIS layer. We exported the feature class as an Esri shapefile (SurfMosaic_py_ll.shp) for public distribution. The layer file 1M_scale_legend.lyr is also included for the convenience of Esri software users (version 9.2) to render the map according to the common legend shown on Alberta Geological Survey Map 601.

  16. M

    MetroGIS Regional Parcel Dataset (Year End 2004)

    • gisdata.mn.gov
    • data.wu.ac.at
    ags_mapserver, fgdb +4
    Updated Apr 6, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MetroGIS (2024). MetroGIS Regional Parcel Dataset (Year End 2004) [Dataset]. https://gisdata.mn.gov/dataset/us-mn-state-metrogis-plan-regonal-parcels-2004
    Explore at:
    html, gpkg, shp, fgdb, jpeg, ags_mapserverAvailable download formats
    Dataset updated
    Apr 6, 2024
    Dataset provided by
    MetroGIS
    Description

    This dataset is a compilation of tax parcel polygon and point layers from the seven Twin Cities, Minnesota metropolitan area counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington. The seven counties were assembled into a common coordinate system. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

    This is an annual version of the MetroGIS Regional Parcel Dataset that can be used with other annual versions to do change analysis and time series investigations. This dataset is intended to contain all updates to each county's parcel data through the end of 2004. It was originally published as the 'January 1, 2005' version of the dataset. See the Currentness Reference below and the Entity and Attribute information in Section 5 for more information about the dates for specific aspects of the dataset.

    The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties will polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. The primary example of this is the condominium. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

    The polygon layer is broken into individual county shape files. The points layer is one file for the entire metro area.

    In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

    Polygon and point counts for each county are as follows (based on the January, 2005 dataset):

    Anoka = 124,042 polygons, 124,042 points
    Carver = 32,910 polygons, 32,910 points
    Dakota = 130,989 polygons, 141,444 points
    Hennepin = 353,759 polygons, 399,184 points
    Ramsey = 148,266 polygons, 163,376 points
    Scott = 49,958 polygons, 49,958 points
    Washington = 93,794 polygons, 96,570 points

    This is a MetroGIS Regionally Endorsed dataset.

    Each of the seven Metro Area counties has entered into a multiparty agreement with the Metropolitan Council to assemble and distribute the parcel data for each county as a regional (seven county) parcel dataset.

    A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2004 document.

    Additional information may be available in the individual metadata for each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person listed in the individual county metadata.

    Anoka = http://www.anokacounty.us/315/GIS

    Caver = http://www.co.carver.mn.us/GIS

    Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx

    Hennepin: http://www.hennepin.us/gisopendata

    Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

    Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

    Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

  17. a

    Surface materials of the Calgary urban area (GIS data, polygon features)

    • catalogue.arctic-sdi.org
    Updated Jun 25, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). Surface materials of the Calgary urban area (GIS data, polygon features) [Dataset]. https://catalogue.arctic-sdi.org/geonetwork/srv/search?keyword=DALROY
    Explore at:
    Dataset updated
    Jun 25, 2024
    Area covered
    Calgary
    Description

    This is a GIS dataset containing digitized and attributed polygon features from scanned Alberta Geological Survey Maps 201, 202, 203 and 204. The data show the surficial geology of the Calgary urban area (NTS areas 82O/01, 82P/04, 82J/16 and 82I/13) and are attributed with stratigraphic unit, lithology, lithogenesis, morphology, veneer material and the unit labels as shown on the maps. The data from the four maps are presented in a single polygon layer.

  18. u

    Surface materials of the Calgary urban area - veneer material (GIS data,...

    • data.urbandatacentre.ca
    • beta.data.urbandatacentre.ca
    Updated Oct 1, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). Surface materials of the Calgary urban area - veneer material (GIS data, polygon overlay features) - Catalogue - Canadian Urban Data Catalogue (CUDC) [Dataset]. https://data.urbandatacentre.ca/dataset/gov-canada-4e82e8da-eb71-449b-b2c8-275864bd5bcf
    Explore at:
    Dataset updated
    Oct 1, 2024
    Description

    This is a GIS dataset containing digitized and attributed polygon features from scanned Alberta Geological Survey Maps 201, 202, 203 and 204. The data show the supplemental surficial geology of the Calgary urban area (NTS areas 82O/01, 82P/04, 82J/16 and 82I/13). Polygons, representing a discontinuous layer, are attributed as sand and silt veneer or buried sand, as shown on the maps. The data from the four maps are presented in a single polygon layer.

  19. M

    MetroGIS Regional Parcel Dataset (Year End 2009)

    • gisdata.mn.gov
    • data.wu.ac.at
    ags_mapserver, fgdb +4
    Updated Apr 2, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MetroGIS (2024). MetroGIS Regional Parcel Dataset (Year End 2009) [Dataset]. https://gisdata.mn.gov/dataset/us-mn-state-metrogis-plan-regonal-parcels-2009
    Explore at:
    fgdb, shp, gpkg, jpeg, html, ags_mapserverAvailable download formats
    Dataset updated
    Apr 2, 2024
    Dataset provided by
    MetroGIS
    Description

    This dataset is a compilation of tax parcel polygon and point layers from the seven Twin Cities, Minnesota metropolitan area counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington. The seven counties were assembled into a common coordinate system. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

    The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties will polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. The primary example of this is the condominium. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

    The polygon layer is broken into individual county shape files. The points layer is one file for the entire metro area.

    In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

    Polygon and point counts for each county are as follows (based on the January 2010 dataset unless otherwise noted):

    polygons / points
    Anoka - 129271 / 129271
    Carver - 38205 / 38205
    Dakota - 136067 / 150436
    Hennepin - 424182 / 424182
    Ramsey - 149101 / 168152
    Scott - 55213 / 55213
    Washington - 98933 / 104100 (October 2009)

    This is a MetroGIS Regionally Endorsed dataset.

    Each of the seven Metro Area counties has entered into a multiparty agreement with the Metropolitan Council to assemble and distribute the parcel data for each county as a regional (seven county) parcel dataset.

    A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2009 document.

    Additional information may be available in the individual metadata for each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person listed in the individual county metadata.

    Anoka = http://www.anokacounty.us/315/GIS

    Caver = http://www.co.carver.mn.us/GIS

    Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx

    Hennepin: http://www.hennepin.us/gisopendata

    Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

    Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

    Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

  20. BLM National SMA Surface Management Agency Area Polygons

    • catalog.data.gov
    • datasets.ai
    • +4more
    Updated May 31, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bureau of Land Management (2025). BLM National SMA Surface Management Agency Area Polygons [Dataset]. https://catalog.data.gov/dataset/blm-natl-sma-surface-management-agency-area-polygons-national-geospatial-data-asset-ngda
    Explore at:
    Dataset updated
    May 31, 2025
    Dataset provided by
    Bureau of Land Managementhttp://www.blm.gov/
    Description

    The Surface Management Agency (SMA) Geographic Information System (GIS) dataset depicts Federal land for the United States and classifies this land by its active Federal surface managing agency. The SMA feature class covers the continental United States, Alaska, Hawaii, Puerto Rico, Guam, American Samoa and the Virgin Islands. A Federal SMA agency refers to a Federal agency with administrative jurisdiction over the surface of Federal lands. Jurisdiction over the land is defined when the land is either: Withdrawn by some administrative or legislative action, or Acquired or Exchanged by a Federal Agency. This layer is a dynamic assembly of spatial data layers maintained at various federal and local government offices. The GIS data contained in this dataset represents the polygon features that show the boundaries for Surface Management Agency and the surface extent of each Federal agency’s surface administrative jurisdiction. SMA data depicts current withdrawn areas for a particular agency and (when appropriate) includes land that was acquired or exchanged and is located outside of a withdrawal area for that agency. The SMA data do not illustrate land status ownership pattern boundaries or contain land ownership attribute details. The SMA Withdrawals feature class covers the continental United States, Alaska, Hawaii, Puerto Rico, Guam, American Samoa and the Virgin Islands. A Federal SMA Withdrawal is defined by formal actions that set aside, withhold, or reserve Federal land by statute or administrative order for public purposes. A withdrawal creates a title encumbrance on the land. Withdrawals must accomplish one or more of the following: A. Transfer total or partial jurisdiction of Federal land between Federal agencies. B. Close (segregate) Federal land to operation of all or some of the public land laws and/or mineral laws. C. Dedicate Federal land to a specific public purpose. There are four major categories of formal withdrawals: (1) Administrative, (2) Presidential Proclamations, (3) Congressional, and (4) Federal Power Act (FPA) or Federal Energy Regulatory Commission (FERC) Withdrawals. These SMA Withdrawals will include the present total extent of withdrawn areas rather than all of the individual withdrawal actions that created them over time. A Federal SMA agency refers to a Federal agency with administrative jurisdiction over the surface of Federal lands. Jurisdiction over the land is defined when the land is either: Withdrawn by some administrative or legislative action, or Acquired or Exchanged by a Federal Agency. This layer is a dynamic assembly of spatial data layers maintained at various federal and local government offices. The GIS data contained in this dataset represents the polygon features that show the boundaries for Surface Management Agency and the surface extent of each Federal agency’s surface administrative jurisdiction. SMA data depicts current withdrawn areas for a particular agency and (when appropriate) includes land that was acquired or exchanged and is located outside of a withdrawal area for that agency. The SMA data do not illustrate land status ownership pattern boundaries or contain land ownership attribute details.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
U.S. Forest Service (2025). Hazardous Fuel Treatment Reduction: Polygon (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/hazardous-fuel-treatment-reduction-polygon-feature-layer-9c557
Organization logo

Hazardous Fuel Treatment Reduction: Polygon (Feature Layer)

Explore at:
2 scholarly articles cite this dataset (View in Google Scholar)
Dataset updated
Jun 5, 2025
Dataset provided by
U.S. Department of Agriculture Forest Servicehttp://fs.fed.us/
Description

Note: This is a large dataset. To download, go to ArcGIS Open Data Set and click the download button, and under additional resources select the shapefile or geodatabase option. The Forest Service's Natural Resource Manager (NRM) Forest Activity Tracking System (FACTS) is the agency standard for managing information about activities related to fire/fuels, silviculture, and invasive species. FACTS is an activity tracking application for all levels of the Forest Service. The application allows tracking and monitoring of NEPA decisions as well as the ability to create and manage KV trust fund plans at the timber sale level. This application complements its companion NRM applications, which cover the spectrum of living and non-living natural resource information. This layer represents activities of hazardous fuel treatment reduction that are polygons. All accomplishments toward the unified hazardous fuels reduction target must meet the following definition: Vegetative manipulation designed to create and maintain resilient and sustainable landscapes, including burning, mechanical treatments, and/or other methods that reduce the quantity or change the arrangement of living or dead fuel so that the intensity, severity, or effects of wildland fire are reduced within acceptable ecological parameters and consistent with land management plan objectives, or activities that maintain desired fuel conditions. These conditions should be measurable or predictable using fire behavior prediction models or fire effects models. Go to this url for full metadata description: https://data.fs.usda.gov/geodata/edw/edw_resources/meta/S_USA.Activity_HazFuelTrt_PL.xml

Search
Clear search
Close search
Google apps
Main menu