[mkgmap-dev] mkgmap can't handle multiple <bounds> elements generated by JOSM

Sun Jul 5 17:17:13 BST 2009

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