Mature Support Notice: This item is in mature support as of December 2024. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. See blog for more information.This web map presents a vector basemap of OpenStreetMap (OSM) data hosted by Esri. It provides a reference layer featuring map labels, boundary lines, and roads and includes imagery. Created from the sunsetted Daylight map distribution, data updates supporting this layer are no longer available.OpenStreetMap is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap site: www.OpenStreetMap.org. Esri is a supporter of the OSM project. Precise Tile Registration: The web map uses the improved tiling scheme “WGS84 Geographic, Version 2” to ensure proper tile positioning at higher resolutions (neighborhood level and beyond). The new tiling scheme is much more precise than tiling schemes of the legacy basemaps Esri released years ago. We recommend that you start using this new basemap for any new web maps in WGS84 that you plan to author. Due to the number of differences between the old and new tiling schemes, some web clients will not be able to overlay tile layers in the old and new tiling schemes in one web map.

Mature Support Notice: This item is in mature support as of December 2024. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. See blog for more information.This tile layer presents a vector basemap of OpenStreetMap (OSM) data hosted by Esri. It provides a reference layer featuring map labels, boundary lines, and roads. This layer is designed to be overlaid on imagery. Created from the sunsetted Daylight map distribution, data updates supporting this layer are no longer available.OpenStreetMap is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap site: www.OpenStreetMap.org. Esri is a supporter of the OSM project. Precise Tile Registration: The tile layer uses the improved tiling scheme “WGS84 Geographic, Version 2” to ensure proper tile positioning at higher resolutions (neighborhood level and beyond). The new tiling scheme is much more precise than tiling schemes of the legacy basemaps Esri released years ago. We recommend that you start using this new basemap for any new web maps in WGS84 that you plan to author. Due to the number of differences between the old and new tiling schemes, some web clients will not be able to overlay tile layers in the old and new tiling schemes in one web map.

This web map presents a vector basemap of OpenStreetMap (OSM) data hosted by Esri. Esri created this vector tile basemap from the Daylight map distribution of OSM data, which is supported by Facebook and supplemented with additional data from Microsoft. It provides a reference layer featuring map labels, boundary lines, and roads and includes imagery. The OSM Daylight map will be updated every month with the latest version of OSM Daylight data. OpenStreetMap is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap site: www.OpenStreetMap.org. Esri is a supporter of the OSM project and is excited to make this enhanced vector basemap available to the ArcGIS user and developer communities.

OpenStreetMap is a source of physical boundary data, including global coastlines that are maintained and refined by OpenStreetMap contributors. These high-quality geographical datasets are processed and regularly updated to provide accurate representations of Earth's physical features, making them suitable for mapping, research, and analysis across a wide range of applications.

These datasets contain OpenStreetMap data related to the Refugee Response in northern Uganda. Data model coordinated with UNHCR. The source is surveys and mapping in northern Uganda performed by HOTOSM and partners.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

refugee = 'yes' AND boundary = 'refugee_camp' OR boundary = 'administrative' OR landuse = 'residential'

Features may have these attributes:

• official_name
• operator:type
• loc_name
• admin_level
• start_date
• population
• access
• name
• type
• place
• name:en
• boundary
• landuse
• capacity
• operator
• refugee

This dataset is one of many "https://data.humdata.org/organization/hot">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

