[mkgmap-dev] GRAVE (WrongAngleFixer)

Sun Feb 11 09:37:29 GMT 2018

Hi,

I got this message compiling a map for Brazil with srtm:

java.lang.AssertionError: boundary node is replaced
    at
uk.me.parabola.mkgmap.osmstyle.WrongAngleFixer.replaceCoord(WrongAngleFixer.java:111)
    at
uk.me.parabola.mkgmap.osmstyle.WrongAngleFixer.access$300(WrongAngleFixer.java:51)
    at
uk.me.parabola.mkgmap.osmstyle.WrongAngleFixer$CenterOfAngle.tryChange(WrongAngleFixer.java:881)
    at
uk.me.parabola.mkgmap.osmstyle.WrongAngleFixer.removeWrongAngles(WrongAngleFixer.java:373)
    at
uk.me.parabola.mkgmap.osmstyle.WrongAngleFixer.optimizeWays(WrongAngleFixer.java:100)
    at
uk.me.parabola.mkgmap.osmstyle.StyledConverter.end(StyledConverter.java:608)
    at
uk.me.parabola.mkgmap.reader.osm.ElementSaver.convert(ElementSaver.java:243)
    at
uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:157)
    at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:154)
    at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:52)
    at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:263)
    at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:259)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Exiting - if you want to carry on regardless, use the --keep-going option
Number of ExitExceptions: 1

And:

GRAVE (WrongAngleFixer): lon-65.00_-64.00lat3.52_3.53_srtm1v3.0.osm.pbf:
boundary node is replaced by node with non-equal coordinates at
http://www.openstreetmap.org/?mlat=3.531611&mlon=-64.611722&zoom=17

I tried different versions of mkgmap, from the most recent to r3991 !

lon-65.00_-64.00lat3.52_3.53_srtm1v3.0.osm.pbf was made with phyghtmap and
I guess the problem didn't occur when I used .osm instead of .pbf.
If necessary I can re-make the .osm, but do you think the problem can be
within mkgmap ?

The file:
http://files.mkgmap.org.uk/download/419/lon-65.00_-64.00lat3.52_3.53_srtm1v3.0.osm.pbf

Steph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20180211/24fcf094/attachment.html>