Planet Earth Open Map Data

Published on May 15, 2023
Updated on September 11, 2024

The data is based on OpenStreetMap and enriched with third party sources. It is organised across eleven themes. Each theme is organised by classes and subclasses. You can drill down from the theme into the classes and from there into subclasses.

  • Administrative: This data set contains the polygons for administrative boundaries at different levels. It includes the name of the administrative area, the quadkey, and the geo coordinates.
  • Building: Contains the type of building and its surface area.
  • Building Detail: Contains additional information on buildings such as building material, construction type, building colour, roof shape and materials used
  • Infrastructure: The infrastructure theme contains information on infrastructure such as bridges, towers, communication (cell towers etc), power stations, towers.
  • Land: The land theme contains information such as forests, volcanoes, grass, wetland etc.
  • Landuse: The landuse theme contains information on the way land is used, e.g. for entertainment, commercial, agriculture etc. purposes.
  • Placename: This theme includes named locations from cities, towns, villages etc.
  • POI: This theme includes points of interests such as amenities, restaurants, cinemas, schools etc.
  • Road: This theme set covers the road network, e.g. motorways, residential streets, cycle ways, national roads etc. It includes the length of road, its usage type, the speed limit and a lot more.
  • Transit: This theme covers airports, railways, and buses.
  • Water: This theme covers anything related to water such as oceans, rivers, lakes etc.

Views

Each theme is represented by a database View in the data set.

V_ADMINISTRATIVE

V_ROAD

V_POI

V_PLACENAME

V_BUILDING

V_LAND

V_LANDUSE

V_TRANSIT

V_INFRASTRUCTURE

V_WATER

V_BUILDING_DETAIL

We have compiled the data dictionary for three of the themes / Views in the data set

V_Administrative

Below is a list of the the most important columns in the Administrative table

ColumnDescription
IDUnique identifier of the form (n/w/r) + osm id + @ (osm version). Example, version 22 of node id=1 : n1@22
CLASSClass of the feature
SUBCLASSSubclass of the feature
QUADKEYThe zoom level 15 quadkey that contains the centroid of the feature.
NAMESJSON-formatted key/value pairs containing the place name in different languages. Keys include local (the common name used in the place) and ISO language codes like en, en-US, and de.
ORIGINAL_SOURCE_TAGSThis specifies the primary OSM id and its properties. JSON-formatted key/value pairs of original OSM tags
GEO_CORDINATESEither of the two lines of latitude and longitude whose intersection determines the geographical point of a place
DISPUTE_SOURCEActual source of the disputed boundary.
ADMIN_LEVELadmin level of the boundary (if a capital city)
BORDER_TYPEIs a key which has frequently been filled by automated data imports, and has also been approved to specify the type of maritime boundary.
DISPUTED_NAMEThis specifies the disputed boundary names.
WIKIDATAWikidata ID (if present)
DESIGNATIONDesignation is used to record the legal classification of an object such as unclassified_county_road, permissive_footpath etc.
CLAIMED_BYThis specify the parties who claim the boundary
BOUNDARYThis shows the type of the administrative boundary
CONTROLLED_BYThis specify the party that actually controls the boundary
DISPUTED_BYThis specify the parties who dispute the boundary
RECOGNIZED_BYThis specifies the administrative boundary is recognised by which country.

V_Road

Below is a list of the most important columns in the Road table and a description

COLUMNSDESCRIPTION
IDUnique identifier of the form (n/w/r) + osm id + @ (osm version). Example, version 22 of node id=1 : n1@22
CLASSClass of the feature e.g. motorway, pedestrian, parking etc. It is the superset of the subclass.
SUBCLASSSubclass of the feature. Such as motorway_link belongs to motorway class.
QUADKEYThe zoom level 15 quadkey that contains the centroid of the feature.
NAMESJSON-formatted key/value pairs containing the place name in different languages. Such as Prince Of Wales Drive in English, promenade Prince Of Wales in French.
GEO_CORDINATESEither of the two lines of latitude and longitude whose intersection determines the geographical point of a place
MAXSPEEDValue of maxspeed
SURFACEValue of Surface such as unpaved, asphalt, paved etc.
IS_TUNNELTrue if tunnel in (building_passage, covered, yes)
LANESValue of lanes
LEVELValue of level
IS_COVEREDTrue if covered=yes
IS_ONEWAYTrue if oneway in (yes, 1) and false if oneway=no
LENGTH_MLength of feature in meters (if a line)
IS_PEDESTRIANTrue if (foot is not NULL and foot != no) or (bicycle is not NULL and bicycle != no)
IS_BRIDGETrue if bridge in (aqueduct, boardwalk, cantilever, covered, low_water_crossing, movable, trestle, viaduct, yes)
SURFACE_AREA_SQ_MArea of the feature in square metres (if a polygon)

