[OSM-dev] Acceptable use of Overpass API?

Peter graphhopper at gmx.de
Fri Apr 17 07:18:00 UTC 2015

Hi Nick,

the recommended GraphHopper-way is to prepare graphhopper files for an
area and setup a server which hosts that files. Another more
developer-intense approach would be to have the complete graph already
loaded and then create such 10x10km slices on-demand. Personally I would
suggest to avoid triggering Overpass API for such bulk requests or setup
your own servers with that API.

What I do not understand: if the user has online access why would you
need the full graphhopper files on the device? Why not use e.g. our
Directions API or host your own graphhopper server? This way the user
just needs a very small path to download and you avoid hitting the
Overpass API.


On 16.04.2015 20:22, Nick Whitelegg wrote:
> Hi,
> As a few of you might know I am developing an augmented reality
> hikers' app for Android. As part of this I would like to develop route
> finding (including AR signposts) facilities, using GraphHopper.
> However I don't want users to have to download a huge OSM or
> GraphHopper file covering the whole of England and Wales: I would
> prefer users to download small tiles of OSM data (say 10km x 10km) of
> their local area, which could then be cached on their device. The
> conversion to GraphHopper format could be done on the device.
> Overpass seems good for this: the usage policy suggests up to 10000
> hits/day is acceptable. I can't see more than a small number of people
> using the app for now: furthermore I could route requests through a
> proxy on my own server which ensures that no more than 5000 (to be
> safe) requests to Overpass per day are made.
> Does this sound an acceptable use of the Overpass API?
> Thanks,
> Nick
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20150417/652cc952/attachment.html>

More information about the dev mailing list