August 2012 - mkgmap-dev - The mkgmap lists

access=no//access=private on short lines vs long lines
by Felix Hartmann 30 Aug '12

30 Aug '12

Mkgmap has some filters that allow for example not putting small areas into the map. It would be great, to have a very simple filter for highways too, called via the style-file. I would imagine the following command to be very useful: highway=service & ( access=private | access=no ) & mkgmap:filter:length<100m {delete highway; delete oneway; delete tunnel; delete bridge} It does not need to be meters, it can be Garmin units, so one can quickly experiment with it. This would come very handy so one could make clean maps without showing the private garden micromapping that is getting more and more common. Excluding all highways with access=no/access=private, however often runs into problems with faulty tagging. Having a length check should get rid of annoying for general use not usable micromapping. As the mkgmap filter would only be called upon request from the style-file, it should not harm performance (checking length of every way would of course). -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

3 5

routing across tile borders
by Minko 30 Aug '12

30 Aug '12

One of my cycle map users reported an issue about non routable roads across tile borders. I investigated the case and came to the following conclusion: -roads marked with toll=yes are not routable across a tile border in case of pedestrian routing. -within the tile itself, routing is ok -Car or bicycle navigation respond as expected, no problems here -this isssue is only observed in Mapsource, not in Basecamp nor on the GPS. -I tested it with several maps and also older mkgmap versions they all show the same issue. BTW I use toll=yes to mark all roads without a cycling route to force the routing on cycling routes when you choose toll road avoidance. Is this a known issue?

2 3

bug in add road-speed-min & add road-speed-max implementation.
by Felix Hartmann 30 Aug '12

30 Aug '12

There is a bug in the implementation of the road-speed-min and road-speed-max command. Here is a table of what is happening, and what should happen: Status quo --> Current Behaviour --> Supposed Behaviour - highway with road_speed=X and road_class=Y, next to a point which has the following action added: add mkgmap:road-class ='-1'; add mkgmap:road-class-min='1' ; add mkgmap:road-class-max='3' ; add mkgmap:road-speed ='-1'; add mkgmap:road-speed-min='1' ; add mkgmap:road-speed-max='3' XY ---> XY ---> XY 00 ---> 11 ---> 00 11 ---> 11 ---> 00 22 ---> 11 ---> 11 33 ---> 22 ---> 22 44 ---> 33 ---> 33 45 ---> 33 ---> 33 (34 would also be a logically sound solution, as the decrease was maximum 1, but it decreased 2). While in this case the road-class-max=3 and road-speed-max=3 is working correctly (though of course it is stupid to set a road-class-max if you decrease the road-class or road-speed - so it is debatable on how to logically solve this ), the important bit of road-class-min and road-class-max is heavily failing. Instead of decreasing it, it actually increases it. If you work with add mkgmap:road-class ='+1 ' or mkgmap:road-speed='+1', the same problem is of course happening. -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

1 0

Bridges over tidal water
by Roger Calvert 30 Aug '12

30 Aug '12

I am using a separate coastline file to avoid local flooding problems, but I find that bridges over tidal water disappear in Mapsource. Without the coastline file, they are fine. Can anybody suggest a remedy, please? Roger -- ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------

2 2

Style: Loch Ness disappears
by WanMil 29 Aug '12

29 Aug '12

Hi, the OSM forum reported that Loch Ness (way 4049566) is not displayed using the default style. It is tagged as name=Loch Ness natural=water tourism=attraction The default style contains the matching rule tourism=* & area!=no & waterway!=* [0x13 resolution 24] The rule for natural=water is included from the waters style but it seems to be ordered after the rules of the default style. I guess included styles are processed last? Two questions: 1. Should the default style be changed so that natural=water supersedes the tourism tag? I think yes. 2. I remember that there have been discussions about inclusion of style. From my unexperienced view (I do not change styles very often) the current inclusion seems to be not very useful. I would prefer to have a kind of #include rule within the style file itself. Another idea would be to have a base-style-pre and base-style-post in the info file. base-style-pre would be included before the stlye whereas base-style-post would be included after the style. The unuseable location style is also an example that the current inclusion system should be improved. Is it possible to change the inclusion of styles so that it is more self-explanatory and more useful? WanMil

4 5

location-autofill=bounds uses a boundary not surrounding the POI
by Bernhard Moser 24 Aug '12

