Hi, They said that they disabled Api V0.5 since JOSM r7013 because V0.6 is out since 2009 and there should be no reason to still support V0.5.
See https://josm.openstreetmap.de/ticket/9975 osmconvert is a good option. From my point of view it would be also ok to stay at V0.5 and add the osmconvert workaround to the documentation. Von meinem iPad gesendet > Am 26.02.2016 um 08:23 schrieb Gerd Petermann > <[email protected]>: > > Hi Michael, > > > yes, JOSM seems to expect metainfo (version, userid, last change timestamp) > and fails to read > a pbf file without that info. No idea why, but I've added a workaround in > splitter r428 right now. > > > I was not aware that JOSM requires version 0.6 now, how crazy is that ? > Instead of using an editor you can use osmconvert: > > osmconvert --fake-version <input-file> -o=output.osm > > I hesitate to change splitter in this case because the extra information > increases the osm.gz files > > by ~2% . I'd first like to understand why JOSM doesn't allow api version 0.5 > anymore. > > > Gerd > > > > > Von: [email protected] > <[email protected]> im Auftrag von Michael Schlenstedt > <[email protected]> > Gesendet: Freitag, 26. Februar 2016 07:38 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] when I use SPLITTER to IMPORT om.pbf files into > JOSM I get error > > Hi Gerd, > > I also struggled around with this incompatibility splitter/JOSM. I used > XML-files, but JOSM does not support API V0.5 for quite a while now, and > splitter still produces v0.5 XML files. > > Dirty Workaround: I open all yml-file in an editor, changed Line 2 into "osm > version='0.6'" and add "version='1'" to all id-instances. For VIM: :%s/ id='/ > version='1' id='/g > > Maybe that's also the reason why JOSM doesn't like the PBF-files... > > Regards, > Michael > > >> Am 25.02.2016 um 23:46 schrieb Gerd Petermann: >> Gerd Petermann wrote >> > Hi Greg. >> > >> > >> > You can use osmconvert which should be able to read the output of >> > splitter, e.g. >> > >> > osmconvert 12360002.osm.pbf -o=12360002-josm.osm.pbf >> >> Sorry, was too quick. >> You probably need option --fake-version for osmconvert: >> osmconvert --fake-version 12360002.osm.pbf -o=12360002-josm.osm.pbf >> >> I think that's the reason for the problem: JOSM doesn't like input >> in pbf format that doesn't have the meta info (version, author etc) >> >> I never cared about that because I use o5m format and an o5m plugin that >> I wrote once for JOSM. It is not in the plugins repo, but I may try again to >> add >> it there. >> >> A 3rd alternative is to use --output=xml in splitter, the files in that >> format are >> no problem in JOSM, but may decrease performance in splitter and mkgmap. >> >> Gerd >> >> >> >> >> -- >> View this message in context: >> http://gis.19327.n5.nabble.com/when-I-use-SPLITTER-to-IMPORT-om-pbf-files-into-JOSM-I-get-error-tp5868501p5868511.html >> Sent from the Mkgmap Development mailing list archive at Nabble.com. >> _______________________________________________ >> mkgmap-dev mailing list >> [email protected] >> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