Administrative boundaries of countries inside the Baltic Sea catchment area. The source is Open Street Maps data downloaded from OSM Boundaries Map (https://wambachers-osm.website/boundaries/)

Here we produced the first 10 m resolution urban green space (UGS) map for the main urban clusters across 371 major Latin American cities as of 2017. Our approach applied a supervised classification of Sentinel-2 satellite imagery and UGS samples derived from OpenStreetMap (OSM). The overall accuracy of this UGS map in 11 randomly selected cities was 0.87, evaluated by independently collected validation samples (‘ground truth’). We further improved mapping quality through a visual inspection and additional sample collection. The resulting UGS map enables studies to measure area, spatial configuration, and human exposures to UGS, facilitating studies about the relationship between UGS and human exposures to environmental hazards, public health outcomes, and environmental justice issues in Latin American cities.UGS in this map series includes grass, shrub, forest, and farmland, and non-UGS included buildings, pavement, roads, barren land, and dry vegetation.The UGS map series includes three sets of files:(1) binary UGS maps at 10 m spatial resolution in GEOTIFF format (UGS.zip), with each of the 371 cities being an individual map. Mapped value of 1 indicates UGS, 0 indicates non-UGS, and no data (with value of -32768) indicates areas outside the mapped boundary or water bodies;(2) a shapefile of mapped boundaries (Boundaries.zip). The boundary file contains city name, country name and its ISO-2 country code, and an ID field linking each city's boundary to the corresponding UGS map.(3) .prj files containing projection information for the binary UGS maps and boundary shapefile. The binary UGS maps are projected with World Geodetic System (WGS) 84 / Pseudo-Mercator projected coordinate system (EPSG: 3857), and the boundary shapefile is projected with WGS 1984 geographic coordinate system (EPSG: 4326)Reference: A 10 m resolution urban green space map for major Latin American cities from Sentinel-2 remote sensing images and OpenStreetMap, published by Scientific Data [link].Citation: Ju, Y., Dronova, I., & Delclòs-Alió, X. (2022). A 10 m resolution urban green space map for major Latin American cities from Sentinel-2 remote sensing images and OpenStreetMap. Scientific Data, 9, Article 1. https://doi.org/10.1038/s41597-022-01701-y

OpenStreetMap is a source of physical boundary data, including global coastlines that are maintained and refined by OpenStreetMap contributors. The coastline is handled somewhat differently than most other features in OSM, and marked with the tag natural=coastline. These features are required to connect end-to-end to form an unbroken line around every island and every continent and the land always has to be on the left side, the water on the right side of those lines.

Description To allow a certain town to be "routable" for pedestrians, map data needs to contain information about streets, turns, intersections, lanes, street lines and pedestrian crossings. This dataset is based on raw data exported from OpenStreetMap. The dataset was fetched from within the following geographical boundaries: Minimal latitude: '41.254323' Minimal longitude: '1.4459896' Maximal latitude: '41.2938497' Maximal longitude: '1.5289021' After pre-processing, processing and verification, this dataset contains 2180 nodes representing a certain address in the given geographic area. All these nodes are confirmed to be reachable by foot (no isolated "islands"). The whole road network is confirmed to be traversable by routing software. # Type Collected & Generated # Nature OpenStreetMap .osm (XML) # Origin OpenStreetMap project by the OpenStreetMap Foundation (OSMF) & Tunnll # License: The data is provided under the Open Data Commons Open Database License (ODbL) where the users are free to copy, distribute, transmit and adapt the data, as long as they credit OpenStreetMap and its contributors. Tunnll does not add any additional clauses to this generated dataset except the requirements to credit Tunnll’s refinements and updates to the dataset.

Consistency between the IRIS polygons of 2013 IRIS contours and the limits of OpenStreetMap municipalities simplified to 5m. https://www.data.gouv.fr/s/resources/decoupage-iris-combine-aux-limites-communales-openstreetmap/20150717-001326/Screenshot_-_17072015_-_000646.png" alt="In green the municipal boundaries OSM (added). In grey the municipal boundaries IGN (deleted). In orange, the boundaries of IRIS IGN (preserved)" title="IRIS Contours & Communes OpenStreetMap"> The infra-municipal limits of IRIS are unchanged from the IGN/INSEE source. IRIS boundaries corresponding to communal boundaries are taken from the OpenStreetMap source, and IRIS are adapted accordingly.

The use of this cutting with precisely geocoded data (by number) makes it possible to keep a coherence between the municipality of implementation of the geocoded point and iris code, which does not offer the source Contours IRIS whose municipal boundaries are very simplified.

The attributes of the original IRIS Contours polygons are preserved in the resulting layer, with the exception of common names, taken from the OpenStreetMap source.

Format of the proposed layer - Delivery unit France - Lambert 93 projection system (EPSG:2154) - Format ESRI Shapefile

The research data to characterizing Territorial Disputes, including comparing data of boundaries.

Ce jeu de données propose une extraction quotidienne des flux de données OpenStreetMap relatives aux limites administratives et territoriales sur les territoires de Provence-Alpes-Côte d’Azur, Occitanie, Auvergne-Rhône-Alpes, ainsi que les régions frontalières en Italie : Ligurie, Piémont, Vallée d’Aoste. Les données extraites concernent les éléments cartographiques associés à la clé boundary d’OpenStreetMap, qui décrit les frontières administratives telles que les communes, départements, régions, mais aussi les limites naturelles ou fonctionnelles selon les cas. Les spécifications suivies sont celles décrites dans la documentation d’OpenStreetMap : 🔗 wiki.openstreetmap.org/wiki/Key:boundary Le traitement et l’extraction des données sont réalisés à l’aide du script Lua disponible sur le dépôt GitLab de DataSud : 🗃️ datasud.lua © Contributeurs de OpenStreetMap.

Honduras administrative level 0-2 boundaries

PLEASE REFER TO THE CAVEATS ABOUT THE ADMINISTRATIVE LEVEL 3 DATA.

24 NOVEMBER UPDATES: Due to the structural inconsistency of the best available administrative level 3 boundary information it has been removed from the standard gazetteer, shapefile, geodatabase, web service, and EMF resources and P-coding of populated places resource. HOWEVER a shapefile and EMF file of the original administrative level 3 boundaries is still included in this dataset. Please see the caveats below for specific information.

Note that a [Honduras Open Street Map populated places dataset is available here](https://data.humdata.org/dataset/cod-ps-hnd).

Vetting and live service provision by Information Technology Outreach Services (ITOS) with funding from USAID.

These boundaries are suitable for database or GIS linkage to the Honduras - Subnational Population Statistics tables.

This layer contains administrative boundaries extracted from OpenStreetMap data using proprietary enhancements.

Geodata on the borders of all regions of Russia is collected using the website OSM-Boundaries. OSM-Boundaries, in turn, retrieves information from OpenStreetMap. To download the data, you will need to log into your OpenStreetMap account.

For my project, I specifically needed data on the borders of Russia, but you can visit the site via the link and download the necessary information for free. You can choose different border levels, countries, and objects on the map.

The data is stored in geojson format, you can view it in my notebook when working with them (via geopandas)

Note: 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 beginning 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.

Purpose
City 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 Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

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

Field and Abbreviation Definitions

• CDTFA_CITY: CDTFA incorporated city name
• CDTFA_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 Bureau
• CENSUS_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 System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• 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 county
• CENSUS_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.

This data is experimental, see the ‘Access Constraints or User Limitations’ section for more details. This dataset has been generalised to 10 metre resolution where it is still but the space needed for downloads will be improved.A set of UK wide estimated travel area geometries (isochrones), from Output Area (across England, Scotland, and Wales) and Small Area (across Northern Ireland) population-weighted centroids. The modes used in the isochrone calculations are limited to public transport and walking. Generated using Open Trip Planner routing software in combination with Open Street Maps and open public transport schedule data (UK and Ireland).The geometries provide an estimate of reachable areas by public transport and on foot between 7:15am and 9:15am for a range of maximum travel durations (15, 30, 45 and 60 minutes). For England, Scotland and Wales, these estimates were generated using public transport schedule data for Tuesday 15th November 2022. For Northern Ireland, the date used is Tuesday 6th December 2022.The data is made available as a set of ESRI shape files, in .zip format. This corresponds to a total of 18 files; one for Northern Ireland, one for Wales, twelve for England (one per English region, where London, South East and North West have been split into two files each) and four for Scotland (one per NUTS2 region, where the ‘North-East’ and ‘Highlands and Islands’ have been combined into one shape file, and South West Scotland has been split into two files).The shape files contain the following attributes. For further details, see the ‘Access Constraints or User Limitations’ section:AttributeDescriptionOA21CD or SA2011 or OA11CDEngland and Wales: The 2021 Output Area code.Northern Ireland: The 2011 Small Area code.Scotland: The 2011 Output Area code.centre_latThe population-weighted centroid latitude.centre_lonThe population-weighted centroid longitude.node_latThe latitude of the nearest Open Street Map “highway” node to the population-weighted centroid.node_lonThe longitude of the nearest Open Street Map “highway” node to the population-weighted centroid.node_distThe distance, in meters, between the population-weighted centroid and the nearest Open Street Map “highway” node.stop_latThe latitude of the nearest public transport stop to the population-weighted centroid.stop_lonThe longitude of the nearest public transport stop to the population-weighted centroid.stop_distThe distance, in metres, between the population-weighted centroid and the nearest public transport stop.centre_inBinary value (0 or 1), where 1 signifies the population-weighted centroid lies within the Output Area/Small Area boundary. 0 indicates the population-weighted centroid lies outside the boundary.node_inBinary value (0 or 1), where 1 signifies the nearest Open Street Map “highway” node lies within the Output Area/Small Area boundary. 0 indicates the nearest Open Street Map node lies outside the boundary.stop_inBinary value (0 or 1), where 1 signifies the nearest public transport stop lies within the Output Area/Small Area boundary. 0 indicates the nearest transport stop lies outside the boundary.iso_cutoffThe maximum travel time, in seconds, to construct the reachable area/isochrone. Values are either 900, 1800, 2700, or 3600 which correspond to 15, 30, 45, and 60 minute limits respectively.iso_dateThe date for which the isochrones were estimated, in YYYY-MM-DD format.iso_typeThe start point from which the estimated isochrone was calculated. Valid values are:from_centroid: calculated using population weighted centroid.from_node: calculated using the nearest Open Street Map “highway” node.from_stop: calculated using the nearest public transport stop.no_trip_found: no isochrone was calculated.geometryThe isochrone geometry.iso_hectarThe area of the isochrone, in hectares.Access constraints or user limitations.These data are experimental and will potentially have a wider degree of uncertainty. They remain subject to testing of quality, volatility, and ability to meet user needs. The methodologies used to generate them are still subject to modification and further evaluation.These experimental data have been published with specific caveats outlined in this section. The data are shared with the analytical community with the purpose of benefitting from the community's scrutiny and in improving the quality and demand of potential future releases. There may be potential modification following user feedback on both its quality and suitability.For England and Wales, where possible, the latest census 2021 Output Area population weighted centroids were used as the starting point from which isochrones were calculated.For Northern Ireland, 2011 Small Area population weighted centroids were used as the starting point from which isochrones were calculated. Small Areas and Output Areas contain a similar number of households within their boundaries. 2011 data was used because this was the most up-to-date data available at the time of generating this dataset. Population weighted centroids for Northern Ireland were calculated internally but may be subject to change - in the future we aim to update these data to be consistent with Census 2021 across the UK.For Scotland, 2011 Output Area population-weighted centroids were used as the starting point from which isochrones were calculated. 2011 data was used because this was the most up-to-date data available at the time of work.The data for England, Scotland and Wales are released with the projection EPSG:27700 (British National Grid).The data for Northern Ireland are released with the projection EPSG:29902 (Irish Grid).The modes used in the isochrone calculations are limited to public transport and walking. Other modes were not considered when generating this data.A maximum value of 1.5 kilometres walking distance was used when generating isochrones. This approximately represents typical walking distances during a commute (based on Department for Transport/Labour Force Survey data and Travel Survey for Northern Ireland technical reports).When generating Northern Ireland data, public transport schedule data for both Northern Ireland and Republic of Ireland were used.Isochrone geometries and calculated areas are subject to public transport schedule data accuracy, Open Trip Planner routing methods and Open Street Map accuracy. The location of the population-weighted centroid can also influence the validity of the isochrones, when this falls on land which is not possible or is difficult to traverse (e.g., private land and very remote locations).The Northern Ireland public transport data were collated from several files, and as such required additional pre-processing. Location data are missing for two bus stops. Some services run by local public transport providers may also be missing. However, the missing data should have limited impact on the isochrone output. Due to the availability of Northern Ireland public transport data, the isochrones for Northern Ireland were calculated on a comparable but slight later date of 6th December 2022. Any potential future releases are likely to contained aligned dates between all four regions of the UK.In cases where isochrones are not calculable from the population-weighted centroid, or when the calculated isochrones are unrealistically small, the nearest Open Street Map ‘highway’ node is used as an alternative starting point. If this then fails to yield a result, the nearest public transport stop is used as the isochrone origin. If this also fails to yield a result, the geometry will be ‘None’ and the ‘iso_hectar’ will be set to zero. The following information shows a further breakdown of the isochrone types for the UK as a whole:from_centroid: 99.8844%from_node: 0.0332%from_stop: 0.0734%no_trip_found: 0.0090%The term ‘unrealistically small’ in the point above refers to outlier isochrones with a significantly smaller area when compared with both their neighbouring Output/Small Areas and the entire regional distribution. These reflect a very small fraction of circumstances whereby the isochrone extent was impacted by the centroid location and/or how Open Trip Planner handled them (e.g. remote location, private roads and/or no means of traversing the land). Analysis showed these outliers were consistently below 100 hectares for 60-minute isochrones. Therefore, In these cases, the isochrone point of origin was adjusted to the nearest node or stop, as outlined above.During the quality assurance checks, the extent of the isochrones was observed to be in good agreement with other routing software and within the limitations stated within this section. Additionally, the use of nearest node, nearest stop, and correction of ‘unrealistically small areas’ was implemented in a small fraction of cases only. This culminates in no data being available for 8 out of 239,768 Output/Small Areas.Data is only available in ESRI shape file format (.zip) at this release.https://www.openstreetmap.org/copyright

Counties Ireland 1911: 34 counties which includes thirty two counties and two urban areas of Belfast and Dublin.This boundary has been generated by aggregation and dissolving boundaries based on common value of County code. Slivers and gaps removed in this processing.The boundaries established for these areas were created from scanned maps and some boundaries were provided from other organizations who previously worked on this. Areas stated on the census tables were used to quality check the areas of each DED. There is no singular and accurate source for mapping representation available - this map is a best effort and indicative of location only.A special thanks to the open source OpenStreetMap (OSM) for providing data for Northern Ireland, and also to Mike Murphy at UCC who provided a map of Ireland at DED level that we could use to reference boundaries.Taillte Éireann provided 1911 boundary maps to the CSO with the following disclaimer: "This cartographic data is a digital representation of the 1911 ED and Poor Law Union datasets. It is for display purposes only and legal boundaries past or present cannot and should not be inferred from this map."OpenStreetMap shapefiles were provided in accordance with their copyright requirements.Scanned copies of Census 1911 Original Reports : Area, houses and population are available here Implements CSO classificationsC04131V04897 - Census 1911 County Classification number

République Démocratiques du Congo, Limites des provinces (admin level 2)

DEDs can be aggregated to form what are known as Urban and Rural Districts (URDs). URDs were administrative divisions in Ireland created in 1899. There were 309 URD's in Ireland in 1911 . This boundary has been generated by aggregation and dissolving boundaries based on common value of URD code. Slivers and gaps removed in this processing.1911 District Electoral Division (DED) map of Ireland. In 2001, the names of DEDs changed to what are now known as Electoral Divisions. There were 3,673 DEDs in Ireland in 1911 and they are the smallest legally defined administrative areas in Ireland. The boundaries established for these areas were created from scanned maps and some boundaries were provided from other organizations who previously worked on this. Areas stated on the census tables were used to quality check the areas of each DED. There is no singular and accurate source for mapping representation available - this map is a best effort and indicative of location only.A special thanks to the open source OpenStreetMap (OSM) for providing data for Northern Ireland, and also to Mike Murphy at UCC who provided a map of Ireland at DED level that we could use to reference boundaries.Taillte Éireann provided 1911 boundary maps to the CSO with the following disclaimer: "This cartographic data is a digital representation of the 1911 ED and Poor Law Union datasets. It is for display purposes only and legal boundaries past or present cannot and should not be inferred from this map."OpenStreetMap shapefiles were provided in accordance with their copyright requirements.Scanned copies of Census 1911 Original Reports : Area, houses and population are available here Implements CSO classificationsC04057V04819 - Census 1911 Urban/Rural Areas Output ClassificationC04131V04897 - Census 1911 County Classification number