<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Micha,<br><br>lines 119 and 120&nbsp; in lines (r3605) are:<br>highway=motorway_link &amp; (mkgmap:exit_hint=true | mkgmap:dest_hint=true) [0x06 road_class=3 road_speed=2 resolution 20]<br>highway=motorway_link [0x09 road_class=3 road_speed=2 resolution 20]<br><br>If you change line 119 as suggested the rule in line 120<br>is never triggered, therefore you will not have a type 0x09 for the <br>motorway_link.<br><br>Gerd<br><br><br><div><hr id="stopSpelling">Date: Thu, 4 Jun 2015 11:36:01 +0200<br>From: micha.lohr@web.de<br>To: mkgmap-dev@lists.mkgmap.org.uk<br>Subject: Re: [mkgmap-dev] process-exits and Oregon 600<br><br>
  
    
  
  
    <font face="Verdana">Hi <font face="Verdana">G</font>erd</font>,<br>
    trying to reproduce the problem with the default style made things
    clearer. If you change line 119 in "lines" to:<br>
    <br>
    highway=motorway_link { name 'generic_exit' } [0x02 road_class=3
    road_speed=2 resolution 20]<br>
    <br>
    routing hints point to "generic_exit". I did a few more test, and it
    seems that there's two ways to get proper routing:<br>
    <br>
    1. Make segments 1 &amp; 3 polyline 0x09 (named or not doesn't
    matter), and segment 2 any type except 0x08 or 0x09 (didn't test
    that, taken from the documentation)<br>
    2. If segments 1 &amp; 3 are not 0x09 then don't name them, and
    again segment 2 any type except 0x08 or 0x09<br>
    <br>
    Micha<br>
    <br>
    <div class="ecxmoz-cite-prefix">Am 04.06.2015 um 09:30 schrieb Gerd
      Petermann:<br>
    </div>
    <blockquote cite="mid:DUB112-W26E8BA1485373EB5F76E6E9EB30@phx.gbl">
      
      <div dir="ltr">Hi Micha,<br>
        <br>
        it's hard to understand without seeing your complete style.<br>
        Maybe you can post a link to it?<br>
        If not, please describe in detail how to reproduce the problem<br>
        with the default style and give an example route<br>
        that shows what you get with and without the modification.<br>
        <br>
        thanks,<br>
        Gerd<br>
        <br>
        <div>
          <hr id="ecxstopSpelling">Date: Thu, 4 Jun 2015 09:20:23 +0200<br>
          From: <a class="ecxmoz-txt-link-abbreviated" href="mailto:micha.lohr@web.de">micha.lohr@web.de</a><br>
          To: <a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>
          Subject: Re: [mkgmap-dev] process-exits and Oregon 600<br>
          <br>
          Hi Gerd,<br>
          my style did (in this order) assign hints to exits, and at the
          very end, assign generic names to all "leftover" unnamed
          roads. This produced exits in 3 segments named "GENERIC_NAME",
          "EXIT_HINT", "GENERIC_NAME" - so mkgmap worked just as
          expected. But: the Oregon now shows "GENERIC_NAME" during
          routing, not "EXIT_HINT". After removing the generic names
          from the 1st and the 3rd segment, everything workes fine.<br>
          <br>
          So I draw two conclusions from this:<br>
          <br>
          Either: mkgmap simly assigns the exit hints to all 3 segments
          (do we need 3 segments at all, then?), though I don't know
          what else might be influenced by this<br>
          <br>
          Or: documentation needs to be updated concerning the
          exit_hints<br>
          <br>
          Micha<br>
          <br>
          <br>
          <div class="ecxmoz-cite-prefix">Am 04.06.2015 um 09:09 schrieb
            Gerd Petermann:<br>
          </div>
          <blockquote cite="mid:DUB112-W4172A38D9A9049B46D58AE9EB30@phx.gbl">
            <div dir="ltr">Hi Micha,<br>
              <br>
              now I am no longer sure what you are talking about. You
              said that your<br>
              problem was solved by removing the line <br>
              highway=motorway_link &amp; mkgmap:label:1!=* { set
              mkgmap:label:1 = 'Exit' } <br>
              from your style. I tried to find out why this line<br>
              causes trouble and found no reason as long<br>
              as the line doesn't appear before the blocks for the hints<br>
              which start at line 36 in the default style file lines of
              r3605:<br>
              (highway=motorway_link | highway=trunk_link) &amp;
              mkgmap:exit_hint=true &amp; mkgmap:dest_hint=true<br>
              ....<br>
              <br>
              I don't use the device for testing, I create a route in
              MapSource and check<br>
              the list of "directions".<br>
              <br>
              Gerd<br>
              <br>
              <br>
              <div>
                <hr id="ecxstopSpelling">Date: Thu, 4 Jun 2015 08:56:37
                +0200<br>
                From: <a class="ecxmoz-txt-link-abbreviated" href="mailto:micha.lohr@web.de">micha.lohr@web.de</a><br>
                To: <a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>
                Subject: Re: [mkgmap-dev] process-exits and Oregon 600<br>
                <br>
                Hi Gerd,<br>
                the exits were always named correctly, I checked that by
                looking directly into the img-files. The GPS just
                wouldn't display the hint.<br>
                <br>
                <div class="ecxmoz-cite-prefix">Am 04.06.2015 um 07:19
                  schrieb Gerd Petermann:<br>
                </div>
                <blockquote cite="mid:DUB112-W12955D02BF1E220D9BD2E199EB30@phx.gbl">
                  <div dir="ltr">Hi Micha,<br>
                    <br>
                    I cannot yet reproduce your result. I tried this:<br>
                    Add the line<br>
                    <br>
                    highway=motorway_link &amp; mkgmap:label:1!=* { set
                    mkgmap:label:1 = 'Exit' } <br>
                    <br>
                    in the default style file at line 65, before the
                    line<br>
                    <br>
                    highway=* {name '${name}' | '${ref}' }<br>
                    <br>
                    Execute mkgmap with options --route --process-exits
                    --process-destinationand this modified style. <br>
                    I see the right hint for node 988993419.<br>
                    <br>
                    Maybe you placed the line before those for the exit
                    hint?<br>
                    In that case it is clear that the exit hints don't
                    work because those rules <br>
                    use the name action which has no effect when
                    mkgmap:label:1 is already set.<br>
                    <br>
                    If that doesn't help, please provide more details.<br>
                    <br>
                    Gerd<br>
                    <br>
                    <div>
                      <hr id="ecxstopSpelling">Date: Wed, 3 Jun 2015
                      18:47:00 +0200<br>
                      From: <a class="ecxmoz-txt-link-abbreviated" href="mailto:micha.lohr@web.de">micha.lohr@web.de</a><br>
                      To: <a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>
                      Subject: Re: [mkgmap-dev] process-exits and Oregon
                      600<br>
                      <br>
                      Hi Gerd, hi Bernd<br>
                      it works because the default style does not name
                      the outer segments (intentionally?). My style
                      treated exits pretty much the same way, with one
                      addition:<br>
                      <br>
                      highway=motorway_link &amp; mkgmap:label:1!=* {
                      set mkgmap:label:1 = 'Exit' }<br>
                      <br>
                      Deleting this line and so not naming the outer
                      segments did the trick. As far as I can tell, line
                      type does not make any difference.<br>
                      <br>
                      Micha<br>
                      <br>
                      <div class="ecxmoz-cite-prefix">Am 03.06.2015 um
                        18:29 schrieb GerdP:<br>
                      </div>
                      <blockquote cite="mid:1433348970255-5846980.post@n5.nabble.com">
                        <pre>Hi Michael,

