- mkgmap-dev - The mkgmap lists

Commit: r3667: Fix style file parse bug in the form: (x|y) & !z &a!=b
by svn commit 12 Feb '16

12 Feb '16

Version mkgmap-r3667 was committed by steve on Fri, 12 Feb 2016 Fix style file parse bug in the form: (x|y) & !z &a!=b

1 0

osm2mp.pl: CountryName not added to POIs
by Michael Schlenstedt 12 Feb '16

12 Feb '16

Hi, I use osm2mp.pl (latest from https://github.com/liosha/osm2mp) to convert from OSM to Polish format. Before converting, I use splitter to split the big OSM file into smaller tiles. The whole process really works fine, including routing over tiles, except that my my map includes several different countries. That is why I cannot use a Default Country and Default Region. Unfortunately, address search on Nuvi does not work (Mapsource is fine) due to missing CountryName= at my POI descriptions. This is how a POI is converted from OSM to MP: ; NodeID = 3307527863 ; place = hamlet [POI] Data0=(27.6784496,85.2754185) EndLevel=2 Type=0x0C00 Label=Jhwah-cha City=Y CityName=Jhwah-cha RegionName=Central Development Region [END] As you can see CityName and RegionName are added perfectly, but CountryName= is missing... I found this code in lib/GarminTools.pl the following (line 50): if ( $address->{country} ) { # $mp_address{country} = rename_country( $address->{country} ); $mp_address{country} = $address->{country}; } I think it should add the country, but it seems not to work. This is how I invoke osm2mp: osm2pl --default-lang en --target-lang en --translit --header id=80000358 --header name=80000358 --header FID=8000 -o 80000358.mp 80000358.osm Anybody can help? I put my sample files to: http://www.schlenn.net/download/temp/ Thanks, Michael

1 0

POI (point) resolution problem
by Alexandre Loss 12 Feb '16

12 Feb '16

Hi guys, I have noticed that the resolution set in the styles' point file is not considered for some types of POI. I'm not sure if this behavior is my fault or a mkgmap bug and therefore I ask your help. To report the problem I have prepared a small fictitious map containing only two streets, a city point, a airport point and a police station point (the attachment 03137600-lagoa_santa.osm). I'm using the latest version of mkgmap (3666) and the original default styles as-is. Attached also the arguments file used: TRU-Teste.args And I'm running mkgmap whit the following command: java -jar mkgmap.jar --style-file=default -c TRU-Teste.args *The first test* In the first test I set/left the resolution as follow: aeroway=airport [0x2f04 resolution 22] amenity=police [0x3001 resolution *24*] And the following images are the results zooming in Mapsource. As expected, the police point starts to be visible in a zoom of 200m: [image: Imagem inline 1] [image: Imagem inline 2] [image: Imagem inline 3] *The second test* In the second test, I changed the police resolution to 20, expecting that Police begins to be visible before than airport. aeroway=airport [0x2f04 resolution 22] amenity=police [0x3001 resolution *20*] However, as you can see in the below images extracted from Mapsource, police point continues to be visible only from a zoom of 200m. [image: Imagem inline 5] [image: Imagem inline 4] So, that's it! Do you have any idea of whats wrong? Thanks, Alexandre Loss

2 2

Problem with !(mkgmap:unpaved=1), found a line in 'line' that DOES NOT cause compile Error
by greg crago 11 Feb '16

11 Feb '16

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

2 2

House number search - inaccuracy in city assignment
by Steffen Neumann 11 Feb '16

11 Feb '16

Morning everybody, playing around with my Garmin Nuvi I came across a problem with the house number search. The location is: Germany, Ottobrunn, Ottostrasse 132 +48.064630, +11.689558 The Nuvi shows the address as: Ottostrasse 132, Hohenbrunn (so the city is Hohenbrunn here) But in OSM the house is tagged as: Ottostrasse 132, Ottobrunn (different city compared to Nuvi) So either the Garmin pulled the wrong city out of the house number information or mkgmap put the wrong info in. Tracking down the phenomenon in mkgmap I believe that CityZipWriter::write(int skip, int[] indexes, int[] prevIndexes) causes the problem. Please let's take a closer look into the mkgmap source below - keep an eye on my comments. class CityZipWriter { -- snip -- private void write(int skip, int[] indexes, int[] prevIndexes) { if (Arrays.equals(indexes, prevIndexes)) return; // we can signal new values for left and / or right side int sidesFlag = 0; if (indexes[0] <= 0 && indexes[1] <= 0){ sidesFlag |= 4; // signal end of a zip code/city interval if (indexes[0] == 0) sidesFlag |= 1; if (indexes[1] == 0) sidesFlag |= 2; } else { if (indexes[1] != indexes[0]){ if (indexes[0] > 0 && indexes[0] != prevIndexes[0]) sidesFlag |= 1; if (indexes[1] > 0 && indexes[1] != prevIndexes[1]) sidesFlag |= 2; } } /*################################### Here the node index will be decremented by 1 but the caller has already cut 1 off (in public boolean compile(List<Numbers> numbers). In my case the actual index offset is 75 but 74 will be written into the file. This in turn would lead to the effect that the stretch before would be assigned to the city of Hohenbrunn (wrong) instead of Ottobrunn. The actual node index sequence is: 0 Ottobrunn 75 Hohenbrunn This is what the Garmin probably reads: 0 Ottobrunn 74 Hohenbrunn The house number 132 belongs to a stretch defined by number node 74-75 (Ottobrunn) but the Garmin believes it is already Hohenbrunn (the city of the next stretch). Don't know why we write skip-1 because skip already represents the offset of the node index before to the current node index - reduced by 1. So we actually write curNodeIndex-lastNodeIndex-2. That can't be right because the reader can not distinguish between skip 1 and skip 2. ###################################*/ int initFlag = Math.max(skip-1,0); if (initFlag > 31){ // we have to write two bytes buf.write((byte) (initFlag & 0x1f | 0x7<<5)); initFlag >>= 5; } initFlag |= sidesFlag << 5; /*################################### Not the problem but just a remark. It's hard to guess for the reader if there's a 2-byte flag coming in when the reader hits 11100000b. It might be the 1st byte of a 2-byte flag or a 1-byte flag with all sidesFlags set. ###################################*/ buf.write((byte) (initFlag & 0xff)); if ((sidesFlag & 4) == 0) { if (indexes[0] > 0 && (sidesFlag == 0 || (sidesFlag & 1) == 1)) writeIndex(indexes[0]); if (indexes[1] > 0 && (sidesFlag & 2) != 0) writeIndex(indexes[1]); } System.arraycopy(indexes, 0, prevIndexes, 0, indexes.length); } I'm probably wrong but it would at least explain the Garmin Nuvi behavior. But any clarification is welcome. Unfortunately I'm neither familiar with the habits of this project nor have I the means for proper testing in order to commit any changes. I just wanted to point out a possible problem. Cheers and thanks for your attention, Steffen

4 17

Commit: r3666: improve error messages when reading of required files fails, throw ExitException to stop processing
by svn commit 11 Feb '16

11 Feb '16

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

1 0

Changing from RESOLUTION RANGE to single RESOLUTION causes compile error in r3665
by greg crago 11 Feb '16

11 Feb '16

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

3 4

TYPViewer
by Mark Bradley 11 Feb '16

11 Feb '16

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

1 0

mkgmap r3665 complie error, removing road_class and road_speed made a non-routable line?
by greg crago 10 Feb '16

10 Feb '16

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

2 2

Suggestions for DESTINATION hint and EXIT hint
by greg crago 10 Feb '16

10 Feb '16

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

2 1