- mkgmap-dev - The mkgmap lists

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

Commit: r2477: Avoid that multipolygon cutting algorithm creates very small polygons
by svn commit 07 Feb '13

07 Feb '13

Version 2477 was committed by wanmil on Wed, 06 Feb 2013 Avoid that multipolygon cutting algorithm creates very small polygons The algorithm has been changed so that cuts with a high aspect ratio are preferred to those that cut multiple inner polygons. This avoids that the cut algorithm creates narrow but wide polygons that are filtered out when zoomed out. This avoids white stripes in sea areas.

3 8

poiDispFlag="0xc" in locatorconfig.xml
by Felix Hartmann 07 Feb '13

07 Feb '13

Just a quick question. I couldn't find anywhere documentation what it does exactly. Why is it added for some countries? And what does regionOffset="number" do? -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

6 10

mkgmap 2470 breakage
by Felix Hartmann 07 Feb '13

07 Feb '13

As of 2470 I run into the following error. If I downgrade to 2468 my map compiles fine again without this error. (I first thought this is due to the remove_short_arcs_v4.patch, but actually I run into it with any mkgmap version >=2470) java.lang.UnsupportedOperationException at uk.me.parabola.mkgmap.osmstyle.eval.AbstractOp.value(AbstractOp.java:110) at uk.me.parabola.mkgmap.osmstyle.eval.EqualsOp.eval(EqualsOp.java:44) at uk.me.parabola.mkgmap.osmstyle.eval.AndOp.eval(AndOp.java:34) at uk.me.parabola.mkgmap.osmstyle.eval.AndOp.eval(AndOp.java:34) at uk.me.parabola.mkgmap.osmstyle.eval.AndOp.eval(AndOp.java:34) at uk.me.parabola.mkgmap.osmstyle.eval.AndOp.eval(AndOp.java:34) at uk.me.parabola.mkgmap.osmstyle.eval.AndOp.eval(AndOp.java:34) at uk.me.parabola.mkgmap.osmstyle.eval.AndOp.eval(AndOp.java:34) at uk.me.parabola.mkgmap.osmstyle.eval.AndOp.eval(AndOp.java:34) at uk.me.parabola.mkgmap.osmstyle.ActionRule.resolveType(ActionRule.java:59) at uk.me.parabola.mkgmap.osmstyle.RuleSet.resolveType(RuleSet.java:68) at uk.me.parabola.mkgmap.osmstyle.StyledConverter.convertWay(StyledConverter.java:216) at uk.me.parabola.mkgmap.reader.osm.ElementSaver.convert(ElementSaver.java:237) at uk.me.parabola.mkgmap.reader.osm.bin.OsmBinMapDataSource.load(OsmBinMapDataSource.java:75) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:144) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:201) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:198) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

3 4

Commit: r2479: Replace poiDispFlag attribute in LocatorConfig.xml with streetBeforeHousenumber and postalcodeBeforeCity
by svn commit 06 Feb '13

06 Feb '13

Version 2479 was committed by wanmil on Wed, 06 Feb 2013 Replace poiDispFlag attribute in LocatorConfig.xml with streetBeforeHousenumber and postalcodeBeforeCity The poiDispFlag value sometimes did overwrite flags that were set at other places (e.g. the transparent flag). In the LocatorConfig.xml only the two flags streetBeforeHousenumber and postalcodeBeforeCity can be set. So it is better to use two separate flags instead a bit coded value with only two relevant bits. This might fix a problem where maps were not transparent in some countries also the --transparent option was set.

1 0