February 2013 - mkgmap-dev - The mkgmap lists

The substitution $(....)
by Ataro A 10 Feb '13

10 Feb '13

I've erroneusly used the substitution $(....) in a rule in the style file lines as follow: highway=* & route=* {set route_ref='$(route_ref), ${ref}' | '${ref}'} and mkgmap don't return with some error or warning. This substitution $(....), as state the manual, are reserved for the use in a apply rule in the relations file and are not usable in other style files. I've found a mkgmap bug or what other? Ataro

2 1

Display name change
by Bob Hawkins 10 Feb '13

10 Feb '13

I last processed downloaded Geofabrik OSM data through mkgmap six months ago. Using the latest splitter and mkgmap .jar files and creating .img files from the split .osm.gz files and a .typ file, Command Prompt displays the following for each file it processes: "WARNING: Style uses tag 'display name' which is deprecated and will be removed soon. Please use the name tag 'mkgmap:display_name' instead.". I am unsure to what file(s) this refers. The mkgmap batch file I use contains the following instruction: "java -ea -Xmx1100m -jar mkgmap.jar --style-file=mystyle_nonrouting --draw-priority=28 --remove-short-arcs --gmapsupp -c template.args 1000A.TYP". I should be grateful for advice that will permit me to resolve this issue.

2 1

Long distance routing
by Steve Ratcliffe 10 Feb '13

10 Feb '13

Hi I was wondering what the current state of long distance routes was thought to be? Although there are comments on the wiki etc that routing only works over a couple of tiles, I see far better results although it depends on the software. In particular with MapSource 6.10 it is almost impossible to route over the SW corner of a tile. In other words if the obvious route enters the tile from the south side, and exits on the west side (or visa versa), it will always pick a route that goes round the tile instead rather than through it - or crash or straight-line if there is no such route. Although I've seen this happen when routing across other corners, not often - it almost always works. However on the latest version of mapsource/basecamp this problem has entirely disappeared. So either it was a mapsource bug (unlikely?) or whatever we were doing wrong no longer matters. ..Steve

2 1

Routing issues
by Fabian S. 09 Feb '13

09 Feb '13

Hi there! we are having a problem with the maps: In some cases, the routing uses streets that don't exist! Here's a video that shows the problem: http://www.youtube.com/watch?v=SUG370VDBFY We are using the following commands with r2479: wget -O map1.osm http://api.openstreetmap.org/api/0.6/map?bbox=57.349,-20.300,57.82,-19.976 wget -O map2.osm http://api.openstreetmap.org/api/0.6/map?bbox=57.298,-20.529,57.818,-20.250 java -jar mkgmap.jar --reduce-point-density=4 --reduce-point-density-polygon=8 --show-profiles=1 --add-pois-to-lines --index --location-autofill=bounds,is_in,nearest --latin1 --ignore-maxspeeds --remove-short-arcs --min-size-polygon=10 --add-pois-to-areas --preserve-element-order --route --name-tag-list=name:en,int_name,name:zh_py,name:engels,name --bounds=bounds --drive-on-left --gmapsupp map1.osm map2.osm Could anybody comment on what might be causing this problem? Is is a bug in mkgmap or in the OSM data? Greets, Fabian

8 12

pebkac - index not working
by Rich 08 Feb '13

08 Feb '13

this is probably me doing something wrong, but i can't figure out what is it :) generating garmin image with, for example : --mapname=1234 --description=Latvia-2013.01.01 --country-name=Latvia --country-abbr=LV --route --remove-short-arcs --add-pois-to-areas --index --gmapsupp the resulting map works great in vista hcx and nuvi 50, but address search does not work - nothing is found at all. if searching for nearby towns/cities, they are found properly, though. using mkgmap-r2337. what am i doing wrong ? -- Rich

3 6

Weekend in Essen
by Steve Ratcliffe 08 Feb '13

08 Feb '13

Hi I've just posted a thank you to those that organised and supported the event last weekend on the news section of the web site and I'd like to repeat those thanks here. It was very useful and great fun! See: http://www.mkgmap.org.uk/news/2013/02/08/weekend-in-essen Here are some of the discussions/requests, which may provide someone with an idea of something that they could do. - Split maps along country borders. This would allow maps to be fully customised to country conventions. I'd always thought of this being a splitter function and it would be ideal to perform it there, but it could perhaps be done using the multi-polygon code. - Newer features such as lane assist and speed limits. It would be worthwhile looking into this as there is perhaps something that we could do that has enough coverage in OSM, but on the whole it is difficult to say how if or when such things could be developed, since development time is limited even for things that we already know how to do, such as house numbers. - Doing something with values that are separated with ';'. This is clearly desirable, but knowing what exactly to do is less clear. I think it would have to be enabled on a tag-by-tag basis. - There was a question about how include files in the style work which I will make a separate post on. ..Steve

2 1

Commit: r2481: Save the net1 offsets when reading road def's.
by svn commit 07 Feb '13

07 Feb '13

Version 2481 was committed by steve on Thu, 07 Feb 2013 Save the net1 offsets when reading road def's.

1 0

highwayCount
by GerdP 07 Feb '13

07 Feb '13

Hi, I think we should clean the code regarding the usage of highwayCount, treatAsNode, onBoundary and other attributes of Coord. My understanding is this: 1) highwayCount should be increased for each coord instance that is part of a road. I think the right place to do that is in an extra loop at the beginning of StyledConverter.removeShortArcsByMergingNodes(). A coord instance that is part of more than one road is considered to become a road junction. 2) in many places I see something like this: if(co.getOnBoundary()) { // this point lies on a boundary // make sure it becomes a node co.incHighwayCount(); } I think this is an abuse of the highwayCount. The highwayCount is used to determine junctions of roads (e.g. in the frigRoundabout() method) and I don't see why the attribute "onBoundary" should change the "highwayCount" If "onBoundary = true" and "highwayCount > 1" both have a meaning like "isRoadJunction" I suggest that we create a new flag with this name. Does that make sense? If yes, how can I verify the results of my changes ? With my logic, I see ~20% fewer coords with highwayCount > 1^, so the change is big. The unit tests do not help much, SimpleRouteTest failes because the NOD size is different, but I doubt that the expected size is a must? ciao, Gerd -- View this message in context: http://gis.19327.n5.nabble.com/highwayCount-tp5748434.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 4

patch for display tool
by GerdP 07 Feb '13

07 Feb '13

Hi Steve, I had to change a few things to get display.jar. I assume you don't compile it with mkgmap from current trunk? display.patch <http://gis.19327.n5.nabble.com/file/n5748533/display.patch> Gerd -- View this message in context: http://gis.19327.n5.nabble.com/patch-for-display-tool-tp5748533.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

1 0

Reading NET section
by Steve Ratcliffe 07 Feb '13

07 Feb '13

Hi I would like to make the attached change when reading files to save the file offset that the road information is found. This will make it possible to fix the NetCheck program to be more accurate. It should have no effect on creating maps. ..Steve

2 1