please check how the default style uses the hint. I think it works
fine.

Gerd


michael lohr wrote
</pre>
                        <blockquote>
                          <pre>Hi Gerd,
my 1st assumption was that I set the road_speed too high, and the 
routing would "jump" overthe 2nd part to the 3rd, 2nd assumption was to 
use a different line type - changing both things made no difference.

Am 03.06.2015 um 17:59 schrieb GerdP:
</pre>
                          <blockquote>
                            <pre>Hi Michael,


michael lohr wrote
</pre>
                            <blockquote>
                              <pre>Finally found the reason: my style assigns generic names to unnamed
roads, so the segments of a motorway_link were named "GENERIC_NAME",
"EXIT_HINT", "GENERIC_NAME". As soon as a name is present on either the
1st or the 3rd segment the Oregon would use this name for routing (btw,
contrary the my previous posts: the Oregon 450 also behaves like that).

Which brings up this question: why not assign the exit_hint to all 3
segments in the first place?
</pre>
                            </blockquote>
                            <pre>My understanding is that the style should be able to use a different
type (not 0x08 / 0x09) for that small 2nd part, so that Garmin uses
the name of it as a hint.

Gerd



--
View this message in context:
<a class="ecxmoz-txt-link-freetext" href="http://gis.19327.n5.nabble.com/process-exits-and-Oregon-600-tp5845444p5846973.html" target="_blank">http://gis.19327.n5.nabble.com/process-exits-and-Oregon-600-tp5845444p5846973.html</a>
Sent from the Mkgmap Development mailing list archive at Nabble.com.
_______________________________________________
mkgmap-dev mailing list

