[mkgmap-dev] mkgmap can't handle multiple <bounds> elements generated by JOSM
From Mark Burton markb at ordern.com on Sun Jul 5 16:29:37 BST 2009
On Sun, 5 Jul 2009 11:42:03 +0000 Ævar Arnfjörð Bjarmason <avarab at gmail.com> 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:) > > 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. mkgmap --help=options says: --ignore-osm-bounds When reading OSM files, ignore any "bounds" elements. Cheers, Mark
- Previous message: [mkgmap-dev] Re: [josm-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