November 2009 - mkgmap-dev - The mkgmap lists

Commit: r1403: Further tweaks to turn restriction diagnostic messages.
by svn commit 23 Nov '09

23 Nov '09

Version 1403 was commited by markb on 2009-11-23 11:43:51 +0000 (Mon, 23 Nov 2009) Further tweaks to turn restriction diagnostic messages.

2 1

Missing browse URL in turn restriction warning
by Marko Mäkelä 23 Nov '09

23 Nov '09

Mark, Could you please change the coordinates in this message to a browse URL for the node? Perhaps there could be a virtual method that would output the browse URL for the OSM primitive, or failing that, coordinates. WARNING (RestrictionRelation): Turn restriction http://www.openstreetmap.org/browse/relation/333165 'from' member should be a Way but is a NODE: 567968919 @ 60,27677/24,99587 Best regards, Marko

1 0

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

22 Nov '09

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 3

[PATCH v2] - round coordinates when zoomed out
by Mark Burton 22 Nov '09

22 Nov '09

v2 - also removes points with the same coordinates as the previous point. I know that this also gets done by the DP filter but it's very easy to do while rounding the coordinates and it does shrink the number of points to be processed by subsequent filters. This version of the patch should produce the same map as v1 of the patch. Unless anyone has any problems with this patch, I intend to commit it in a few days as I think the line gap-filling is worthwhile. ------- Having filled some gaps with that last little patch, I was wondering why I still had quite a few gaps when zoomed out. Obviously, the coords weren't being rounded to nearest given the zoom level. So, the attached patch does that rounding and, lo and behold, even more gaps have disappeared. Please give it a go, especially for maps that cross the equator/day line where the coords flip signs. Sure to be buggy but it's looking quite promising. BTW - this patch does not contain the last patch but they probably should be used together. Mark

3 7

Overview Map still broken
by Felix Hartmann 22 Nov '09

22 Nov '09

I am not sure if you are aware, that the overview map still is not correct (this causes on my compile of Asia large parts of the map to be invisible in Mapsource). Also for smaller maps it often seems to be too small. See the two following screenshots: 1. overview map of Asia missing in the middle (or is this a Mapsource problem with maps spanning too large areas?): 2. Overview map broken for a small testmap that I use as a legend. See the boundaries that are partly outside of the map area: The actual side of the white background seems correct, but moved. If I zoom in the boundary will dissapear outside of the white area.

2 3

Commit: r1402: If a polish map contains any background polygons, don't generate one.
by svn commit 22 Nov '09

22 Nov '09

Version 1402 was commited by markb on 2009-11-22 22:21:55 +0000 (Sun, 22 Nov 2009) If a polish map contains any background polygons, don't generate one. Normally, a polygon of type 0x4b is automatically generated to cover the map's background. For OSM maps that can't explicitly contain such a polygon, this is reasonable. Polish maps can contain polygons of type 0x4b. So if a Polish map does contain any polygons of type 0x4b, suppress the automatic generation of the background polygon.

1 0

Commit: r1401: Added RoundCoordsFilter to round lat/lon to nearest when shift > 0.
by svn commit 22 Nov '09

22 Nov '09

Version 1401 was commited by markb on 2009-11-22 22:21:51 +0000 (Sun, 22 Nov 2009) Added RoundCoordsFilter to round lat/lon to nearest when shift > 0. Also removes identical consecutive points - they will get removed later anyway but it's very easy to do here and it makes sense to remove them early to reduce the number of points needed to be processed by the following filters.

1 0

Commit: r1363: Merge the mapset branch back to trunk.
by svn commit 22 Nov '09

22 Nov '09

Version 1363 was commited by steve on 2009-11-09 10:42:25 +0000 (Mon, 09 Nov 2009) Merge the mapset branch back to trunk. Makes it possible to have maps with different family id's in the same gmapsupp.

3 3

Missing bicycle turn directions
by Marko Mäkelä 22 Nov '09

22 Nov '09

I did not get two turn instructions on my latest bicycle ride. Luckily, it was a familiar route and I was paying attention to the map, not keying in the ref= of a bus stop or something. The first occurrence was when I was approaching http://www.openstreetmap.org/browse/way/5053613/history from north. (It was version 3; I tried to make the angle a little steeper in version 4. For what it is worth, I built the map with mkgmap --adjust-turn-headings.) The second occurrence was a T crossing at the north end of http://www.openstreetmap.org/browse/way/34137262/history (I did not move the north node in the last revision.) I was supposed to turn left at the end of the way, but I did not receive any instructions. Could adjust-turn-headings be straightening the line too much? Or should I move the curve of http://www.openstreetmap.org/browse/way/23098405 a little bit to the west to improve the routing instructions? Best regards, Marko

2 2

Routing issue
by Nakor 22 Nov '09

22 Nov '09

Hello, I have spotted a routing issue with a mkgmap generated map. I was able to reproduce it in several versions: 1188, 1228 and 1265. The source file is the Cloudmade Michigan file (Sep 30), that I split using splitter. I can reproduce the issue either using the whole Michigan state (5 tiles) or just the tile where it happens. The tile were it happens has the following bounding box: 44.472656,-87.890625 to 47.548828,-83.144531 You can look at the following map: http://maps.cloudmade.com/?layers=&lat=46.115967&lng=-85.494747&zoom=13&dir… If I try to route from A to B, either on MapSource or on my etrex Vista, I get a line from A to D and a line from D to C If I try to route from A to C (or west of C), MapSource shows an error and the GPS can route but stille displays A-D-B lines. If you try either route (A to B or A to C) in Cloudmade, they work fine. I can provide the osm data (22 Mb gzipped) if needed. Thanks, N.

4 15