<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Bitstream Vera Sans";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:Consolas;
color:black;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>With all the address stuff I’ve completely dropped NHD off my plate.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I had been working on a NHD to OSM conversion and had gotten so far as to get a Potlatch2 instance with it as a background layer, see <a href="http://lists.openstreetmap.org/pipermail/talk-us/2012-November/009515.html">http://lists.openstreetmap.org/pipermail/talk-us/2012-November/009515.html</a> and <a href="http://took.paulnorman.ca/potlatch2/potlatch2.html">http://took.paulnorman.ca/potlatch2/potlatch2.html</a>.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The NHD data model changed shortly after bsupnik wrote his conversions and some fcodes changed. This makes using his conversions difficult.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I would welcome a review of the tagging which I am proposing, which can be found at <a href="https://github.com/pnorman/ogr2osm-translations/blob/us_nhd/us_nhd.py">https://github.com/pnorman/ogr2osm-translations/blob/us_nhd/us_nhd.py</a>. I can also generate a .osm file for any sub-basin (4 digit code), or extract part of a subbasin.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>ogr2osm isn’t too hard to run, but compiling ogr to have .mdb support to open up the files from the USGS is difficult, so if you want me to convert an area let me know the bbox and sub-basin.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Mack Stanley [mailto:mcs1937@gmail.com] <br><b>Sent:</b> Monday, March 11, 2013 9:34 PM<br><b>To:</b> talk-us@openstreetmap.org<br><b>Subject:</b> [Talk-us] Questions about bsupnik's NHD OSM files<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Bitstream Vera Sans","serif"'>I have some questions regarding bsupnik's osm xml files made from the NHD<br>flowline, waterbody, line, and point shapefiles. <br><br>I was very happy, belatedly, to find these files graciously created and hosted by<br>bsupnik. Fall of 2011, I worked up some ogr2osm translations to do the same thing<br>on shapefiles laboriously downloaded using the balky USGS National Map Viewer,<br>unaware of bsupnik's work.<br><br>I've read a lot about the tagging and integration issues that make bulk uploading<br>NHD data to OSM a bad idea. My goal was just to use it to make a hydrography<br>layer for my own use, while conforming to consensus tagging conventions,<br>potentially to make it useful to others.<br><br>I'd love to use bsupnik's files, instead. My main problem is that GNIS names of<br>streams and waterbodies aren't included. I've seen this mentioned in this list's<br>archives, but couldn't find why this is, or how to fix it. <br><br>I looked into adding name tags from GNIS feature files, but this looks more or<br>less impossible. Names in feature files are attached to points. The name point<br>for a tributary is often at its confluence with the stream it feeds, making the<br>name assignments difficult to determine mechanically. <br><br>The rest of my questions are about tags. I've looked in detail at four files<br>(15010014, 16040201, 17090006, and 18040011). <br><br>Three great things about bsupnik's files are that they are small, they are easy to<br>read by humans, and the ultimate objects (points in point files, ways in flowline<br>files, and relations in area and waterbody files) are tagged with their fcodes.<br>This last feature means that other tags are frosting on the cake---it's trivial to<br>rewrite with different tags. Bsupnik's wise preference seems to be to simply<br>leave objects without regular osm tags in cases where the correct tagging is<br>uncertain.<br><br>Nevertheless ...<br><br>In Flowline files, why is<br><br>fcode 33400 (connector) is tagged waterway:stream rather than waterway:canal ?<br><br>fcode 46000 (Stream/River no attributes) is not tagged, rather than<br>waterway:stream ? (Other Stream/River fcodes are tagged waterway:stream.)<br><br>fcode 46007 (Stream/River ephemeral) is tagged just waterway:stream, rather than<br>waterway:stream intermittent:yes ?<br><br>In Waterbodies files, why is<br><br>fcode 39001 (Lake/pond intermittent) tagged natural:water<br>occurrence:intermittent, rather than natural:water intermittent:yes ?<br><br>All of the other intermittent tags that I have run across in the bsupnik nhd files<br>follow the more common usage (judging by taginfo) intermittent:yes rather than occurrence:intermittent.<br><br>fcode 46600 (Swamp/Marsh no attribute) is tagged natural:wetland, but<br>fcode 46601 (Swamp/Marsh intermittent) is not tagged, and<br>fcode 46602 (Swamp/Marsh perennial) is not tagged.<br><br>Why not tag all three natural:wetland with intermittent:yes added to 46601 ?<br><br>Thanks for your time and interest,<br><br>Mack</span><o:p></o:p></p></div></div></body></html>