I was just looking around Greenbelt, MD and come across a collection of tagless points. They all appear to be from one specific changeset (which I’ve commented on).
There are also tagless lines (e.g. here) which appear to be building outlines but this seems to be related to a different changeset by a different user.
Thought I’d flag here for local mappers to consider fixing.
Well, to understand the reason of unconnected nodes (points) without tag you usually have to take a deeper look at the history. I think in this case the parent way was deleted but not the nodes which leads us directly to the ways (lines) without any tags. Both seem related to Changeset: 134232663 | OpenStreetMap which is a bad, ongoing import. Way: 1158000014 | OpenStreetMap even had a broken shape with several duplicate nodes, fixed in Changeset: 134283422 | OpenStreetMap.
As other changesets of the import (e.g. Changeset: 134783047 | OpenStreetMap) show other problems like adding building=Yes (with a capital Y in the value) and addr:city=UPPER MARLBORO (the whole value in capitals), e.g. Way: 1161399038 | OpenStreetMap, it would be best to ask the author of the import to rework her/his workflow and to use some proper QA tool like JOSM validator before uploading.
No response to my comments and the badly designed import continues. Mean while, I wrote a PM in addition:
Hallo, would you please respond to changeset comments, OpenStreetMap (OSM) Changeset Discussions, and stop your badly designed import plus review all your changes of the last five weeks and fix the errors.
Your workflow and “ArcGIS Editor for OpenStreetMap” do not seem to work properly. Please, update your workflow and use a better editor software, like JOSM, to get warnings about unconnected nodes, duplicated way nodes, way contains segment twice, self crossing ways, self-intersecting ways and incorrect values of tags. Additionally many buildings should be simplified by removing useless nodes. Last but not least, please make sure your source is up-to-date as available aerial imagery sometimes show different results.
Thanks a lot and all the best,
skyper
As I won’t have much time the next days and as I am tired to discuss with paid mappers doing a poor job, maybe, some one else can take over.
I have viewed the messages/comments and appreciate the input. I am addressing the issues with the ArcGIS Editor workflow and rethinking our upload process. Any tips for updating such a large area are greatly appreciate. To address the aerials, the aerials that are being used should be more up to date than Bing.
Thank you and I look forward to any tips for better data!
If you have followed it then I would encourage to link import documentation page here in this thread and in any future changeset (in changeset tags or edit description)
For the manual parts like deleting or replacing, I highly suggest to use JOSM as the utilsplugin2 ships the action “Replace Geometry” which is also used by the conflation plugin. Additionally, JOSM Validator is a good QA tool and it can be quite easily extended by custom rules.
Indeed, but we really need to get the first parts of the import guidelines sorted out before we start thinking about fixing the data, What even is the licence? I notice that @M-NCPPC_Import has been active in the last 15 minutes but still hasn’t replied here or updated the import catalogue.
If communication doesn’t occur any other way I’ll have to don a DWG hat again and ask them to contact us by email (and block the account until they do). That’d be a pain because it’d prevent them posting here until the block is lifted (and obviously we want them to post here first!).
Unfortunately M-NCPPC Planning Department - OpenStreetMap Wiki seems to work as both, the project page and the import description. There is a line in the table at Import/Catalogue but its status is still “planned”. Looking at other lines of the table updating seems to be a common problem and not tied to this import.