November 2009 - mkgmap-dev - The mkgmap lists

Commit: r1407: Revert "Reduce MAX_ARC_LENGTH to 35000 as larger values cause routing failures."
by svn commit 27 Nov '09

27 Nov '09

Version 1407 was commited by markb on 2009-11-27 17:39:42 +0000 (Fri, 27 Nov 2009) Revert "Reduce MAX_ARC_LENGTH to 35000 as larger values cause routing failures." This reverts commit 1373 (git bfa62e6c57160e9bfca8acaeecf4c9acc350e506).

1 0

Commit: r1406: Stop the DP filter from removing points that are located at nodes.
by svn commit 27 Nov '09

27 Nov '09

Version 1406 was commited by markb on 2009-11-27 17:27:52 +0000 (Fri, 27 Nov 2009) Stop the DP filter from removing points that are located at nodes. Until now, the DP filter would consider any point that isn't actually a routing node fair game for removal. However, if two lines are generated from the same set of points and one has nodes and the other doesn't, they will end up different shapes which looks wrong. So now, the DP filter will avoid removing any points that have been marked as "preserved".

1 0

Commit: r1405: Remove boundary from CoordNode class as Coord has a similar field.
by svn commit 27 Nov '09

27 Nov '09

Version 1405 was commited by markb on 2009-11-27 17:27:48 +0000 (Fri, 27 Nov 2009) Remove boundary from CoordNode class as Coord has a similar field.

1 0

weird: file missing when # of files > 10?
by Valentijn Sessink 27 Nov '09

27 Nov '09

Hi list, I wrote about this before: my first map in the mapset, 63240001.img, is missing. I tracked this down to revision r1363 (which is a merge from the mapset branch) and today even further tracked it down to revision 1323 within the (deleted) mapset branch. However, I can't find any clues in r1323 as to what causes this. Further experiments showed even weirder results: as I compile my maps from a template.args file, it showed that having 63240001-63240009 in there would give me the correct map; having a 10th file in there made the first one missing. (Currently, while compiling the Netherlands, my template.args file has 14 entries. Any number above 9 makes the first one disappear). And indeed, when I duplicated the first file like so: mapname: 99999999 input-file: 63240001.osm.gz mapname: 63240001 input-file: 63240001.osm.gz mapname: 63240002 [...] ... the map would be correct (with the void 99999999 probably missing, and 63240001 included). Now I'm stumped. Would anyone know what's going on here? I thought of a race condition and removed the --max-jobs option, but that makes no difference. Best regards, Valentijn

2 6

[PATCH v3] make DP filter avoid removing points located at nodes
by Mark Burton 27 Nov '09

27 Nov '09

v3 - hopefully, now works again after being broken by the round coords filter. --------- v2 - based on r1402. ----------- Hi Felix, Please try the attached patch. I've tested it inasmuch that it doesn't blow up but whether it actually does the right thing when you have a routable and non-routable way from the same set of points, I don't know. Cheers, Mark

2 1

Map end user documentation?
by Marko Mäkelä 27 Nov '09

27 Nov '09

Now that the days are getting short at my latitude (60N), I can easily distinguish lit=yes/no for highway=bus_stop, shelter=yes. I am going to submit a patch to the default style, to replace the '+' for shelter=yes with '*' if the shelter is lit. The use case would be that you get a flat tyre from the scrambled stones that they are spreading on cycleways in the hope that it might get icy for a couple of days before the spring. Then you might want to find the nearest lit shelter where you can fix the tyre, so that you don't have to stand in the rain under a street lamp. I was thinking that these */+/- codes can be cryptic for map users. Is there already some map user documentation for mkgmap-generated maps? Where should it live? In the OSM wiki or on the mkgmap server? The master copy could live in the mkgmap source repository (so that it would be updated in sync with the default style), but I think that it would be good to have a browseable copy somewhere else. Best regards, Marko

2 3

Re: [mkgmap-dev] [PATCH] patch (V8) for simplifying ways and reducing img size
by Johann Gail 27 Nov '09

27 Nov '09

Patch V8 updated to r1404. - do not merge lines at resolution 24, as the dp filter is disabled. With this change there should be no longer routing problems. ------------------------------------------------------------------- Patch V7 is now based on the R1041 (and the SizeFilter.patch) - removing of the -- suppress-dead-end-nodes option, as it causes problems with routing. - code cleanup, introduction of new classes. ------------------------------------------------------------------- Patch V4 now supports three options. Its build on top of r972. With all three options used, it will reduce the four bavaria tiles from 58MB to 46MB. Drawing at low zoom levels gets speed up significantly at my etrex. This will not be the last version of the patch. I'm working further on it, but have no idea, how fast work will progress. The options are as follows: +--reduce-point-density=num + Simplifies the ways with the douglas peucker algorithm. + num is the maximal allowed error distance, by which the resulting + way may differ from the original one. + This distance gets shifted with lower zoom levels. + Recommended setting is 10, this should lead to only small differences + (Default is 2.6, which should lead to invisible changes) + +-- suppress-dead-end-nodes + Do not generate nodes at the end of an dead end way. + Decrease file size and should speed up routing slightly. + May possibly cause errors, but not seen any one at the moment. + +--merge-lines + Try to merge lines. This helps the simplify filter to straighten out + longer chunks at lower zoom levels. Decreases file size more. + Increases paint speed at low zoom levels .

2 2

[PATCH v1] make DP filter avoid removing points located at nodes
by Mark Burton 27 Nov '09

27 Nov '09

Hi Felix, Please try the attached patch. I've tested it inasmuch that it doesn't blow up but whether it actually does the right thing when you have a routable and non-routable way from the same set of points, I don't know. Cheers, Mark

6 27

DP Filter and areas at Resolution=24
by Felix Hartmann 26 Nov '09

26 Nov '09

Could the DP Filter not remove any points at resolution=24? Or is there another reason why many small polygons like buildings get mashed? In most cases there are not even any reductions in points needed to draw the areas. mkgmap: vs mapnik:

4 5

Log-File for mkgmap-processing
by Jan Tappenbeck 26 Nov '09

26 Nov '09

hi ! is there a possiblity to get a log-report for the steps of mkgmap-processing ??? the result is empty so i want to find the reason. regards Jan :-)

2 3