100+ datasets found
  1. BLM OR Wilderness Study Area Boundary Line Hub

    • catalog.data.gov
    • datasets.ai
    • +1more
    Updated Nov 20, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bureau of Land Management (2024). BLM OR Wilderness Study Area Boundary Line Hub [Dataset]. https://catalog.data.gov/dataset/blm-or-wilderness-study-area-boundary-line-hub
    Explore at:
    Dataset updated
    Nov 20, 2024
    Dataset provided by
    Bureau of Land Managementhttp://www.blm.gov/
    Description

    WSA_ARC: This data set represents Wilderness Study Area (WSA) boundaries as inventoried in the mid1980's and defined in the October 1991 "Wilderness Study Report". Wilderness Study Areas are essentially roadless areas under BLM jurisdiction. Wilderness Study Areas have special management restrictions and priorities. They are a one-time designation and new WSA or additions to WSA are rare. For a complete description of this data consult the Wilderness Study Areas Spatial Data Standard. http://www.blm.gov/or/datamanagement/index.php

  2. a

    Municipal Service Area Boundaries

    • hub.arcgis.com
    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • +1more
    Updated Jul 18, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Idaho Department of Water Resources (2022). Municipal Service Area Boundaries [Dataset]. https://hub.arcgis.com/documents/be1d6de188e54f89becd69a5f91ee0ba
    Explore at:
    Dataset updated
    Jul 18, 2022
    Dataset authored and provided by
    Idaho Department of Water Resources
    Description

    This data represents the general service area of the place of use for organizations with water rights who qualify as municipalities or municipal providers under I.C. Title 42 or the 1996 Municipal Water Rights Act and who have a municipal water right on file at IDWR. The service area is for illustrative purposes. This data does not necessarily represent the boundary of city limits. Drainage Districts and Tribal boundaries are not represented in this data.This dataset is derived from the following queries of IDWR water right and recommendation databases: Status = Active, LPOU = Yes, And (WaterUse = Municipal or WaterUse = Municipal From Storage). A Large POU (LPOU) is a water right place of use for which the delivery of water is described with a digital boundary as defined by I.C. Section 42-202B(2) and authorized pursuant to I.C. Section 42-1411(2)(h). If a specific owner has multiple rights represented by different PlaceOfUseIDs, the PlaceofUseID representing the largest area is used. If there is significant divergence in location between different PlaceofUseIDs, the shapes are merged and PlaceofUseID of -999 is assigned.

  3. t

    Character Area Boundary

    • open.tempe.gov
    • performance.tempe.gov
    • +7more
    Updated Feb 17, 2022
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Tempe (2022). Character Area Boundary [Dataset]. https://open.tempe.gov/datasets/character-area-boundary/about
    Explore at:
    Dataset updated
    Feb 17, 2022
    Dataset authored and provided by
    City of Tempe
    License

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

    Area covered
    Description

    The Character Area Boundaries layer shows the areas or groups of neighborhoods that contain common design, land use and commercial characteristics distinct from neighboring areas. Similarities in age of housing, styles of architecture, patterns of development, materials, land use or street patterns, lot size, landscaping, landmarks, social magnets, and/or physical barriers form some of the recognizable differences.Contact: Robbie AaronContact E-mailContact Phone: 480-350-8690Link: N/AData Source: ArcGIS ServerData Source Type: GeospatialPreparation Method: N/APublish Frequency: As information changesPublish Method: AutomaticData Dictionary

  4. a

    Participating Area Boundary Current

    • data-soa-dnr.opendata.arcgis.com
    • gis.data.alaska.gov
    • +1more
    Updated Apr 11, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Alaska Department of Natural Resources ArcGIS Online (2024). Participating Area Boundary Current [Dataset]. https://data-soa-dnr.opendata.arcgis.com/datasets/participating-area-boundary-current
    Explore at:
    Dataset updated
    Apr 11, 2024
    Dataset authored and provided by
    Alaska Department of Natural Resources ArcGIS Online
    Area covered
    Description

    This dataset contains participating area boundaries in the state of alaska. A participating area is part of an oil and gas lease unit area approved as being reasonably known to be underlain by hydrocarbons and known or reasonably estimated through use of geological, geophysical, or engineering data to be capable of producing or contributing to production of hydrocarbons in paying quantities.

  5. City and County Boundary Line Changes

    • data.ca.gov
    • catalog.ogopendata.com
    • +4more
    Updated Aug 5, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Tax and Fee Administration (2025). City and County Boundary Line Changes [Dataset]. https://data.ca.gov/dataset/city-and-county-boundary-line-changes
    Explore at:
    arcgis geoservices rest api, htmlAvailable download formats
    Dataset updated
    Aug 5, 2025
    Dataset provided by
    California State Board of Equalizationhttp://www.boe.ca.gov/
    Authors
    California Department of Tax and Fee Administration
    Description

    This map includes change areas for city and county boundaries filed in accordance with Government Code 54900. The initial dataset was first published on October 20, 2021, and was based on the State Board of Equalization's 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 jurisdictions. The boundaries are continuously being revised 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 and should not be used to determine precise city or county boundary line locations.

    The data is updated within 10 business days of the CDTFA receiving a copy of the Board of Equalization's acknowledgement letter.

    BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number (see note*); CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance (see note*); RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES = additional clarifying information about the action.

    *Note: A COFILE number ending in "000" is a boundary correction and the effective date used is the date the map was corrected.

    BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; 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 (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

  6. d

    Study area boundary derived from 1:1,000,000-scale hydrographic areas and...

    • catalog.data.gov
    • data.usgs.gov
    • +1more
    Updated Nov 1, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey (2024). Study area boundary derived from 1:1,000,000-scale hydrographic areas and flow systems for the Great Basin carbonate and alluvial aquifer system of Nevada, Utah, and parts of adjacent states [Dataset]. https://catalog.data.gov/dataset/study-area-boundary-derived-from-1-1000000-scale-hydrographic-areas-and-flow-systems-for-t
    Explore at:
    Dataset updated
    Nov 1, 2024
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Area covered
    Great Basin, Nevada, Utah
    Description

    This dataset contains the amalgamation of the hydrographic area (HA) boundaries and polygons for the GBCAAS study area. The study area consists of 165 HAs based on Great Basin HAs defined by the USGS in 1988 (Harrill and others, 1988; Buto, 2009). This dataset does not contain the HA boundaries or geologic details included in the source dataset. For that information, please see the metadata for the source dataset at https://water.usgs.gov/GIS/metadata/usgswrd/XML/sir2010_5193_ha1000.xml The study area boundary dataset is used by the Office of Groundwater, U.S. Geological Survey, in its hyrogeological framework website.

  7. m

    MassDEP Estimated Public Drinking Water System Service Area Boundaries

    • gis.data.mass.gov
    • geo-massdot.opendata.arcgis.com
    Updated Aug 19, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MassGIS - Bureau of Geographic Information (2024). MassDEP Estimated Public Drinking Water System Service Area Boundaries [Dataset]. https://gis.data.mass.gov/maps/d77c022b9fd946e0831904774aa114e1
    Explore at:
    Dataset updated
    Aug 19, 2024
    Dataset authored and provided by
    MassGIS - Bureau of Geographic Information
    Area covered
    Description

    Terms of UseData Limitations and DisclaimerThe user’s use of and/or reliance on the information contained in the Document shall be at the user’s own risk and expense. MassDEP disclaims any responsibility for any loss or harm that may result to the user of this data or to any other person due to the user’s use of the Document.This is an ongoing data development project. Attempts have been made to contact all PWS systems, but not all have responded with information on their service area. MassDEP will continue to collect and verify this information. Some PWS service areas included in this datalayer have not been verified by the PWS or the municipality involved, but since many of those areas are based on information published online by the municipality, the PWS, or in a publicly available report, they are included in the estimated PWS service area datalayer.Please note: All PWS service area delineations are estimates for broad planning purposes and should only be used as a guide. The data is not appropriate for site-specific or parcel-specific analysis. Not all properties within a PWS service area are necessarily served by the system, and some properties outside the mapped service areas could be served by the PWS – please contact the relevant PWS. Not all service areas have been confirmed by the systems.Please use the following citation to reference these data:MassDEP, Water Utility Resilience Program. 2025. Community and Non-Transient Non-Community Public Water System Service Area (PubV2025_3).IMPORTANT NOTICE: This MassDEP Estimated Water Service datalayer may not be complete, may contain errors, omissions, and other inaccuracies and the data are subject to change. This version is published through MassGIS. We want to learn about the data uses. If you use this dataset, please notify staff in the Water Utility Resilience Program (WURP@mass.gov).This GIS datalayer represents approximate service areas for Public Water Systems (PWS) in Massachusetts. In 2017, as part of its “Enhancing Resilience and Emergency Preparedness of Water Utilities through Improved Mapping” (Critical Infrastructure Mapping Project ), the MassDEP Water Utility Resilience Program (WURP) began to uniformly map drinking water service areas throughout Massachusetts using information collected from various sources. Along with confirming existing public water system (PWS) service area information, the project collected and verified estimated service area delineations for PWSs not previously delineated and will continue to update the information contained in the datalayers. As of the date of publication, WURP has delineated Community (COM) and Non-Transient Non-Community (NTNC) service areas. Transient non-community (TNCs) are not part of this mapping project.Layers and Tables:The MassDEP Estimated Public Water System Service Area data comprises two polygon feature classes and a supporting table. Some data fields are populated from the MassDEP Drinking Water Program’s Water Quality Testing System (WQTS) and Annual Statistical Reports (ASR).The Community Water Service Areas feature class (PWS_WATER_SERVICE_AREA_COMM_POLY) includes polygon features that represent the approximate service areas for PWS classified as Community systems.The NTNC Water Service Areas feature class (PWS_WATER_SERVICE_AREA_NTNC_POLY) includes polygon features that represent the approximate service areas for PWS classified as Non-Transient Non-Community systems.The Unlocated Sites List table (PWS_WATER_SERVICE_AREA_USL) contains a list of known, unmapped active Community and NTNC PWS services areas at the time of publication.ProductionData UniversePublic Water Systems in Massachusetts are permitted and regulated through the MassDEP Drinking Water Program. The WURP has mapped service areas for all active and inactive municipal and non-municipal Community PWSs in MassDEP’s Water Quality Testing Database (WQTS). Community PWS refers to a public water system that serves at least 15 service connections used by year-round residents or regularly serves at least 25 year-round residents.All active and inactive NTNC PWS were also mapped using information contained in WQTS. An NTNC or Non-transient Non-community Water System refers to a public water system that is not a community water system and that has at least 15 service connections or regularly serves at least 25 of the same persons or more approximately four or more hours per day, four or more days per week, more than six months or 180 days per year, such as a workplace providing water to its employees.These data may include declassified PWSs. Staff will work to rectify the status/water services to properties previously served by declassified PWSs and remove or incorporate these service areas as needed.Maps of service areas for these systems were collected from various online and MassDEP sources to create service areas digitally in GIS. Every PWS is assigned a unique PWSID by MassDEP that incorporates the municipal ID of the municipality it serves (or the largest municipality it serves if it serves multiple municipalities). Some municipalities contain more than one PWS, but each PWS has a unique PWSID. The Estimated PWS Service Area datalayer, therefore, contains polygons with a unique PWSID for each PWS service area.A service area for a community PWS may serve all of one municipality (e.g. Watertown Water Department), multiple municipalities (e.g. Abington-Rockland Joint Water Works), all or portions of two or more municipalities (e.g. Provincetown Water Dept which serves all of Provincetown and a portion of Truro), or a portion of a municipality (e.g. Hyannis Water System, which is one of four PWSs in the town of Barnstable).Some service areas have not been mapped but their general location is represented by a small circle which serves as a placeholder. The location of these circles are estimates based on the general location of the source wells or the general estimated location of the service area - these do not represent the actual service area.Service areas were mapped initially from 2017 to 2022 and reflect varying years for which service is implemented for that service area boundary. WURP maintains the dataset quarterly with annual data updates; however, the dataset may not include all current active PWSs. A list of unmapped PWS systems is included in the USL table PWS_WATER_SERVICE_AREA_USL available for download with the dataset. Some PWSs that are not mapped may have come online after this iteration of the mapping project; these will be reconciled and mapped during the next phase of the WURP project. PWS IDs that represent regional or joint boards with (e.g. Tri Town Water Board, Randolph/Holbrook Water Board, Upper Cape Regional Water Cooperative) will not be mapped because their individual municipal service areas are included in this datalayer.PWSs that do not have corresponding sources, may be part of consecutive systems, may have been incorporated into another PWSs, reclassified as a different type of PWS, or otherwise taken offline. PWSs that have been incorporated, reclassified, or taken offline will be reconciled during the next data update.Methodologies and Data SourcesSeveral methodologies were used to create service area boundaries using various sources, including data received from the systems in response to requests for information from the MassDEP WURP project, information on file at MassDEP, and service area maps found online at municipal and PWS websites. When provided with water line data rather than generalized areas, 300-foot buffers were created around the water lines to denote service areas and then edited to incorporate generalizations. Some municipalities submitted parcel data or address information to be used in delineating service areas.Verification ProcessSmall-scale PDF file maps with roads and other infrastructure were sent to every PWS for corrections or verifications. For small systems, such as a condominium complex or residential school, the relevant parcels were often used as the basis for the delineated service area. In towns where 97% or more of their population is served by the PWS and no other service area delineation was available, the town boundary was used as the service area boundary. Some towns responded to the request for information or verification of service areas by stating that the town boundary should be used since all or nearly all of the municipality is served by the PWS.Sources of information for estimated drinking water service areasThe following information was used to develop estimated drinking water service areas:EOEEA Water Assets Project (2005) water lines (these were buffered to create service areas)Horsely Witten Report 2008Municipal Master Plans, Open Space Plans, Facilities Plans, Water Supply System Webpages, reports and online interactive mapsGIS data received from PWSDetailed infrastructure mapping completed through the MassDEP WURP Critical Infrastructure InitiativeIn the absence of other service area information, for municipalities served by a town-wide water system serving at least 97% of the population, the municipality’s boundary was used. Determinations of which municipalities are 97% or more served by the PWS were made based on the Percent Water Service Map created in 2018 by MassDEP based on various sources of information including but not limited to:The Winter population served submitted by the PWS in the ASR submittalThe number of services from WQTS as a percent of developed parcelsTaken directly from a Master Plan, Water Department Website, Open Space Plan, etc. found onlineCalculated using information from the town on the population servedMassDEP staff estimateHorsely Witten Report 2008Calculation based on Water System Areas Mapped through MassDEP WURP Critical Infrastructure Initiative, 2017-2022Information found in publicly available PWS planning documents submitted to MassDEP or as part of infrastructure planningMaintenanceThe

  8. o

    Local area boundary

    • vancouver.opendatasoft.com
    • opendata.vancouver.ca
    csv, excel, geojson +1
    Updated Jun 24, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2023). Local area boundary [Dataset]. https://vancouver.opendatasoft.com/explore/dataset/local-area-boundary/api/
    Explore at:
    json, geojson, csv, excelAvailable download formats
    Dataset updated
    Jun 24, 2023
    License

    https://opendata.vancouver.ca/pages/licence/https://opendata.vancouver.ca/pages/licence/

    Description

    This data set contains the boundaries for the City's 22 local areas (also known as local planning areas). Data currencyThese boundaries do not change. Data accuracyLocal area boundaries generally follow street centrelines; centrelines are in the approximate centre of streets.

  9. K

    New Orleans Neighborhood Area Boundary

    • koordinates.com
    csv, dwg, geodatabase +6
    Updated Jun 25, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of New Orleans, Louisiana (2019). New Orleans Neighborhood Area Boundary [Dataset]. https://koordinates.com/layer/103284-new-orleans-neighborhood-area-boundary/
    Explore at:
    csv, shapefile, mapinfo mif, geopackage / sqlite, mapinfo tab, geodatabase, pdf, kml, dwgAvailable download formats
    Dataset updated
    Jun 25, 2019
    Dataset authored and provided by
    City of New Orleans, Louisiana
    Area covered
    Description

    Geospatial data about New Orleans Neighborhood Area Boundary. Export to CAD, GIS, PDF, CSV and access via API.

  10. PSAP 911 Service Area Boundaries

    • wifire-data.sdsc.edu
    • hub.arcgis.com
    • +1more
    csv, esri rest +4
    Updated May 31, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    CA Governor's Office of Emergency Services (2019). PSAP 911 Service Area Boundaries [Dataset]. https://wifire-data.sdsc.edu/dataset/psap-911-service-area-boundaries
    Explore at:
    geojson, html, kml, esri rest, zip, csvAvailable download formats
    Dataset updated
    May 31, 2019
    Dataset provided by
    California Governor's Office of Emergency Services
    License

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

    Description

    911 Public Safety Answering Point (PSAP) service area boundaries in the United States According to the National Emergency Number Association (NENA), a Public Safety Answering Point (PSAP) is a facility equipped and staffed to receive 9-1-1 calls. The service area is the geographic area within which a 911 call placed using a landline is answered at the associated PSAP. This dataset only includes primary PSAPs. Secondary PSAPs, backup PSAPs, and wireless PSAPs have been excluded from this dataset. Primary PSAPs receive calls directly, whereas secondary PSAPs receive calls that have been transferred by a primary PSAP. Backup PSAPs provide service in cases where another PSAP is inoperable. Most military bases have their own emergency telephone systems. To connect to such a system from within a military base, it may be necessary to dial a number other than 9 1 1. Due to the sensitive nature of military installations, TGS did not actively research these systems. If civilian authorities in surrounding areas volunteered information about these systems, or if adding a military PSAP was necessary to fill a hole in civilian provided data, TGS included it in this dataset. Otherwise, military installations are depicted as being covered by one or more adjoining civilian emergency telephone systems. In some cases, areas are covered by more than one PSAP boundary. In these cases, any of the applicable PSAPs may take a 911 call. Where a specific call is routed may depend on how busy the applicable PSAPs are (i.e., load balancing), operational status (i.e., redundancy), or time of day / day of week. If an area does not have 911 service, TGS included that area in the dataset along with the address and phone number of their dispatch center. These are areas where someone must dial a 7 or 10 digit number to get emergency services. These records can be identified by a "Y" in the [NON911EMNO] field. This indicates that dialing 911 inside one of these areas does not connect one with emergency services. This dataset was constructed by gathering information about PSAPs from state level officials. In some cases, this was geospatial information; in other cases, it was tabular. This information was supplemented with a list of PSAPs from the Federal Communications Commission (FCC). Each PSAP was researched to verify its tabular information. In cases where the source data was not geospatial, each PSAP was researched to determine its service area in terms of existing boundaries (e.g., city and county boundaries). In some cases, existing boundaries had to be modified to reflect coverage areas (e.g., "entire county north of Country Road 30"). However, there may be cases where minor deviations from existing boundaries are not reflected in this dataset, such as the case where a particular PSAPs coverage area includes an entire county plus the homes and businesses along a road which is partly in another county. At the request of NGA, text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. At the request of NGA, all diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics.


    Homeland Security Use Cases: Use cases describe how the data may be used and help to define and clarify requirements. 1) A disaster has struck, or is predicted for, a locality. The PSAP that may be affected must be identified and verified to be operational. 2) In the event that the local PSAP is inoperable, adjacent PSAP locations could be identified and utilized.

  11. a

    Study Area Boundaries

    • hub.arcgis.com
    Updated Jun 9, 2016
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Federal Communications Commission (2016). Study Area Boundaries [Dataset]. https://hub.arcgis.com/maps/cbd47993de8d4a78934ccb5221398f3a
    Explore at:
    Dataset updated
    Jun 9, 2016
    Dataset authored and provided by
    Federal Communications Commission
    Area covered
    Description

    The map displays the study area boundaries submitted and certified by incumbent local exchange carriers and state commissions through May 5th, 2016. As a result of confidentiality requests, certain boundaries for Verizon and AT&T are not displayed.

  12. v

    Study area boundary for the Death Valley regional ground-water flow system,...

    • res1catalogd-o-tdatad-o-tgov.vcapture.xyz
    • data.usgs.gov
    • +6more
    Updated Sep 18, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey (2024). Study area boundary for the Death Valley regional ground-water flow system, Nevada and California [Dataset]. https://res1catalogd-o-tdatad-o-tgov.vcapture.xyz/dataset/study-area-boundary-for-the-death-valley-regional-ground-water-flow-system-nevada-and-cali-306a1
    Explore at:
    Dataset updated
    Sep 18, 2024
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Area covered
    Death Valley, California, Nevada
    Description

    This digital data set represents the Death Valley regional ground-water flow system (DVRFS) study area which encompasses approximately 100,000-square kilometers in Nevada and California and is bounded by latitudes 35-degrees north and 38-degrees 15-minutes north and by longitudes 115-degrees west and 118-degrees west. The study area boundary encompasses the DVRFS model domain which is the area simulated by a transient ground-water flow model. The DVRFS transient ground-water flow model is the most recent in a number of regional-scale models developed by the U.S. Geological Survey (USGS) for the U.S. Department of Energy (DOE) to support investigations at the Nevada Test Site (NTS) and at Yucca Mountain, Nevada (see "Larger Work Citation", Chapter A, page 8, for details).

  13. n

    PSAP 911 Service Area Boundaries - Dataset - CKAN

    • nationaldataplatform.org
    Updated Feb 28, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). PSAP 911 Service Area Boundaries - Dataset - CKAN [Dataset]. https://nationaldataplatform.org/catalog/dataset/psap-911-service-area-boundaries
    Explore at:
    Dataset updated
    Feb 28, 2024
    License

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

    Description

    911 Public Safety Answering Point (PSAP) service area boundaries in the United States According to the National Emergency Number Association (NENA), a Public Safety Answering Point (PSAP) is a facility equipped and staffed to receive 9-1-1 calls. The service area is the geographic area within which a 911 call placed using a landline is answered at the associated PSAP. This dataset only includes primary PSAPs. Secondary PSAPs, backup PSAPs, and wireless PSAPs have been excluded from this dataset. Primary PSAPs receive calls directly, whereas secondary PSAPs receive calls that have been transferred by a primary PSAP. Backup PSAPs provide service in cases where another PSAP is inoperable. Most military bases have their own emergency telephone systems. To connect to such a system from within a military base, it may be necessary to dial a number other than 9 1 1. Due to the sensitive nature of military installations, TGS did not actively research these systems. If civilian authorities in surrounding areas volunteered information about these systems, or if adding a military PSAP was necessary to fill a hole in civilian provided data, TGS included it in this dataset. Otherwise, military installations are depicted as being covered by one or more adjoining civilian emergency telephone systems. In some cases, areas are covered by more than one PSAP boundary. In these cases, any of the applicable PSAPs may take a 911 call. Where a specific call is routed may depend on how busy the applicable PSAPs are (i.e., load balancing), operational status (i.e., redundancy), or time of day / day of week. If an area does not have 911 service, TGS included that area in the dataset along with the address and phone number of their dispatch center. These are areas where someone must dial a 7 or 10 digit number to get emergency services. These records can be identified by a "Y" in the [NON911EMNO] field. This indicates that dialing 911 inside one of these areas does not connect one with emergency services. This dataset was constructed by gathering information about PSAPs from state level officials. In some cases, this was geospatial information; in other cases, it was tabular. This information was supplemented with a list of PSAPs from the Federal Communications Commission (FCC). Each PSAP was researched to verify its tabular information. In cases where the source data was not geospatial, each PSAP was researched to determine its service area in terms of existing boundaries (e.g., city and county boundaries). In some cases, existing boundaries had to be modified to reflect coverage areas (e.g., "entire county north of Country Road 30"). However, there may be cases where minor deviations from existing boundaries are not reflected in this dataset, such as the case where a particular PSAPs coverage area includes an entire county plus the homes and businesses along a road which is partly in another county. At the request of NGA, text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. At the request of NGA, all diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics.Homeland Security Use Cases: Use cases describe how the data may be used and help to define and clarify requirements. 1) A disaster has struck, or is predicted for, a locality. The PSAP that may be affected must be identified and verified to be operational. 2) In the event that the local PSAP is inoperable, adjacent PSAP locations could be identified and utilized.

  14. v

    California City Boundaries and Identifiers

    • res1catalogd-o-tdatad-o-tgov.vcapture.xyz
    Updated Jul 24, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Technology (2025). California City Boundaries and Identifiers [Dataset]. https://res1catalogd-o-tdatad-o-tgov.vcapture.xyz/dataset/california-city-boundaries-and-identifiers
    Explore at:
    Dataset updated
    Jul 24, 2025
    Dataset provided by
    California Department of Technology
    Area covered
    California City
    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://res1gisd-o-tdatad-o-tcad-o-tgov.vcapture.xyz/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 Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More

  15. v

    WAC Administrative Area Boundary

    • res1catalogd-o-tdatad-o-tgov.vcapture.xyz
    • opendata.maryland.gov
    • +1more
    Updated Aug 2, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    opendata.maryland.gov (2025). WAC Administrative Area Boundary [Dataset]. https://res1catalogd-o-tdatad-o-tgov.vcapture.xyz/dataset/wac-administrative-area-boundary
    Explore at:
    Dataset updated
    Aug 2, 2025
    Dataset provided by
    opendata.maryland.gov
    Description

    Polygon layer representing the administrative boundary of Washington College property.

  16. A

    Utah BLM Land Use Planning Area Boundary Existing Polygons

    • data.amerigeoss.org
    • datadiscoverystudio.org
    zip
    Updated Jul 30, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    United States[old] (2019). Utah BLM Land Use Planning Area Boundary Existing Polygons [Dataset]. https://data.amerigeoss.org/sr/dataset/utah-blm-land-use-planning-area-boundary-existing-polygons
    Explore at:
    zipAvailable download formats
    Dataset updated
    Jul 30, 2019
    Dataset provided by
    United States[old]
    License

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

    Area covered
    Utah
    Description

    This polygon feature class represents the spatial extent and boundaries for existing BLM Land Use Planning Area (LUPA) polygons in Utah. Land Use Planning Areas are geographic areas within which the BLM will make decisions during a land use planning effort. Land Use Planning Area Boundaries shift from an "in-progress" status and become Existing Land Use Planning Areas when the Land Use Plan has been approvided and a Record of Decision Date has been established. At this point, these LUPAs are officially "existing".

  17. Data from: Watershed Boundary Dataset (WBD)

    • data.ca.gov
    • data.cnra.ca.gov
    • +1more
    Updated Apr 9, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Water Resources (2025). Watershed Boundary Dataset (WBD) [Dataset]. https://data.ca.gov/dataset/watershed-boundary-dataset-wbd
    Explore at:
    arcgis geoservices rest api, file geodatabase or shapefile, pdf, websiteAvailable download formats
    Dataset updated
    Apr 9, 2025
    Dataset authored and provided by
    California Department of Water Resourceshttp://www.water.ca.gov/
    License

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

    Description

    The Watershed Boundary Dataset (WBD) from USGS' The National Map (TNM) defines the perimeter of drainage areas formed by the terrain and other landscape characteristics. The drainage areas are nested within each other so that a large drainage area, such as the Sacramento River, will be composed of multiple smaller drainage areas, such as the Feather River. Each of these smaller areas can further be subdivided into smaller and smaller drainage areas. The WBD uses six different levels in this hierarchy, with the smallest averaging about 30,000 acres. The WBD is made up of polygons nested into six levels of data respectively defined by Regions, Subregions, Basins, Subbasins, Watersheds, and Subwatersheds. For additional information on the WBD, go to https://www.usgs.gov/core-science-systems/ngp/national-hydrography/watershed-boundary-dataset. DWR was the steward for NHD and WBD in California. We worked with other organizations to edit and improve NHD and WBD, using the business rules for California. California's WBD improvements are sent to USGS for certification and incorporation to the national geodatabase. The certified WBD is included within the National Hydrography Dataset downloadable file geodatabase, and is also available in shapefile format and as web map services accessible from the USGS website. (https://www.usgs.gov/core-science-systems/ngp/national-hydrography/access-national-hydrography-products).

    The final static version of the WBD was published in January 2025. No edits to this dataset are being accepted by USGS. Future mapping of drainage areas will be done by USGS as the 3D Hydrography Program (3DHP) is built out. DWR and its stewardship partners are actively producing LiDAR-derived hydrography data for inclusion in the California portion of 3DHP data and eventually its companion set of drainage areas. For now, the WBD is considered the authoritative source for watershed delineations in California.

  18. C

    Milwaukee Water Works Service Area Boundary

    • data.milwaukee.gov
    zip
    Updated Aug 19, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Milwaukee Water Works (2022). Milwaukee Water Works Service Area Boundary [Dataset]. https://data.milwaukee.gov/dataset/milwaukee-water-works-service-area-boundary
    Explore at:
    zip(145651)Available download formats
    Dataset updated
    Aug 19, 2022
    Dataset authored and provided by
    Milwaukee Water Works
    License

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

    Area covered
    Milwaukee
    Description

    Update frequency: As needed

    Milwaukee Water Works service area by customer type.

  19. O

    CT DCF Area Boundaries

    • data.ct.gov
    • cloud.csiss.gmu.edu
    • +3more
    application/rdfxml +5
    Updated Jan 29, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Department of Children and Families (2025). CT DCF Area Boundaries [Dataset]. https://data.ct.gov/Health-and-Human-Services/CT-DCF-Area-Boundaries/iax9-vzun
    Explore at:
    csv, xml, application/rdfxml, json, application/rssxml, tsvAvailable download formats
    Dataset updated
    Jan 29, 2025
    Dataset authored and provided by
    Department of Children and Families
    Area covered
    Connecticut
    Description

    This is a boundary file showing the catchment area for which each of the 14 DCF Area Offices is responsible. Catchment areas are comprised of complete Towns, but not necessarily complete Zip Codes. Data is as of 7/1/2014, is unlikely to change frequently, and will be updated only as changes are made to the catchment areas.

  20. A

    Utah BLM Land Use Planning Area Boundary In-Progress Polygons

    • data.amerigeoss.org
    • datadiscoverystudio.org
    zip
    Updated Jul 26, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    United States[old] (2019). Utah BLM Land Use Planning Area Boundary In-Progress Polygons [Dataset]. https://data.amerigeoss.org/es/dataset/1f148b3d-4b13-472c-bad5-ec25a08094e8
    Explore at:
    zipAvailable download formats
    Dataset updated
    Jul 26, 2019
    Dataset provided by
    United States[old]
    License

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

    Area covered
    Utah
    Description

    This polygon feature class represents the spatial extent and boundaries for in-progress BLM Land Use Planning Areas (LUPAs). Land Use Planning Areas are geographic areas within which the BLM will make decisions during a land use planning effort. "In Progress" Planning Area Boundaries are created during the planning process and do not have a Record of Decision.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Bureau of Land Management (2024). BLM OR Wilderness Study Area Boundary Line Hub [Dataset]. https://catalog.data.gov/dataset/blm-or-wilderness-study-area-boundary-line-hub
Organization logo

BLM OR Wilderness Study Area Boundary Line Hub

Explore at:
Dataset updated
Nov 20, 2024
Dataset provided by
Bureau of Land Managementhttp://www.blm.gov/
Description

WSA_ARC: This data set represents Wilderness Study Area (WSA) boundaries as inventoried in the mid1980's and defined in the October 1991 "Wilderness Study Report". Wilderness Study Areas are essentially roadless areas under BLM jurisdiction. Wilderness Study Areas have special management restrictions and priorities. They are a one-time designation and new WSA or additions to WSA are rare. For a complete description of this data consult the Wilderness Study Areas Spatial Data Standard. http://www.blm.gov/or/datamanagement/index.php

Search
Clear search
Close search
Google apps
Main menu