[mkgmap-dev] RFC: Consider heightmeters for routing
From Felix Hartmann extremecarver at googlemail.com on Tue Apr 7 09:37:40 BST 2009
I thought about that one too, but wouldn't that need a complete rewrite of the style system? You could solve it by reading in all streets, checking them for inclination, and then upon the inclination/height difference between every intersection provide a incline key, that you can then call upon in the style-file. I still wonder though about the amount of cpu power needed to get that data - knowing that my pc calculated about 12 hours (Pentium M 2.26GHz, by that time 2GB RAM, harddisk with 60MB/s average write, 65 read) on converting SRTM1" into Garmin contourlines with 10m seperation - for Austria only. Ralf Kleineisel wrote: > Johann Gail wrote: > > >> So my idea is, to virutally lengthen the roads by the height distance. >> This is, if a road has 1km and goes straight then it gets an entry of 1 >> km in the routing data.. If another road has a length of 1km and a >> height difference of 10m, then it gets a length entry of 1.1km. >> > > Have you thought about changing the road_speed instead of the length? I.e. a > road going up/downhill would get a lower road_speed than a flat one and when > calculating a fastest route the Garmin should prefer the flat one. > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20090407/a616dcb5/attachment.html
- Previous message: [mkgmap-dev] RFC: Consider heightmeters for routing
- Next message: [mkgmap-dev] RFC: Consider heightmeters for routing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list