Introduction
A data block that provides vector layers from the free OpenStreetMap (OSM) database using the Overpass API.
See this block on the marketplace.
Technical information
Compatible blocks
- Count Objects
Geographic coverage
The geographic coverage is global.
Dataset information
| Specifications | Description |
|---|---|
| Data provider | OpenStreetMap |
| Map features | Water bodies, buildings, highways, towers, railways, shops, motels etc. The features are extracted based on OSM tags, which are made up of key-value pairs (highway=motorway). For more information: OSM Map Features. |
| Geometry type | Point MultiPoint LineString MultiLineString Polygon MultiPolygon |
| File format | GeoJSON The vector file(s) are based on the number of OSM tags and timestamps. |
| Coordinate system | WGS84/EPSG:4326 |
Map feature examples
| Key | Value | Description |
|---|---|---|
natural | wood | Forest |
natural | water | Inland water body |
highway | motorway | Equivalent to freeway, normally with 2 or more running lanes plus emergency hard shoulder. |
landuse | farmland | An area of farmland used for tillage. |
building | hotel | A building designed with separate rooms available for overnight accommodation. |
Limitations
The block does not support test queries or quicklooks.
How it works
| Supported JSON parameters | Default value | Min | Max | Examples |
|---|---|---|---|---|
bbox | null | n.a. | n.a. | Please check the examples from the JSON parameters. |
time | "2018-12-01T00:00:00+00:00/2021-12-31T23:59:59+00:00" | n.a. | n.a. | "2019-12-01T00:00:00+00:00/2019-12-31T23:59:59+00:00" |
osm_tags | "highway=*", "landuse=*", "natural=water", "building=*" | n.a. | n.a. | "osm_tags": [ "highway=motorway", "landuse=industrial", "natural=water", "building=farm"] |
time_series | null | n.a. | n.a. | "time_series": [ "2020-03-27T00:00:00+00:00/2020-04-02T00:00:00+00:00", "2019-09-30T00:00:00+00:00/2019-10-05T00:00:00+00:00", "2017-09-12T00:00:00+00:00/2017-09-20T00:00:00+00:00"] |
Good to know
The parameters time and/or time_series will only consider the end date for fetching the data. This behaviour is imposed because the changesets are not extensive within shorter periods of a few months. If a future date is supplied, the result will default to the latest available timestamp.
Examples
Example based on a workflow created with the data block OpenStreetMap:
Loading...
Capabilities
Output
vector
| custom | |
|---|---|
object_type | ${osm_tags} |
| up42_standard | |
|---|---|
format | GeoJSON |
geometry_type | {
"or": [
"MultiPoint",
"MultiLinestring",
"MultiPolygon",
"Polygon",
"Linestring",
"Point"
]
} |
To know more please check the block capabilities specifications.