What about deleting the following lines, what is the reason?
"ferry".equals(currentWay.getTag("route")))) {
AND
long cyclwayId = currentWay.getId() + CYCLWAY_ID_OFFSET;
Will enabling the --make-opposite-cycleways now overwrite the underlying
road?
Mark Burton wrote:
Hi Marco,
I've experienced the same problem: a short arc disappered in Rome (I'm still
looking for it...). And the routing gets broken. Did you understand why those
short arcs (with no collapsing end nodes) get deleted?
Bug found, fix committed.
The min arc length can still be specified with --remove-short-arcs (note
correct name!) but it shouldn't be needed any more.
Zero length arcs must still be removed so you do need to specify
--remove-short-arcs (but without the min length). Once this has proven
to be trustworthy, we could think about making the zero length arc
removal the default behaviour when routing is enabled.
Cheers,
Mark
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev