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

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

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,

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

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 |

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

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] 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

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 > * > > > > > > > > > > >

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

Sorry Greg. I mistook the destination / exit, single output, not with this abbreviation quotes. ___ Anor C. A. de Souza

[mkgmap-dev] Improve error reporting for a corrupted sea.zip file

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

[mkgmap-dev] Compile Errors with this command !(mkgmap:unpaved=1), help!

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-dev] Problem with !(mkgmap:unpaved=1), found a line in 'line' that DOES NOT cause compile Error

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 |

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

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

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

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

[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

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

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

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

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

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

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

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]

[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

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

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

[mkgmap-dev] Commit: r3666: improve error messages when reading of required files fails, throw ExitException to stop processing

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

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

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

[mkgmap-dev] TYPViewer

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