April 2013 - mkgmap-dev - The mkgmap lists

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

multi-word street search
by Michał Rogala 18 Dec '14

18 Dec '14

Hello! I've a problem regarding street search. In Poland (and I suppose few more countries also may have this issue) person-named streets can have two forms - long one: Miroslawa Dudka or short one: Dudka there is no standard for tagging such names in OSM. Problem is that Garmin/Mapsource search function is matching names from the beginning of the string, so if I enter "Dudka" it will find all streets named "Dudka" but not "Miroslawa Dutka". Do you have any idea how can I deal with such issue? best regards Michal Rogala

12 67

frig-roundabouts doesn't work
by GerdP 28 Sep '13

28 Sep '13

Hi, The option is described in the wiki, and I find a peace of source in the HighwayHook that evaluates it, but it doesn't work. What is missing? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/frig-roundabouts-doesn-t-work-tp5748545.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 3

Commit: r2580: - correct check-styles: overlays are not used for points and polygons
by svn commit 10 May '13

10 May '13

Version 2580 was committed by gerd on Sat, 27 Apr 2013 - correct check-styles: overlays are not used for points and polygons - separate code for check-styles and list-styles option, check only a single style if --style was used.

4 4

Commit: r2567: roads_first_v1.patch: Make sure that roads are placed before other lines
by svn commit 06 May '13

06 May '13

Version 2567 was committed by gerd on Thu, 11 Apr 2013 roads_first_v1.patch: Make sure that roads are placed before other lines in each sub division.

4 10

StyledConverter.addRoadAfterSplittingLoops and roundabouts
by WanMil 05 May '13

05 May '13

Hi programmers, the StyledConverter.addRoadAfterSplittingLoops seems to splits each roundabout at least into two MapRoad objects because they contain the same point twice (start and end point). I wonder if that's the desired function? The comment says: // check each point in the way to see if it is the same // point as a following point in the way (actually the // same object not just the same coordinates) But I think it's curious that Garmin would not allow that for roundabouts. WanMil

2 2

merge-lines and routing
by GerdP 04 May '13

04 May '13

Hi, the help file says merge-lines < ... > At the moment this option causes routing errors. Use only if routing is not needed in your map. Maybe I found the reason for the routing errors: If the segments of a road are merged, it might happen that the LineSplitterFilter has to split it because it has more than 250 points. The current implementation of LineSplitterFilter does this: The first part of a road is added as a road, all remaining parts are added as lines. With a simple change all parts are added as roads: Index: LineSplitterFilter.java =================================================================== --- LineSplitterFilter.java (revision 2581) +++ LineSplitterFilter.java (working copy) @@ -84,7 +84,7 @@ log.debug("saving next part"); l.setPoints(coords); next.doFilter(l); - l = new MapLine(line); + l = line.copy(); count = 0; first = false; The interesting part for me is that the following routines seem to expect exactly this, but parts of the code was never executed. See also http://gis.19327.n5.nabble.com/PATCH-v1-highwayCount-tp5748554p5748864.html I also wonder if it really makes sense to limit the check "Non-routable way with routable type ..." to resolution 24. I'll try to find out more tomorrow. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/merge-lines-and-routing-tp5758913.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

5 26

Commit: r2585: correct check regarging non-routable type usage: check only on resolution 24
by svn commit 04 May '13

04 May '13

Version 2585 was committed by gerd on Tue, 30 Apr 2013 correct check regarging non-routable type usage: check only on resolution 24

4 4

garmin 08 and 09 error
by steve sgalowski 03 May '13

03 May '13

how can i correct the codeing now , so that i can make my maps again as i have a non- routable way now in all of my maps with a garmin 08 , 09 error code Stephen

3 7

question reg. display tool
by GerdP 02 May '13

02 May '13

Hi Steve, the NetCheck displays some messages like this: ERROR: node-count=6, nblocks=0 [VIA VITTORIO VENETO] 1afd I don't understand why the node-count value is compared with def.nblocks The write routine in mkgmap doesn't write the number of nodes to the place where display tool reads the def.nblocks value. Am I missing something? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/question-reg-display-tool-tp5759106.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 4