January 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

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

Why is there a code-page in the .typ-file? And - is there a code-page a gmapsupp.img?
by Felix Hartmann 20 Mar '15

20 Mar '15

Hi Everyone 1. Switching to unicode I ask myself If I should also change the typ-file to code-page=65001 - is this only for the case that you want to label a line/poi/polygon using unicode characters - or should any .typ-file that is "bundled" by a unicode map, also be unicode? Does anyone know a garmin unicode map that has a .typ-file? 2. I couldn't notice any change on compiling a gmapsupp.img regarding a code-page set. Is there actually a code-page for a gmapsupp.img? Especially regarding address index. Or is the code-page only for the map.img files themselves? Felix -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

4 5

patches
by GerdP 08 Feb '15

08 Feb '15

Hi Steve, again and again users report that they don't know what to do with patches. Do you think it would be possible to implement a service on http://www.mkgmap.org.uk/ which allows to upload a patch to get a binary? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/patches-tp5831932.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

4 3

Copyright message not showing up starting 3433
by Ervin Malicdem 01 Feb '15

01 Feb '15

Hi I believe we had a change regarding copyright messages on 3430. It seems on 3433, Copyright message is no longer shown on the device (About page or About>Detailed Maps page) I am only using license text and copyright message but not copyright file. License text is showing up without problems on Basecamp but Copyright Message is no longer seen on the device. I test it on Nuvi 1360 and GPSMap 62s. Thanks. Ervin M. *Schadow1 Expeditions* - A Filipino must not be a stranger to his own motherland. http://www.s1expeditions.com

2 2

Commuter rail stations
by Brian Egge 01 Feb '15

01 Feb '15

When I look at POIs with a Garmin map, I have a category for 'Suburban Rail Station'. In the NYC area, there are hundreds of commuter rail stations and a handful of regional stations. Having the two listed separately in the POI search is useful, as usually you are searching for one or the other. When using an mkgmap, it only has the single railway station type. I believe the suburban railway stations can be tagged with commuter=yes, but I do not know what Garmin hex code causes this category to appear. Any idea what the code is or how to figure it out? Brian

2 1

FW: Lines distorted
by Gerd Petermann 01 Feb '15

01 Feb '15

From: gpetermann_muenchen(a)hotmail.com To: daveswarthout(a)gmail.com Subject: RE: [mkgmap-dev] Lines distorted Date: Fri, 30 Jan 2015 09:02:45 +0100 Hi Dave, up to now the reduce-point-xxx options are used for the DouglasPeuckerFilter which smoothes lines at lower resolutions. They are ignored for resolution 24, in which the WrongAngleFixer is used to guess how an object can be placed on the Garmin raster so that it looks as much as possible like the OSM described by the OSM data. If you want to play with that: The WrongAngleFixer has a few constants, e.g. you may increase the value MAX_DIFF_ANGLE_STRAIGHT_LINE = 3; or change the method calcMaxErrorDistance() to allow larger errors. Gerd From: daveswarthout(a)gmail.com Date: Fri, 30 Jan 2015 07:14:07 +0700 To: mkgmap-dev(a)lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Lines distorted I want to continue Enrico's questioning a bit. I have a similar issue with the way polygons display on my Garmin device. What appears as a smooth curve on the OSM slippy map are very blocky on the device. I have played with the reduce-point-density=4 and reduce-point-density-polygon=8 parameters in an attempt to smooth those curves but they seem to have no effect. I can live with the distortion but I wonder, what do these two parameters actually control? Cheers,Dave On Fri, Jan 30, 2015 at 12:22 AM, Andrzej Popowski <popej(a)poczta.onet.pl> wrote: Hi Enrico, Garmin maps have limited resolution, about 2.4m. One can't draw precisely a line, which length is near to this resolution. You can try to assign the same Garmin object type to all these segments, then probably mkgmap will be able to merge them and smooth. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

5 19

PT rules in relations file
by Bernd Weigelt 31 Jan '15

31 Jan '15

Hi i'm playing around with the PT rules in relations, as example this node [1]. The node belongs to two route relations (RE8 and RB27) and one track relation (2324) When i enable the rules in relations i got the labels Unkel (Re8,re8,rb27,rb27) my wanted result is to get only one entry per relations, btw apply_once didn't help this is my code # Public transportation routes. type=route & (route=bus| route=trolleybus| route=ferry| route=subway| route=train| route=tram) & (ref=* | name=*) { add ref='${name}'; apply { set route_ref='$(route_ref),${ref}' | '${ref}'; set mkgmap:relref='${ref}'; apply role=passengers { set route_ref='$(route_ref),${mkgmap:relref}' | '${mkgmap:relref}'; } delete mkgmap:relref; } } How can get this result? And where is my error? Bernd [1] http://www.openstreetmap.org/way/58522211

2 4

Patch: New filter "not-contained"
by "Maxim Düster" 31 Jan '15

31 Jan '15

6 17

leading and trailing spaces
by Mike Baggaley 31 Jan '15

31 Jan '15

Good evening all, I've noticed that there are a number of unwanted leading and trailing spaces in OSM data. You can get a list of the ones on the name field using the following: name~'.* ' {echotags "name ends with a space"} name~' .*' {echotags "name starts with a space"} I can't see any facility in mkgmap to remove these, and was wondering whether the best way would be simply to code them out by replacing the following line in parseDense, parseNodes, ParseWays and parseRelations: String val = getStringById(...); With String val = getStringById(...).trim(); I can't think of any reason why a value would need to start or end with a space, so it seems reasonable to just remove them. Are there any other suggestions, or reasons why this should not be done? Regards, Mike

4 7