Re: [mkgmap-dev] process-exits and Oregon 600
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? Micha Am 01.06.2015 um 09:47 schrieb michael lohr: Hello Bernd. I compared your style and your maps with mine - exits are split and labeled the same way, but my Oregon shows either the 1st or the 3rd segment of the exit (can't really tell which one) and not the labeled 2nd one. Nüvi mode or not makes no difference. All in all this looks like a device issue - can anyone confirm? Or have I just overlooked something in the settings? Micha Am 29.05.2015 um 17:09 schrieb Bernd Weigelt: Hello Michael Didn't use my O650 for routing in the last weeks, only a cheap nüvi, but both devices show the exit hints if expected, tested a few minutes ago, the maps are created with mkgmap housenumbers2 r3601 In my style are some difference to the default style, you can find my style here:https://github.com/berndw1960/aiostyles the exit hints are defined by the file inc/exit_dest Bernd Am Freitag, 29. Mai 2015, 16:09:26 schrieb michael lohr: I use the nüvi mode, and my own map style (which worked on the 450 and has not been modified since). ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] process-exits and Oregon 600
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 mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] process-exits and Oregon 600
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 >> > mkgmap-dev@.org >> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >> > > ___ > mkgmap-dev mailing list > mkgmap-dev@.org > 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 mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] process-exits and Oregon 600
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 mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] process-exits and Oregon 600
Hi Gerd As i am remember, WanMil presumed to use 0x07 as the second part, i use this in my style Bernd Hier sollte eigentlich eine Signatur stehen. -Original Message- From: GerdP To: mkgmap-dev@lists.mkgmap.org.uk Sent: Mi., 03 Juni 2015 18:10 Subject: Re: [mkgmap-dev] process-exits and Oregon 600 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 mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] [Patch v1] improve handling of exits
Hi all,
I've just noticed that this patch was not yet applied.
If nobody complains I'll commit it on friday.
Gerd
GerdP wrote
> Hi Dave,
>
> the patch changes the rules in the default style so that exist on primary
> roads are taken
> into account.
> More important for your test case: It also changes the code so that
> exists on motorway_links to other motorway_links are taken into account.
> The old code only looked at exits on highway=motorway and highway=trunk,
> the new code checks these highway types:
> "motorway", "trunk", "primary", "motorway_link", "trunk_link",
> "primary_link"
>
> So, when you use the patched binary with your own style, the big change is
> that the
> condition
> (highway=motorway_link | highway=trunk_link) & mkgmap:exit_hint=true &
> mkgmap:dest_hint=true
>
> is now true, and that's why echotags is executed.
>
> You can double check by adding this rule to your lines file:
> (mkgmap:exit_hint=* | mkgmap:dest_hint=*) { echotags "hint" }
>
> Test this once with the patched binary and once with the normal one and
> you should
> see the difference.
>
> Gerd
>
> From:
> daveswarthout@
> Date: Tue, 19 May 2015 18:37:26 -0700
> To:
> mkgmap-dev@.org
> Subject: Re: [mkgmap-dev] [Patch v1] improve handling of exits
>
> When you say you didn't change the echotags code, did you rewrite the
> style rule? If you did that I'm embarrassed to admit I am unable to see
> the difference.
> AFAIK I'm using the exact same style file for both runs, but the run with
> the older executables produced no output. I replaced that jar file with
> the new one (modified r3598) and all of a sudden output from echotags
> appeared.
> Anyway, it's all good.
>
>
> On Tue, May 19, 2015 at 11:03 AM, GerdP <
> gpetermann_muenchen@
> > wrote:
> Hi Dave,
>
>
>
> I am not sure if you understand that echotags always worked.
>
> The problem is/was that the rule was not executed because
>
> the expression evaluated to false.
>
> In other words, I did not change the echotags code,
>
> I changed the code so that it is more likely that the
>
> term "mkgmap:exit_hint=true & mkgmap:dest_hint=true"
>
> evaluates to true.
>
>
>
> Gerd
>
>
>
>
>
> Dave Swarthout wrote
>
>> On Mon, May 18, 2015 at 7:51 AM, Gerd Petermann <
>
>
>
>> gpetermann_muenchen@
>
>
>
>>> wrote:
>
>>
>
>>
>
>>> @Dave: Please note the changes in the default style.
>
>>> It would be great if you could test this patch and maybe suggest
>
>>> a better description of the two options.
>
>>>
>
>>
>
>> Sorry for the delay in responding. The modified r3598 produced output
>> from
>
>> the echotags function. I did not see anything regarding the exit_to tags
>
>> but my test destination tag was processed and this output went to stderr:
>
>>
>
>> 4611686018427392234 (168231839) -
>
>> [highway=motorway_link,destination=Beltline Road
>
>> East,mkgmap:exit_hint=true,mkgmap:dest_hint=true,bicycle=yes,mkgmap:way-has-pois=true,mkgmap:exit_hint_ref=195A,mkgmap:label:1=Dest:
>
>> Beltline Road East,oneway=yes] before
>
>> 4611686018427392234 (168231839) -
>
>> [highway=motorway_link,destination=Beltline Road
>
>> East,mkgmap:exit_hint=true,mkgmap:dest_hint=true,bicycle=yes,mkgmap:way-has-pois=true,mkgmap:exit_hint_ref=195A,mkgmap:label:1=Dest:
>
>> Beltline Road East,oneway=yes] after
>
>>
>
>> *(highway=motorway_link | highway=trunk_link) & mkgmap:exit_hint=true &*
>
>> *mkgmap:dest_hint=true*
>
>> * { echotags "before";*
>
>> *name '${destination:ref|subst: =>} ${destination|subst:;=> |subst:/=> }'
>
>> |*
>
>> * '${ref|subst: =>} ${destination|subst:;=> |subst:/=> }' |*
>
>> * '${destination|subst:;=> |subst:/=> }' |*
>
>> * 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' |*
>
>> * 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_exit_to}' |*
>
>> * 'Exit ${mkgmap:exit_hint_exit_to}' |*
>
>> * 'Exit ${mkgmap:exit_hint_name}' |*
>
>> * 'Exit ${mkgmap:exit_hint_ref}' ;*
>
>> *echotags "after"*
>
>> * }*
>
>>
>
>> This is my rule for debugging the destination tag and it appears before
>
>> the
>
>> rule above:
>
>>
>
>> *destination=* & (highway=motorway_link | highway=trunk_link) {name
>> 'Dest:
>
>> ${destination}' }*
>
>>
>
>> My exit_to rule is for points is here:
>
>>
>
>> *exit_to=* {name 'Exit ${ref} ${exit_to}' | '${exit_to}' } [0x12615
>
>> resolution 24]*
>
>>
>
>> This produces the desired output on my maps but doesn't show up in stderr
>
>> because I haven't yet put echotags into my points style file.
>
>>
>
>> Thanks for the good work
>
>>
>
>>
>
>>
>
>>
>
>>
>
>> --
>
>> Dave Swarthout
>
>> Homer, Alaska
>
>> Chiang Mai, Thailand
>
>> Travel Blog at http://dswarthout.blogspot.com
>
>>
>
>> ___
>
>> mkgmap-dev mailing list
>
>
>
>> mkgmap-dev@.org
>
>
>
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
>
>
>
>
>
>
>
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
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@.org
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
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Exception with location-autofill option on r3605
Hi all, I've updated mkgmap from r3596 to r3605 to try the house number improvements. Nothing else in my toolchain changed. mkgmap returns the following exception 6 times, I can't explain why they appear as nothing in the change logs is related to this option (location-autofill: is-in,nearest) : [java] java.lang.IllegalArgumentException: is-in is not a known sub option for option location-autofill: is-in,nearest [java] at uk.me.parabola.mkgmap.build.LocatorUtil.parseAutofillOption(LocatorUtil.java:75) [java] at uk.me.parabola.mkgmap.build.Locator.(Locator.java:52) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryLocationPreparer.(BoundaryLocationPreparer.java:57) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryQuadTree.(BoundaryQuadTree.java:107) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryUtil.loadQuadTreeFromStream(BoundaryUtil.java:493) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryUtil.loadQuadTrees(BoundaryUtil.java:176) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryGrid.init(BoundaryGrid.java:103) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryGrid.(BoundaryGrid.java:66) [java] at uk.me.parabola.mkgmap.reader.osm.LocationHook.end(LocationHook.java:98) [java] at uk.me.parabola.mkgmap.reader.osm.OsmReadingHooksChain.end(OsmReadingHooksChain.java:79) [java] at uk.me.parabola.mkgmap.reader.osm.bin.OsmBinMapDataSource.load(OsmBinMapDataSource.java:63) [java] at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:130) [java] at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:154) [java] at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:52) [java] at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:255) [java] at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:251) [java] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [java] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [java] at java.lang.Thread.run(Thread.java:744) The produced files are corrupt. Cheers, Paco___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Exception with location-autofill option on r3605
Hi Paco, you are right, I forgot to mention that I've added a check to check the parameters for the location-autofill option. Please correct the spelling of is-in, it should be is_in. Gerd From: paco.ty...@free.fr Date: Wed, 3 Jun 2015 23:53:53 +0200 To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] Exception with location-autofill option on r3605 Hi all, I've updated mkgmap from r3596 to r3605 to try the house number improvements. Nothing else in my toolchain changed. mkgmap returns the following exception 6 times, I can't explain why they appear as nothing in the change logs is related to this option (location-autofill: is-in,nearest) : [java] java.lang.IllegalArgumentException: is-in is not a known sub option for option location-autofill: is-in,nearest [java] at uk.me.parabola.mkgmap.build.LocatorUtil.parseAutofillOption(LocatorUtil.java:75) [java] at uk.me.parabola.mkgmap.build.Locator.(Locator.java:52) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryLocationPreparer.(BoundaryLocationPreparer.java:57) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryQuadTree.(BoundaryQuadTree.java:107) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryUtil.loadQuadTreeFromStream(BoundaryUtil.java:493) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryUtil.loadQuadTrees(BoundaryUtil.java:176) [java] at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryGrid.init(BoundaryGrid.java:103) [java]at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryGrid.(BoundaryGrid.java:66) [java] at uk.me.parabola.mkgmap.reader.osm.LocationHook.end(LocationHook.java:98) [java] at uk.me.parabola.mkgmap.reader.osm.OsmReadingHooksChain.end(OsmReadingHooksChain.java:79) [java] at uk.me.parabola.mkgmap.reader.osm.bin.OsmBinMapDataSource.load(OsmBinMapDataSource.java:63) [java]at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:130) [java] at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:154) [java] at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:52) [java] at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:255) [java] at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:251) [java] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [java] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [java] at java.lang.Thread.run(Thread.java:744) The produced files are corrupt. Cheers,Paco ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] process-exits and Oregon 600
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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@.org
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
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Patch to fix 'allow to' typo in splitter documentation
On 06/02/2015 08:38 AM, Gerd Petermann wrote: > thanks, I've committed your patch and with r425 I've added some missing > options in the > help file. I hope I did not mess up the formatting in the man file and the > xml format. Thanks for applying the patch. There was a small issue with the usage which I fixed with the attached patch. In slightly related news, the mkgmap-splitter package for Debian was accepted into the archive yesterday after being in the NEW queue since January. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 splitter-docbook.patch Description: inode/symlink ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@.org
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
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___ mkgmap-dev mailing
list mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
