GIScience / ohsome-api

API for analysing OpenStreetMap history data
https://api.ohsome.org
GNU Affero General Public License v3.0
47 stars 8 forks source link

Give hint how to get access to data within some named area #244

Open matkoniecz opened 3 years ago

matkoniecz commented 3 years ago

Use Case Description

Overpass turbo has amazing feature that allows to query for things like "amenity=atm in Poland"

I want to do the same in ohsome (hoping that it is more efficient for such queries, trying to do this for all countries on Overpass is straining it and requires waiting a lot for quota respawn)

Request Description

From what I see in https://api.ohsome.org/v1/swagger-ui.html#/ https://heigit.org/farm-shops-are-ohsome/ https://heigit.org/how-to-become-ohsome-part-1-visualizing-the-historical-evolution-of-osm-buildings-of-your-city/ ohsome both allows and requires to specify arbitrary boundaries.

It may allow some interesting queries, but is there some reasonable way to get country boundary? Both in detail sufficient to avoid significant inaccuracies and simplified enough to not crash ohsome servers?

I looked also through the entire https://github.com/GIScience/ohsome-api#ohsome-api and through https://heigit.org/exploring-osm-history-the-example-of-health-related-amenities/ (pity that no reproduction source code was provided), https://docs.ohsome.org/ohsome-api/v1/boundaries.html (I really hoped to find something there)

Additional Information

I am trying to implement fix for https://github.com/streetcomplete/StreetComplete/issues/3202 and workaround for https://github.com/Sophox/sophox/issues/27

matkoniecz commented 3 years ago

https://ohsome.org/apps/dashboard/ has country boudaries, but it is not clear how to import them/recreate them

matkoniecz commented 3 years ago

https://heigit.org/ohsome-region-of-the-month-august/ has

For sending requests to the ohsome API you need input boundaries first, be it a GeoJSON (bpolys) or the coordinates of a region of interest (bboxes). As usual, we sent a “bpolys-request” and got our data from osm-boundaries.

!

I would consider making it a bit more prominent - at least mentioning it in https://docs.ohsome.org/ohsome-api/v1/boundaries.html

Maybe even directly in the readme.

bonaparten commented 3 years ago

You can find two issues related to that here: #30 and #219. You are probably right, we could provide a link to osm-boundaries (the website is not related to us) and we should provide at least an example of a query using a GeoJSON file with CURL in our documentation.