December 2014 - mkgmap-dev - The mkgmap lists

Commit: r3391: correction: Coord.shortestDistToLineSegment sometimes returned
by svn commit 24 Dec '14

24 Dec '14

Version mkgmap-r3391 was committed by gerd on Wed, 24 Dec 2014 correction: Coord.shortestDistToLineSegment sometimes returned too large values, esp. for points far from the equator. Expected effect of the change: Small improvements in the DouglasPeuckerFilter as it is more likely keeping the right points.

1 0

Error in distance calculations
by Gerd Petermann 24 Dec '14

24 Dec '14

Hi programmers, we are using a formular to calculate the shortest distance between a point P and a line segment A-B (A,B, and P are coordinates) The result is either the distance between P and A or P and B or the perpendicular distance between the closest point on the line A-B and P. In the current code that we use to find out what case we have we are using the deltas of the garmin lat/lon values. This formular completely ignores the fact that we have coordinaties on a sphere (well, nearly a sphere). The distance between two points with the same deltaLat and deltaLong is very different depending on the position on the earth, the farer away from the equator the longer the distance. The effect of the error is that HousenumberGenerator sometimes fails to find the right road segment for a housenumber, and probably the DouglasPeuckerFilter sometimes removes the wrong points. The algos I am talking about: HousenumberGenerator.getFrac() HousenumberGenerator.distanceToSegment() and Coord.shortestDistToLineSegment() which is more or less a copy of the above. Up to now I found only one computation that seems to work: http://stackoverflow.com/questions/1299567/how-to-calculate-distance-from-a… and esp. parts of the code from here: https://github.com/Epsidon/PhoneGapExperiments/blob/master/Data/src/Distanc… The problem: This algo uses a lot of trigonometric functions to calculate the result (convert to and from cartesian coordinates) , so it is ~30 times slower. We do this computation very often in HousenumberGenerator and DouglasPeuckerFilter. Is anybody aware of a better compromise between calculation speed and error? Gerd

2 3

[Patch v3] addr:interpolation
by Gerd Petermann 23 Dec '14

23 Dec '14

Hi all, attached is v3 of the patch. Major change to v2: - change distance to road segment calculation I noticed that some house numbers were associated with the wrong part of a road. Example: The housenumber 22 from way 144166632 was associated to the end of way 10049349 instead of way 10049349. Both are named Ahornstraße and form a T, the building is a the junction node. @WanMil: The code is still not 100% correct, as getFrac() should probably use Math.cos() somewhere, else values with large latitudes are very wrong. Do you have a better one? Gerd

1 0

Commit: r3390: After Label2 implemented in last patch, the sizes of the label sections have increased.
by svn commit 22 Dec '14

22 Dec '14

Version mkgmap-r3390 was committed by steve on Mon, 22 Dec 2014 After Label2 implemented in last patch, the sizes of the label sections have increased. Fix the polish tests for label and road name sizes.

1 0

Commit: r3389: 1. Line RouteParam= have most parameters optional, "oneway" and "toll" too. Mkgmap should use defaults, when parameters are missing.
by svn commit 22 Dec '14

22 Dec '14

Version mkgmap-r3389 was committed by steve on Mon, 22 Dec 2014 1. Line RouteParam= have most parameters optional, "oneway" and "toll" too. Mkgmap should use defaults, when parameters are missing. 2. CGPSmapper supports multiple labels, I have added support for lines "Label2=" and "Label3=". 3. Country name can have separator and short name. I have included function unescape() for "Country=". - Andrzej Popowski

1 0

[Patch v2] addr:interpolation
by Gerd Petermann 22 Dec '14

22 Dec '14

Hi all, attached is v2. It turned out to be quite complicated to interpret the data provided with this tag, and I found only few places were this helps to provide better data. On the other hand, I see no negative effects besides the additional code complexity. A good place to see how address search is improved is here: http://www.openstreetmap.org/way/36787892#map=17/51.88859/-8.57449 With the trunk version, a search for 178 Rosewood lists several numbers, e.g. 184, 170, 199 and so on. None is really correct. The patched version shows exactly one entry, which is probably very close. Same result with other numbers which do not appear as housenumbers. A patched binary based on r3366 is here: http://files.mkgmap.org.uk/download/236/mkgmap.jar Gerd

