March 2009 - mkgmap-dev - The mkgmap lists

Commit: r990: In fact line should be deleted altogether
by svn commit 31 Mar '09

31 Mar '09

Version 990 was commited by steve on 2009-03-31 22:24:32 +0100 (Tue, 31 Mar 2009) In fact line should be deleted altogether - Gleb Smirnoff

1 0

Commit: r989: There is a small error in StylePrinter.java, that leads to printing
by svn commit 31 Mar '09

31 Mar '09

Version 989 was commited by steve on 2009-03-31 22:07:45 +0100 (Tue, 31 Mar 2009) There is a small error in StylePrinter.java, that leads to printing into two different output streams and garbled output. The attached patch fixs. - Gleb Smirnoff

2 1

[PATCH] Enable some POI translations
by Marko Mäkelä 31 Mar '09

31 Mar '09

The attached patch enables some POI translations that I have tested previously on my Garmin Edge 705. The key=value pairs are based on Tagwatch or the OpenStreetMap wiki: http://tagwatch.stoecker.eu/Europe/En/ignored_amenity.html http://tagwatch.stoecker.eu/Europe/En/keystats_tourism.html http://wiki.openstreetmap.org/wiki/Tag:shop%3Dgeneral Marko

1 0

[PATCH] Translate amenity=restaurant cuisine=...
by Marko Mäkelä 31 Mar '09

31 Mar '09

I tested the attached patch in my Garmin Edge 705. The menu item names below are my translations from Finnish. cuisine=steak shows up in the "food+drink"/"steak restaurant" menu. cuisine=grill, cuisine=barbecue are "food+drink"/"grill restaurant". cuisine=asian is "other Asian". That's why I threw in cuisine=korean and cuisine=japanese. The fallback cuisine=* is listed in "food"/"other". Restaurants without cuisine will only be listed in "food+drink"/"all classes" not even in "food+drink"/"other". cuisine=cafe/diner is at resolution 21, to match the translation of amenity=cafe. In my test (mapping one cafe resolution 20 and another to 21), two "food+drink"/"cafe" menus were generated, one for each cafe. The values for cuisine are from http://tagwatch.stoecker.eu/Europe/En/keystats_cuisine.html Please consider applying the patch. Marko

1 0

Commit: r988: Generate sorted road data to enable finding addresses and intersections.
by svn commit 31 Mar '09

31 Mar '09

Version 988 was commited by markb on 2009-03-30 21:50:43 +0100 (Mon, 30 Mar 2009) Generate sorted road data to enable finding addresses and intersections. Incremental search for alphanumeric street names basically works but could do with more testing with non-ascii characters. Incremental search for numeric street names and all city names does not work although if you input the whole name it will match. No support yet for house numbers.

4 3

[patch] fix output of StylePrinter
by Gleb Smirnoff 31 Mar '09

31 Mar '09

There is a small error in StylePrinter.java, that leads to printing into two different output streams and garbled output. The attached patch fixs. -- Totus tuus, Glebius. GLEB-RIPE

1 0

patch to correct plazas in default style
by Ben Konrath 31 Mar '09

31 Mar '09

Hi, Currently the default style creates a residential road for plazas correctly marked with highway=pedestrian, area=yes. An example of such a plaza can be found here: http://openstreetmap.org/?lat=9.932554&lon=-84.071404&zoom=18&layers=B000FTF A patch to correct this behaviour is attached. Comments are appreciated. Cheers, Ben diff --git a/resources/styles/default/lines b/resources/styles/default/lines index 9594a9a..cc21b2c 100644 --- a/resources/styles/default/lines +++ b/resources/styles/default/lines @@ -24,7 +24,7 @@ highway=footway [0x16 road_class=0 road_speed=0 resolution 23] highway=minor [0x06 road_class=1 road_speed=2 resolution 21] highway=motorway {add oneway = yes } [0x01 road_class=4 road_speed=6 resolution 12] highway=motorway_link [0x01 road_class=4 road_speed=3 resolution 16] -highway=pedestrian [0x06 road_class=0 road_speed=0 resolution 22] +highway=pedestrian & area!=yes [0x06 road_class=0 road_speed=0 resolution 22] highway=primary [0x02 road_class=3 road_speed=4 resolution 19] highway=primary_link [0x03 road_class=3 road_speed=3 resolution 19] highway=residential | highway=living_street [0x06 road_class=0 road_speed=2 resolution 21] @@ -40,7 +40,7 @@ highway=unclassified [0x06 road_class=1 road_speed=2 resolution 21] highway=unsurfaced [0x0a road_class=0 road_speed=1 resolution 21] # Mop up any unrecognised highway types -highway=* [0x07 ] +highway=* & area!=yes [0x07 ] natural=coastline [0x15 resolution 12] power=line [0x29 resolution 20] diff --git a/resources/styles/default/polygons b/resources/styles/default/polygons index 606f26f..74b5d74 100644 --- a/resources/styles/default/polygons +++ b/resources/styles/default/polygons @@ -42,4 +42,9 @@ natural=wood [0x50 resolution 18] place=village [0x03 resolution 18] +# squares and plazas +highway=pedestrian & area=yes [0x17 resolution 20] +# other highways that have area=yes set must be parking lots +highway=* & area=yes [0x05 resolution 21] + waterway=riverbank [0x46 resolution 20]

