[mkgmap-dev] Suggestions for DESTINATION hint and EXIT hint

[greg crago]

I have added some SUBST to make the resultant strings look more like City
Navigator.

In you LINE file, look for "# start of rules for process-exits and
process-destination options
"

dest_hint=* { delete dest_hint }
(highway=motorway_link | highway=trunk_link | highway=primary_link |
highway=secondary_link | highway=tertiary_link) & mkgmap:dest_hint=true
#  { set dest_hint = '${destination:ref|subst: =>} ${destination|subst:;=>
|subst:/=> }' |
  { set dest_hint = '${destination:ref|subst: =>|subst: South=> S|subst:
North=> N|subst: East=> E|subst: West=> W} ${destination:street|subst:
Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst:
Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy} -
${destination|subst:;=>,|subst:/=>,}' |


 '${destination:street|subst: Road=> Rd|subst: Street=> St|subst:
Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=>
Pkwy|subst: Highway=> Hwy} - ${destination|subst:;=>,|subst:/=>,}'
'${ref|subst: =>|subst: South=> S|subst: North=> N|subst: East=> E|subst:
West=> W} - ${destination|subst:;=>,|subst:/=>,}' |
'${exit_hint_ref|subst: South=> S|subst: North=> N|subst: East=> E|subst:
West=> W} ${exit_hint_name|subst: Road=> Rd|subst: Street=> St|subst:
Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=>
Pkwy|subst: Highway=> Hwy}' |
'${exit_to|subst: Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst:
Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=>
Hwy}' |
 '${destination|subst:;=>,|subst:/=>,}';
   }
# build exit hint
exit_hint=* { delete exit_hint }
(highway=motorway_link | highway=trunk_link | highway=primary_link |
highway=secondary_link | highway=tertiary_link) & mkgmap:exit_hint=true
  { set exit_hint = 'Exit ${mkgmap:exit_hint_ref}
${mkgmap:exit_hint_name|subst: Road=> Rd|subst: Street=> St|subst: Avenue=>
Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst:
Highway=> Hwy}' |
 'Exit ${ref|subst: South=> S|subst: North=> N|subst: East=>
E|subst: West=> W}' |
'Exit ${mkgmap:exit_hint_ref|subst: South=> S|subst: North=> N|subst:
East=> E|subst: West=> W} ${mkgmap:exit_hint_exit_to|subst: Road=>
Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst:
Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy}' |
 'Exit ${mkgmap:exit_hint_exit_to|subst: Road=> Rd|subst: Street=>
St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst:
Parkway=> Pkwy|subst: Highway=> Hwy}' |
 'Exit ${mkgmap:exit_hint_name|subst: Road=> Rd|subst: Street=>
St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst:
Parkway=> Pkwy|subst: Highway=> Hwy}' |
 'Exit ${mkgmap:exit_hint_ref|subst: South=> S|subst: North=>
N|subst: East=> E|subst: West=> W}';
   }

# use destination hint and/or exit hint to build name
(highway=motorway_link | highway=trunk_link | highway=primary_link |
highway=secondary_link | highway=tertiary_link) & (mkgmap:exit_hint=true |
mkgmap:dest_hint=true)
  { name '${exit_hint} ${dest_hint}' | '${dest_hint}' | '${exit_hint}'}


It might be nice if we could ABBREVIATE road names in the Default style,
 because all GPS have limited number of characters.


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

[mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN DROP" on your GPS?

[greg crago]

I asked this question a couple weeks ago, but no response.
City Navigator show Dynamic Addresses in BASECAMP and on my GPS.

Can we do this with MKGMAP r3665?

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

Re: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN DROP" on your GPS?

[A. Carlos]

Greg,
Yes, this active since mkgmap-r3662

  
 
 
 
 
 
 

___

Anor C. A. de Souza 
  
 
  
 
 
 
 
 
 
 


Date: Wed, 10 Feb 2016 10:03:14 -0500
From: gregcr...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN   
DROP" on your GPS?

I asked this question a couple weeks ago, but no response. City Navigator show 
Dynamic Addresses in BASECAMP and on my GPS.
Can we do this with MKGMAP r3665?
Greg

___
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] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN DROP" on your GPS?