24 Aug '12

Hi, I've generated a map covering Innsbruck in Tyrol (Austria) with the default mkgmap built-in style. Then I was wondering why almost all POI close to the city center have obtained the correct address regarding country, region, streetname and housenumber except the city tag. Instead of showing an address like, for example, ..., 6020 Innsbruck, Bezirk Innsbruck-Stadt , the postcode and the city name from the neighboring town Natters are used resulting to an address like ..., 6161 Natters, Bezirk Innsbruck-Stadt . The address tags are obtained by using the setting location-autofill=bounds - neither is_in nor nearest - with the newest bounds files from [1]. The entry in the style file to get the mkgmap:city tag is mkgmap:country=AUT & mkgmap:city!=* & mkgmap:admin_level8=* { set mkgmap:city='${mkgmap:admin_level8}' } from the default mkgmap style. After studying the OSM data I've probaly found the source of the error. As expected mkgmap is searching for an precompiled boundary with mkgmap:admin_level8 tag close to the POI. But in OSM data there exists no boundary with admin_level=8 for the city Innsbruck. The next boundary surrounding the city and therefore the POI is the county border of Innsbruck-Stadt with admin_level=6, see [2], which is used for mkgmap:region correctly. There exists no other administrative boundary with reasonable admin_level for obtaining the city tag SURROUNDING the city and especially the POI. Therefore I would expect that the style file including the line above will not set any mkgmap:city tag associated with the precompiled bounds. But as observed, the administrative boundary of the neighboring county Natters, see [3], is used instead. This boundary, obviously used for obtaining the city tag, is NOT surrounding the POI and therefore should not be used for assigning any address tag to this POI! The reason for this effect might be an imperfection in the precompiling process for the boundary files - please correct me if I'm wrong. Either the location-autofill process is using the nearest boundary with matching admin_level rather than searching for the surrounding one or the OSM data is causing these troubles on the other hand. Both boundaries [2][3] close to the POI share some lines and are implemented as relations. Resolving whether the POI is inside or outside of the boundary might be faulty. Is this effect known or can somebody reproduce this? Greetings, Bernhard [1] http://www.navmaps.eu/wanmil/bounds_20120708.zip [2] http://www.openstreetmap.org/browse/relation/113642 [3] http://www.openstreetmap.org/browse/relation/942840

5 10

compile maps
by steve sgalowski 24 Aug '12

24 Aug '12

after splitting maps , and starting to compile them how do i split the maps into 2 gb maps ? and in the mkgmap compile mode , how do i somehow extract poi files from either pbf or osm input files Stephen

1 0

Problem creating index
by Hakim DWAIK 23 Aug '12

23 Aug '12

Hi Steve, I dont have the compiling error anymore ! Thanks a lot. But i also dont have my index in the img file. I'm trying different solutions with the osm tools. I don't want to bother this mailing list about compilation options if this is only a dev forum. Do you know other forums for osmtools (osmconvert, osmfilter and mkgmap) ? Many thanks. Hakim.

2 1

Routing problem on cut between maps
by Jan Dolman 23 Aug '12

23 Aug '12

I am having problems with the following intersection between the N402 and the N201 on my generated map: http://www.openstreetmap.org/?lat=52.22506&lon=5.01017&zoom=16 The problem occurs on the N201 at the point where the two one-way roads merge again, just to the west of the intersection. Eastbound, there is no problem. Westbound, the generated map won't let me route past the point where the roads merge again. Problem occurs both in Mapsource and my GPS device (276C). I split the map using the following two tiles, which cut the map just a couple of metres to the east of the merge point: West tile (52.119140625,4.74609375) to (52.294921875,5.009765625) East tile (52.119140625,5.009765625) to (52.294921875,5.361328125) It looks like this adds a new merge point for the one-way roads on the cut between the tiles. As a result there are now two one-way streets exactly on top of each other between this new merge point and the original one. The routing software is apparently only using the eastbound one. Software used: mkgmap 2311 and splitter r200 Used OSM data from Aug. 11 Hope I'm clear... Jan

1 0

Commit: r2314: Ignore access=permissive|designated|official just like access=yes.
by svn commit 22 Aug '12

22 Aug '12

Version 2314 was commited by marko on 2012-08-15 21:07:57 +0100 (Wed, 15 Aug 2012) Ignore access=permissive|designated|official just like access=yes.

8 15