March 2009 - mkgmap-dev - The mkgmap lists

[PATCH v7] alpha support for motorway exits and service areas
by Mark Burton 10 Mar '09

10 Mar '09

Patch version 7 (based on r974) - hot on the heels of v6, this patch now splits an area if it contains more than 255 points - if you get any of the error messages about not adding POI to index then something's not right yet. ---------------------- 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. Oh yes, you must have a region defined for your map, if you don't, the exits will not be generated. All feedback is welcome. Cheers, Mark

1 0

[PATCH v6] alpha support for motorway exits and service areas
by Mark Burton 10 Mar '09

10 Mar '09

Patch version 6 (based on r974) - now avoids assertion when too many POIs are in a subdivision - this is just a quick fix to allow the map to be generated - the real solution (I guess) would be to split the subdivision. ---------------------- 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. Oh yes, you must have a region defined for your map, if you don't, the exits will not be generated. All feedback is welcome. Cheers, Mark

1 0

how-to in using mkgmap
by maning sambale 10 Mar '09

10 Mar '09

Hi, I prepared a simple how-to in making garmin map with mkgmap. This is a request from several people. http://epsg4253.wordpress.com/2009/03/06/diy-garmin-routable-map-from-opens… Please have a look and correct if there are errors or a better way in doing it. -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

7 9

Too many indexed points?
by Wolfgang v. Hansen 10 Mar '09

10 Mar '09

Hi, I am wondering what the message "Can't set city point index for <city> (too many indexed points in division)" really means. I only get it in areas that are not very well mapped but contain a significant amount of populated places. Furthermore I have the impression that the presence of a road network helps to suppress this error. -Wolfgang

1 0

Mapsource feedback
by David 09 Mar '09

09 Mar '09

Routing with the latest Windows XP Mapsource version and Ireland.osm from Geofabrik.de (03/09/2009) built with mkgmap revision 974 works fine ! "Chapeau bas" to all the developers. Now routes respects oneway restriction on motorways and round about. To obtain this result I use the splitter on the file. The result is a osm file size divided by 2. Thank you.

1 0

No airports in map
by Carlos Dávila 09 Mar '09

09 Mar '09

Although there are some nodes tagged as airports (aeroway=aerodrome) in my osm data, I can't search them in the map generated with mkgmap in my nuvi, neither under "Transit" nor under "Spell name" options. Are they lacking in style file or some other reason for that? Regards Carlos

2 2

Style file rule: English name in addition to default name
by Clinton Gladstone 09 Mar '09

09 Mar '09

Hello, I would like to do something like the following in my points style file: place=* & name:en=* & name:en != name {name '${name} (${name:en})' | '${name:en}' } That is, for places which have an English name ('name:en') defined, and where the English name is not the same as the plain 'name' tag, I wish to display the English name in parenthesis after the plain name. For example, I would like to display "München (Munich)" in my map, but I would also like to simply display "Karlsruhe" instead of the redundant "Karlsruhe (Karlsruhe)". I know I can set a default for the name (for example, to have name:en always take precedence), but this isn't quite what I would like. Also, I know from the documentation that in theory 'name' "is distinct from any 'name' tag on the element", so my rule should not work. I also know that it does not work in practice. :-) Is there any trick for doing this? Cheers.

2 1

[PATCH v4] alpha support for motorway exits and service areas
by Mark Burton 09 Mar '09

09 Mar '09

Patch version 4 (based on r974) - misc fixes ---------------------- 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. Oh yes, you must have a region defined for your map, if you don't, the exits will not be generated. One disappointment. So far, I have not yet been able to make the exits findable. I am working on that aspect but don't know when I will succeed. All feedback is welcome. Cheers, Mark

2 3

No through routing support now in trunk
by Mark Burton 09 Mar '09

09 Mar '09

Hi, I committed the no through routing (access=destination) stuff as the only feedback received was +ve and I don't believe it should cause serious breakage. If you have any problems, I will fix it! Cheers, Mark

3 2

Commit: r974: Added support for "no through routing" (only affects car routing).
by svn commit 09 Mar '09

09 Mar '09

Version 974 was commited by markb on 2009-03-09 12:23:55 +0000 (Mon, 09 Mar 2009) Added support for "no through routing" (only affects car routing). One of the Table A access bits appears to enable "no through routing" so use that to implement the "destination" access restriction. It only affects the routing of cars/motorcycles.

1 0