[mkgmap-dev] Re: [josm-dev] mkgmap can't handle multiple <bounds> elements generated by JOSM
From Shaun McDonald osm at shaunmcdonald.me.uk on Sun Jul 5 13:08:05 BST 2009
On 5 Jul 2009, at 12:42, Ævar Arnfjörð Bjarmason wrote: > I was generating a map of Potsdam with mkgmap from an .osm file which > I had produced by making multiple API requests in JOSM as no extract > was available (and XAPI is down). > > This resulted in a JOSM .osm file with multiple bounds elements. > mkgmap couldn't handle this and clipped the map to one of them > (presumably the first one) so my generated map showed only a part of > the area I had data for. > > Maybe multiple <bounds> elements are invalid, or maybe mkgmap should > handle them. I can't find it on the wiki so you guys figure it out:) Multiple changesets are not invalid. They are used by the update data command to know where to redownload the data into JOSM. mkgmap, should probably ignore them, or take all of them into about, rather than just one of them. Shaun > > For reference I'm attaching the changes I made to my .osm file to make > it work, which consisted of removing all the <bounds> elements. > <remove-bounds-from- > potsdam.patch>_______________________________________________ > josm-dev mailing list > josm-dev at openstreetmap.org > http://lists.openstreetmap.org/listinfo/josm-dev
- Previous message: [mkgmap-dev] mkgmap can't handle multiple <bounds> elements generated by JOSM
- Next message: [mkgmap-dev] mkgmap can't handle multiple <bounds> elements generated by JOSM
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list