October 2009 - mkgmap-dev - The mkgmap lists

some comments on mkgmap default style
by maning sambale 06 Feb '10

06 Feb '10

Hi, some observation about the default style: 1. Coastlines are shown as thin blue lines, is it possible to render coastline as polygon, where sea areas are shaded as blue. A work around I did before is to manually edit all sea-areas and then add a natural=water tag (bad data edit) . 2. Administrative boundaries clutter the map. They appear like roads and can be confusing while driving. Suggestion is to make the admin boundaries thinner. Hope it helps improving the default stylesheet. -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

5 8

amenity=embassy not handled by mkgmap ?
by Hendrik Oesterlin 03 Jan '10

03 Jan '10

Hello, First, I would introduce myself: I am living in New Caledonia and I bought an Garmin nüvi 755 GPS because I have the possibility to import the data from openstreetmap.org. I have to travel to New Zealand next month, and during my last stay there I was sad of using my non-graphic GPS to report my position to an paper map.... especially during driving ;-) In the meantime, I got the virus and I added plenty of data to New Caledonia and I compiled an gmapsupp.img for NC. Now I noticed that an POI amenity=embassy added in OSM is not available in the produced gmapsupp.img (both with mkgmap v1303 et 1311) Is this an error in mkgmap? How can I make embassies correctly display in Garmin maps? Some of them are just tagged as amenity=public_building and display correctly on the Garmin map. But this seems to be an dirty work around, as the dedicated amenity=embassy exists. -- Kind regards Hendrik Oesterlin New Caledonia ___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

5 8

[PATCH v1] Merge similar lines and ways
by Thilo Hannemann 30 Nov '09

30 Nov '09

The attached will merge lines that are similar* after styling. It is activated by the switch "--merge-lines". As there are less way fragments, the Douglas-Peucker filter will work better and the routing should improve somewhat, because the ways will be longer and the routing algorithm won't give up too soon. The size of the resulting map is reduced a little bit as well. The patch is based on code published by Johann Gail on this mailing list. *) similar means that they have the same attributes: name, ref, access, etc. Regards Thilo

6 15

Turn restrictions in foot mode
by Chris-Hein Lunkhusen 25 Nov '09

25 Nov '09

Hi, I tested some turn restrictions in Mapsource and found that they are used in all modes (car/bicycle/foot). Is there an option to disable them for foot ? In Germany the traffic signs for T.R. are only valid for vehicles. Chris

4 4

access=no on a cycleway doesn't work?
by Federico Cozzi 24 Nov '09

24 Nov '09

Hello, I am not subscribed to the list but I read an interesting message by Marko Mäkelä in the archive which I quote here: -------------------- > In my neighbourhood there's a highway=cycleway that is currently blocked > due to construction works. As the cycleway is still there (the cycleway > itself is not under construction), I tagged it access=no. However, > mkgmap still tries to route me over it. > Is that because styles file saying: "highway=cycleway {add access = no; > add bicycle = yes;" ? Or just use the "native" tags, but explicitly translate "access" to the vehicle-class tags and do not treat "access" specially in the core, e.g., access=no { add bicycle=no; add foot=no; add motorcar=no; add taxi=no; ... } -------------------- I do not know how mkgmap internally works, but I think that "access" should not even belong to the core! As far as I know Garmin maps only handle a fixed number of vehicle classes (e.g. motorcar, taxi, bicycle, etc.), not a general purpose catch-all vehicle class. Therefore the style file should say: access = no {add motorcar = no; add taxi = no; add bicycle = no; ...} highway = cycleway {add motorcar=no; add taxi=no; add bicycle = yes; ...} This way, a standard highway=cycleway with no additional tags would get bicycle=yes (and everything else = no); a highway=cycleway with access=no would get bicycle = no (and also everything else = no) Bye, Federico

5 11

Missing bicycle turn directions
by Marko Mäkelä 22 Nov '09

22 Nov '09

I did not get two turn instructions on my latest bicycle ride. Luckily, it was a familiar route and I was paying attention to the map, not keying in the ref= of a bus stop or something. The first occurrence was when I was approaching http://www.openstreetmap.org/browse/way/5053613/history from north. (It was version 3; I tried to make the angle a little steeper in version 4. For what it is worth, I built the map with mkgmap --adjust-turn-headings.) The second occurrence was a T crossing at the north end of http://www.openstreetmap.org/browse/way/34137262/history (I did not move the north node in the last revision.) I was supposed to turn left at the end of the way, but I did not receive any instructions. Could adjust-turn-headings be straightening the line too much? Or should I move the curve of http://www.openstreetmap.org/browse/way/23098405 a little bit to the west to improve the routing instructions? Best regards, Marko

2 2

Routing issue
by Nakor 22 Nov '09

22 Nov '09

