[OSM-dev] traces, export, download and update

Peter Gervai grinapo at gmail.com
Fri Jan 6 22:27:43 GMT 2012

On Thu, Jan 5, 2012 at 20:40, Tom Hughes <tom at compton.nu> wrote:
> On 05/01/12 17:59, Peter Gervai wrote:
>> On Thu, Jan 5, 2012 at 17:06, Tom Hughes<tom at compton.nu>  wrote:
>> Apart from that is there any plans to implement differential retrieval
>> (I'm sure I'm not alone with this) and listing only the trace id's of
>> a bounding box?
> The plan is just to provide a dump - if other people want to build clever
> tools on top of that data then that's fine.

Hmm, what I meant was that JOSM uses the API to retrieve map data and
traces and trace retrieval is horribly slow. Since old traces never
change it would be pretty easy to use a local cache and a
highwatermark to retrieve only the new ones.

Of course it's rather easy to create an external tool from the dump
but then JOSM should use that external tool. Probably not a problem
for the developers but sounds funny to retrieve the "official" traces
from somewhere else.

> IIRC the dump contains an index that lists all the public traces, along with
> the original data file for them (not an extract from the database) plus a
> single file containing all the non-public points (extracted from the
> database).

Sounds good. I hope someone would find some time to actually install
it and generate the dumps.


More information about the dev mailing list