[mkgmap-dev] Rounding bug in splitter?
From Chris Miller chris.miller at kbcfp.com on Thu Aug 13 06:48:14 BST 2009
> --=-=-= > > Felix Hartmann <extremecarver at googlemail.com> writes: > >> D:\Garmin\mkgmap>start /low /b /wait java -enableassertions -jar >> -Xmx1200M splitter.jar --mapid=63200000 --maxnodes=1000000 >> --resoultion=15 switzerland.osm >> >> /D:\Garmin\mkgmap>start /low /b /wait java -enableassertions -jar >> -Xmx1200M splitter.jar --mapid=63200000 /-/-maxnodes=1000000 >> --resoultion=15 switzerland.osm / >> > You have spelled resolution incorrectly. Perhaps the splitter (and > mkgmap) should error out when given an unknown option. --maxnodes too should in fact be --max-nodes. Improving the command-line handling has been on my todo list, though performance, key features and bugfixes have been higher priorities so far. Chris
- Previous message: [mkgmap-dev] Rounding bug in splitter?
- Next message: [mkgmap-dev] Routing with the default style
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list