Mark,
Sorry for the misunderstanding. Without looking, I assumed the SEVERE
error had been introduced by your patch, while it was probably somewhere
between r1127 and r1131 (not sure, did not look again). Without your
patch, the same errors show up.
However, experimenting a bit with the
Hi Valentijn,
Thanks for the feedback.
I have now posted a new patch that should fix the majority of the short
arcs introduced by the clipping. It's not perfect but (I hope) a step
in the right direction.
My own testing shows that the presence of a short arc does not
guarantee that the routing
Hi Mark,
Mark Burton schreef:
v2 of this patch not only enables remove-short-arcs by default when
routing is in use (as previously discussed on ML) but it also fixes some
problems in the way splitting code.
I would be grateful if people could test this patch because it could
possibly cure
Hi Valentijn,
Thanks for the feedback.
I can see where the problem is occuring. Wherever you have a node that
is within the minimum arc length from a tile boundary you will get an
error message. The question is: Is the routing actually broken at those
locations?
Cheers,
Mark
Hi Mark,
At Wed, Aug 12, 2009 at 09:19:36PM +0100, Mark Burton wrote:
I can see where the problem is occuring. Wherever you have a node that
is within the minimum arc length from a tile boundary you will get an
error message.
Your mail now sounds much less SEVERE than the error message :-)
At Wed, Aug 12, 2009 at 10:37:14PM +0200, Valentijn Sessink wrote:
The question is: Is the routing actually broken at those locations?
Will check. Tomorrow.
Actually, while thinking about it: I'm not sure what to test. Should I check
one of the sites that has a SEVERE message? Does your
Mark,
Again, a quick check, but I can't seem to route on the Fransiscusdreef:
F'dreef to Vechtdijk sends me on a 1.2km odyssee :)
Here's the data:
63240003: 0x24d000,0x34000 to 0x251000,0x3b000
63240008: 0x251000,0x25000 to 0x255000,0x39000
63240009: 0x251000,0x39000 to 0x255000,0x4
java
