[Imports] Florida Landuse Import

[Attila Kun]

Chill. Imports work like the following:
1. community buy in, you did that
2. Import list questions, well there were some questions
3.**You documented how are you going to do it
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

When I imported WV state forest 
boundaries(https://wiki.openstreetmap.org/wiki/Import/West_Virginia_State_Forests_Import), 
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.

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.

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.

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.

Since Florida is a big state, please rethink your workflow.

(Ok, I see you deleted the information from 
https://wiki.openstreetmap.org/wiki/Florida_Landuse_Import)

I've spent a lot of time manually mapping forests in West Virginia 
(https://tasks.openstreetmap.us/projects/258/ , 
https://wiki.openstreetmap.org/wiki/Marshall_County,_West_Virginia and 
https://wiki.openstreetmap.org/wiki/User:Ottwiz/ottwiz-mapping-wv), 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.

Even if the landcover's quality is good, an import is only good if it 
has no issues whatsoever.

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)

I hope this was useful information for you and please consider my tips.

BR,
Attila

On 2022. 02. 28. 16:53, Hiausirg wrote:
> 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 ofhttps://www.remote.org/frederik/tmp/import_mismatch.jpg  - 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
> Imports at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/imports
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20220228/f1552a7a/attachment.htm>