Overpass API developpement

[mmd <>]

Hi,

Am 14.11.2015 um 20:30 schrieb michael spreng:

>  Yes that is an option. 

That's fantastic!

> But I would prefer that overpass supports
> the history file. So I might also try to make that work directly. This
> will be time consuming either way.

The rationale behind my approach was: we already know that Overpass can
handle .osc files to update the database today. Also, .osc files are
quite easy to understand and we can validate any .osc file based on a
full history without much effort. I would also assume that writing a
tool based on libosmium is not rocket science. It just takes some time
to get familiar with the API. Also, limiting the size of an .osc file is
not too difficult, giving us full control on the memory consumption side
as well. And the best thing: we don't have to touch any existing
Overpass coding to make this happen.

On the other hand, processing full history files in Overpass API is a
very special use case, and the update process is already extremely
complex anyway. I suggest to take a look at the respective *_updater.*
files in the osm-backend directory to get a first impression. Squeezing
in yet another file format is likely to introduce a lot of additional
complexity and will likely break the whole thing (at least if I would
try to do it). Before starting any activities in that direction I'd
definitively recommend to discuss this in detail with Roland.


> 
> And a few weeks ago I thought I'm so close to getting it to work :)
> 


hmmm... I know exactly what you're talking about ;)

cheers

--