logo separator

[mkgmap-dev] [PATCH v2] grok unpavedness + ferry nature

From Mark Burton markb at ordern.com on Tue Dec 8 13:57:14 GMT 2009

v3 - turns out they handle ferry routes in a similar fashion as to
unpaved roads so I've added support for avoiding them (when route=ferry
tag is present) - untested here due to paucity of ferries in
Cheshire but I have verified that the unpaved stuff still works.


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".

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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mb-unpaved-v3.patch
Type: text/x-patch
Size: 10309 bytes
Desc: not available
Url : http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20091208/54cd9494/attachment.bin 

More information about the mkgmap-dev mailing list