[OSM-dev] OSM export incompatibilities between JOSM and Merkaartor

Chris Browet cbro at semperpax.com
Sat Sep 20 15:05:05 BST 2008


2008/9/20 Frederik Ramm <frederik at remote.org>

> in http://trac.openstreetmap.org/ticket/1163, a user complains rightfully
>> that the OSM exports from JOSM and Merkaartor are incompatibles, due to the
>> fact that JOSM is using pure numeric IDs while Merkaartor is using text GUID
>> for not-yet-uploaded objects.
>>
>
> If an object is newly created, it will have a negative id.


Ok, thanks.

>
> I don't want to sound too patronising but until now I thought that the way
> JOSM does it was a kind of established standard (which is, to the best of my
> knowledge, also shared by bulk uploaders, i.e. you can use a JOSM-saved file
> and throw it to a bulk uploader and it will all turn out nicely).


I'm afraid you definitely sound like patronizing a tiny little... I we all
had stuck to "established standards", we'd all still use Windows and .doc,
wouldn't we...

Whatever, I think you missed the point. I'm speaking about stateless OSM,
i.e. like downloaded from openstreetmap.org, just with IDs not yet in the
DB, not statefull, for which we have something completely different (.MDC,
which includes layers, tracks, full undo/redo, etc... Sorry for the
"standard").

The OSM Merkaartor generates is not for uploading, but for
transport/extract.
Actually, I don't see much point to export OSM with not-uploaded data from
Merkaartor, but, well, if it could be of some use to OSM mappers, I'm glad
to help them.

Anyway, I'll do the one-liner for JOSM OSM to be handled without errors in
Merkaartor and create a separate ticket for being able to import your
statefull format.
Unless some Merkaartor dev wants to support exporting the full JOSM OSM,
I'll then transfer the Trac ticket to you. You'll then be absolutely be free
to "wontfix" it.

Regards
- Chris -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20080920/63fbd521/attachment.html>


More information about the dev mailing list