<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Ian, <br>
I want to import this data because I think its important for a
complete map. We have national forest, wilderness and national
park boundaries in OSM! This is no different. If you look at
many maps they show all of them.<br>
<br>
I'd like it to show up on any map that I use. I'm working on a
'better' version for garmin using mkgmap. I hope it gets rendered
with OpenAndroMaps too. I haven't used the onine osm.org map very
much.<br>
<br>
I am excited to participate and improve OSM and in my opinion this
is a big gap in the OSM database. Where I live, we don't use OSM
for building footprints, we use it to find our way in the national
forest, the BLM land and the national parks. It's very useful to
know what is public or private land.<br>
<br>
Brad <br>
<br>
<div class="moz-cite-prefix">On 1/5/19 8:19 PM, Ian Dees wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAG91b3TBtO9t0o_aQ08nV7M-cCe4fJ02VKpMBFQxF6qXV3aHdw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi Brad, thanks for proposing this import and posting it
here.</div>
<div><br>
</div>
<div>I would strongly prefer that we not import boundaries like
this into OSM. Boundaries of all sorts are almost impossible
to verify with OSM's "on the ground" rule, but BLM boundaries
in particular are such an edge case (they have no other analog
in the world, really) and almost never have apparent markings
on the ground to check. Since these boundaries aren't visible,
this data can never be improved by an OpenStreetMap
contributor. The boundaries are defined by the government, and
any sort of change to them would make them diverge from the
official source.</div>
<div><br>
</div>
<div>But having said that, I'm curious why you wanted to import
this data? Did you want to have it show up on the <a
href="http://osm.org" moz-do-not-send="true">osm.org</a>
map? Are you trying to build a custom map? Or are you excited
to participate and improve OSM? If it's the latter, there's
lots of other data that is a better fit to import into OSM:
address points and building footprints come to mind, for
example.</div>
<div><br>
</div>
<div>-Ian</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Sat, Jan 5, 2019 at 9:03 PM brad <<a
href="mailto:bradhaack@fastmail.com"
moz-do-not-send="true">bradhaack@fastmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">I'd like to import BLM
(US Bureau of Land Management) boundaries into <br>
OSM. This is not an automated import as you can see from
my workflow.<br>
<br>
Workflow:<br>
Download shape file from PADUS (1 state at a time): <br>
<a href="https://gapanalysis.usgs.gov/padus/data/download/"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://gapanalysis.usgs.gov/padus/data/download/</a><br>
Load into Qgis and filter for BLM boundaries<br>
Clean up as necessary (there are some extraneous ways at
state <br>
boundaries & elsewhere)<br>
<br>
Convert to OSM with ogr2osm and the following tags<br>
tags.update({'type':'boundary'})<br>
tags.update({'boundary':'protected_area'})<br>
tags.update({'operator':'BLM'})<br>
tags.update({'ownership':'national'})<br>
tags.update({'protect_class':'27'})<br>
tags.update({'source':'US BLM'})<br>
use the shapefile attribute 'Unit_Nm' as the name<br>
<br>
Import with JOSM<br>
<br>
The San Luis unit (CO) is here for your inspection.<br>
<a
href="https://www.dropbox.com/s/qxv5gny2396ewki/sanLuisBLM.osm?dl=0"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.dropbox.com/s/qxv5gny2396ewki/sanLuisBLM.osm?dl=0</a><br>
<br>
Comments?<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>