Skip to content

Instantly share code, notes, and snippets.

@jqtrde
Last active August 29, 2015 13:58
Show Gist options
  • Save jqtrde/9978316 to your computer and use it in GitHub Desktop.
Save jqtrde/9978316 to your computer and use it in GitHub Desktop.
Using NHD in Tilemill

For most maps, detailed hydrography isn't important, which means OSM works just fine. For the finer scale, restoration oriented maps than I need to create for SHARE, the OSM data is not up to snuff.

The benefits of NHD data are:

  • Lines for ephemeral, intermittent, and perennial streams. OSM data data does not even consist of a network, just the outlines of larger water bodies.
  • It's a continuous network, with appropriate hunctions.

Things that suck:

  • There are SO many line-strings
  • Labelling is tough.

The saving grace of NHD data, is that each line has an FCode attribute. Here are the relevant data:

  • 55800 - Artificial paths (larger rivers)
  • 46003 - Intermittent streams
  • 46006 - Perennial streams

OSM Waterways

Linear features (Rivers & Streams)

  • waterway=river
  • waterway=stream
  • intermittent=yes
  • natural-spring
  • waterway=dam

Resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment