mkgmap can't handle multiple <bounds> elements generated by JOSM
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.
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@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
On Sun, 5 Jul 2009 11:42:03 +0000 Ævar Arnfjörð Bjarmason <avarab@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
Hi
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.
Yes the current behaviour is never what anyone expects. I am want to change the behaviour so that the bounds are ignored if there is more than one bounds element. The bounds cutting is specifically for tiling and so it is unnecessary for random downloaded areas such that you might get from JOSM. There are other things that could be done, so if anyone has any arguments either way let me know. ..Steve
IMHO the multiple bounds should be 'merged', ie. all content inside any of the bounds should be included in the img file. This would allow to define more complexe shapes which are not rectangles. It is not a must have feature, but this is, was I would expect to happen when more than one boundraries are given. Regards, Johann Steve Ratcliffe schrieb:
Hi
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.
Yes the current behaviour is never what anyone expects. I am want to change the behaviour so that the bounds are ignored if there is more than one bounds element.
The bounds cutting is specifically for tiling and so it is unnecessary for random downloaded areas such that you might get from JOSM.
There are other things that could be done, so if anyone has any arguments either way let me know.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev .
participants (5)
-
Johann Gail -
Mark Burton -
Shaun McDonald -
Steve Ratcliffe -
Ævar Arnfjörð Bjarmason