[Imports] Florida Landuse Import

[Hiausirg]

The test file does not work (at least on my PC). When i try to load it, the "Reading OSM data..." window just closes after a few minutes. However, i have some larger unsplitted .osm files, some almost 300 MB in size. When loading them, it takes a while and it also freezes ~1-3 min, but they load and i can edit them, so my pc isn't too slow for the 100 MB Taylor County File.
 
About excluding populated areas: A town should have at least +10k inhabitants to be excluded (or have a lot of already existing landuses) in my opinion. But it's up to you. (my very last offer would be +5k)
 
About merging "same" landuses: I'm againest that, because -on the ground- they arent the same. You changed all residential landuse specifications on the wiki page to use only residential e.g. high/low rise, high/low density, single family, trailer park etc now all landuse=residential. If anyone wants to specifiy such stuff like low/high density (kinda important information IMO) later, it gets very hard. Another thing: Assuming, there are "Low Density, Fixed Single Family Units" next to "Low Density, Mobile Home Units", and they both have an landuse=residential tag and nothing else. Sounds redudant to use two areas first. But maybe the trailer park has a name -okay, it is very likely it has an name- someone can come later and add that name to the landuse without having to seperate the "Single Family Units" from the trailer park first. It would make mapper's lifes easier.
Other example: "7100: Beaches other than swimming beaches " and "7200: Sand Other Than Beaches". Both currently natural=sand -> would be merged. Maybe someone will have the idea later to tag the 7100s with natural=beach/swimming=no and leave the 7200 with natural=sand. If the areas are not merged, then the detailing can be done with much less work.
About keeping the orginal description tag: If areas are merged, then it is obviously impossible/useless. If nothing gets merged (i hope, but it's your decision) it should be keeped definitly, as it makes detailing like mentioned above much easier (for example).
 
About used tag transformations: You want to exclude power/pipeline corridors because you haven't mapped them in Alabama either? How is that a reason to not import something. You also havent mapped any residential landuses in Bibb County, so should we exclude them here now too? By the way: A while ago, i mapped some landuse in Charlton County, GA here -> https://www.openstreetmap.org/#map=10/30.6899/-82.2038 ...and i mapped power corridors. And same thing as above: It is possible to tag such scrub/grass areas as utilitiy corridors later, if a common tagging emerges. Also: Power/Pipeline corridors can be tagged differently too: I took a closer look at various corridors (with street level images), and there's a difference: Power lines are usually scrub, cleared rarely. Pipelines are never scrub, always grassland (i haven't seen any scrubs). I assume thats because its easier to detect spills or other problems (and maybe also required by law).
You said you added more FDEP tags to the wiki page - im pretty sure some are still missing, i assume that there is another tag for the large sugarcane fields around Lake Okeechobee and other stuff - i only added tags used in the area between Penscola and Jacksonville.
 
"I do not know how he was able to import all of that without thousands of error messages"
I had a lot of error messages - and i fixed them. Please don't assume i fixed nothing and ignored everything - it's nonsense.
"The original import was indeed buggy"
Luckily it was reverted fast enough after extensive discussion to avoid search for any systematic problems/mistakes/"bugs". I also know nothing about any systematic errors - specifc problems aren't given anywhere. By the way: An poorly drawn pond which overlaps imported landuses that matched the ground pefectly (https://www.remote.org/frederik/tmp/import_mismatch.jpg) is not an systematic problem - definitly not.
 
Greetings