April 2013 - mkgmap-dev - The mkgmap lists

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

mkgmap support for JRE 1.6.x will be discontinued
by toc-rox 02 Apr '13

02 Apr '13

=========================================================== You are using an old Java runtime environment 1.6.0_26 mkgmap support for JRE 1.6.x will be discontinued after June 2013. Please update the JRE to the latest release. =========================================================== What are the reasons for this ? Regards Klaus BTW: Java 1.7 isn't yet available as installable package on all platforms. -- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-support-for-JRE-1-6-x-will-be-discont… Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 1

Commit: r2544: Apply destination hints in the same way like exit hints
by svn commit 01 Apr '13

01 Apr '13

Version 2544 was committed by wanmil on Mon, 01 Apr 2013 Apply destination hints in the same way like exit hints When having set the process-destination option mkgmap now cuts all _link ways with a destination set into two or three parts. The second part is tagged with mkgmap:dest_hint=true which can be used by style implementors to set a routable Garmin id (not 0x08 and 0x09) with a name that hints to the destination. This is better than the old method of forwarding destinations because all destinations within complex motorway junctions are also used now. The cut algorithm has been improved as it tries much harder to use existing points instead of adding new points. This looks smoother. Also use 0x06 (residential) instead of 0x01 (motorway) for the hints. This looks better in the default style of MapSource.

1 0

wrong elevationprofiles
by Henning Scholland 01 Apr '13

01 Apr '13

Hi there, I've finished my holidayand brought you a problem with the elevationprofil. What I did: Generate elevationlines, merged them to osm-data generated a map (in end 12/2012) with style-rules and set-profile=1. The shown elevation-lines were almost correct, but the estimated altimeters generated by my Oregon 300 out of the profile were very bad and doesn't fit to reality and the elevation-lines. As example I've chosen the incline of Arthurs Pass in New Zealand ( http://www.openstreetmap.org/?lat=-42.8397&lon=171.6113&zoom=12&layers=Q ). This is the generated profile: http://www.aighes.de/data/71.bmp This is the route: http://www.aighes.de/data/133.bmp This is the recorded profile (which fits with reality and elevation-lines): http://www.aighes.de/data/profile.png Does anybody discovered similar effects? I'm pretty new to using set-profile=1, so maybe this isn't a bug in mkgmap and I made just an error. Henning, who is very surprised about the things happend to mkgmap during my holiday...great!!!

5 7

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

Commit: r2543: Add some javadoc to the house number code
by svn commit 01 Apr '13

01 Apr '13

Version 2543 was committed by wanmil on Mon, 01 Apr 2013 Add some javadoc to the house number code

1 0

Patch v3 for overview map
by GerdP 01 Apr '13

01 Apr '13

Hi List, while trying to implement a decoder for data with extended types I found two bugs in the version 2 of the patch: 1) the img format allows (normal) types 0x01 - 0x3f for lines and 0x01-0x7f for polygons, the original code made no destinction 2) the first point of a line or shape was dropped, this caused esp. many lines to be missing in the overview map. overview_v3.patch <http://gis.19327.n5.nabble.com/file/n5755292/overview_v3.patch> The compiled binary is here: http://files.mkgmap.org.uk/download/97/mkgmap.jar Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Patch-v3-for-overview-map-tp5755292.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 5