Dguillen, it looks like you accidentally "squared" and uploaded a very long tertiary route here, which destroyed its geometry. Please be careful! You should ask an experienced mapper how to undo your changeset, or manually fix the road you mangled.

Marek the starting point of your analysis is incorrect. It assumes that the existing, hyper-noded wood areas are precisely correct with no uncertainty or error bars. Consider the factors involved - imprecise criteria, human variability, seasonality, poor resolution, loose rectification, etc. it is absurd to claim certainty or accuracy within 20%, or for some parts of Nepal with even worse imagery, 50%. A change of 5% in the area only reflects the mathematical adjustment due to a larger number of convex than concave polygons in the digitization. It is completely dwarfed by the uncertainty.

Apply a strong simplification to these bad landuse polygons, or the community will have to do it for you (again).

OK, thanks! I am much reassured that quality is being cared for and you aren't just making work for me to clean up later :)

OK, it's possible that the places i checked were worse than average, but consider the fine-grained nature of these features, like at changeset/49780057#map=17/34.37226/104.93077 When the nodes are as close as 2.4m but the source data (Landsat) is 28m (!) then there is something terribly wrong here. I am worried I will have to come in here and do another massive simplification cleanup.

I spot-checked these imported forests and they bear no similarity to what is actually on the ground.

Could you please explain what these edits are? I truly hope it is not the "USGS treecover 2010" which is derived from low-resolution LandSat which is entirely inappropriate for mass-import into OSM. Or did you get this import discussed and approved?

For what it's worth, I wrote OSM messages to marek kleciak explaining these edits, and even described the detailed steps he can do in JOSM to do the cleanup himself.

For an example of BAG problems, see buildings like way/277899879 which has a "sliver" which is 18cm wide and 3m long; it is clearly a mechanical error. I have manually fixed hundreds of these problems.

For what it's worth, I recognize unlike other mass imports I'd had to clean up (Canvec, NHD, Tiger...) this data is much better in precision as well as accuracy. That's why i use thresholds not of 70-110 cm as with NHD, but as little as 6 cm for BAG, guaranteeing that cleanup stays within the accuracy of the source data and everything is improved, absolutely nothing is lost.

Hi, if you take a close look, you will see that no "details" were removed. As part of other cleanup (maproullette farm->farmland), I've been run the JOSM validator on some of the nearby buildings and landuse, and tidying up the results. The BAG buildings have numerous issues (including tiny slivers of geometry that are obviously artifacts) which i clean up along with other bad modelling. The is also overlapping identical landuse (which i fix) and some very poor overnoding (which i fix). I am an expert at what I'm doing and I'm happy to defend any node or way that anyone has an issue with. The final result is a map that loads and renders faster, is free of topological issues, and is easier to manually maintain.

Example: before: http://i.imgur.com/HuJTxvi.png
After: http://i.imgur.com/VDAa6uE.png

Notice how the nodes for the selected are reduced from 1832 to 241, without affecting the accuracy of the data at all.

Hi there, many of the ways in this changeset are EXTREMELY overnoded. When you upload, you need to check the data FIRST for this problem and solve it before uploading. Otherwise it creates 26903 nodes in the OSM database, then someone has to come along afterwards and clean it up by deleting ~90% of the nodes. This is really wasteful on the servers and also makes work for other.

To answer your last question, Yes.

Yes, it's NHD. Welcome to my world, Jeopardy. I've spent much of the last 6 months of my life cleaning up North Carolina's NHD (outdated wetlands just like these here in Florida). It's just a huge task, thanks for helping!

It's two days later, and JOSM in this area still reports errors unclosed ways. Please fix your import before importing any more, thanks.

Rather than import huge amounts (>500K changed features on the day of this changeset!), I'd strongly recommend doing smaller sections (like ~10K features/day) so you can check it for errors _before_ uploading, thanks.

When I load a small area around this feature, the JOSM validator reports "Errors: Duplicated ways (98), Duplicated nodes (s), Warning: natural type water - Unclosed way (46)"

Rps, there are some serious issues with this import. For example, consider way way/413668789 It is "water", but unclosed. It is also duplicated, as is all the other sections of water which should have been joined here. PLEASE stop importing millions of features until these issues are addressed.

Hello Davaadulam, I see you changed the english name (name:en) of this street from "Olympic Avenue" to "Олимпийн өргөн чөлөө". The English name is actually "Olympic Avenue, correct? Why did you change it?

Kendall, you added ways which should be paths or service roads, but you tagged them as "motorway" with names like "I-40 West" which is very odd and confusing. I will attempt to fix the tagging, but what did you intend here?