<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>Also, one more question:<br></div><div dir="auto"><br></div><div dir="auto">" Data license: Public domain" - how we know this? <br></div><div dir="auto">Where it was specified? <br></div><div dir="auto"><br></div><div dir="auto"><a href="https://geodata.dep.state.fl.us/datasets/FDEP::current-landuse-landscape-support-index-lsi/about">https://geodata.dep.state.fl.us/datasets/FDEP::current-landuse-landscape-support-index-lsi/about</a> <br></div><div dir="auto">is missing indicator of that<br></div><div><br></div><div dir="auto">(I posted also at OSM Wiki talk page)<br></div><div dir="auto"><br></div><div dir="auto">> Step 6: Change desctiptive tags to OSM tags (see the table above), using find&replace<br></div><div dir="auto"><br></div><div dir="auto">Custom validator rules with autoreplace may be a better idea. <br></div><div dir="auto">Depending on format: maybe some automated script?<br></div><div dir="auto">If you are unfamiliar with programming I would recommend at least asking<br></div><div dir="auto">(on Slack/Discord/IRC) after resolving all other issues<br></div><div dir="auto">it should be relatively easy to implement it - there is chance that someone<br></div><div dir="auto">has something easily adaptable or can write one.<br></div><div><br></div><div>Feb 23, 2022, 18:14 by impiaaa@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><p>Some small tagging suggestions, after reading the wiki and then
verifying in the sample:<br></p><p>1220 and 1320 seem more like residential=trailer_park than
residential=urban<br></p><p>1210 and 1310 seem more like residential=single_family than
residential=urban<br></p><p>1454 seems more like tourism=caravan_site than
landuse=residential<br></p><p>A lot of the categories with landuse=industrial sound like they
could be more specific, like industrial=oil with 1540,
industrial=depot (or landuse=depot) with 8130, or
industrial=shipyard (and landuse=industrial) with 1551.<br></p><div>1750 seems more like landuse=civic_admin than landuse=commercial<br></div><p>2400 seems like it's conflating landuse=vineyard and
landuse=plant_nursey<br></p><p>by the way, "nursey" should be "nursery"<br></p><p>7410 sounds too broad to use with natural=scrub. from viewing, it
seems just as likely to be a plains, forest, or brownfield<br></p><p>I don't see anything that gets mapped as landuse=retail, which
makes me suspicious. What OSM calls "retail landuse" is often
called "commercial" zoning in the US, and what OSM calls
"commercial landuse" is often called "industrial parks" in the US.
Be careful that you're not making that mistake.<br></p><p>It might be good to include a tag with the original code, to
provide more detail and allow for later corrections. However, I
don't think note=* is a good place for it, rather it should go in
an import-specific tag. Something like fdep:level3, or
fdep:landuse_code maybe?<br></p><p>The geometry in the sample looks good. I'm glad that there seem
to be no overlaps within the data. I would agree with the others
that multipolygons should be stripped to be outer rings only, or
split when they are multiple outer rings.<br></p><div class="">On 2/22/22 9:34 AM, Hiausirg wrote:<br></div><blockquote type="cite"><div style="font-family: Verdana;font-size: 12.0px;"><div><div><div>Hello,<br></div><div> 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 class="" target="_blank" href="https://geodata.dep.state.fl.us/datasets/FDEP::current-landuse-landscape-support-index-lsi/about" rel="noopener noreferrer">https://geodata.dep.state.fl.us/datasets/FDEP::current-landuse-landscape-support-index-lsi/about</a><br></div></div><div><div><br></div><div>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 class="" target="_blank" href="https://wiki.openstreetmap.org/wiki/User:Hiausirg/Florida_Landuse_Import#Tagging_Plans" rel="noopener noreferrer">https://wiki.openstreetmap.org/wiki/User:Hiausirg/Florida_Landuse_Import#Tagging_Plans</a><br></div></div><div><div><br></div><div>The best way is to get convinced of the quality of the data
for yourself:<a class="" target="_blank" href="https://www.mediafire.com/file/53cbubxbkikcwi2/FLLanduse_NWF_Part3.osm/file" rel="noopener noreferrer">https://www.mediafire.com/file/53cbubxbkikcwi2/FLLanduse_NWF_Part3.osm/file</a> and <a class="" target="_blank" href="https://www.mediafire.com/file/8476ovczmljikvu/FLLanduse_NWF_Part7.osm/file" rel="noopener noreferrer">https://www.mediafire.com/file/8476ovczmljikvu/FLLanduse_NWF_Part7.osm/file</a> are two examples. Simply drag & drop into JOSM.<br></div><div> 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.<br></div></div><div><div><br></div><div>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.<br></div></div><div><div><br></div><div>Any questions?<br></div></div><div>Greetings<br></div></div><div> <br></div><div class=""> <br></div></div><div><br></div><pre class="" wrap="">_______________________________________________
Imports mailing list
<a href="mailto:Imports@openstreetmap.org" class="" rel="noopener noreferrer" target="_blank">Imports@openstreetmap.org</a>
<a href="https://lists.openstreetmap.org/listinfo/imports" class="" rel="noopener noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/imports</a>
<br></pre></blockquote></blockquote><div dir="auto"><br></div> </body>
</html>