[josm-dev] [OSM-dev] OSM export incompatibilities between JOSM and Merkaartor
frederik at remote.org
Sat Sep 20 16:06:37 BST 2008
Chris Browet wrote:
> Whatever, I think you missed the point. I'm speaking about stateless
> OSM, i.e. like downloaded from openstreetmap.org
> <http://openstreetmap.org>, just with IDs not yet in the DB, not
So let me get this right - when you download data from OSM into
Merkaartor, and then make a few edits, you will then have the choice of
saving your session "stateful" in a special format, or "stateless" in an
format that is almost like OSM XML, just with occasional non-numeric
So anyone who wants to continue editing in Merkaartor will choose the
"stateful" format because it provides much more edit metadata. Correct?
The "stateless" format is only there so that the data in the editor can
be exported to other applications that expect OSM XML as their input
(e.g. scripts, renderers, JOSM, ...) without uploading it first. Correct?
Then the fact that JOSM cannot work with these files currently is only a
small piece of the problem - neither will, for example, Osmosis, Mapnik,
or any of a number of Perl scripts in the repository that assume the
object ID to be numeric. (I'm not 100% sure which software actually
makes the "numeric" assumption and which doesn't. I believe Osmarender
would possibly work with non-numeric IDs also.) - What, then, *is* the
current use case for your stateless export format if it cannot be
processed by most applications anyway?
Frederik Ramm ## eMail frederik at remote.org ## N49°00'09" E008°23'33"
More information about the josm-dev