- mkgmap-dev - The mkgmap lists

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

minor enhancement to tile-splitter
by Jon Burgess 08 Mar '09

08 Mar '09

The attached patch makes the tile splitter look at the width of the area at both the min & max latitude. This slightly reduces the number of tiles needed for the planet and makes the splitting slightly faster. Based on planet-071010.osm.bz2 * original => 49 tiles * with patch => 44 tiles Mkgmap does not manage to generate a map from the output though, it fails with an out of heap space error. I'll try adding something which limits the maximum bounds of each tile too. Jon

2 2

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

08 Mar '09

Rev 3 - avoid NPE when POI doesn't have a name. Hi, The attached patch (based on r973) 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

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

08 Mar '09

Hi, The attached patch (based on r973) 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 2

POI Addresses and POIs for areas, documentation for map-features
by Paul Ortyl 08 Mar '09

08 Mar '09

Hello, I have just tried the latest version of mkgmap from trunk with --add-pois-to-areas. It looks like the addresses were attached only to the original POIs but not for the generated for areas. Bug? I have tried to change/add/remove displayed POIs and the zoom level where they are visible. Have I properly understood, that information in resources/styles/default/* is identical to map-features.csv. If that is correct, what is the preferred way for modification of the presentation style? What documentation would you recommend? The wiki (http://wiki.openstreetmap.org/wiki/Mkgmap/help/custom) is a bit short ;) Where can I find a readable list of all these hex numbers used in style specification. Thanks, Paul -- Don't take life too seriously; you will never get out of it alive. -- Elbert Hubbard

3 5

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

08 Mar '09

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 2

Fast Food and --add-pois-to-areas
by Dermot McNally 08 Mar '09

08 Mar '09

Hi folks, With the POI stuff now merged, I build latest SVN to try the --add-pois-to-areas option. My test POI was a fast food restaurant: http://www.openstreetmap.org/browse/way/4482136 This doesn't show up as a POI on the generated map - have I just made a poor choice and used a POI type not yet supported for areas or is something else wrong? Thanks, Dermot -- -------------------------------------- Iren sind menschlich

2 5

Polygonal tiles?
by Wolfgang v. Hansen 06 Mar '09

06 Mar '09

Hi, can mkgmap produce a routable map from non-rectangular tiles? -Wolfgang

3 3

[PATCH] - In search of the fabled "destination only routing" bit
by Mark Burton 06 Mar '09

06 Mar '09

Hi, The other day, Bernhard said: > Has anybody played with the RoadNetwork.DELIVERY field until know ? To > me it looks like this might solve the problem. If the access is totally > blocked to a area the routing gets very strange. If I want to go into > this area I get routed via a unpaved road which is also blocked. If I > set the RoadNetwork.DELIVERY field the routing gets more useful. I can now confirm that what used to be called RoadNetwork.DELIVERY bit is, in fact, the fabled "destination only routing" bit. If you set this bit for a road, mapsource (and presumably, the gps also) will avoid routing you through that road unless your destination is only accessible using that way. It only appears to affect the routing of cars/motorcycles - for all the other types of vehicles, it makes no difference. The attached patch activates this feature when it sees either access=destination, motorcar=destination or motorcycle=destination tags. It issues a warning for access=destination to remind the map maker that only car routing is affected. Please test the attached patch. Many thanks Bernhard for pointing me in the right direction. Cheers, Mark PS - still don't know what the other spare bit (what was called "emergency") is for.

3 5