[mkgmap-dev] POIs without POI-search

2015-06-04 Thread Arndt 
Hello experts,
 
there are many POIs like barrier, traffic lights, trees an so on. Is it possible
to show them in the map, but without a hit in the poi-search?
 
Best regards
 
Arndt___
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

2015-06-04 Thread GerdP 
Hi Paco,
 
reg. your patch:
please note that r3596 and before acepted any value, but only is_in and 
nearest (and 1,2,3) had an effect. I don't think that the hint in the docu
is
needed.

Gerd


Paco Tyson wrote
> Hi Gerd,
> 
> is_in indeed works OK with r3605 and r3596. Attached is a patch to add a
> note to the "options" doc.
> 
> Cheers,
> Paco
> 
> 
> Le 4 juin 2015 à 06:37, Gerd Petermann <

> gpetermann_muenchen@

> > a écrit :
> 
>> 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.tyson@

>> Date: Wed, 3 Jun 2015 23:53:53 +0200
>> To: 

> mkgmap-dev@.org

>> 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@.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
> 
> 
> ___
> mkgmap-dev mailing list

> mkgmap-dev@.org

> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 
> is-in.patch (673 bytes)
> ;





--
View this message in context: 
http://gis.19327.n5.nabble.com/Exception-with-location-autofill-option-on-r3605-tp5847000p5847143.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] Wrong adresses for 3 french cities

2015-06-04 Thread Paco Tyson 
Hi,

I had a look at the default style for addresses and found out what I think is a 
bug for 3 French cities.
We shouldn't have the lines : 

mkgmap:country=FRA & mkgmap:city!=* & mkgmap:admin_level9=* { set 
mkgmap:city='${mkgmap:admin_level9}' }
mkgmap:country=FRA & mkgmap:city!=* & mkgmap:admin_level8=* { set 
mkgmap:city='${mkgmap:admin_level8}' }

As described in this 2 year old thread : 
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2013q2/017982.html
It seems WanMil never deleted those 2 lines.

Can somebody please update the inc/address file ?

Thanks,
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

2015-06-04 Thread Paco Tyson 
Hi Gerd,is_in indeed works OK with r3605 and r3596. Attached is a patch to add a note to the "options" doc.Cheers,Paco

is-in.patch
Description: Binary data
Le 4 juin 2015 à 06:37, Gerd Petermann  a écrit :Hi Paco,you are right, I forgot to mention that I've added a check tocheck the parameters for the location-autofill option.Please correct the spelling of is-in, it should be is_in.GerdFrom: paco.ty...@free.frDate: Wed, 3 Jun 2015 23:53:53 +0200To: mkgmap-dev@lists.mkgmap.org.ukSubject: [mkgmap-dev] Exception with location-autofill option on r3605Hi 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 listmkgmap-dev@lists.mkgmap.org.ukhttp://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] IndexOutOfBoundsException in US map with mkgmap 3605

2015-06-04 Thread GerdP 
Hi Ben,

please try again with r3606. It should either report errors 
with the tile name or run without problems.

Gerd


Ben Konrath wrote
> Hi,
> 
> I have a IndexOutOfBoundsException while generating a map of the United
> States with mkgmap 3605. I think this is related to the recent house
> number
> merge because 3598 worked fine and the problem seems to come from house
> number related code.
> 
> java.lang.IndexOutOfBoundsException: bitIndex < 0: -1
> at java.util.BitSet.get(BitSet.java:615)
> at
> uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator$RoadSegmentIndex.createHousenumberMatch(HousenumberGenerator.java:2055)
> at
> uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.findClosestRoadsToHouse(HousenumberGenerator.java:794)
> at
> uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.generate(HousenumberGenerator.java:621)
> at
> uk.me.parabola.mkgmap.osmstyle.StyledConverter.end(StyledConverter.java:619)
> at
> uk.me.parabola.mkgmap.reader.osm.ElementSaver.convert(ElementSaver.java:250)
> at
> uk.me.parabola.mkgmap.reader.osm.o5m.O5mBinMapDataSource.load(O5mBinMapDataSource.java:53)
> at
> uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:130)
> at
> uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:154)
> at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:52)
> at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:255)
> at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:251)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 
> Here's how I'm calling mkgamp:
> 
> java -Xmx14000M -jar -Dlog.config=/home/ben/osm/confs/logging.properties
> /home/ben/osm/mkgmap/dist/mkgmap.jar --latin1 --gmapsupp --index --route
> --min-size-polygon --series-name="United States 2015.06.03"
> --family-name="United States 2015.06.03"
> --location-autofill=bounds,is_in,nearest --remove-ovm-work-files
> --bounds=/home/ben/osm/data/bounds
> --precomp-sea=/home/ben/osm/data/sea_20150602.zip --generate-sea
> --add-pois-to-areas --process-destination --process-exits
> --pois-to-areas-placement="entrance=main;entrance=yes;building=entrance"
> --check-roundabout-flares --remove-short-arcs --family-id=14244
> --product-id=1 --make-opposite-cycleways --drive-on=detect,right
> --check-roundabouts --housenumbers -c template.args --description="United
> States 2015.06.03" /home/ben/osm/confs/typ.txt
> 
> Obviously a full US map is big so I don't know exactly where the problem
> is. What's the best way to help narrow done the problem? Let me know what
> I
> can do.
> 
> Thanks, Ben
> 
> ___
> 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/IndexOutOfBoundsException-in-US-map-with-mkgmap-3605-tp5847079p5847116.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] Commit: r3606: - don't process roads with less than two points

