[PATCH v2] grok unpavedness
v2 - sans syntax error --------- Bloody typical, you wait around for ages hoping for a new routing capability to be added to mkgmap and then two come along on the same day. I've been trying to discover how unpavedness is encoded for at least 6 months. Every now and again, I return to think about it some more. Check and re-check the same old data structures. Very frustrating, no progress. Damn those cunning bastards at Garmin.... However, a month or two ago, I discovered that Table C contains more than just turn restrictions. I still don't know many of it's little secrets but, today, having exhausted all other possibilities, I finally twigged that Table C contains the key to understanding "unpavedness". Gotcha! The attached patch allows you to add either unpaved=yes/true/1 or paved=no/false/0 to a way and then it will be ignored for routing purposes when the GPS has been told to avoid unpaved roads. Not sure if those are the best tags to use - any thoughts? BTW - the unpaved road line type 0x0a has nothing to do with unpavedness, it's just a routable way that gets drawn as a dashed line (default rendering). Feedback, etc. Mark
Patch seems to work mighty fine. I exchanged add toll=yes with add unpaved=yes and got the same behaviour. I think you can commit it to trunk. This leaves only Ferries and Seasonal Road Closures missing from mkgmap. (or has anyone any success using avoid ferries?) to complete the avoidance features. (and a way to tweeze arcs so that they are NOT considered U-Turns) On 07.12.2009 23:34, Mark Burton wrote:
v2 - sans syntax error
---------
Bloody typical, you wait around for ages hoping for a new routing capability to be added to mkgmap and then two come along on the same day.
I've been trying to discover how unpavedness is encoded for at least 6 months. Every now and again, I return to think about it some more. Check and re-check the same old data structures. Very frustrating, no progress. Damn those cunning bastards at Garmin....
However, a month or two ago, I discovered that Table C contains more than just turn restrictions. I still don't know many of it's little secrets but, today, having exhausted all other possibilities, I finally twigged that Table C contains the key to understanding "unpavedness". Gotcha!
The attached patch allows you to add either unpaved=yes/true/1 or paved=no/false/0 to a way and then it will be ignored for routing purposes when the GPS has been told to avoid unpaved roads.
Not sure if those are the best tags to use - any thoughts?
BTW - the unpaved road line type 0x0a has nothing to do with unpavedness, it's just a routable way that gets drawn as a dashed line (default rendering).
Feedback, etc.
Mark
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
The patch v2 does work on my Edge 705 after all. The reason why it did not work before was that I added the style rules to the points file, not to the lines file. :-( I wonder if there is an easy way to misuse map layers so that one could choose in the device menu on-the-go what the paved bit is mapped to. For example, you might want to avoid unlit roads, or you might want to avoid paved cycleways. (Yes, I prefer unpaved roads in "winter" when they are not snowy or muddy. Between November and April or so, all paved cycleways are covered by very sharp-edged grit that easily breaks any tyre, even the supposedly puncture-proof ones. We might have snow or ice on the cycleways for about 30 days during those 5 months.) Marko
participants (3)
-
Felix Hartmann -
Mark Burton -
Marko Mäkelä