[OSM-dev] how to make way and relation history less expensive

[Martin Koppenhoefer]

2012/10/17 Roland Olbricht <roland.olbricht at gmx.de>:
> The solution to an API overload is always: use an appropriate third party tool. In this case for example:
>
> https://github.com/MaZderMind/osm-history-splitter
>
> If you want to make a good service to the community then please make the splitted files publicly accessible on some server.


OK, but besides of reducing the load on the API the suggested
behaviour would also be more clearly laid out, at least for everything
that is not quite small. You won't usually look in detail at a list of
tens or hundreds of nodes and multiplied by every single version (and
maybe hundreds of versions).

cheers,
Martin