On Thu, May 28, 2015 at 4:14 PM, Clifford Snow cliff...@snowandsnow.us
wrote:
Notes provides that feedback as long as the poster was logged in.
Notes are often missing three things: the feedback mechanism, the route
origin destination, and a clear description of the problem.
Improvement to
On Thu, May 28, 2015 at 2:54 PM, Daniel Koć daniel@koć.pl wrote:
Yes, I did it. But it means it's another complexity to consider when
reporting problems with their engine.
I don't know how open.mapquest.org routing service is different (in terms
of routing code) from what we have on OSM
On 5/28/2015 11:25 AM, Daniel Koć wrote:
With MapQuest it was much harder to find how can I report another bug.
Finally I have found Residential Map or Route Errors link on Support
page ( https://support.mapquest.com/hc/en-us - looks like the link
itself is dynamic, because it has issue
W dniu 28.05.2015 23:11, Paul Norman napisał(a):
On 5/28/2015 11:25 AM, Daniel Koć wrote:
promises as to when we might get to this. Maybe our technical team
should talk with theirs to make better feedback channel available?
I would suggest reproducing the issue on open.mapquest.com and
W dniu 28.05.2015 18:33, Janko Mihelić napisał(a):
I'd like the following procedure:
4. Later a mapper clicks the note, and it shows the text and the
problematic route.
I'm also interested in 5. - standard procedure for reporting routing
errors to engine operators. =}
For OSRM I have
I have encountered some routing errors using our main website, but while
trying to report it, I've found nowhere I could do it on the website and
Tom said there's only one way to report it - directly at respective
routing providers.
I will manage that, but I think we should have better
Hi Daniel,
On Thu, May 28, 2015 at 11:15:34AM +0200, Daniel Koć wrote:
I have encountered some routing errors using our main website, but
while trying to report it, I've found nowhere I could do it on the
website and Tom said there's only one way to report it - directly at
respective routing
W dniu 28.05.2015 11:45, Florian Lohoff napisał(a):
Hi Daniel,
On Thu, May 28, 2015 at 11:15:34AM +0200, Daniel Koć wrote:
the current provider and maybe note on the map (in case this is a
tagging problem).
Typically there is no such thing as a route error. The engine consumes
the OSM
On Thu, May 28, 2015 at 3:00 AM, Daniel Koć daniel@koć.pl wrote:
User wouldn't know it and that's why I proposed also a note. We
(OSM+routing providers) should resolve it or reject if this is not the real
problem or it's too hard/too esoteric (#WONTFIX), but there should be an
easy way of
I'd like the following procedure:
1. user makes a route and finds an error
2. There is a button Found an error in your route?
3. You click the button, and it behaves the same as the existing note
button. You drag the pointer to the problematic part of your route and
write you can't turn left
10 matches
Mail list logo