[Gerd Petermann]

Hi Greg,


AFAIK this is not possible with the img format that mkgmap creates. Your City 
Navigator is probable

a so called NT map, we don't understand the format of NT maps as it is 
encrypted, so we can't write it.


Gerd


Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
 im Auftrag von greg crago 

Gesendet: Mittwoch, 10. Februar 2016 16:03
An: Development list for mkgmap
Betreff: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN DROP" 
on your GPS?

I asked this question a couple weeks ago, but no response.
City Navigator show Dynamic Addresses in BASECAMP and on my GPS.

Can we do this with MKGMAP r3665?

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

Re: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN DROP" on your GPS?

[Gerd Petermann]

Hi Anor,

why do you think that the changes in r3662 are related to this?

Did I miss something?


Gerd



Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
 im Auftrag von A. Carlos 

Gesendet: Mittwoch, 10. Februar 2016 16:22
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN 
DROP" on your GPS?

Greg,

Yes, this active since 
mkgmap-r3662









___


Anor C. A. de Souza


















Date: Wed, 10 Feb 2016 10:03:14 -0500
From: gregcr...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN DROP" 
on your GPS?

I asked this question a couple weeks ago, but no response.
City Navigator show Dynamic Addresses in BASECAMP and on my GPS.

Can we do this with MKGMAP r3665?

Greg

___ 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] Improve error reporting for a corrupted sea.zip file

[paco . tyson]

Hi all,

I found that mkgmap can display an exception with a confusing description :

Time started: Wed Feb 10 14:27:05 CET 2016
GRAVE (SeaGenerator): D:\tmp\idf-generic\14070303.osm.pbf: Cannot read index 
file index.txt.gz
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:215)
at java.util.zip.ZipFile.(ZipFile.java:145)
at java.util.zip.ZipFile.(ZipFile.java:159)
at 
uk.me.parabola.mkgmap.reader.osm.SeaGenerator.init(SeaGenerator.java:161)
at 
uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.pluginChain(OsmMapDataSource.java:209)
at 
uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.setupHandler(OsmMapDataSource.java:180)
at 
uk.me.parabola.mkgmap.reader.osm.bin.OsmBinMapDataSource.load(OsmBinMapDataSource.java:49)
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)

At first, I understood that the pbf file is corrupted (this exception is thrown 
for each .pbf file). Actually, the pbf files are OK : the error is the sea.zip 
file that is corrupted. I improved the error reporting in the attached patch.
I'd like to have mkgmap fail when this happens but I don't know how to do that.


Lambertus, I think you're the person providing the sea and bounds files at 
http://osm2.pleiades.uni-wuppertal.de/ , can you provide a checksum file for 
these files in order to detect bad downloads ?


Thanks,
Paco
Index: mkgmap/reader/osm/SeaGenerator.java
===
--- mkgmap/reader/osm/SeaGenerator.java	(revision 3665)
+++ mkgmap/reader/osm/SeaGenerator.java	(working copy)
@@ -184,7 +184,7 @@
 			try{
 precompData = loadIndex(indexStream);
 			} catch (IOException exp) {
-log.error("Cannot read index file " + indexFileName,
+log.error("Cannot read index file " + indexFileName + " in " + precompSeaDir,
 		exp);
 			}
 			
@@ -198,7 +198,7 @@
 			indexStream.close();
 		}
 	} catch (IOException exp) {
-		log.error("Cannot read index file " + indexFileName,
+		log.error("Cannot read index file " + indexFileName + " in " + precompSeaDir,
 exp);
 
 	}
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN DROP" on your GPS?

[greg crago]

How to I turn this ON?

What options?

Greg

On Wed, Feb 10, 2016 at 10:22 AM, A. Carlos  wrote:

> Greg,
>
> Yes, this active since *mkgmap-r3662
> *
>
>
>
>
>
>
>
>
>
>
> *___*
>
> *Anor C. A. de Souza
>  *
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> Date: Wed, 10 Feb 2016 10:03:14 -0500
> From: gregcr...@gmail.com
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN
> DROP" on your GPS?
>
>
> I asked this question a couple weeks ago, but no response.
> City Navigator show Dynamic Addresses in BASECAMP and on my GPS.
>
> Can we do this with MKGMAP r3665?
>
> Greg
>
> ___ 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] Compile Errors with this command !(mkgmap:unpaved=1), help!

