Yes, I agree this will lead to problems and it would be better if mkgmap also recognize and skips processing the overview img and other index img's (*_mdr.img) before compiling img tiles.
it might be there if you execute mkgmap twice, once with *.osm as input, next time with *.img I am not sure yet if the other combiner options like --gmapsupp, --index etc. have problems with this.
Gerd
Minko-2 wrote
Hi Gerd,
Well, the point is that a default overview file has to be made out of those img's, so it wont be there yet.
it is quite easy to exclude the ovm_* files, but you can have similar problems with other files like the default overview file osmmap.img. I am not sure what to do in this case, as the name is configurable.
@Steve: Is there a simple way to identify an img file that contains the overview map?
Gerd
mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5762858.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev