February 2013 - mkgmap-dev - The mkgmap lists

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: r2443: Change mkgmap default map license text to ODbL
by svn commit 12 Apr '13

12 Apr '13

Version 2443 was committed by wanmil on Thu, 10 Jan 2013 Change mkgmap default map license text to ODbL

4 3

Suppressing dead-end-checks for parking entrance/exit
by Marko Mäkelä 02 Apr '13

02 Apr '13

Hi, I would like to suppress warnings for oneways leading to or from underground parking when the entrance and exit are not connected by underground lines. One of these two parking sites is using a relation to group the entrance and exit together. 2013/02/26 10:33:43 WARNING (RouteNode): 63240005.osm.pbf: Oneway road (http://www.openstreetmap.org/browse/way/187642343) goes nowhere at http://www.openstreetmap.org/?mlat=60.86977&mlon=26.70146&zoom=17 2013/02/26 10:33:43 WARNING (RouteNode): 63240005.osm.pbf: Oneway road (http://www.openstreetmap.org/browse/way/135634060) comes from nowhere at http://www.openstreetmap.org/?mlat=60.86846&mlon=26.70092&zoom=17 2013/02/26 10:33:43 WARNING (RouteNode): 63240005.osm.pbf: Oneway road (http://www.openstreetmap.org/browse/way/207169562) goes nowhere at http://www.openstreetmap.org/?mlat=60.86960&mlon=26.70261&zoom=17 I tried adding fixme=continue in the points file: resources/styles/default/points Index: resources/styles/default/points =================================================================== --- resources/styles/default/points (revision 2498) +++ resources/styles/default/points (working copy) @@ -79,7 +79,10 @@ amenity=library [0x2c03 resolution 24] amenity=nightclub [0x2d02 resolution 24] amenity=nursing_home [0x2b04 resolution 24] -amenity=parking [0x2f0b resolution 24 default_name 'Parking'] +# Disable dead-end-checks for parking entrance/exit +entrance=* | amenity=parking_exit { add fixme=continue } +amenity=parking | amenity=parking_entrance | parking=* +{add fixme=continue} [0x2f0b resolution 24 default_name 'Parking'] amenity=pharmacy [0x2e05 resolution 24] amenity=place_of_worship [0x2c0b resolution 24] amenity=police [0x3001 resolution 24] It did not suppress the warnings, because the way parser would interpret the original tags for nodes, not processed ones. Any ideas how to resolve this? I do not feel like adding checks for the parking and entrance tags to the way parser. Best regards, Marko

3 17

locator rules and transparent maps
by Thorsten Kukuk 01 Apr '13

01 Apr '13

Hi, I tried to create a transparent map (an additinal layer on top of my basemap) containing address informations, but this does not seem to work. If I include the locator rules (means only create mkgmap:* variables), the maps are no longer transparent, independent of what I use for options. If I remove all mkgmap:* assignements, the map is transparent again. Any idea about this? Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

4 5

uncommitted patches for mkgmap
by GerdP 17 Mar '13

17 Mar '13

Hi, I got no feedback on these posts regarding patches: http://gis.19327.n5.nabble.com/Why-do-we-have-the-Area-too-small-to-split-a… http://gis.19327.n5.nabble.com/PATCH-v1-Optimize-filters-for-shapes-tp57441… I used both of them and I think they are ok. Is it okay to commit them? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/uncommitted-patches-for-mkgmap-tp5749600.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 6

Flooding in Biograd
by RheinSkipper 15 Mar '13

15 Mar '13

After deleting the remove-short-arcs option from my settings, I can see the correct coastline in Biograd (Croatia) now. But even when I precompile sea from recent shape files or use the latest from Wanmil, I have some flooding in the harbor. I have seen other OSM maps which do not have this problem. Which option does the trick?

4 11

Address include in polygons style file superfluous?
by WanMil 12 Mar '13

12 Mar '13

Hi, I have started writing some pages for the new mkgmap documentation about address search. This made me thinking if the address include is required for the polygons style file. Is it possible to see the address information of a polygon in a Garmin map (or better a mkgmap created map)? If the answer is no we could remove the include from the polygons style file which saves some memory and some processing steps. Additionally we could remove the processing of polygons from the LocationHook. The only thing that need to be changed is the -add-pois-to-areas option. The POIs created by this option must be worked out by the LocationHook because the polygons do not contain the address info any more. But I think this would be easy. Any comments? WanMil

4 5

Commit: r2493: tuning: use memory efficient map based on fastutil to store coords
by svn commit 09 Mar '13

09 Mar '13

Version 2493 was committed by gerd on Wed, 20 Feb 2013 tuning: use memory efficient map based on fastutil to store coords

2 1

Why does the --process-exits option only work on motorways
by Franco Bez 07 Mar '13

07 Mar '13

Hi everybody, first of all I'd like to say that the --process-exits option does a marvelous job on motorways. The display on the Nüvi 40 finally shows sensible texts. Now I'm wondering why this option only works for motorways. IMHO trunk roads are almost the same thing from a driver's point of view. So motorways and trunk roads should be handled in a very similar manner. It would vastly improve the displayed texts on the Nüvi. Currently I get "Roundabout" in the display on almost every trunk exit. ( Down here in Bavaria it's quite fashionable to have roundabouts distributing the traffic from and to trunk roads. ) Or is there any deeper reason for --process-exits option only working on motorways ? Ciao, Franco

2 3