<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Chill. Imports work like the following:<br>
1. community buy in, you did that<br>
2. Import list questions, well there were some questions<br>
3.<b> </b>You documented how are you going to do it<br>
4. You probably forgot this: please check the data quality because
it can happen that some landuses overlap. JOSM warns for you for
overlapping, if you simply ignore it, you didn't pay much
attention to your import<br>
<br>
When I imported WV state forest
boundaries(<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Import/West_Virginia_State_Forests_Import">https://wiki.openstreetmap.org/wiki/Import/West_Virginia_State_Forests_Import</a>),
I managed to clean off the multipolygon errors, since the source
contained some. (Well, it's another tale whether the boundaries
are correct, since as I noticed these boundaries not always align
to the parcel boundaries, or at least not in GIS data, but still
better than nothing, since sometimes some friends tell me they go
to xy State Forest (eg. Cabwaylingo, actually one of my friends
went there), and i'm glad it's in OSM so I can have an idea where
they went) I always try to do my best, to see how correct the
stuff is.<br>
<br>
Remember, when I messaged one of your changesets in WV (in
Chester, you know, the teapot town)? Most of the building you
imported were OK but some weren't and you didn't check it, however
if you import something you should improve its quality.<br>
<br>
I don't want to mention other people who did similarly import on
certain states but I'm aware that those people improved the
landcover quality since then.<br>
<br>
Hungary is still suffering from the CLC import but i've fixed a
lot of issues since then (especially in southwestern and eastern
Hungary), since I gotta learn how to deal with landcovers.</p>
<p>Since Florida is a big state, please rethink your workflow.</p>
<p>(Ok, I see you deleted the information from
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Florida_Landuse_Import">https://wiki.openstreetmap.org/wiki/Florida_Landuse_Import</a>)</p>
<p>I've spent a lot of time manually mapping forests in West
Virginia (<a class="moz-txt-link-freetext" href="https://tasks.openstreetmap.us/projects/258/">https://tasks.openstreetmap.us/projects/258/</a> ,
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Marshall_County,_West_Virginia">https://wiki.openstreetmap.org/wiki/Marshall_County,_West_Virginia</a>
and
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/User:Ottwiz/ottwiz-mapping-wv">https://wiki.openstreetmap.org/wiki/User:Ottwiz/ottwiz-mapping-wv</a>),
the quality of it is very good, especially that now Bing imagery
is being updated in a lot of counties, however, sometimes I have
to stick to NAIP due to the misalignment of Bing or that Bing
didn't update to the 2020 imagery in the area, or the imagery is
too dark to take advantage of its high resolution.</p>
<p>Even if the landcover's quality is good, an import is only good
if it has no issues whatsoever.<br>
<br>
If you did some pilot importing and you sent us the .osm file for
checking, we would've given any feedback on the situation (or at
least i would've given, because I give a damn about stuff if it's
not correct)</p>
<p>I hope this was useful information for you and please consider my
tips.<br>
</p>
<p>BR,<br>
Attila<br>
</p>
<div class="moz-cite-prefix">On 2022. 02. 28. 16:53, Hiausirg wrote:<br>
</div>
<blockquote type="cite"
cite="mid:trinity-e9348b1b-0239-4c06-b527-af1037b8eb5a-1646063637236@3c-app-gmx-bap20">
<pre class="moz-quote-pre" wrap="">So this guy reverts my stuff. Nice. He gave zero fucks about my arguments, it is obvious that he hasn't even read my posts at the mailing lists. (e.g. "fdep:landuse_code was never mentioned in any of the documentation/discussion" is a blatant lie.) He doesn't address a single one of my arguments; instead, he spreads lies and untruths around. I guess the discussion on slack wasn't read also. He never edits anything in Florida, not even the US, he has ZERO "local knowledge". He blames me for "insufficint discussion", BUT HASEN'T DISCUSSED THIS REVERT ANYWHERE. I discussed this import with many people and got at least 90% positive feedback. He reverted it, because of <a class="moz-txt-link-freetext" href="https://www.remote.org/frederik/tmp/import_mismatch.jpg">https://www.remote.org/frederik/tmp/import_mismatch.jpg</a> - Someone drew in a poorly aligned pond and it now it is my responsibility to fix it?!?!? The data i uploaded matched what was on the ground perfectly. He acts like a god; "i dont like this so ill revert". This is ridiculous.
I'm out now, i won't put any further work in this import. Not if such associal behavior is tolerated here. Trace the shit yourself, or "use it as a guide".
Oh, and congratulations. Now we have an real mess. He deleted all relations and a lot of ways, but nodes are still all there. Now, overlaps, broken landuses and empty nodes are everywhere. Have fun cleaning that up.
_______________________________________________
Imports mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Imports@openstreetmap.org">Imports@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/imports">https://lists.openstreetmap.org/listinfo/imports</a>
</pre>
</blockquote>
</body>
</html>