6 16

[PATCH v10] support for motorway exits (last call before committing to trunk)
by Mark Burton 30 Mar '09

30 Mar '09

Patch version 10 (based on r983) - minor tweaks - no real differences Please test this if you can. If no one reports that it stops the map being built or that it wrecks the the map, I shall commit this patch soon, imperfect though it is (exit search still doesn't use the right map by default). ---------------------- Hi, The attached patch provides basic support for processing motorway exits. It's still work in progress but I am posting it so that people can try it out, find what breaks and suggest improvements. Exits in the garmin world have to be associated with a motorway (sounds reasonable) but they don't have to coincide with a node on the motorway, i.e. the exit node doesn't have to be on the motorway! In the case where the exit is defined with a "motorway_junction" tag on one of the motorway's nodes, nothing needs to be done for an exit POI to be generated as mkgmap will work out the association itself (only for roads that are "motorway" or "trunk"). If your "motorway_junction" node is separate from the motorway (not very sensible, perhaps) or you are using a "highway=services" tag on a node (which probably will be near the road but not actually on it) you will need to add a "exit:road_ref" tag to specify the reference of the road that the exit is associated with. Here's example tags that associates a services with the road A41. name=Toy Town Services highway=services exit:road_ref=A41 Note, at this time "highway=services" for areas is not yet supported. Seems to me that it could be by using the new area POIs functionality to make a POI automatically. One attribute of exits is that they exit to somewhere and you need to be able to specify where the exit is going to because mkgmap can't guess that (well, not yet, anyway). To do this, use an "exit:to" tag. So you can say: highway=motorway_junction ref=5 exit:to=Telford East Garmin allow you to specify all sorts of facilities info for an exit and this is described in the cgpsmapper docs. Of course, there is no standard OSM means to express that so we have yet another tag "exit:facility" that should be set to a comma separated set of values that describe the facility. The syntax is exactly the same as used in mp files. Something like this (values are examples, not sensible): exit:facility=0x01,N,0x04,Hello World Yet more flexibility is introduced by the fact that the type code for the exit can be one of a huge range. At the moment, I am using: highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } highway=motorway_junction [0x2000 resolution 16] highway=services { name '${ref} ${name}' | '${ref}' | '${name}' } highway=services [0x210f resolution 16] 0x2000 means "exit no services" 0x210f means "exit (service") I played around with the codes and on my gps some codes make little symbols appear to show that the exit has food, hotel, etc. We can probably make it use a suitable code from the facilities info but I haven't looked into that yet. All feedback is welcome. Cheers, Mark

5 5

Correct use of codepages
by Nop 30 Mar '09

30 Mar '09

Hi! When one tries to create a map of greece and all names look good in the .osm but are garbled in the images, I guess the reason must be an improper use of the codepage parameter. How would you call mkgmap to translate greek characters correctly? thanks Nop

2 1

Motorway exits and the base map
by Toby Speight 30 Mar '09

30 Mar '09

Whilst looking at motorway exits on my Legend recently, I noticed that in "Find/Exits" the context menu lets you choose which map to use for exits (unlike all other searches). By default, "choose best maps" is selected; I don't know how it makes this choice - perhaps the map has some sort of resolution/accuracy field somewhere, and ours isn't marked as being more accurate than the base map? I know it's a bit late to add to this old discussion, but perhaps it might help.

2 1