On 2014-10-18 21:28, Yves wrote:
For users to check if it's an error or not, and to correct if needed.
QA softwares look at possible error according to automatic rules in
this exact purpose.
Yes, obviously. But why flag this as a possible error?
Regards,
Maarten
Le 18 octobre 2014 20:37:21 CEST, Maarten Deen <md...@xs4all.nl> a
écrit :
On 2014-10-16 18:04, Yves wrote:
Because its the purpose of this particular software.
Not wanting to diminish this search, but why would you show an error
"roads not connected" when they are connected? What is the rationale
behind flagging this as a possible error?
Regards,
Maarten
On 16 octobre 2014 17:10:03 UTC+02:00, Maarten Deen
<md...@xs4all.nl>
wrote:
On 2014-10-16 15:43, SomeoneElse wrote:
On 16/10/2014 14:28, Maarten Deen wrote:
On 2014-10-16 15:15, Dave F. wrote:
I had a footpath between them.
So the problem is also that the check is wrong. Apperantly it looks
at
major roads that are apart, but doesn't see that they are connected
by
another road.
IMHO these cases should not be shown at all.
Quite possibly, but as (Andrew Buck has already said) what really
happened here is that a mapper made a mistake.
But he would not have been led there if it wasn't pointed out as an
error.
It's not a software
problem so much as a human one
I beg to differ. The roads were connected. Why show an error "two
roads
are not connected" when there is a connection.
Regards,
Maarten
-------------------------
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk [1] [1]
--
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la
brièveté.
Links:
------
[1] https://lists.openstreetmap.org/listinfo/talk [1]
-------------------------
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk [1]
--
Yves
From my phone
Links:
------
[1] https://lists.openstreetmap.org/listinfo/talk
_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