V_POI

ColumnDescription
IDUnique identifier of the form (n/w/r) + osm id + @ (osm version). Example, version 22 of node id=1 : n1@22
CLASSClass of the feature
SUBCLASSSubclass of the feature
QUADKEYZoom level 15 quadkey (Bing Tile) that contains this feature.
NAMESLocal name of the point of interest
ORIGINAL_SOURCE_TAGSThis specifies the primary OSM id and its properties. JSON-formatted key/value pairs of original OSM tags
GEO_CORDINATESEither of the two lines of latitude and longitude whose intersection determines the geographical point of a place
AMENITYThe value of the amenity tag.
BUILDING_LOCATIONThis provides the building location such as coordinates, GPS location, street address etc.
SHOPValue of shop tag in source
HEIGHT_MHeight in meters: value of height in source if present (converted if in feet), or building:levels * 3.42 (a default height for one level)
WIKIDATAWikidata ID (if present)
IS_AREATrue/False if this point is the centroid of an OSM polygonal feature
BUILDING_LEVELSThe building:levels tag is used for marking the number of above-ground levels of a building ( building =*) or part of a building ( building:part =*). The underground levels and the roof do not count as levels here. However, levels that are part-way underground do count.
IS_BUILDINGTrue/False/Name of building type
TOURISMValue of tourism tag in source
LAYERValue of layer tag in source
MIN_HEIGHT_MMinimum height in meters: value of min_height in source if present, or building:min_level * 3.42 (a default height for one level)
SURFACE_AREA_SQ_MArea of feature in square metres (if a polygon)

Use cases and sample Queries

Use cases

Logistics and supply chain management: Road data can be used to analyse transportation routes and optimise delivery schedules.

Urban planning: Road data can be used to analyse the accessibility of different neighbourhoods and identify areas with inadequate transportation infrastructure.

Real estate: Road data can be used to analyse the impact of road proximity and traffic noise on property values.

Market analysis: Administrative boundary data can aid in market analysis by segmenting markets based on geographical regions.

Trade area analysis: The data can be used to define trade areas around existing stores or business locations.

Store location analysis: The data can aid businesses in determining optimal locations for new stores or branch offices

Service coverage analysis: Infrastructure data can be utilised to assess service coverage areas for communication networks.

Real estate market analysis: Building data, particularly square metre footage, is crucial for assessing property values and conducting market analysis.

Location-based marketing: Amenity data can be used for location-based marketing campaigns. By analysing the distribution of amenities, businesses can target their marketing efforts to specific areas based on the presence of relevant amenities.

Retail site selection: Amenity data is valuable for retail site selection.

Property valuation and rental pricing: Amenity data can be used in property valuation and rental pricing analysis.

Sample queries

POI density

We want to analyse which area has the highest density of POIs.

We can use the quadkey in the POI theme to count the number of fast food restaurants per quadkey and then plot them on a map.

For this query we use quadkeys at zoom level 15.

Road network analysis

We will analyse the road network in the London boroughs of Camden and Croyden.

The following query will return the geo coordinates for both of those London boroughs

In a next step we can lookup the various classes and subclasses of roads from the ROAD table against the geo coordinates of Camden and Croyden.

We want to compare the types of roads that exist in both boroughs and the length in metres of the road network in each.

Building analysis

Comparing the types of building and square metres between the London boroughs of Camden and Croyden.

Infrastructure analysis

Analyse the number of bridges, power stations, communication facilities between the London boroughs of Camden and Croyden