- mkgmap-dev - The mkgmap lists

Style Rules for naming objects
by Minko 09 Apr '13

09 Apr '13

Hi, In the default style there is a file called "name" in the inc directory which leads to unwanted names at for instance cities. # Rules for naming objects, based on the following tags: # name, brand, operator, ref One of the rules puts operator in front of the name tag. name '${operator}: ${ref} ${name}' | '${operator}: ${name}' | '${operator}: ${ref}' | '${operator}' | '${ref}' In the case of the city of Leuven this leads to strange rendering of the city Leuven: "Toerisme Vlaams-Brabant: Leuven" http://www.openstreetmap.org/browse/node/1448497912 Suggestion for improvement: Better use these rules only where it is meant for (amenity=* | shops=*)? and not for city pois.

1 0

NullPointerException & housenumber rules
by Minko 08 Apr '13

08 Apr '13

Hi, I've got a NullPointerException error when I add the following line to the address rules (inc/address file) addr:housenumber=* & addr:street=* & source=BAG {delete addr:housenumber} I put this line before the following lines: mkgmap:street!=* & addr:street=* { set mkgmap:street='${addr:street}' } mkgmap:street!=* & addr:housename=* { set mkgmap:street='${addr:housename}' } This rule I want to add because I merge so called BAG dataset later to my osm extract, and I want to filter all BAG data that has already been imported in the NL's until now. If you put the line at the end of the address file everything is ok (but probably doesn't do anything). It happens with the default style as well as my own styles. The NPE occurs with mkgmap-r2544, r2560 and mkgmap-overview2 jar files with --x-housenumbers With mkgmap-r2538 this NPE does not occur. One of the tiles that is affected and contains the tag addr:housenumber=* & addr:street=* & source=BAG as well as my merged BAG data is uploaded here: http://mijndev.openstreetmap.nl/~ligfietser/test/10010033.o5m The error message is java.lang.NullPointerException at java.util.regex.Matcher.getTextLength(Unknown Source) at java.util.regex.Matcher.reset(Unknown Source) at java.util.regex.Matcher.<init>(Unknown Source) at java.util.regex.Pattern.matcher(Unknown Source) at uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberMatch.parseHousenumber(HousenumberMatch.java:121) at uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberMatch.<init>(HousenumberMatch.java:50) at uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.match(HousenumberGenerator.java:206) at uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.generate(HousenumberGenerator.java:147) at uk.me.parabola.mkgmap.osmstyle.StyledConverter.end(StyledConverter.java:342) at uk.me.parabola.mkgmap.reader.osm.ElementSaver.convert(ElementSaver.java:244) at uk.me.parabola.mkgmap.reader.osm.o5m.O5mBinMapDataSource.load(O5mBinMapDataSource.java:53) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:115) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:144) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:228) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:225) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

2 1

Commit: r2562: Housenumbers: catch the case when a house number tag is removed by the style
by svn commit 08 Apr '13

08 Apr '13

Version 2562 was committed by wanmil on Mon, 08 Apr 2013 Housenumbers: catch the case when a house number tag is removed by the style

1 0

Default style for Bridleway
by Roger Calvert 07 Apr '13

07 Apr '13

I have noticed that the default style allocates code 0x07 to both bridleways and service roads. This means they come out looking the same on devices (I identified this in the field on my GPSmap60CSx, and confirmed it with MapSource and Basecamp, before finding it in the 'lines' file). In my view, it would be better to use either 0x16 (footway/path) or 0x0a (track) for bridleway, with appropriate permissions. But would this have routing implications? (I am a walker, not a rider or cyclist, so I'm not directly concerned about routing.) I can of course modify my copy of the 'lines' file, but is there a case for changing the default? Roger -- ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------

5 4

Routing issue to POI
by Enrico Liboni 06 Apr '13

06 Apr '13

Folks, I'm sometime getting routing issues to some POIs - most seems ok but some are always showing the problem. I'm wondering if what I'm hitting is the problem described at: http://wiki.openstreetmap.org/wiki/Mkgmap/known_issues#add-pois-to-areas_so… Here's what happens: * In my garmin device I select a poi * the device calculates the route, but the purple path displayed does not follow real streets (it goes mostly parallel to them - see below pictures) Any idea? In the example the POI name is: Where To->Point if Interest->Hospitals "Ospedale Ca' Foncell" - it's near Treviso, Italy) http://imageshack.us/a/img829/3130/leftt.jpg http://imageshack.us/a/img198/3915/overviewer.jpg http://imageshack.us/a/img6/1766/poiv.jpg I'm using splitter r299, mkgmap r2540 (same issue with older version), fresh maps from geofabrick and command line is: java -Xmx2000M -jar ./mkgmap/mkgmap.jar --family-name="OSM Ita and Alps" --description="OSM Ita and Alps" --route --remove-short-arcs --add-pois-to-areas --bounds=bounds --location-autofill=bounds,nearest,is_in --index --gmapsupp --output-dir="./data/" ./data/6*osm.pbf Many thanks as usual!!! Enrico

4 14

Commit: r2560: Omit highway=proposed ways.
by svn commit 06 Apr '13

06 Apr '13

Version 2560 was committed by marko on Sat, 06 Apr 2013 Omit highway=proposed ways.

1 0

Configuration for overview map
by GerdP 06 Apr '13

06 Apr '13

Hi all, Yesterday I've committed r2546 in the overview2 branch. In addition to the functionality implemented in overview_v3.patch this implements also the support of data with extended types. Please try it with the known options: --x-overview-add-polygons --x-overview-add-lines --x-overview-add-points Now I wonder what kind of further configuration we could need. The following points were discussed: 1) Allow to read data from other levels, not only the one with the lowest resolution. I tried it and I don't think this will increase quality, but it increases run time quite heavily. 2) Allow to apply filters, so that fewer objects are placed in the overview map. I think this could be implemented with a simple list like this: # filter for overview map point:type_1 point:type_2 ... point:type_n line:* polygon: This would add points with the type type_1 to type_n, all lines and no polygons. The file woud replace the --x-overview-add-xxx options. I will try to implement it in this way, please suggest changes if something else is needed. 3) Style files for the overview map I don't see how this could be used when the data is read from *.img files. 4) Read data from other sources, e.g. precompiled sea/land polygons. I don't plan to code that but I think this remains a possible option to increase quality. Open questions: 1) The current implementation adds a background polygon with type 0x4a even if option --transparent is used. I assume this is correct? 2) The background is now added as a rectangle. This could be changed so that it covers only the areas covered by the *.img files. Is this needed? Ciao, Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Configuration-for-overview-map-tp5755669.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

6 35

Address Search Debugging
by Valerii Pekarskyi 04 Apr '13

04 Apr '13

Hello, Can anyone tell me how can I check countries/regions/cities/streets/housenumbers that mkgmap converts to my img file? I would like to check it while or just after the conversion, before loading map set to my Garmin unit or to the MapSource. Why I want such information? I am trying to make that "full address search" that is announced on the Mkgmap page on the OpenStreetMap wiki, and have a lot of troubles with it: 1) there is no house search at all (is it not done yet?) 2) some cities have street search while others do not and I have troubles with separating ones from others 3) I heard there are two search indexes could be generated with mkgmap - could anyone provide a bit more details? Which indexes are used on Dakota and on Nuvi, for example, and which are used by MapSource? How can I check they are generated as I expected I am converting Ukraine with a bit changed style of Max Vasilev (original here:https://velo100mapper.googlecode.com/svn/trunk) and my changed styles that I am trying to make working are here: https://github.com/Larry0ua/ua-convert/tree/master/mkgmap-stranger/stranger…. If someone is interested he could find generation parameters a folder up. I am sorry if that question was already written to this mail list before me, but search given nothing to me. Best Regards, Larry0ua

5 11

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