|
Hello The node 1558695405 is not recognized as an intersection in routing tool mapquest. Also not node 370582313. Both have black rectangle and no turning restrictions. Is it an error in OSM or Mapquest routing? Thanks |
|
Hello, We (mapquest) are processing the latest planet for our routing servers due to some connectivity issues that we uncovered in our database. In the meantime, I will update the ways so that they get picked up via the daily updates. Sorry for the inconvenience. --Greg. 1
@gknisely: Thanks! Could you please mention the correct contact channel (see my suggestion in my answer) for possible future cases?
(01 Nov '13, 14:03)
aseerel4c26 ♦
4
Sure. We have a forum that is monitored by a support team. Would be best to post issues there. http://developer.mapquest.com/web/info/forums Have a good day!
(01 Nov '13, 14:11)
gknisely
|
|
Not sure what is wrong there, I could not find problems in the data and the routing with osrm works. Maybe Mapquest uses some old data for routing (although I also could find recent edits to the data by a short search). I think this should be reported to mapquest (not sure if reports via the "report an error" link in the map's right click menu arrive also at mapquest or only in skobbler's mapdust). |
Can you give us a link to a route that exhibits the problem ? Mapquest doesn't seem to accept raw coordinates for directions, and I didn't manage to ask for a route that ought to pass through those points.
http://mapq.st/1aNz6kz