Hello, I have spotted a routing issue with a mkgmap generated map. I was able to reproduce it in several versions: 1188, 1228 and 1265. The source file is the Cloudmade Michigan file (Sep 30), that I split using splitter. I can reproduce the issue either using the whole Michigan state (5 tiles) or just the tile where it happens. The tile were it happens has the following bounding box: 44.472656,-87.890625 to 47.548828,-83.144531 You can look at the following map: http://maps.cloudmade.com/?layers=&lat=46.115967&lng=-85.494747&zoom=13&dir… If I try to route from A to B, either on MapSource or on my etrex Vista, I get a line from A to D and a line from D to C If I try to route from A to C (or west of C), MapSource shows an error and the GPS can route but stille displays A-D-B lines. If you try either route (A to B or A to C) in Cloudmade, they work fine. I can provide the osm data (22 Mb gzipped) if needed. Thanks, N.

4 15

Continue patch not working on two routable roads.
by Felix Hartmann 21 Nov '09

21 Nov '09

In general the continue patch works great. However the continue patch does not seems to drop stuff if mkgmap later on thinks it is identical?? After messing for 3 hours now trying to find out why some actions don't work I have found out that mkgmap does not enact the "continue" action, in case it thinks that the result is identical - or the tags are identical. OR if there is a difference in the routing attributes (or oneway). So currently it is not possible to put two oneway streets counterfacing via continue command, nor two identical ways with different routing speed. So lets start easy: *The following also does not work * highway=* [0x01 road_class=0 road_speed=1 resolution 20 continue] highway=* [0x01 road_class=0 road_speed=1 resolution 24] highway=* [0x01 road_class=0 road_speed=1 resolution 24] *While the following works without probs:* highway=* [0x02 road_class=0 road_speed=1 resolution 20 continue] highway=path [0x01 road_class=0 road_speed=1 resolution 24] highway=path [0x01 road_class=0 road_speed=1 resolution 24] *The following example simply does not work:* highway=* & incline=down {set oneway=yes; set copy=98} highway=* & incline=up {set oneway=-1; set copy=99} highway=* & incline<0 {set oneway=yes; set copy=98} highway=* & incline>0 {set oneway=-1; set copy=99} highway=* & copy=* [0x16 *road_class=4 road_speed=3* resolution 20 continue] highway=* & copy=99 {set oneway=yes} [0x01 road_class=0 road_speed=1 resolution 24] highway=* & copy=98 {set oneway=-1} [0x01 road_class=0 road_speed=1 resolution 24] *- here 0x16 only is output. The following example will work however:* highway=* & incline=down {set oneway=yes; set copy=98} highway=* & incline=up {set oneway=-1; set copy=99} highway=* & incline<0 {set oneway=yes; set copy=98} highway=* & incline>0 {set oneway=-1; set copy=99} highway=* & copy=* [0x16 continue resolution 20] highway=* & copy=99 {set oneway=yes} [0x01 road_class=0 road_speed=1 resolution 24] highway=* & copy=98 {set oneway=-1} [0x01 road_class=0 road_speed=1 resolution 24]

2 2

NSIS patch
by Nakor 16 Nov '09

16 Nov '09

Hello, Please find attached a patch that will generate a .nsi file if --nsis is provided on the command line. This .nsi file can be use with NSIS ( http://nsis.sourceforge.net) to build an EXE installer for installing the maps with MapSource on Windows. Known limitation: for now I assume that --index and --tdbfile were present on the command line. If not the installer will probably fail because of missing files. Please let me know your feedback. Thanks, N.

5 12

[PATCH] Display road name instead of ref in routing directions
by Clinton Gladstone 12 Nov '09

12 Nov '09

The attached patch causes road names (instead of refs) to be displayed in routing directions. That is, you will get "Turn right onto Weseler Strasse (B58)" instead of just "Turn right onto B58". If you use a style other than the default, you will have to add a "add display_name = '${name} (${ref})'" statement to the appropriate lines in your style file. Example: highway=secondary {name '${ref|highway-symbol:oval} ${name}' | '${ref|highway-symbol:oval}' | '${name}'; add display_name = '${name} (${ref})' } The patch reads the display_name tag according to the style file, and writes it as a second label. This second label will be used for routing directions, at least in the case where a highway symbol is displayed on the map for the road in question. - In the patch, display_name is set in the style file to "Name (Ref)". You may adjust this to your liking. It may be expedient to simply display just the name without the ref in brackets. Since this may significantly improve routing directions in certain circumstances, I would appreciate your feedback. Some additional comments: - display_name may not be the best name for the style file tag. - The patch to StyledConverter.java simply prepends the display_name to the list of references. This takes advantage of the side-effect that the refs are all written sequentially as additional labels. It might be a cleaner approach to directly write the display name as a secondary label, but the patch was a very quick and cheap way of testing this concept. - The display_name will also be displayed in Mapsource when you cursor over the road with the mouse. Cheers.

7 10