[greg crago]

I am trying to use this line:

(highway=residential | highway=living_street | highway=minor |
highway=unclassified) & !(mkgmap:unpaved=1) & bridge!=yes [0x06
road_class=0 road_speed=2 resolution 22 continue]


I want (THESE HIGHWAYS) and (PAVED) and (NO BRIDGE) to get 0x06 linetype

 !(mkgmap:unpaved=1) would give me 'paved' or 'not dirt' roads.

Can someone help with the syntax?

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

Re: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN DROP" on your GPS?

[A. Carlos]

Sorry Greg.

 I mistook the destination / exit, single output, not with this abbreviation 
quotes.

  
 
 
 
 
 
 

___

Anor C. A. de Souza 
 
  
 
 
 
 
 
 
 


Date: Wed, 10 Feb 2016 11:13:24 -0500
From: gregcr...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN 
DROP" on your GPS?

How to I turn this ON?
What options?
Greg
On Wed, Feb 10, 2016 at 10:22 AM, A. Carlos  wrote:



Greg,

Yes, this active since mkgmap-r3662

  
 
 
 
 
 
 

___

Anor C. A. de Souza 
  
 
  
 
 
 
 
 
 
 


Date: Wed, 10 Feb 2016 10:03:14 -0500
From: gregcr...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: [mkgmap-dev] Can MKGMAP show DYNAMIC ADDRESS when you use a "PIN   
DROP" on your GPS?

I asked this question a couple weeks ago, but no response. City Navigator show 
Dynamic Addresses in BASECAMP and on my GPS.
Can we do this with MKGMAP r3665?
Greg

___
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

[mkgmap-dev] Problem with !(mkgmap:unpaved=1), found a line in 'line' that DOES NOT cause compile Error

[greg crago]

I found this line that uses very similar !(unpaved) type command but does
NOT CAUSE an error on mkgmap compile.


highway=tertiary_link & !(mkgmap:unpaved=1) & bridge!=yes [0x08
road_class=1 road_speed=1 resolution 20 continue]


but I do have a complie error with :

(highway=residential | highway=living_street | highway=minor |
highway=unclassified) & !(mkgmap:unpaved=1) & bridge!=yes [0x06
road_class=0 road_speed=2 resolution 22 continue]


The only difference I can see is 2 Parentheses back to back seems to cause
a problem


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

Re: [mkgmap-dev] Problem with !(mkgmap:unpaved=1), found a line in 'line' that DOES NOT cause compile Error

[Steve Ratcliffe]

Hi Greg


I found this line that uses very similar !(unpaved) type command but
does NOT CAUSE an error on mkgmap compile.

highway=tertiary_link & !(mkgmap:unpaved=1) & bridge!=yes [0x08
road_class=1 road_speed=1 resolution 20 continue]

but I do have a complie error with :

(highway=residential | highway=living_street | highway=minor |
highway=unclassified) & !(mkgmap:unpaved=1) & bridge!=yes [0x06
road_class=0 road_speed=2 resolution 22 continue]



Yes, you have found a bug.  I will try to fix it.

As a workaround you can add a highway=*
This doesn't change the result but it does allow it to compile
with the current version.


(highway=residential | highway=living_street | highway=minor | 
highway=unclassified)

& highway=*
& !(mkgmap:unpaved=1)
& bridge!=yes
   [0x06 road_class=0 road_speed=2 resolution 22 continue]

Thanks for reporting this problem.

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

Re: [mkgmap-dev] Suggestions for DESTINATION hint and EXIT hint

[Andrzej Popowski]

Hi Greg,

> It might be nice if we could ABBREVIATE road names
> in the Default style

Your example works only for English and isn't suitable for universal 
style, because it can damage valid names in other languages.


You can add conditions like mkgmap:country=USA but then it could all 
became unreadable.


--
Best regards,
Andrzej

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

