September 2015 - 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

highway=razed
by Gerd Petermann 20 Oct '15

20 Oct '15

Hi all, the lines file in the default style contains this rule: # Mop up any unrecognised highway types highway=* & highway!=proposed & area!=yes [0x07 road_class=0 road_speed=0 resolution 23] I've changed it to highway=* & highway!=proposed & area!=yes { echotags "mop up" } [0x07 road_class=0 road_speed=0 resolution 23] to see what it does and it "mops up" all kings of problem cases, e.g. mapping errors like highway=turning_circle or removed highways with the highway=razed I think the default style should not add these ways as routable, if at all. It also catches many highway=platform and highway=rest_area Most of these ways are areas, but don't have the area=yes tag. I am not sure why the "mop up" rule would ignore them when the area=yes tag exists. Gerd

5 7

process-exits vs process-destination
by Franco Bez 08 Oct '15

08 Oct '15

Hi all, is there a way to combine the features process-exits and process-destination in a single style ? Based on my experience process-desitnation does a marvellous job when entering a motorway ( does it also work with also trunk roads ? ), while process-extis is perfect when leaving a motorway or trunk road. For instance the roundabout here http://www.openstreetmap.org/?lat=47.89665&lon=10.64805&zoom=17 has two exits towards the B12. Routing from the "Sudetenstraße" going North (maybe towards Augsburg) I would like the Garmin device to announce "5 th Exit - B12 (München)". On the other hand routing to the South (maybe Kempten) it should announce "2nd exit - B12 (Kempten)". Using process-exits this does not work, it's only "5th Exit - B12" resp. "2nd Exit - B12". I would have to use process-destination instead to get the desired messages displayed. Coming home from the trip, routing from the B12 towards "Sudetenstraße" I would like "exit to the right - Exit Kaufbeuren". Using process-exits this works perfectly. Would I use process-destination I would get "exit to the right towards B12 Verteilerring" or even "exit to the right towards Sudetenstraße" a really useless announcement as the sign on the trunk road reads "Kaufbeuren / Neugablonz / Mauerstetten". So this is why I would like to have an option that combines the functionality of process-exits and process-destination. Do you see any way to achieve this in one single style ? Ciao, Franco

7 6

Speedlimit on Nüvi ?
by Thomas Morgenstern 29 Sep '15

29 Sep '15

Hi to all, is there a option in the style-file or in the mkgmap-options, that i can use to generate a tile (12345678.img ), which show me the speedlimit for any road on Nüvi ? If i drive faster then allowed it gets 'red' ? my current version mkgmap is 3622. thomas

5 10

[patch] add support for information=guidepost POI in default style
by Ben Konrath 27 Sep '15

27 Sep '15

Hi, The default style currently has information=guidepost POIs set as a toilet icon. This patch changes information=guidepost to be an 'i' in a circle. For reference, here's an example of a POI with this tag: https://www.openstreetmap.org/node/2883638464 Thanks, Ben

3 5

OT : Geschlossen vor vor ...
by Gerd Petermann 27 Sep '15

27 Sep '15

Hi, don't know who is responsible for this, but when I look at e.g. https://www.openstreetmap.org/history#map=15/55.0688/-2.5680 I see generated messages like "Geschlossen vor vor etwa 10 Stunden von ..." (note the duplicated "vor") Who's maintaining that code? Gerd

2 1

Problem with aeroway=aerodrome as a relation
by Nelson A. de Oliveira 24 Sep '15

24 Sep '15

Could somehow mkgmap have an issue with aeroway=aerodrome as a relation? (instead a simple closed way) For example, this airport http://www.openstreetmap.org/way/90834745 have its internal grasses properly represented like here: http://cocardl.com.br/pv/viracopos.jpg On the other hand, this airport http://www.openstreetmap.org/relation/3896781 seems to overlap every internal feature (like grasses): http://cocardl.com.br/pv/galeao.jpg Is mkgmap giving different treatments for aeroway=aerodrome as a closed way and as a relation?

4 13

Marine charts and Garmin 4+ firmware : "Map format not supported" Error
by ubik 22 Sep '15

22 Sep '15

Hello, I wonder if someone is working or has a solution for marine Garmin's plotters firmware 4+ (e.g. echoMAP 4.60). It seems that no one is working on the infamous "map format not supported" error given by newer devices and openseamap charts. Maybe there is someone who is expert in RE field and take a look at the latest firmware upgrades. A downgrade to earlier versions is not a good solution; in any case ... it is not a firmware bug (as mentioned in the wiki of osm) but it is a "feature" introduced on purpose to block third-party map producers. I'm a developer but I do not have all the necessary skills to investigate and research completely by himself. I would like to know if there is someone I can get in touch... thanks, Leo

1 0

Commit: r3643: ignore highway=razed
by svn commit 22 Sep '15

22 Sep '15

Version mkgmap-r3643 was committed by gerd on Sat, 19 Sep 2015 ignore highway=razed remove obsolete checks for highway=proposed, the line highway=proposed {delete highway;delete junction} catches and removes them earlier.

3 4

Attributes that correspond with Garmin Format?
by Nick Papadonis 20 Sep '15

20 Sep '15

Hi Folks, I’m have a number of trail maps in ArcMap format that I’m considering converting to Garmin .img. I have tried a few different utilities, however it appears they are having issues with incorrect or null attribute formats. What I notice is these vector maps consist of a number of polylines with attributes ObjectID, Shape, Type, Name, Shape_Length and Code. The Type field is <Null> on all the lines, however the Code changes depending on the type of line. I’d like to convert this data to Polish MP or OSM and use mkgmap to create the Garmin image file, however I’m a bit puzzled by the attribute fields and what to use for values. Is there a mapping somewhere of what attribute fields mkgmap and/or Garmin format expects? I.e. field and value which would specify a trail, a road, etc? Thanks so much, Nick

1 0