Changeset: 41776742
Canvec 32J11 Import
Closed by LogicalViolinist
Tags
created_by | JOSM/1.5 (10786 en) |
---|---|
source | NRCan-CanVec-10.0 |
Discussion
-
Comment from Nakaner
Please use a dedicated account for importing data. Otherwise anyone might revert your edits without any other reason because of violation of the Import Guidline. https://wiki.openstreetmap.org/wiki/Import/Guidelines#Use_a_dedicated_user_account
-
Comment from LogicalViolinist
Reverting on the sole purpose that it's not a dedicated account is counter productive and a waste of time. I will use a dedicated account as it's the proper way to do things, but reverting good commits is very bad for the osm community.
-
Comment from Nakaner
I will revert this an similar changesets in the next hours or days (its just a question of time until the load of the API is low enough). I will revert them mainly due to low quality of the imported data. Just compare it to satellite imagery, logic and Good_Practice at OSM wiki.
I will also revert all changeset which tried to fix this import.
-
Comment from Nakaner
Reverts will cover changeset 41761086 to 41786190 and maybe more changesets if I find more changesets with similar issues.
-
Comment from LogicalViolinist
Could you not revert work that is being done?????? I'm forwarding this to the DWG
-
Comment from Nakaner
Full explanation of issues of this import (changesets 41761086 to 41786190):
1. The imported data has overlapping, duplicated ways. Way #439632327 (natural=water) has exactly the same nodes as way #439632406 (no tags, inner member of forest multipolygon). Both ways have been uploaded at the same changeset. This issue exists all over the whole import.
2. There are areas which is mapped as natural=wood (multipolygon) which seems to have no trees at all according to Bing. If zoom out, the high-res imagery is replaced by low-res Landsat imagery. High-res is covered by snow while low-res is not covered by snow. The summer imagery shows a dark green only at that areas which are covered by trees on the winter imagery. Example: https://www.openstreetmap.org/#map=19/49.76484/-74.57356
3. A high-voltage power line crosses the area you imported and has already been mapped before. After your import it is still there but it runs next to its cutting through the forest. https://wiki.openstreetmap.org/wiki/File:Import-Fails-Powerlines-Not-Inside-Cutting.png
4. You uploaded address interpolation line(s) (way #439631732) whose curves are smoother than the sharp corners of the road.
5. The roads you uploaded are not connected with other roads and were uploaded although there have been roads before. http://overpass-turbo.eu/s/i6r
6. I doubt that way #439632682 is really a footway and assume that it is more likely a path. (That's more a tagging issue which can feed a long discussion at a mailing list)
-
Comment from LogicalViolinist
I remind anyone following this that Nakaner has took it uppon himself to revert multiple changesets without prior discussion on the talk-ca or any other medium. He has just left comments like: I'm going to revert this (moments later) Ok it's reverted. Not letting the importers the chance to fix their import
-
Comment from LogicalViolinist
I have downloaded all the data from this import and saved it. If you revert it, it will be reuploaded with fixes. I see that there are problems with the map and I am working on correcting them.
-
Comment from LogicalViolinist
Those powerlines are a result of tracing Bing imagery data(which was not part of this import and done previously), which is highly likely to be off by a few meters, especially in the north. These are things that must be corrected, but again reverting work that's being done is counter-productive and bad for the osm community
-
Comment from Nakaner
LogicalViolinist, why didn't you check and improve/adapt the existing data BEFORE you uploaded your import?
-
Comment from LogicalViolinist
I will do so in the future as I was unsure about somethings, but now I'm fixing them and committed to doing this. Most of the errors have to do with multipolygons which I now understand how to properly map thanks to this:
http://wiki.openstreetmap.org/wiki/Multipolygon_Examples#Forest_with_two_lakes_and_an_island_.28Nested_multipolygons.29 -
Comment from LogicalViolinist
Also the nodes that are not connected in Chibougamau were not even in this region (32J01 - 32J11) and not my prerogative to connect them. I will how ever connect the disconnected roads in my import and then after correct Chibougamau's inner city roads
-
Comment from LogicalViolinist
Also Bing imagery can be stale in the north as much as 15-20 years. It is a good indicator, but totally untrust worthy in Canada's Northern regions. Rule of thumb is if it's not in a highly populated area, the imagery will most likely be out of date.
-
Comment from LogicalViolinist
32J01 Should be fixed, working on others
-
Comment from LogicalViolinist
32J02 fixed
-
Comment from LogicalViolinist
32J03 fixed
-
Comment from LogicalViolinist
75% of it fixed
Ways (141-160 of 3675)
Relations (1-20 of 113)
- Lac Albert (6541062), v1
- Lac Gaulin (6541063), v1
- Lac Lafargue (6541064), v1
- Lac Mineray (6541065), v1
- Lac Perdu (6541066), v1
- Lac Savournin (6541067), v1
- Lac Savournin (6541068), v1
- Lac Sirmac (6541069), v1
- Lac de la Bruine (6541070), v1
- 6541071, v1
- 6541072, v1
- 6541073, v1
- 6541074, v1
- 6541075, v1
- 6541076, v1
- 6541077, v1
- 6541078, v1
- 6541079, v1
- 6541080, v1
- 6541081, v1
Nodes (1-20 of 16617)
- 659531338, v2
- 659531339, v2
- 659531343, v2
- 659531344, v2
- 659531346, v2
- 659531378, v2
- 659531380, v2
- 659531416, v2
- 659531417, v2
- 659531418, v2
4372772189, v24372822385, v24372822386, v24372822387, v24372822388, v24372822389, v24372822390, v24372822391, v24372822392, v24372822393, v2
Welcome to OpenStreetMap!
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
Hosting is supported by Fastly, OSMF corporate members, and other partners.
https://openstreetmap.org/copyright | https://openstreetmap.org |
Copyright OpenStreetMap and contributors, under an open license |