[mkgmap-dev] mkgmap r3665 complie error, removing road_class and road_speed made a non-routable line?

[greg crago]

I made a map and was using my GPS in AUTO RECALCULATE mode and had an
avtice Route destination behind me and was deliberately driving in the
opposite direction to test out the maps Routing capability. One
recalculated route told me to turn on to a RAILROAD TRACK, I looked at my
line file and noticed that I gave a ROAD_CLASS and ROAD_SPEED to the
RAILROAD LINETYPE 0x01:

(railway=rail | railway=tram | railway=disused | railway=subway |
railway=narrow_gauge | railway=light_rail | railway=preserved) &
tunnel!=yes & bridge=yes [0x01 road_class=0 road_speed=1 resolution 20]


So I removed the the road class and road speed:

(railway=rail | railway=tram | railway=disused | railway=subway |
railway=narrow_gauge | railway=light_rail | railway=preserved) &
tunnel!=yes & bridge=yes [0x01 resolution 20]

But now I get a COMPILE ERROR:

Warning: routable type 0x01 is used for non-routable line with level 0.
This may break routing. Style file lines, line 273

How did just removing the road class and road speed change this to be a
non-routable line??

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

Re: [mkgmap-dev] mkgmap r3665 complie error, removing road_class and road_speed made a non-routable line?

[Gerd Petermann]

Hi Greg,


a line is considered to be a routable line when it has a road_speed or 
road_classs (or both).

A few line types are special and should not be used for non-routable ways when 
the map

is created with --route. The style manual says

"It is known that the usage of routable types for non-routable lines in 
resolution 24 can cause
routing problems (e.g. address search doesn't work). The check will flag rules 
that assign a routable type for a line in resolution 24 without giving 
road_class or road_speed. A routable type is between 0x01 and 0x13 or one of: 
0x1a, 0x1b, 0x16.
If road_class or road_speed is given in combination with a non-routable type, 
the rule is flagged.  "


OK?

Gerd


Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
 im Auftrag von greg crago 

Gesendet: Mittwoch, 10. Februar 2016 22:54
An: Development list for mkgmap
Betreff: [mkgmap-dev] mkgmap r3665 complie error, removing road_class and 
road_speed made a non-routable line?

I made a map and was using my GPS in AUTO RECALCULATE mode and had an avtice 
Route destination behind me and was deliberately driving in the opposite 
direction to test out the maps Routing capability. One recalculated route told 
me to turn on to a RAILROAD TRACK, I looked at my line file and noticed that I 
gave a ROAD_CLASS and ROAD_SPEED to the RAILROAD LINETYPE 0x01:

(railway=rail | railway=tram | railway=disused | railway=subway | 
railway=narrow_gauge | railway=light_rail | railway=preserved) & tunnel!=yes & 
bridge=yes [0x01 road_class=0 road_speed=1 resolution 20]


So I removed the the road class and road speed:

(railway=rail | railway=tram | railway=disused | railway=subway | 
railway=narrow_gauge | railway=light_rail | railway=preserved) & tunnel!=yes & 
bridge=yes [0x01 resolution 20]

But now I get a COMPILE ERROR:

Warning: routable type 0x01 is used for non-routable line with level 0. This 
may break routing. Style file lines, line 273

How did just removing the road class and road speed change this to be a 
non-routable line??

Greg




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

[mkgmap-dev] Changing from RESOLUTION RANGE to single RESOLUTION causes compile error in r3665

[greg crago]

Default line style has this:

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 15-17
continue]

I wanted to only show this on RESOLUTION 17, so I changed it to this:

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17 continue]

Now when I compile using mkgmap -r3665 I get this error:

Warning: routable type 0x02 is used for non-routable line with level 0.
This may break routing. Style file lines, line 165.

How does changing the Resolution Range to a single Resolution cause this
error?

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

Re: [mkgmap-dev] Changing from RESOLUTION RANGE to single RESOLUTION causes compile error in r3665

[Gerd Petermann]

The rule

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17 continue]

means res 17 - 24. You have to use 17-17.

Gerd

Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
 im Auftrag von greg crago 

Gesendet: Mittwoch, 10. Februar 2016 23:11
An: Development list for mkgmap
Betreff: [mkgmap-dev] Changing from RESOLUTION RANGE to single RESOLUTION 
causes compile error in r3665

Default line style has this:

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 15-17 continue]

I wanted to only show this on RESOLUTION 17, so I changed it to this:

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17 continue]

Now when I compile using mkgmap -r3665 I get this error:

Warning: routable type 0x02 is used for non-routable line with level 0. This 
may break routing. Style file lines, line 165.

How does changing the Resolution Range to a single Resolution cause this error?

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

Re: [mkgmap-dev] Changing from RESOLUTION RANGE to single RESOLUTION causes compile error in r3665

[Steve Sgalowski]

i run my resolution from 24-18  on all my poi files , due to the type of
work i do in australia

Stephen


On Thu, Feb 11, 2016 at 8:11 AM, greg crago  wrote:

> Default line style has this:
>
> highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 15-17
> continue]
>
> I wanted to only show this on RESOLUTION 17, so I changed it to this:
>
> highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17
> continue]
>
> Now when I compile using mkgmap -r3665 I get this error:
>
> Warning: routable type 0x02 is used for non-routable line with level 0.
> This may break routing. Style file lines, line 165.
>
> How does changing the Resolution Range to a single Resolution cause this
> error?
>
> Greg
>
> ___
> 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] mkgmap r3665 complie error, removing road_class and road_speed made a non-routable line?

[greg crago]

Thank you Gerd, that makes sense.

I was using routable linetype 0x01 because PINNS website stated that 0x01
(normally used to motorways) does not get over drawn by any other linetype
and I was adding a special BRIDGE linetype=0x01 because I wanted it to be
drawn on top of all other lines.

Since 0x01 is routable and I removed the road_class and road_speed, I made
it non-routable and hence the error occurred.

To fix this, I will have to use another non-routable linetype and make it
look like my 'other' rout-able BRIDGES linetype, and then my railroads
bridges will look similar to my routable road bridges.

Greg

On Wed, Feb 10, 2016 at 5:02 PM, Gerd Petermann <
gpetermann_muenc...@hotmail.com> wrote:

> Hi Greg,
>
>
> a line is considered to be a routable line when it has a road_speed or
> road_classs (or both).
>
> A few line types are special and should not be used for non-routable ways
> when the map
>
> is created with --route. The style manual says
>
> "It is known that the usage of routable types for non-routable lines in
> resolution 24 can cause
> routing problems (e.g. address search doesn't work). The check will flag
> rules that assign a routable type for a line in resolution 24 without
> giving road_class or road_speed. A routable type is between 0x01 and 0x13
> or one of: 0x1a, 0x1b, 0x16.
> If road_class or road_speed is given in combination with a non-routable
> type, the rule is flagged.  "
>
>
> OK?
>
> Gerd
>
> --
> *Von:* mkgmap-dev-boun...@lists.mkgmap.org.uk <
> mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von greg crago <
> gregcr...@gmail.com>
> *Gesendet:* Mittwoch, 10. Februar 2016 22:54
> *An:* Development list for mkgmap
> *Betreff:* [mkgmap-dev] mkgmap r3665 complie error, removing road_class
> and road_speed made a non-routable line?
>
> I made a map and was using my GPS in AUTO RECALCULATE mode and had an
> avtice Route destination behind me and was deliberately driving in the
> opposite direction to test out the maps Routing capability. One
> recalculated route told me to turn on to a RAILROAD TRACK, I looked at my
> line file and noticed that I gave a ROAD_CLASS and ROAD_SPEED to the
> RAILROAD LINETYPE 0x01:
>
> (railway=rail | railway=tram | railway=disused | railway=subway |
> railway=narrow_gauge | railway=light_rail | railway=preserved) &
> tunnel!=yes & bridge=yes [0x01 road_class=0 road_speed=1 resolution 20]
>
>
> So I removed the the road class and road speed:
>
> (railway=rail | railway=tram | railway=disused | railway=subway |
> railway=narrow_gauge | railway=light_rail | railway=preserved) &
> tunnel!=yes & bridge=yes [0x01 resolution 20]
>
> But now I get a COMPILE ERROR:
>
> Warning: routable type 0x01 is used for non-routable line with level 0.
> This may break routing. Style file lines, line 273
>
> How did just removing the road class and road speed change this to be a
> non-routable line??
>
> Greg
>
>
>
>
>
> ___
> 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] Changing from RESOLUTION RANGE to single RESOLUTION causes compile error in r3665

[greg crago]

Gerd, I still do not understand.

Let's say I WANT resolution 17-24

The rule

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17 continue]

means res 17 - 24.



but when I use this ([0x02 resolution 17 continue]) , I get an error
compiling. All of the other instances of a single resolution (which means
x-24) do not give compile errors, it seems only lines with


 ( network=e-road | int_ref=* )


Greg

On Wed, Feb 10, 2016 at 5:15 PM, Steve Sgalowski 
wrote:

> i run my resolution from 24-18  on all my poi files , due to the type of
> work i do in australia
>
> Stephen
>
>
> On Thu, Feb 11, 2016 at 8:11 AM, greg crago  wrote:
>
>> Default line style has this:
>>
>> highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 15-17
>> continue]
>>
>> I wanted to only show this on RESOLUTION 17, so I changed it to this:
>>
>> highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17
>> continue]
>>
>> Now when I compile using mkgmap -r3665 I get this error:
>>
>> Warning: routable type 0x02 is used for non-routable line with level 0.
>> This may break routing. Style file lines, line 165.
>>
>> How does changing the Resolution Range to a single Resolution cause this
>> error?
>>
>> Greg
>>
>> ___
>> 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] TYPViewer

[Mark Bradley]

Thanks to everyone who gave me suggestions on where to locate the latest
version of TYPViewer to download.  In the end I ended up using Nev Wedding's
suggestion by going to this link:

 

http://www.gpspower.net/creating-maps/218482-typ-viewer-24.html?

 

This new version is compatible with Windows 10.

 

Mark Bradley

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

Re: [mkgmap-dev] Changing from RESOLUTION RANGE to single RESOLUTION causes compile error in r3665

[Gerd Petermann]

Hi Greg,


the problem is similar to the one here:

http://gis.19327.n5.nabble.com/mkgmap-r3665-complie-error-removing-road-class-and-road-speed-made-a-non-routable-line-tp5867289p5867294.html


Your change made the line with 0x02 visible in res 24, and that triggers the 
warning.


Gerd



Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
 im Auftrag von greg crago 

Gesendet: Mittwoch, 10. Februar 2016 23:28
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Changing from RESOLUTION RANGE to single RESOLUTION 
causes compile error in r3665

Gerd, I still do not understand.

Let's say I WANT resolution 17-24


The rule

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17 continue]

means res 17 - 24.



but when I use this ([0x02 resolution 17 continue]) , I get an error compiling. 
All of the other instances of a single resolution (which means x-24) do not 
give compile errors, it seems only lines with


 ( network=e-road | int_ref=* )


Greg

On Wed, Feb 10, 2016 at 5:15 PM, Steve Sgalowski 
mailto:steve.sgalow...@gmail.com>> wrote:
i run my resolution from 24-18  on all my poi files , due to the type of work i 
do in australia

Stephen


On Thu, Feb 11, 2016 at 8:11 AM, greg crago 
mailto:gregcr...@gmail.com>> wrote:
Default line style has this:

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 15-17 continue]

I wanted to only show this on RESOLUTION 17, so I changed it to this:

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17 continue]

Now when I compile using mkgmap -r3665 I get this error:

Warning: routable type 0x02 is used for non-routable line with level 0. This 
may break routing. Style file lines, line 165.

How does changing the Resolution Range to a single Resolution cause this error?

Greg

___
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] Commit: r3666: improve error messages when reading of required files fails, throw ExitException to stop processing

[svn commit]

Version mkgmap-r3666 was committed by gerd on Thu, 11 Feb 2016

improve error messages when reading of required files fails, throw 
ExitException to stop processing 
when files for --bounds or --precomp-sea option are corrupted
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev