<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 07.12.2009 22:36, Mark Burton wrote:
<blockquote cite="mid:20091207213646.03c6ef1a@crow" type="cite">
<pre wrap="">
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
</pre>
</blockquote>
I have problems compiling with that patch: <br>
<br>
compile:<br>
[javac] Compiling 317 source files to
d:\Garmin\mkgmap_svn_trunk3\build\classes<br>
[javac]
d:\Garmin\mkgmap_svn_trunk3\src\uk\me\parabola\mkgmap\osmstyle\StyledConverter.java:1418:
illegal start of expression<br>
[javac] if(way.isBoolTag("unpaved") ||
way.isNotBoolTag("paved")))<br>
[javac]
^<br>
[javac] 1 error<br>
<br>
Will try again against a clean trunk but I am not using many patches
currently (basicly only the blacklist/whitelist patch plus some simple
value changes that should not affect anything).<br>
BTW I think the blacklist / whitelist tag file patch would be good to
include as no-one noticed anything broken (I don't need it and just
used it for testing - but I think it can be useful for some mapmakers).<br>
<blockquote cite="mid:20091207213646.03c6ef1a@crow" type="cite">
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
mkgmap-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a class="moz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
</blockquote>
</body>
</html>