</pre>
                          </blockquote>
                        </blockquote>
                        <blockquote>
                          <pre><a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@.org">mkgmap-dev@.org</a>
</pre>
                        </blockquote>
                        <blockquote>
                          <blockquote>
                            <pre><a class="ecxmoz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a>

</pre>
                          </blockquote>
                          <pre>_______________________________________________
mkgmap-dev mailing list
</pre>
                        </blockquote>
                        <blockquote>
                          <pre><a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@.org">mkgmap-dev@.org</a>
</pre>
                        </blockquote>
                        <blockquote>
                          <pre><a class="ecxmoz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a>
</pre>
                        </blockquote>
                        <pre>--
View this message in context: <a class="ecxmoz-txt-link-freetext" href="http://gis.19327.n5.nabble.com/process-exits-and-Oregon-600-tp5845444p5846980.html" target="_blank">http://gis.19327.n5.nabble.com/process-exits-and-Oregon-600-tp5845444p5846980.html</a>
Sent from the Mkgmap Development mailing list archive at Nabble.com.
_______________________________________________
mkgmap-dev mailing list
<a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a class="ecxmoz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a>

</pre>
                      </blockquote>
                      <br>
                      _______________________________________________
                      mkgmap-dev mailing list <a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
                      <a class="ecxmoz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></div>
                  </div>
                  <br>
                  <fieldset class="ecxmimeAttachmentHeader"></fieldset>
                  <br>
                  <pre>_______________________________________________
mkgmap-dev mailing list
<a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a class="ecxmoz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
                </blockquote>
                <br>
                _______________________________________________
                mkgmap-dev mailing list <a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
                <a class="ecxmoz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></div>
            </div>
            <br>
            <fieldset class="ecxmimeAttachmentHeader"></fieldset>
            <br>
            <pre>_______________________________________________
mkgmap-dev mailing list
<a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a class="ecxmoz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
          </blockquote>
          <br>
          _______________________________________________
          mkgmap-dev mailing list
          <a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
          <a class="ecxmoz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></div>
      </div>
      <br>
      <fieldset class="ecxmimeAttachmentHeader"></fieldset>
      <br>
      <pre>_______________________________________________
mkgmap-dev mailing list
<a class="ecxmoz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a class="ecxmoz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
    </blockquote>
  

<br>_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</div>                                               </div></body>
</html>