Commit: r1216: Added ability to display bounding boxes of route centres.
Version 1216 was commited by markb on 2009-09-22 10:40:17 +0100 (Tue, 22 Sep 2009) Added ability to display bounding boxes of route centres. For diagnostic/development purposes, it's now possible to display the bounding boxes of the route centres by using: --route-center-boundary=TYPE Where TYPE is the Garmin line type to use (decimal, not hex). Not documented in options because it's only useful for developers.
svn commit wrote:
Version 1216 was commited by markb on 2009-09-22 10:40:17 +0100 (Tue, 22 Sep 2009)
Added ability to display bounding boxes of route centres.
For diagnostic/development purposes, it's now possible to display the bounding boxes of the route centres by using:
--route-center-boundary=TYPE
Where TYPE is the Garmin line type to use (decimal, not hex).
Not working for me, or is there something wrong in my commandline?: start /low /b /wait java -enableassertions -jar -Xmx2800M mkgmap.jar --max-jobs=3 --latin1 --ignore-maxspeeds --ignore-turn-restrictions --remove-short-arcs=1 --road-name-pois=0x2f2d --add-pois-to-are as --location-autofill=1 --description=openmtbmap_at_22.09.2009 --route --route-center-boundary=0x27 --country-abbr=at --style-file=new2 --country-name=austria --mapname=63650000 --family-id=6365 --product-id=1 --series-n ame=openmtbmap_at_22.09.2009 --family-name=mtbmap_at_22.09.2009 --tdbfile --overview-mapname=mapset00 --keep-going 63650*.osm.gz I did define 0x27 in my TYP file to be sure that it would display. Resulting map size is identical to not using the line "--route-center-boundary=0x27" Mapsource is definitely not showing them - or are they difficult to find?
Not documented in options because it's only useful for developers. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Felix,
Where TYPE is the Garmin line type to use (decimal, not hex).
The option parsing code doesn't seem to know about hex so it only works with decimal types. A pain, but I can't be bothered to do anything about it. Mark
Mark Burton wrote:
Felix,
Where TYPE is the Garmin line type to use (decimal, not hex).
The option parsing code doesn't seem to know about hex so it only works with decimal types. A pain, but I can't be bothered to do anything about it.
Mark
So instead of 0x27 I would have to write 0x39?? It should have worked with 0x27 as decimal being 0x1b in hex too, as I have definition for 0x1b in Typfile. Where is my error? Or do only 0x00 up to 0x09 work (cause hex identical to decimal) ?
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Felix Hartmann -
Mark Burton -
svn commit