-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing Street Names in New South Wales #6
Comments
As pointed out at https://lists.openstreetmap.org/pipermail/talk-au/2017-December/011574.html, to be consistent with current tagging, it should be |
Thanks for the feedback @andrewharvey |
I'm seeing a lot of changes of street names from the Microsoft Open Maps team recently, like https://osmcha.mapbox.com/changesets/61847421/ I'm concerned as many names have been changed without:
Especially more concerning when it was tagged as survey, which should have higher weighting and priority than the LPI Base Map. The LPI Basemap is not the gospel, the name tag should have what the street sign says, and while many of these are errors in OSM and you've been correcting them, I feel you should be going through the due diligence of checking Mapillary etc first and checking with the mapper via a changeset comment first. |
For example https://www.openstreetmap.org/changeset/50908854 a changeset comment on the changeset that added the previous name was able to confirm the situation on the ground. |
Hey Andrew, Thanks for sharing this with us. We are not aware what name is in LPI all the way we navigate to it's position. Oisin talked about it in his session in Milan which is available online to look at it on demand. PS. We are using Mapillary in process of checking street sign, but very often there is lack of imagery. It is always nice to talk with you, |
Hey Nemanja, Thanks for confirming you do use Mapillary, I know it's sparse, but still good to check if we can.
Great! Feel free to add Mapillary to the object source or changeset source. It does help to keep track of where the name are coming from and have been cross checked with. Also for cases like https://www.openstreetmap.org/changeset/50908854 it's good to use
No doubt. Leaving a changeset comment gives the originally mapper an opportunity to be notified that something they entered is changing, and sometimes they might have more information about it. |
Dear @andrewharvey, I have found planty of the examples where "local" editors used "survay" or "signpost" as a source for adding names. Munro Road should be Graham Lane and it is obvious that user continued to map road after he finished first part of Munro Road. So it is nonsense to spend additional valeuble time to contact the user if it is so obvious (even there is no Mapillary) that he/she put this tag without the reason. Two different sources that we are using shows this street should be named as Graham Lane. Best Regards, |
Task Description
This task includes identifying updating missing street names in New South Wales, Australia. Improvements to the existing road network will include:
Sources
The State government agency of New South Wales has granted explicit permission to use road information from their public source to update OpenStreetMap.
A web service to be used as a backdrop for editing is available here.
This Overpass query shows extensive use of the NSW LPI Base Map already in use as a source for OSM data.
The team will use all available imagery sources to help to confirm alignment of streets.
Identifying streets missing names can be done simply by using custom paint styles in JOSM.
Changeset Comments
The team will use changeset comments consistent with OSM Changeset Guidelines
The team will also include a source:name=* tag (i.e.=NSW LPI Base Map) so the source of the name is clear.
The text was updated successfully, but these errors were encountered: