<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">As a long time Florida mapper all over
the state (10+ years) and someone very familiar with the land
cover data sets in FL (I helped managed a land cover mapping
contract for a round of this in the 1990s at St Johns Water
Management District - its been a long running effort by the 5 WMDs
and FDEP), I HIGHLY SUGGEST going very slow with this and feel
uneasy about the whole thing. I started and stopped a FL water
import based on the land cover data due to a variety of reasons
and that was dead simple compared to what is proposed here. Having
said that - MAYBE its a decent idea in rural and very lightly
mapped areas on a piece by piece basis. This is not like a
building or address import, which can go much smoother. Polygons
with shared borders, multi-polygons and the land cover vs land use
issues greatly complicate things. Look to others past experiences
with these issues. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I reviewed parts of the sample data set
and when you get into urban areas especially, my gut feeling is
just don't do it. Use it as a guide. There's so many gotchas
waiting to bite you and everyone. Especially the land cover vs
land use issues. What should follow parcel boundaries vs not, etc,
etc, etc. When you get into natural areas and possibly
agricultural areas, maybe. The data does do a pretty good job of
differentiating various natural land cover types and ag areas.
Again, best advice is use it as a guide. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">FYI: I have parcel boundary data
everyone can use as an overlay for FL. JOSM Imagery URL below:<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">wms:<a class="moz-txt-link-freetext" href="https://maps1.mapwise.com/cgi-bin/mapserv?map=maps/osm-florida.map&FORMAT=image/png&TRANSPARENT=TRUE&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&LAYERS=parcels-all-outline&STYLES=&SRS=">https://maps1.mapwise.com/cgi-bin/mapserv?map=maps/osm-florida.map&FORMAT=image/png&TRANSPARENT=TRUE&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&LAYERS=parcels-all-outline&STYLES=&SRS=</a>{proj}&WIDTH={width}&HEIGHT={height}&BBOX={bbox}<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Brian aka grouper<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2/22/2022 12:34 PM, Hiausirg wrote:<br>
</div>
<blockquote type="cite"
cite="mid:trinity-885f5283-de8b-45c7-a7a3-f98057dd1f9d-1645551297762@3c-app-gmx-bs25">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>Hello,<br>
I am currently planning an landuse import covering (nearly)
the complete US State of Florida. The data is published by
the Florida Department of Enviromental Protection (=Public
Domain) at <a
href="https://geodata.dep.state.fl.us/datasets/FDEP::current-landuse-landscape-support-index-lsi/about"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://geodata.dep.state.fl.us/datasets/FDEP::current-landuse-landscape-support-index-lsi/about</a></div>
<div><br>
The data quality is extremely good. I think it is save to
say that it is far better than at least half of all existing
landuse data in the US. A distinction is made between normal
farmland and fallow (unused) farmland. Cutlines in forests
for power-/pipelines are precisely cut out, and so on. Which
tags in the original dataset have been changed to which OSM
tags is listed on the wiki page: <a
href="https://wiki.openstreetmap.org/wiki/User:Hiausirg/Florida_Landuse_Import#Tagging_Plans"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://wiki.openstreetmap.org/wiki/User:Hiausirg/Florida_Landuse_Import#Tagging_Plans</a></div>
<div><br>
The best way is to get convinced of the quality of the data
for yourself: <a
href="https://www.mediafire.com/file/53cbubxbkikcwi2/FLLanduse_NWF_Part3.osm/file"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.mediafire.com/file/53cbubxbkikcwi2/FLLanduse_NWF_Part3.osm/file</a>
and <a
href="https://www.mediafire.com/file/8476ovczmljikvu/FLLanduse_NWF_Part7.osm/file"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.mediafire.com/file/8476ovczmljikvu/FLLanduse_NWF_Part7.osm/file</a>
are two examples. Simply drag & drop into JOSM.<br>
5 days ago I already posted about this project in the
#local-florida Slack channel. I also wrote directly to
several people who map a lot in Florida. There was almost
only positive feedback about the data quality. The only
problem is that there are relatively often overlaps of roads
and land covers like natural=wood or similar. However, it
only happens with minor roads, and I don't think it's a big
problem per se.</div>
<div><br>
Conflation will be done largely manually with the JOSM
validator. Exact steps are described on the wikipage linked
above. Since the state is in most locations completely empty
(regarding landuses), this shouldn't take too long. Areas
with already good coverage (Jacksonville, Orlando,
Tallahassee & Gainesville) won't be touched.</div>
<div><br>
Any questions?</div>
<div>Greetings</div>
</div>
<div> </div>
<div class="signature"> </div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
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>
<br>
</body>
</html>