February 2016 - mkgmap-dev - The mkgmap lists

Mapsource crashes while calculating a route
by Andrzej Popowski 29 Sep '16

29 Sep '16

Hi, I have observed crashes for some time. Mapsource 6.16.3 indicates a bug in module MPL_MAP.CPP. Basecamp reports an error or goes into infinite loop. Now I have extracted minimal source data, which creates faulty map. Removing any road or even a crossing point restore routing. Bug exist in mkgmap r2815, r2857, r2889, r2975 and r2976. Map created by mkgmap r2795 works correctly. I'm attaching here files to reproduce problem: mkgmap.bat - batch, which I have used to create the map, test-a.pbf - very simple OSM source data, route.gpx - short route, which causes a crash in Mapsource. -- Best regards, Andrzej

4 15

Problem with Exit info while on a BRIDGE
by greg crago 11 Mar '16

11 Mar '16

While traveling East on I-94 (in Michigan), my DESCRIPTION TEXT on my GPS ( the Nuvi layout) said "Bridge" when it should have stated "Exit 139" Example: https://www.openstreetmap.org/node/184647257 here is my exit and destination commands from my lines file: 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}'} This only seems to happen when highway=motorway_junction is sitting on a BRIDGE. Greg

2 10

Maintenance Sun 6th March
by Steve Ratcliffe 07 Mar '16

07 Mar '16

Hello The mkgmap server and website will be down from around 4pm GMT on Sunday 6th March so they can be upgraded. This should take less than two hours, probably much less. During the upgrade, mailing list, svn and downloads will not be available. Any mails sent should still arrive afterwards. There will be an announcement on the mailing list just before the downtime and then just afterwards. ..Steve

1 2

[Patch v1] now option handle-element-version for splitter
by Gerd Petermann 02 Mar '16

02 Mar '16

Hi all, the attached patch adds the option --handle-element-version with three possible values "keep", "fake", and "remove". With "remove" (the default) splitter works like r428, means, the version of OSM elements is not written to the output files, I also did not notice any changes regarding performance. With "keep" splitter writes the version that is found in the input file. With "fake" splitter sets the version to 1. I am not sure what to do when the input file(s) contain elements without (or invalid) version info and option keep is used. Another special case is the pbf format: Since r428 splitter always writes version 1 for nodes, this was a work-around for a problem in the JOSM pbf plugin. This is still done even with --handle-element-version=remove A last special case: with output=xml and --handle-element-version=keep or fake splitter will write api version 0.6 instead of 0.5 A binary based on r428 is available here: http://files.mkgmap.org.uk/download/291/splitter.jar Please let me know what you think about this change. Gerd <http://files.mkgmap.org.uk/download/291/splitter.jar>

3 3

Anyone determine which linetypes are NOT visable in BaseCamp?
by greg crago 29 Feb '16

29 Feb '16

Running BaseCamp ver 4.6.1 and have determined that it will not display linetype 0x17,0x31,0x32 and 0x34 anyone got a complete list of linetypes to avoid if you want you mkgmap to look correct in Basecamp? Will it show extended linetypes >=0x010000 ? Greg

6 13

Problem uploading data to JOSM wit 20 hour old OSM data, maybe a SPLIITTER issue?
by greg crago 29 Feb '16

29 Feb '16

I downloaded .a mapset (michigan-latest.osm.pbf) from http://download.geofabrik.de/north-america.html yesterday. The data is about 20 hours old. I had to use SPLITTER r428 with this command: java -Xmx1024m -Xms1024m -ea -jar \MKGMAP\splitter-r428\splitter.jar --max-nodes=1400000 --mapid="12390000" --geonames-file=\MKGMAP\cities15000.zip --description=MI-greg --max-areas="255" --no-trim --status-freq="600" michigan-latest.osm.pbf Since I could not load the entire Michigan 96MB file into JOSM r9329. The resulting file, 12390006.osm.pbf, is 10.8MB and I imported it into JOSM and copied a NODES tags to an underlying POLYGON and deleted the NODE and tried to upload to the OSM server and got this error message: "Uploading failed because the server has a newer version of one of your nodes, ways, or relations. Click Synchronize entire dataset to synchronize the entire local dataset with the server" It is possible that SPLITTER r428 is not preserving the dataset versions or is setting them all to 1 when they really have different versions (eg. 2,3,4) Greg

4 9

splitter r428 : work-around for JOSM problem
by Gerd Petermann 27 Feb '16

27 Feb '16

Hi all, I've changed splitter to write fake metadata (version, author, timestamp) when using pbf output format. The change in the output files is minimal, and it allows to open the output files in JOSM without using a tool like osmconvert. I can also change the output format of the xml files (osm.gz) to api 0.6. This would mean that each element (node, way, relation) gets an additional <version=1> string which increases the compressed file size by 2% and the uncompressed xml file by ~ 12% , see attached patch splitter_josm_v1.patch . Not sure if that makes sense ? Gerd

3 3

when I use SPLITTER to IMPORT om.pbf files into JOSM I get error
by greg crago 27 Feb '16

27 Feb '16

I am trying to use JOSM for offline editing and osm.pbf files created by splitter r427 cause this error when importing into JOSM r9329 with the pbf import plugin: Could not read file '12360002.osm.pbf'. Error is: java.lang.IndexOutOfBoundsException: Index: 0 I think I saw a post that there might be missing meta data from the osm.pbf files produced by splitter. JOSM has a max of 50000 node for input files. Is there a different 'splitter' that JOSM can import?

6 7

layout HBOX REF
by anor 24 Feb '16

24 Feb '16

Hi, in my style / lines have: highway = motorway {name '$ {ref | highway-symbol: hbox:20:8}' | '$ {Name}'; AddLabel '$ {ref} $ {name}'} highway = trunk {name '$ {ref | highway-symbol: box:20:8}' | '$ {Name}'; AddLabel '$ {ref} $ {name}'} highway = primary {name '$ {ref | highway-symbol: box:20 8}' | '$ {Name}'; AddLabel '$ {ref} $ {name}'} highway = secondary {name '$ {ref | highway-symbol: oval:20:8}' | '$ {Name}'; AddLabel '$ {ref} $ {name}'} where with {ref | highway-symbol: box:20:8} increase my text box and it can put up to 3 REF example SP-310, BR-267, BR-364. <http://gis.19327.n5.nabble.com/file/n5868414/1.jpg> But this is in line BOX. Its they become column as the ID line instead of <http://gis.19327.n5.nabble.com/file/n5868414/2.jpg> -- View this message in context: http://gis.19327.n5.nabble.com/layout-HBOX-REF-tp5868414.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

1 0

Option "link pois to ways"
by Jakob Mühldorfer 22 Feb '16

22 Feb '16

Hi, one more question I was not able to figure out from documentation or source. When the option "link pois to ways" is used, does it automatically process traffic signals in a way that adds a time penalty for routing through them in the map data. Thanks for help on that Jakob

3 6