100+ datasets found
  1. City and County Boundary Line Changes

    • gis.data.ca.gov
    • hub.arcgis.com
    • +2more
    Updated Mar 6, 2015
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Tax and Fee Administration (2015). City and County Boundary Line Changes [Dataset]. https://gis.data.ca.gov/maps/93f73ae0070240fca9a4d3826ddb83cd
    Explore at:
    Dataset updated
    Mar 6, 2015
    Dataset authored and provided by
    California Department of Tax and Fee Administrationhttp://cdtfa.ca.gov/
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    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).

  2. a

    California City and County Boundaries

    • hub.arcgis.com
    • gis-calema.opendata.arcgis.com
    Updated Nov 30, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    CA Governor's Office of Emergency Services (2022). California City and County Boundaries [Dataset]. https://hub.arcgis.com/maps/391744b558df4a75a33b4f52fa690feb
    Explore at:
    Dataset updated
    Nov 30, 2022
    Dataset authored and provided by
    CA Governor's Office of Emergency Services
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    This feature service includes change areas for city boundaries and county line adjustments filed in accordance with Government Code 54900. The boundaries in this map are based on the State Board of Equalization's tax rate area maps for the assessment roll year specified in the COFILE field. The information is updated regularly within 10 business days of the most recent BOE acknowledgement date. Some differences may occur between actual recorded boundaries and boundary placement in the tax rate area GIS map. Tax rate area boundaries are representations of taxing jurisdictions for the purpose of determining property tax assessments and should not be used to determine precise city or county boundary line locations. BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number; CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance; 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. 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 BOE'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).

  3. U

    USGS National Boundary Dataset (NBD) Downloadable Data Collection

    • data.usgs.gov
    • s.cnmilf.com
    • +2more
    Updated Apr 29, 2010
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey, National Geospatial Technical Operations Center (2010). USGS National Boundary Dataset (NBD) Downloadable Data Collection [Dataset]. https://data.usgs.gov/datacatalog/data/USGS:6dcde538-1684-48a0-a8d6-cb671ca0a43e
    Explore at:
    Dataset updated
    Apr 29, 2010
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Authors
    U.S. Geological Survey, National Geospatial Technical Operations Center
    License

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

    Description

    The USGS Governmental Unit Boundaries dataset from The National Map (TNM) represents major civil areas for the Nation, including States or Territories, counties (or equivalents), Federal and Native American areas, congressional districts, minor civil divisions, incorporated places (such as cities and towns), and unincorporated places. Boundaries data are useful for understanding the extent of jurisdictional or administrative areas for a wide range of applications, including mapping or managing resources, and responding to natural disasters. Boundaries data also include extents of forest, grassland, park, wilderness, wildlife, and other reserve areas useful for recreational activities, such as hiking and backpacking. Boundaries data are acquired from a variety of government sources. The data represents the source data with minimal editing or review by USGS. Please refer to the feature-level metadata ...

  4. d

    Data from: Digital map of the state (political) boundaries of Mexico

    • catalog.data.gov
    • data.usgs.gov
    • +4more
    Updated Sep 2, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey (2024). Digital map of the state (political) boundaries of Mexico [Dataset]. https://catalog.data.gov/dataset/digital-map-of-the-state-political-boundaries-of-mexico
    Explore at:
    Dataset updated
    Sep 2, 2024
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Area covered
    Mexico
    Description

    This data set represents the state (political) boundaries of Mexico. The Digitial Chart of the World data set had incomplete state boundaries, which was the reason to create this coverage. It was digitized from a 1992 CIA map at a scale of 1:3 million. The coast line came from the Digital Chart of the world at a scale of 1:1 million. The state names were labeled from the map and an attribute to help fill the states was added. The labeling process was done manually.

  5. l

    City Boundary

    • geohub.lacity.org
    • visionzero.geohub.lacity.org
    • +6more
    Updated Nov 14, 2015
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    boegis_lahub (2015). City Boundary [Dataset]. https://geohub.lacity.org/maps/city-boundary
    Explore at:
    Dataset updated
    Nov 14, 2015
    Dataset authored and provided by
    boegis_lahub
    License

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

    Area covered
    Description

    City Boundary

  6. d

    500 Cities: City Boundaries

    • catalog.data.gov
    • healthdata.gov
    • +5more
    Updated Feb 3, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Centers for Disease Control and Prevention (2025). 500 Cities: City Boundaries [Dataset]. https://catalog.data.gov/dataset/500-cities-city-boundaries
    Explore at:
    Dataset updated
    Feb 3, 2025
    Dataset provided by
    Centers for Disease Control and Prevention
    Description

    This city boundary shapefile was extracted from Esri Data and Maps for ArcGIS 2014 - U.S. Populated Place Areas. This shapefile can be joined to 500 Cities city-level Data (GIS Friendly Format) in a geographic information system (GIS) to make city-level maps.

  7. a

    World: Political Boundaries

    • hub.arcgis.com
    • edu.hub.arcgis.com
    Updated Sep 7, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Education and Research (2023). World: Political Boundaries [Dataset]. https://hub.arcgis.com/maps/a5b85739696c46cf87403639ab1f95c1
    Explore at:
    Dataset updated
    Sep 7, 2023
    Dataset authored and provided by
    Education and Research
    Area covered
    Description

    Explore a full description of the map.This 2020 political boundary data is from Garmin International and the United States Central Intelligence Agency The World Factbook and compiled by Esri. One layer includes the boundary lines for countries and another for states and provinces. These layers do not include contested boundaries and any you see are likely on the basemap you have chosen.CreditsEsri; Global Mapping International; U.S. Central Intelligence Agency (The World Factbook). From National Geographic MapMaker.Terms of Use This work is licensed under the Esri Master License Agreement.View Summary | View Terms of Use

  8. Data from: California County Boundaries

    • gis.data.ca.gov
    • data.cnra.ca.gov
    • +6more
    Updated Oct 16, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Forestry and Fire Protection (2019). California County Boundaries [Dataset]. https://gis.data.ca.gov/datasets/CALFIRE-Forestry::california-county-boundaries/about
    Explore at:
    Dataset updated
    Oct 16, 2019
    Dataset authored and provided by
    California Department of Forestry and Fire Protectionhttp://calfire.ca.gov/
    Area covered
    Description

    In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata.A dataset was made available (approximately 2004) through CALFIRE - FRAP and the California Spatial Information Library (CaSIL), with additional updates throughout subsequent years. More recently, an effort was made to improve the coastal linework by using the previous interior linework from the 24k data, but replacing the coastal linework based on NOAA's ERMA coastal dataset (which used NAIP 2010). In this dataset, all bays (plus bay islands and constructed features) are merged into the mainland, and coastal features (such as islands and constructed features) are not included, with the exception of the Channel Islands which ARE included.This service represents the latest released version, and is updated when new versions are released. As of June, 2019 it represents cnty19_1.

  9. a

    California City Boundaries and Identifiers

    • hub.arcgis.com
    • data.ca.gov
    • +1more
    Updated Sep 16, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Technology (2024). California City Boundaries and Identifiers [Dataset]. https://hub.arcgis.com/datasets/8cd5d2038c5547ba911eea7bec48e28b
    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

  10. K

    Los Angeles City Boundary

    • koordinates.com
    csv, dwg, geodatabase +6
    Updated Oct 3, 2018
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Los Angeles, California (2018). Los Angeles City Boundary [Dataset]. https://koordinates.com/layer/98158-los-angeles-city-boundary/
    Explore at:
    shapefile, geopackage / sqlite, mapinfo tab, geodatabase, dwg, csv, pdf, mapinfo mif, kmlAvailable download formats
    Dataset updated
    Oct 3, 2018
    Dataset authored and provided by
    City of Los Angeles, California
    Area covered
    Description

    Polygon vector map data covering boundaries for the City of Los Angeles containing 4 features.

    Boundary GIS (Geographic Information System) data is spatial information that delineates the geographic boundaries of specific geographic features. This data typically includes polygons representing the outlines of these features, along with attributes such as names, codes, and other relevant information.

    Boundary GIS data is used for a variety of purposes across multiple industries, including urban planning, environmental management, public health, transportation, and business analysis.

    Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

  11. NERRS Boundaries Map Service Description

    • catalog.data.gov
    • s.cnmilf.com
    • +2more
    Updated Oct 19, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    NOAA National Centers for Environmental Information (Point of Contact) (2024). NERRS Boundaries Map Service Description [Dataset]. https://catalog.data.gov/dataset/nerrs-boundaries-map-service-description3
    Explore at:
    Dataset updated
    Oct 19, 2024
    Dataset provided by
    National Centers for Environmental Informationhttps://www.ncei.noaa.gov/
    National Oceanic and Atmospheric Administrationhttp://www.noaa.gov/
    Description

    This layer represents the boundaries of all of the reserves in the National Estuarine Reserve System.

  12. a

    Web Map - Administrative Boundaries

    • hub.arcgis.com
    Updated Dec 27, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Minnesota Pollution Control Agency (2020). Web Map - Administrative Boundaries [Dataset]. https://hub.arcgis.com/maps/0d7dc3db0b7f4870a3eb8101e4ac3c81
    Explore at:
    Dataset updated
    Dec 27, 2020
    Dataset authored and provided by
    Minnesota Pollution Control Agency
    Area covered
    Description

    The purpose of the Administrative Boundaries map is to help orient readers to the Watershed and provide context for how the watershed(s) relate to administrative boundaries (e.g. cities, townships, counties) in the state.This data has been modified from the original source data to serve a specific business purpose. This data is for cartographic purposes only.

  13. c

    Northeastern States Town Boundary Set

    • deepmaps.ct.gov
    • data.ct.gov
    • +5more
    Updated Oct 30, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Department of Energy & Environmental Protection (2019). Northeastern States Town Boundary Set [Dataset]. https://deepmaps.ct.gov/maps/2ffebffd806542c98406f4bb1794a6da
    Explore at:
    Dataset updated
    Oct 30, 2019
    Dataset authored and provided by
    Department of Energy & Environmental Protection
    License

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

    Area covered
    Description

    Northeastern United States Town Boundary data are intended for geographic display of state, county and town (municipal) boundaries at statewide and regional levels. Use it to map and label towns on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)

  14. CA Geographic Boundaries

    • data.ca.gov
    • s.cnmilf.com
    • +1more
    shp
    Updated May 3, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Technology (2024). CA Geographic Boundaries [Dataset]. https://data.ca.gov/dataset/ca-geographic-boundaries
    Explore at:
    shp(136046), shp(10153125), shp(2597712)Available download formats
    Dataset updated
    May 3, 2024
    Dataset authored and provided by
    California Department of Technologyhttp://cdt.ca.gov/
    Description

    This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.

  15. Geolocet | Administrative boundaries map data | Europe | Countries, Regions,...

    • datarade.ai
    Updated Nov 3, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Geolocet (2023). Geolocet | Administrative boundaries map data | Europe | Countries, Regions, Provinces, Municipalities, and more | Fully customizable format [Dataset]. https://datarade.ai/data-products/geolocet-administrative-boundaries-map-data-europe-coun-geolocet
    Explore at:
    .json, .xml, .csv, .xls, .sql, .txtAvailable download formats
    Dataset updated
    Nov 3, 2023
    Dataset authored and provided by
    Geolocet
    Area covered
    Lithuania, Belgium, Germany, Bulgaria, Luxembourg, Italy, United Kingdom, Hungary, Estonia, Finland
    Description

    Geolocet's Administrative Boundaries Spatial Data serves as the gateway to visualizing geographic distributions and patterns with precision. The comprehensive dataset covers all European countries, encompassing the boundaries of each country, as well as its political and statistical divisions. Tailoring data purchases to exact needs is possible, allowing for the selection of individual levels of geography or bundling all levels for a country with a discount. The seamless integration of administrative boundaries onto digital maps transforms raw data into actionable insights.

    🌐 Coverage Across European Countries

    Geolocet's Administrative Boundaries Data offers coverage across all European countries, ensuring access to the most up-to-date and accurate geographic information. From national borders to the finest-grained administrative units, this data enables informed choices based on verified and official sources.

    🔍 Geographic Context for Strategic Decisions

    Understanding the geographical context is crucial for strategic decision-making. Geolocet's Administrative Boundaries Spatial Data empowers exploration of geo patterns, planning expansions, analysis of regional demographics, and optimization of operations with precision. Whether it is for establishing new business locations, efficient resource allocation, or policy impact analysis, this data provides the essential geographic context for success.

    🌍 Integration with Geolocet’s Demographic Data

    The integration of Geolocet's Administrative Boundaries Spatial Data with Geolocet's Demographic Data creates a synergy that enriches insights. The combination of administrative boundaries and demographic information offers a comprehensive understanding of regions and their unique characteristics. This integration enables tailoring of strategies, marketing campaigns, and resource allocation to specific areas with confidence.

    🌍 Integration with Geolocet’s POI Data

    Combining Geolocet's Administrative Boundaries Spatial Data with our POI (Points of Interest) Data unveils not only the administrative divisions but also insights into the local characteristics of these areas. Overlaying POI data on administrative boundaries reveals details about the number and types of businesses, services, and amenities within specific regions. Whether conducting market research, identifying prime locations for retail outlets, or analyzing the accessibility of essential services, this combined data empowers a holistic view of target areas.

    🔍 Customized Data Solutions with DaaS

    Geolocet's Data as a Service (DaaS) model offers flexibility tailored to specific needs. The transparent pricing model ensures cost-efficiency, allowing payment solely for the required data. Whether nationwide administrative boundary data or specific regional details are needed, Geolocet provides a solution to match individual objectives. Contact us today to explore how Geolocet's Administrative Boundaries Spatial Data can elevate decision-making processes and provide the essential geographic data for success.

  16. Large Scale International Boundaries

    • catalog.data.gov
    • geodata.state.gov
    • +1more
    Updated Jul 4, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of State (Point of Contact) (2025). Large Scale International Boundaries [Dataset]. https://catalog.data.gov/dataset/large-scale-international-boundaries
    Explore at:
    Dataset updated
    Jul 4, 2025
    Dataset provided by
    United States Department of Statehttp://state.gov/
    Description

    Overview The Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.4 (published 24 February 2025). The 11.4 release contains updated boundary lines and data refinements designed to extend the functionality of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control. National Geospatial Data Asset This dataset is a National Geospatial Data Asset (NGDAID 194) managed by the Department of State. It is a part of the International Boundaries Theme created by the Federal Geographic Data Committee. Dataset Source Details Sources for these data include treaties, relevant maps, and data from boundary commissions, as well as national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process includes analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground. Cartographic Visualization The LSIB is a geospatial dataset that, when used for cartographic purposes, requires additional styling. The LSIB download package contains example style files for commonly used software applications. The attribute table also contains embedded information to guide the cartographic representation. Additional discussion of these considerations can be found in the Use of Core Attributes in Cartographic Visualization section below. Additional cartographic information pertaining to the depiction and description of international boundaries or areas of special sovereignty can be found in Guidance Bulletins published by the Office of the Geographer and Global Issues: https://data.geodata.state.gov/guidance/index.html Contact Direct inquiries to internationalboundaries@state.gov. Direct download: https://data.geodata.state.gov/LSIB.zip Attribute Structure The dataset uses the following attributes divided into two categories: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | Core CC1_GENC3 | Extension CC1_WPID | Extension COUNTRY1 | Core CC2 | Core CC2_GENC3 | Extension CC2_WPID | Extension COUNTRY2 | Core RANK | Core LABEL | Core STATUS | Core NOTES | Core LSIB_ID | Extension ANTECIDS | Extension PREVIDS | Extension PARENTID | Extension PARENTSEG | Extension These attributes have external data sources that update separately from the LSIB: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | GENC CC1_GENC3 | GENC CC1_WPID | World Polygons COUNTRY1 | DoS Lists CC2 | GENC CC2_GENC3 | GENC CC2_WPID | World Polygons COUNTRY2 | DoS Lists LSIB_ID | BASE ANTECIDS | BASE PREVIDS | BASE PARENTID | BASE PARENTSEG | BASE The core attributes listed above describe the boundary lines contained within the LSIB dataset. Removal of core attributes from the dataset will change the meaning of the lines. An attribute status of “Extension” represents a field containing data interoperability information. Other attributes not listed above include “FID”, “Shape_length” and “Shape.” These are components of the shapefile format and do not form an intrinsic part of the LSIB. Core Attributes The eight core attributes listed above contain unique information which, when combined with the line geometry, comprise the LSIB dataset. These Core Attributes are further divided into Country Code and Name Fields and Descriptive Fields. County Code and Country Name Fields “CC1” and “CC2” fields are machine readable fields that contain political entity codes. These are two-character codes derived from the Geopolitical Entities, Names, and Codes Standard (GENC), Edition 3 Update 18. “CC1_GENC3” and “CC2_GENC3” fields contain the corresponding three-character GENC codes and are extension attributes discussed below. The codes “Q2” or “QX2” denote a line in the LSIB representing a boundary associated with areas not contained within the GENC standard. The “COUNTRY1” and “COUNTRY2” fields contain the names of corresponding political entities. These fields contain names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the ‘"Independent States in the World" and "Dependencies and Areas of Special Sovereignty" lists maintained by the Department of State. To ensure maximum compatibility, names are presented without diacritics and certain names are rendered using common cartographic abbreviations. Names for lines associated with the code "Q2" are descriptive and not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS denote independent states. Names rendered in normal text represent dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user. Descriptive Fields The following text fields are a part of the core attributes of the LSIB dataset and do not update from external sources. They provide additional information about each of the lines and are as follows: ATTRIBUTE NAME | CONTAINS NULLS RANK | No STATUS | No LABEL | Yes NOTES | Yes Neither the "RANK" nor "STATUS" fields contain null values; the "LABEL" and "NOTES" fields do. The "RANK" field is a numeric expression of the "STATUS" field. Combined with the line geometry, these fields encode the views of the United States Government on the political status of the boundary line. ATTRIBUTE NAME | | VALUE | RANK | 1 | 2 | 3 STATUS | International Boundary | Other Line of International Separation | Special Line A value of “1” in the “RANK” field corresponds to an "International Boundary" value in the “STATUS” field. Values of ”2” and “3” correspond to “Other Line of International Separation” and “Special Line,” respectively. The “LABEL” field contains required text to describe the line segment on all finished cartographic products, including but not limited to print and interactive maps. The “NOTES” field contains an explanation of special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, limitations regarding the purpose of the lines, or the original source of the line. Use of Core Attributes in Cartographic Visualization Several of the Core Attributes provide information required for the proper cartographic representation of the LSIB dataset. The cartographic usage of the LSIB requires a visual differentiation between the three categories of boundary lines. Specifically, this differentiation must be between: International Boundaries (Rank 1); Other Lines of International Separation (Rank 2); and Special Lines (Rank 3). Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary. Please consult the style files in the download package for examples of this depiction. The requirement to incorporate the contents of the "LABEL" field on cartographic products is scale dependent. If a label is legible at the scale of a given static product, a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field contains the preferred description for the three LSIB line types when they are incorporated into a map legend but is otherwise not to be used for labeling. Use of the “CC1,” “CC1_GENC3,” “CC2,” “CC2_GENC3,” “RANK,” or “NOTES” fields for cartographic labeling purposes is prohibited. Extension Attributes Certain elements of the attributes within the LSIB dataset extend data functionality to make the data more interoperable or to provide clearer linkages to other datasets. The fields “CC1_GENC3” and “CC2_GENC” contain the corresponding three-character GENC code to the “CC1” and “CC2” attributes. The code “QX2” is the three-character counterpart of the code “Q2,” which denotes a line in the LSIB representing a boundary associated with a geographic area not contained within the GENC standard. To allow for linkage between individual lines in the LSIB and World Polygons dataset, the “CC1_WPID” and “CC2_WPID” fields contain a Universally Unique Identifier (UUID), version 4, which provides a stable description of each geographic entity in a boundary pair relationship. Each UUID corresponds to a geographic entity listed in the World Polygons dataset. These fields allow for linkage between individual lines in the LSIB and the overall World Polygons dataset. Five additional fields in the LSIB expand on the UUID concept and either describe features that have changed across space and time or indicate relationships between previous versions of the feature. The “LSIB_ID” attribute is a UUID value that defines a specific instance of a feature. Any change to the feature in a lineset requires a new “LSIB_ID.” The “ANTECIDS,” or antecedent ID, is a UUID that references line geometries from which a given line is descended in time. It is used when there is a feature that is entirely new, not when there is a new version of a previous feature. This is generally used to reference countries that have dissolved. The “PREVIDS,” or Previous ID, is a UUID field that contains old versions of a line. This is an additive field, that houses all Previous IDs. A new version of a feature is defined by any change to the

  17. T

    Boundaries: State of Texas Counties

    • datahub.austintexas.gov
    • data.austintexas.gov
    • +2more
    Updated Jul 1, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    US Census (2025). Boundaries: State of Texas Counties [Dataset]. https://datahub.austintexas.gov/Locations-and-Maps/Boundaries-State-of-Texas-Counties/tnsq-nquk
    Explore at:
    csv, application/rssxml, application/geo+json, xml, tsv, application/rdfxml, kmz, kmlAvailable download formats
    Dataset updated
    Jul 1, 2025
    Dataset authored and provided by
    US Census
    License

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

    Area covered
    Texas
    Description

    Cartographic Boundary Map provided the State of Texas Open Data Portal here: https://data.texas.gov/dataset/Texas-Counties-Cartographic-Boundary-Map/sw7f-2kkd/about_data

    Terms of Use This product is for informational purposes and may not have been prepared for or be suitable for legal, engineering, or surveying purposes. It does not represent an on-the-ground survey and represents only the approximate relative location of property boundaries. This product has been provided by the City of Austin via the US Census Bureau for the sole purpose of geographic reference. No warranty is made by the City of Austin regarding specific accuracy or completeness.

  18. u

    HUC Boundaries Map

    • nhgeodata.unh.edu
    • granit.unh.edu
    • +2more
    Updated Jun 7, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    New Hampshire GRANIT GIS Clearinghouse (2020). HUC Boundaries Map [Dataset]. https://www.nhgeodata.unh.edu/documents/d70352e927c54812be6577ff643d2dd8
    Explore at:
    Dataset updated
    Jun 7, 2020
    Dataset authored and provided by
    New Hampshire GRANIT GIS Clearinghouse
    Description

    This map is to help people locate LiDAR-derived 2-ft contour data sets in New Hampshire. Both HUC 8 and HUC 10 units are displayed along with the HUC labels so that users can find which contour service covers their area of interest. For services residing on ArcGIS Online, contour services are available by HUC 10. HUC 8 services (including HUC 10 sub layers) are available in the EDP folder on nhgeodata.unh.edu/nhgeodata/rest/services.

  19. n

    Municipal Boundaries (Generalized)

    • linc.osbm.nc.gov
    • ncosbm.opendatasoft.com
    csv, excel, geojson +1
    Updated Feb 26, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). Municipal Boundaries (Generalized) [Dataset]. https://linc.osbm.nc.gov/explore/dataset/municipal-boundaries-generalized/
    Explore at:
    excel, geojson, csv, jsonAvailable download formats
    Dataset updated
    Feb 26, 2024
    Description

    This map service is provided by NC Department of Transportation and represents Municipal Boundaries defined through the Powell Bill 2023.This data was created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System. Municipal boundaries are recognized as a base cartographic layer for location analysis. The data are current for fiscal year 2023.These Municipal Boundaries data are based on the Powell Bill Program maps for the 2023 fiscal year. Municipalities in North Carolina that participate in the Powell Bill Program are required to submit to NCDOT on a regular basis. These data include incorporated municipalities in North Carolina that participate in the Powell Bill Program. Boundaries of municipalities which do not participate in the Powell Bill Program are also included in this data. Sources for the boundaries vary in scale and format as provided by the Municipalities.Additional metadata: GIS Data Layers (ncdot.gov)

  20. l

    City Boundaries Lines

    • data.lacounty.gov
    • geohub.lacity.org
    • +1more
    Updated Oct 8, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    County of Los Angeles (2020). City Boundaries Lines [Dataset]. https://data.lacounty.gov/datasets/city-boundaries-lines
    Explore at:
    Dataset updated
    Oct 8, 2020
    Dataset authored and provided by
    County of Los Angeles
    Area covered
    Description

    This line feature layer contains Legal City boundaries within Los Angeles County.

    The principal attribute is BDRY_TYPE which represents the boundary feature types. Use its values below for definition queries and layer symbology for your mapping needs.

    Coast - This value represents the coastline. This data is carefully maintained by DPW staff, based Los Angeles Region Imagery Acquisition Consortium data.

    Land City - This value represents city boundaries on land.

    Land County - This value represents the county boundary on land.

    Pier - One example is the Santa Monica Pier. Man-made features may be regarded as extensions of the coastline.

    Breakwater - Examples include the breakwater barriers that protect the Los Angeles Harbor.

    Water - This value is used to separate features representing internal navigable waters and the ocean. Examples of internal waters are found in the Long Beach Harbor and in Marina del Rey.

    Ocean - This value is used to represent ocean boundaries between cities in addition to the seaward boundaries of coastal cities. Per the Submerged Lands Act, the seaward boundaries of coastal cities and unincorporated county areas are three nautical miles (a nautical mile is 1852 meters) from the coastline.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
California Department of Tax and Fee Administration (2015). City and County Boundary Line Changes [Dataset]. https://gis.data.ca.gov/maps/93f73ae0070240fca9a4d3826ddb83cd
Organization logo

City and County Boundary Line Changes

Explore at:
Dataset updated
Mar 6, 2015
Dataset authored and provided by
California Department of Tax and Fee Administrationhttp://cdtfa.ca.gov/
License

MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically

Area covered
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).

Search
Clear search
Close search
Google apps
Main menu