2015-06-04 Thread svn commit 

Version mkgmap-r3606 was committed by gerd on Thu, 04 Jun 2015

- don't process roads with less than two points
- add test to catch invalid data in RoadPoint
___
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

2015-06-04 Thread Bernd Weigelt 
Hi Michael

at the top of my inc/lines file is a list of routable types of lines for 
Garmin devices 
very special are 0x08, 0x09, 0x0c, 0x13, 0x16 and 0x1a, IMHO they never should 
be used for other kind of ways. 

Bernd

Am Donnerstag, 4. Juni 2015, 12:04:02 schrieb michael lohr:
> 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...

-- 
amarok2 now playing:




___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] IndexOutOfBoundsException in US map with mkgmap 3605

2015-06-04 Thread Ben Konrath 
Hi,

I have a IndexOutOfBoundsException while generating a map of the United
States with mkgmap 3605. I think this is related to the recent house number
merge because 3598 worked fine and the problem seems to come from house
number related code.

java.lang.IndexOutOfBoundsException: bitIndex < 0: -1
at java.util.BitSet.get(BitSet.java:615)
at
uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator$RoadSegmentIndex.createHousenumberMatch(HousenumberGenerator.java:2055)
at
uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.findClosestRoadsToHouse(HousenumberGenerator.java:794)
at
uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.generate(HousenumberGenerator.java:621)
at
uk.me.parabola.mkgmap.osmstyle.StyledConverter.end(StyledConverter.java:619)
at
uk.me.parabola.mkgmap.reader.osm.ElementSaver.convert(ElementSaver.java:250)
at
uk.me.parabola.mkgmap.reader.osm.o5m.O5mBinMapDataSource.load(O5mBinMapDataSource.java:53)
at
uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:130)
at
uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:154)
at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:52)
at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:255)
at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:251)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Here's how I'm calling mkgamp:

java -Xmx14000M -jar -Dlog.config=/home/ben/osm/confs/logging.properties
/home/ben/osm/mkgmap/dist/mkgmap.jar --latin1 --gmapsupp --index --route
--min-size-polygon --series-name="United States 2015.06.03"
--family-name="United States 2015.06.03"
--location-autofill=bounds,is_in,nearest --remove-ovm-work-files
--bounds=/home/ben/osm/data/bounds
--precomp-sea=/home/ben/osm/data/sea_20150602.zip --generate-sea
--add-pois-to-areas --process-destination --process-exits
--pois-to-areas-placement="entrance=main;entrance=yes;building=entrance"
--check-roundabout-flares --remove-short-arcs --family-id=14244
--product-id=1 --make-opposite-cycleways --drive-on=detect,right
--check-roundabouts --housenumbers -c template.args --description="United
States 2015.06.03" /home/ben/osm/confs/typ.txt

Obviously a full US map is big so I don't know exactly where the problem
is. What's the best way to help narrow done the problem? Let me know what I
can do.

Thanks, Ben
___
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

2015-06-04 Thread michael lohr 

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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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: micha.l...@web.de 
To: mkgmap-dev@lists.mkgmap.org.uk

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: micha.l...@web.de 
To: mkgmap-dev@lists.mkgmap.org.uk

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



--

Re: [mkgmap-dev] process-exits and Oregon 600

2015-06-04 Thread 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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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: micha.l...@web.de

  To: mkgmap-dev@lists.mkgmap.org.uk

  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: micha.l...@web.de

To: mkgmap-dev@lists.mkgmap.org.uk

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 ou

Re: [mkgmap-dev] process-exits and Oregon 600

2015-06-04 Thread michael lohr 

Hi Gerd,
in 3602 (which i used) these are lines 118/119.

I meantchanging

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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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: micha.l...@web.de 
To: mkgmap-dev@lists.mkgmap.org.uk

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: micha.l...@web.de 
To: mkgmap-dev@lists.mkgmap.org.uk

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 wo

Re: [mkgmap-dev] process-exits and Oregon 600

2015-06-04 Thread 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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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: micha.l...@web.de

  To: mkgmap-dev@lists.mkgmap.org.uk

  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: micha.l...@web.de

To: mkgmap-dev@lists.mkgmap.org.uk

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}' | '${r

Re: [mkgmap-dev] process-exits and Oregon 600

2015-06-04 Thread michael lohr 

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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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: micha.l...@web.de 
To: mkgmap-dev@lists.mkgmap.org.uk

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: 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,

Re: [mkgmap-dev] process-exits and Oregon 600

2015-06-04 Thread 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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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: micha.l...@web.de

  To: mkgmap-dev@lists.mkgmap.org.uk

  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: 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 th

Re: [mkgmap-dev] process-exits and Oregon 600

2015-06-04 Thread michael lohr 

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 mkgmapworked 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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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: 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.
___

Re: [mkgmap-dev] process-exits and Oregon 600

2015-06-04 Thread 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: micha.l...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
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: 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