3 4

Tile contains both drive-on-left and drive-on-right roads
by Stéphane MARTIN 21 Dec '14

21 Dec '14

Hi, I got this line in a log file : "2014/12/20 17:36:29 GRAVE (StyledConverter): 29730001.o5m: Attention: Tile contains both drive-on-left (95) and drive-on-right roads (7568)" How to find what is the wrong road(s) ? - mkgmap-r3383 - log.props : # This is the logging properties file for use with mkgmap: # java -ea -Dlog.config=logging.properties -jar mkgmap.jar ... # The default level FINE, WARNING, INFO, SEVERE .level=SEVERE #handlers: java.util.logging.ConsoleHandler handlers: java.util.logging.FileHandler # package or class name with .level appended and then the level #uk.me.parabola.imgfmt.level=INFO #uk.me.parabola.mkgmap.build.level=INFO uk.me.parabola.mkgmap.main.Main.level=WARNING #uk.me.parabola.mkgmap.main.MapMaker.level=INFO uk.me.parabola.mkgmap.general.RoadNetwork.level=WARNING #uk.me.parabola.mkgmap.general.MapLine.level=INFO uk.me.parabola.mkgmap.osmstyle.level=SEVERE uk.me.parabola.mkgmap.osmstyle.StyledConverter.level=WARNING uk.me.parabola.mkgmap.reader.osm.level=WARNING uk.me.parabola.mkgmap.reader.osm.MultiPolygonRelation.level=SEVERE uk.me.parabola.mkgmap.reader.osm.RestrictionRelation.level=WARNING uk.me.parabola.mkgmap.reader.osm.Restriction.level=WARNING uk.me.parabola.mkgmap.reader.osm.boundary.level=WARNING #uk.me.parabola.mkgmap.osmstyle.stats.level=INFO # For ConsoleHandler java.util.logging.ConsoleHandler.level=FINE java.util.logging.ConsoleHandler.formatter=uk.me.parabola.log.UsefulFormatter # For FileHandler java.util.logging.FileHandler.level=FINE java.util.logging.FileHandler.encoding=UTF-8 java.util.logging.FileHandler.formatter=uk.me.parabola.log.UsefulFormatter #java.util.logging.FileHandler.limit=5000000 #java.util.logging.FileHandler.count=4 java.util.logging.FileHandler.pattern=mkgmap.log java.util.logging.FileHandler.append=false Steph

4 8

Corrections for mp reader
by Andrzej Popowski 21 Dec '14

21 Dec '14

Hi, I have made 3 simple corrections for reader of Polish mp format. Proposed patch is included. 1. Line RouteParam= have most parameters optional, "oneway" and "toll" too. Mkgmap should use defaults, when parameters are missing. Probably there should be syntax check added, but I don't know how to invoke exit with error message. 2. CGPSmapper supports multiple labels, I have added support for lines "Label2=" and "Label3=". 3. Country name can have separator and short name. I have included function unescape() for "Country=". -- Best regards, Andrzej

1 0

Commit: r3388: prevent ArrayIndexOutOfBoundsException with empty map
by svn commit 21 Dec '14

21 Dec '14

Version mkgmap-r3388 was committed by gerd on Sun, 21 Dec 2014 prevent ArrayIndexOutOfBoundsException with empty map

1 0

Roundabouts in wrong direction
by News 21 Dec '14

21 Dec '14

I've recently updated to the latest version of mkgmap, compiled my maps with my normal script and it seems that in the finished img file all the roundabouts are in the wrong direction. The log file starts with..... Option drive-on-left is deprecated. Will use drive-on=left as replacement for drive-on-left Fair enough - I need to update that option in my script. I then see thousands of entries throughout the file similar to below.... 2014/12/19 09:25:46 WARNING (StyledConverter): /home/paul/Maps/mkgmap/mkgmap/dist/00001001.osm.pbf: Roundabout 6959640 direction is wrong - reversing it (see http://www.openstreetmap.org/?mlat=57.199238&mlon=-2.208389&zoom=17) Of the 15 or so roundabouts that I've manually checked they are correct at OSM so I think that mkgmap is incorrectly reversing them. When using my 805 to autoroute the pink line also goes around the roundabout the wrong way Thanks Paul

2 1