Hello,

I bought a software that uses openstreetmap API. I've noticed some mapping errors while using this software, so I'd like to report them.

For example on that website http://open.mapquest.fr/ , if I search "rue pasteur villeneuve d'ascq (France)" I get 2 results. This is a mistake, only the first result is correct.

So I clicked on "report an error" for the 2nd result and explained this. I got a message "Error created: 3146532"

What is this number related to? How can I follow this error? Who's in charge of correcting, and how can I know it's done?

Thanks, and sorry for asking such a basic question, I'm quite new to all of this.

asked 29 Apr '15, 08:24

A%20Macquet's gravatar image

A Macquet
26112
accept rate: 0%

edited 30 Apr '15, 14:33

aseerel4c26's gravatar image

aseerel4c26 ♦
32.0k16238549

2

If you want to report a problem with our map data in future, it is more easy/useful if you use our error reporting system: "Notes" – or try to fix yourself (see also Simon's answer). Just be careful to not "fix" something which is not broken in the data but in the software (Nominatim or whereever). :-)

(30 Apr '15, 13:51) aseerel4c26 ♦

Just be careful to not "fix" something which is not broken in the data but in the software (Nominatim or whereever).

I'm sorry I don't get it. What do you mean?

In the future, should I correct the map directly on openstreetmap.org through the iD tool? It's quiet easy to use.

(30 Apr '15, 14:18) A Macquet

I mean that e.g. for this query several results are right, so there you should not edit the data to only get one result. More or less applicable info/explanation of such issues: https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer

Yes, you should correct the map directly if the data is wrong. If you are not sure, just ask.

(30 Apr '15, 14:28) aseerel4c26 ♦

Ok, thank you very much for your help and explanations.

(30 Apr '15, 14:41) A Macquet

Hi and welcome to OpenStreetMap

While reporting an error is naturally OK, OSM is really about fixing issues and mapping yourself. And, just on 1st principles, given that you are the person that has run in to an issue you are the best suited and motivated to resolve the problem.

Most things in OSM are fairly easy to do, so you shouldn't have concerns. If you want to try and fix the issue yourself http://www.openstreetmap.org/fixthemap Further there is a strong French OSM community that you can turn to for help http://openstreetmap.fr/

Now back to your concrete issue: many organisations use OSM data to power their applications and MapQuest is one of them. There are a number of MQ employees in the active OSM community and I'll point your question out to them given that they know what is actually being done behind the scenes.

permanent link

answered 29 Apr '15, 08:41

SimonPoole's gravatar image

SimonPoole ♦
38.3k13284609
accept rate: 19%

edited 29 Apr '15, 09:00

1

Hi Simon and thanks for answering me.

Yeah if someone from MQ could tell me what happens once an error number is given after a click on "report en error", I'd appreciate. Because once you've have clicked, you really don't know what happens next.

Meanwhile I'll try to fix the issue by myself.

(29 Apr '15, 08:57) A Macquet

Those errors go to MapDust. In this particular case you can see that the OpenStreetMap-hosted Nominatim instance also returns two results, so there's nothing MapQuest specific happening with the error.

This specific result appears to be because there are two streets named Rue Pasteur, one a tertiary highway and the other a pedestrian highway.

permanent link

answered 29 Apr '15, 18:05

pnorman's gravatar image

pnorman
2.3k52140
accept rate: 19%

A bit more clear (regarding the original question): so, to "follow reported errors on [Mapquest] maps" you need to go to http://www.mapdust.com and enter the error number in the big search box ("Bug ID") on the top. There you can see comments from other user and/or leave additional comments yourself.

You may want to integrate this into your answer, @pnorman.

(29 Apr '15, 20:56) aseerel4c26 ♦

regarding the problem itself and to make it explicit: as far as I can see this (several objects with the same street name) is a perfectly okay data situation (with our current, usual street data model/tagging). Nothing has to be fixed in the data here.

Oh, wait, A Macquet says "only the first result is correct". Is the street named wrongly? Okay, well, we will discuss it at the bug report - that is the better location. The bug is there: http://www.mapdust.com/detail/3146532 - @A Macquet: please click on the "comments / additional info" tab to see my comment and leave your answer there.

(29 Apr '15, 21:06) aseerel4c26 ♦

Hi

@aseerel4c26 -> thanks for the informations about mapdust. I answered you there for details about my request.

(30 Apr '15, 09:09) A Macquet

Looking at Mapdust plugin's changelog, I gotta wonder if that database is dead, and if there's any OSMbugs style conflation with Notes upcoming.

(07 May '15, 18:32) Paul Johnson
1

FWIW "scout" notes get added straight into OSM. Telenav bought Skobbler, and "Scout" is their product in the US, I believe. To see current "scout" notes you can look at:

http://api.openstreetmap.org/api/0.6/notes/search?q=scout&closed=0

Like Skobbler notes, many are not especially helpful:

https://www.openstreetmap.org/note/359352

IMHO it wouldn't be beneficial to add the notes from mapdust to OSM as notes - most of them are useless.

(07 May '15, 18:56) SomeoneElse ♦
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×232
×177
×28
×3

question asked: 29 Apr '15, 08:24

question was seen: 4,755 times

last updated: 07 May '15, 18:56

powered by OSQA