Hi Gerd
yes all fine - we should just update the documentation: I didn't know 08
and 09 are special and had to find out the hard way...
Micha
Am 04.06.2015 um 11:57 schrieb Gerd Petermann:
Hi Micha,
okay, same effect: no 0x09 type for the motorway_link.
My understanding is that the types 0x08 and 0x09 are special
as they tell Garmin to use the name of the next road which doesn't
have 0x08 or 0x09 as the hint.
So, you need a part of the link that is 0x08/0x09 and
the hint on the next part of the link which is NOT 0x08/0x09.
That's what the default style does. OK?
Gerd
------------------------------------------------------------------------
Date: Thu, 4 Jun 2015 11:51:26 +0200
From: [email protected]
To: [email protected]
Subject: Re: [mkgmap-dev] process-exits and Oregon 600
Hi Gerd,
in 3602 (which i used) these are lines 118/119.
I meant changing
highway=motorway_link [0x09 road_class=3 road_speed=2 resolution 20]
to
highway=motorway_link { name 'generic_exit' } [0x02 road_class=3
road_speed=2 resolution 20]
Micha
Am 04.06.2015 um 11:47 schrieb Gerd Petermann:
Hi Micha,
lines 119 and 120 in lines (r3605) are:
highway=motorway_link & (mkgmap:exit_hint=true |
mkgmap:dest_hint=true) [0x06 road_class=3 road_speed=2 resolution 20]
highway=motorway_link [0x09 road_class=3 road_speed=2 resolution 20]
If you change line 119 as suggested the rule in line 120
is never triggered, therefore you will not have a type 0x09 for the
motorway_link.
Gerd
------------------------------------------------------------------------
Date: Thu, 4 Jun 2015 11:36:01 +0200
From: [email protected] <mailto:[email protected]>
To: [email protected]
<mailto:[email protected]>
Subject: Re: [mkgmap-dev] process-exits and Oregon 600
Hi Gerd,
trying to reproduce the problem with the default style made things
clearer. If you change line 119 in "lines" to:
highway=motorway_link { name 'generic_exit' } [0x02 road_class=3
road_speed=2 resolution 20]
routing hints point to "generic_exit". I did a few more test, and
it seems that there's two ways to get proper routing:
1. Make segments 1 & 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)
2. If segments 1 & 3 are not 0x09 then don't name them, and again
segment 2 any type except 0x08 or 0x09
Micha
Am 04.06.2015 um 09:30 schrieb Gerd Petermann:
Hi Micha,
it's hard to understand without seeing your complete style.
Maybe you can post a link to it?
If not, please describe in detail how to reproduce the problem
with the default style and give an example route
that shows what you get with and without the modification.
thanks,
Gerd
------------------------------------------------------------------------
Date: Thu, 4 Jun 2015 09:20:23 +0200
From: [email protected] <mailto:[email protected]>
To: [email protected]
<mailto:[email protected]>
Subject: Re: [mkgmap-dev] process-exits and Oregon 600
Hi Gerd,
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.
So I draw two conclusions from this:
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
Or: documentation needs to be updated concerning the exit_hints
Micha
Am 04.06.2015 um 09:09 schrieb Gerd Petermann:
Hi Micha,
now I am no longer sure what you are talking about. You
said that your
problem was solved by removing the line
highway=motorway_link & mkgmap:label:1!=* { set
mkgmap:label:1 = 'Exit' }
from your style. I tried to find out why this line
causes trouble and found no reason as long
as the line doesn't appear before the blocks for the hints
which start at line 36 in the default style file lines of
r3605:
(highway=motorway_link | highway=trunk_link) &
mkgmap:exit_hint=true & mkgmap:dest_hint=true
....
I don't use the device for testing, I create a route in
MapSource and check
the list of "directions".
Gerd
------------------------------------------------------------------------
Date: Thu, 4 Jun 2015 08:56:37 +0200
From: [email protected] <mailto:[email protected]>
To: [email protected]
<mailto:[email protected]>
Subject: Re: [mkgmap-dev] process-exits and Oregon 600
Hi Gerd,
the exits were always named correctly, I checked that by
looking directly into the img-files. The GPS just wouldn't
display the hint.
Am 04.06.2015 um 07:19 schrieb Gerd Petermann:
Hi Micha,
I cannot yet reproduce your result. I tried this:
Add the line
highway=motorway_link & mkgmap:label:1!=* { set
mkgmap:label:1 = 'Exit' }
in the default style file at line 65, before the line
highway=* {name '${name}' | '${ref}' }
Execute mkgmap with options --route --process-exits
--process-destinationand this modified style.
I see the right hint for node 988993419.
Maybe you placed the line before those for the exit hint?
In that case it is clear that the exit hints don't
work because those rules
use the name action which has no effect when
mkgmap:label:1 is already set.
If that doesn't help, please provide more details.
Gerd
------------------------------------------------------------------------
Date: Wed, 3 Jun 2015 18:47:00 +0200
From: [email protected] <mailto:[email protected]>
To: [email protected]
<mailto:[email protected]>
Subject: Re: [mkgmap-dev] process-exits and Oregon 600
Hi Gerd, hi Bernd
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:
highway=motorway_link & mkgmap:label:1!=* { set
mkgmap:label:1 = 'Exit' }
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.
Micha
Am 03.06.2015 um 18:29 schrieb GerdP:
Hi Michael,
please check how the default style uses the hint. I think
it works
fine.
Gerd
michael lohr wrote
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:
Hi Michael,
michael lohr wrote
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?
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:
http://gis.19327.n5.nabble.com/process-exits-and-Oregon-600-tp5845444p5846973.html
Sent from the Mkgmap Development mailing list
archive at Nabble.com.
_______________________________________________
mkgmap-dev mailing list
[email protected] <mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected] <mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
--
View this message in
context:http://gis.19327.n5.nabble.com/process-exits-and-Oregon-600-tp5845444p5846980.html
Sent from the Mkgmap Development mailing list archive at
Nabble.com.
_______________________________________________
mkgmap-dev mailing list
[email protected]
<mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list [email protected]
<mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
<mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev
mailing list [email protected]
<mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
<mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev
mailing list [email protected]
<mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected] <mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing
list [email protected]
<mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected] <mailto:[email protected]>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing
list [email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
