<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I am also very interested in getting the NHD data into OSM. We have a
few people here with plenty of experience working with USGS data,
especially NHD, and I'll try to get their reactions. I am new to
tagging and OSM in general but would like to get involved, particularly
with roads and hydro. A few quick questions:<br>
<br>
<br>
1) I would like to load our states (Delaware) NHD data using one of
Ian's converters. Ian, does it make sense for us to start now and let
you know which HUCs we've loaded, or should we wait until your data
gets in?<br>
<br>
<br>
2) Can features have more tags that what is on the Wiki,
<a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/index.php/Key:waterway">http://wiki.openstreetmap.org/index.php/Key:waterway</a>? For example, can
we leave the FCODE or FTYPE attributes in there? or add a reach
code? or use landuse=water even though it's not in the official
key-value list?<br>
<br>
<br>
3) How would we tag the HUC boundaries, which are essentially
watersheds? There are multiple levels of HUC groupings (4, 6, 8, 10,
12-digit HUCs), depending on what scale you're at. These would be
areas, possibly using the natural or landuse or boundary keys? <br>
<br>
<br>
4) I've used the online editor (Potlatch?) for simple editing and
creating new features. I got JOSM up and running, which I believe I
need to use for editing large number of features. What is the
procedure if I need to replace features, for example, if there exists
in OSM a river, lake (or road for that matter) where I have a more
accurately digitized version of? It seems like I should be able to
update/add tags in my own dataset then publish to OSM. Do I delete the
existing version first? or maybe give it the same feature ID as in OSM
and the replacement is done on the back end? <br>
<br>
<br>
- John<br>
<br>
<pre class="moz-signature" cols="72">****************************************
John Callahan
Geospatial Application Developer
Delaware Geological Survey
University of Delaware
227 Academy St, Newark DE 19716-7501
Tel: (302) 831-3584
Email: <a class="moz-txt-link-abbreviated" href="mailto:john.callahan@udel.edu">john.callahan@udel.edu</a>
<a class="moz-txt-link-freetext" href="http://www.dgs.udel.edu">http://www.dgs.udel.edu</a>
****************************************</pre>
<br>
<br>
<br>
David Carmean wrote:
<blockquote cite="mid:20081001225915.A21099@halibut.com" type="cite">
<pre wrap="">On Wed, Oct 01, 2008 at 06:19:09PM -0500, Ian Dees wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Wed, Oct 1, 2008 at 6:08 PM, David Carmean <a class="moz-txt-link-rfc2396E" href="mailto:dlc@halibut.com"><dlc@halibut.com></a> wrote:
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I think the mapping of FCode to OSM features is going to be very sparse,
and
I'm currently wishing we had an entire new set of "hydrology=something"
feature
tags :)
</pre>
</blockquote>
<pre wrap="">
There really are only a few features I'd like to see put into OSM:
- rivers
- lakes
- swamp areas
- drainage ditches
- reservoirs
All of these things have descriptions in NHD, but not all of them have
descriptions in OSM. Perhaps we should make some tagging proposals, get them
approved/discussed, then continue with the import.
</pre>
</blockquote>
<pre wrap=""><!---->
I've extracted the FCode table from the dataset for my area, and am mapping those
to existing and proposed map features/tags as found on the wiki. We can add some
selection criteria later. I can upload it to a wiki page when I'm finished.
I think we need a new key, which will be of use in other scopes as well:
"existence". In particular, for hydrographic features it could have the
values "perennial", "intermittent", or "ephemeral". In other contexts,
"seasonal", "event", etc.
_______________________________________________
Talk-us mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstreetmap.org/listinfo/talk-us">http://lists.openstreetmap.org/listinfo/talk-us</a>
</pre>
</blockquote>
</body>
</html>