[mkgmap-dev] [PATCH v1] grok unpavednessFrom Mark Burton markb at ordern.com on Mon Dec 7 21:36:46 GMT 2009
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 -------------- next part -------------- A non-text attachment was scrubbed... Name: mb-unpaved-v1.patch Type: text/x-patch Size: 9085 bytes Desc: not available Url : http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20091207/f58f17f1/attachment.bin
- Previous message: [mkgmap-dev] Commit: r1420: Map amenity=embassy to 0x3003, the same code as amenity=townhall.
- Next message: [mkgmap-dev] [PATCH v1] grok unpavedness
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list