Hi Felix,
I started a new branch low-res-opt. I think the handling of the "preserved"
status of points needs more work. Current code preserves too many points which
are not important. Filters try to keep preseved points and that means more
points and more zig-zagging.
I think
- we MUST
Hi Felix,
if you see random results with routing please check if you use
--preserve-element-order. For tests like this I really recommend it.
OTOH it would be very interesting to find out that the order of data has an
influence on routing in a way that a better or worse route is calculated. So
Hi Felix,
the more-merge.patch should have no effect on routing. In my tests NET and NOD
data was identical. Did you really compare it with an unpatched version? If
there are differences in routing my understanding of the data structures is
wrong.
Gerd
yes I tried it out now without additional DP changes. Routing was identical
in 18 out of 20 routes. Twice a tiny difference, hard to say if worse or
better. Pretty similar. As for if the visual quality was improved, The
jaggedness is a bit better - but still quite a lot of unneeded zig zags.
Hi Felix,
please try first just my patch, not any further modifications from your side.
You can use unpatched DouglasPeuckerFilter from trunk.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Sonntag, 2. Mai 2021 15:09
An: Development
Going to test out the patch a bit more right now. Only problem for me is -
I cannot set custom dp filter anymore.. But I guess you will implement that
anyhow soon?
compile:
[javac] Compiling 1 source file to C:\garmin\mkgmap_trunk\build\classes
[javac]
Hi Felix,
attached patch allows to merge roads at levels > 0. This reduced file file and
zig-zagging. I didn't see routing problems but didn't test this much.
The patch contains also experimtal code for DouglasPeuckerFilter which is not
yet enabled. It reduces a bit more but is not yet tested.
Hi all,
the message
"Found multiple points with equal coords as CoordPOI at
http://www.openstreetmap.org/?mlat=56.835675=37.404949=17;
is produced because the nodes
https://www.osm.org/node/2924385337
https://www.osm.org/node/2924351922
are so close together that mkgmap could not distinguish the
