Hydrography Webinar Series - Session 2

Video Transcript
Download Video
Right-click and save to download

Detailed Description

 

The USGS Hydrography Webinar Series shares success stories from users, provides information on The National Hydrography Dataset (NHD) and other related products, and provides a forum for users to learn more about Hydrography-related topics.

Details

Date Taken:

Length: 00:59:06

Location Taken: US

Transcript

0:09
Jeff Simley: Hello, this is Jeff Simley from the US Geological Survey, and welcome to
0:12
the Hydrography Seminar Series.
0:14
This is session three, recorded July 30th, 2015.
0:17
Your hosts for these sessions are myself, Jeff
0:21
Simley, and Al Rea.
0:22
The agenda for today is, we start off with a brief introduction, and then
0:26
Anita Stohr will talk about putting NHD to work in the state of Washington.
0:30
This will be about a 20 minute talk.
0:32
This will be followed by discussion, questions, and answers.
0:34
And then that will be followed by two lightning talks, the UFINCH - Adjusting Unit
0:40
Flows in NHD Plus by Dave Holtschlag, that will be a five minute talk.
0:45
And then that will be followed by Local-Resolution NHD
0:48
Stream Delineation from Lidar by Susan Phelps, that will be another five minute talk.
0:53
The purpose of these seminars is to share success stories from users who have solved
0:58
real world problems using hydrographic data.
1:01
Also, to provide information on the NHD, WBD, and related products.
1:05
And thirdly, to provide a forum for users similar to what
1:08
might be encountered in a conference setting.
1:11
These topics include hydrology, resource management, pollution control, fisheries,
1:17
emergency management, mapping, and elevation/hydrography integration.
1:23
Formats for these series are use cases, underlying technology,
1:26
the lightning talks, and collecting feedback from users on these sessions.
1:31
You can find out more about the hydrography seminar series by looking at the NHD website,
1:38
under the hydrography seminar series tab, that'll give you information about all past
1:42
and upcoming seminars.
1:44
Also, you'll find information in the NHD Newsletter and mailing
1:48
list for the NHD Newsletter, so if you get the NHD Newsletter you'll get a notification
1:52
about these.
1:53
Also the American Water Resources Association and other organizations
1:57
will have information about the seminar series.
2:01
And then contact info from the webinar sign up, which means that if you signed up
2:05
for one of these seminars, we'll send you an email letting you know about future
2:09
sessions.
2:10
We expect to give these about every six to eight weeks and after the seminar is
2:15
over with there'll be questions and answers that you can ask via the chat feature in the
2:22
webex.
2:23
So today's Seminar is Putting NHD to work in the state of Washington by Anita Stohr.
2:28
Anita Stohr is the National Hydrography Dataset steward for Washington State.
2:32
She works in the geospatial and environmental
2:34
systems support unit within the Washington Department of Ecology, and coordinates NHD
2:39
use and improvements in all state and private lands.
2:41
Prior to her role as the state steward, she worked as a senior hydrologist
2:45
performing water quality and quantity modeling.
2:49
So Anita go ahead.
2:51
Anita Stohr: Okay, thanks.
2:53
Washington State adopted the NHD as its standard hydrography dataset in January of 2011, and
3:01
since that time the states focused on the associating the highest priority water resources,
3:05
human health, and fisheries datasets to the NHD.
3:09
We've also been correcting the largest errors in line work, and providing
3:13
access to a wide variety of users.
3:17
Washington has a wide variety of landscapes, water
3:20
types, and resources which led to the development and use of many GIS hydrography
3:27
datasets early on.
3:29
This first slide shows the photo of Puget Sound.
3:33
The Department of Ecology samples water quality here and around the state.
3:38
In Puget Sound, a float plane is used to collect many of the samples.
3:41
Sample points are attached to the NHD, but they used to be on our
3:47
own hydrography layer which was called BOSWIS(sp?)
3:52
Forestry is also a big industry in the state and our Department of Natural Resources
3:56
manages forestry.
3:58
So this photo here shows the Lewis River watershed, they need
4:03
to know where streams are located to manage riparian buffers and road maintenance
4:09
associated with logging activity.
4:12
And they care not only about the large streams, but
4:14
they care about small streams like this, this is a
4:17
small headwater stream in the Willapa watershed and its called one of our tight end
4:22
headwater streams, and they're important for protecting species such as the Pacific Giant
4:28
Salamander.
4:29
If you go over to the east side of the state, it's a lot drier and there's a lot of irrigated
4:34
agriculture.
4:35
Even though when you look from aerial photos lots of these streams look small to folks,
4:41
if we go and zoom in I'm going to zoom in to one of these streams with the road
4:44
crossing this is what one of those looks like in June of this year.
4:49
During snow melt those streams get pretty big and then they'll
4:53
dry up lots of times by the end of the year, depending on how much irrigation is being
4:58
pumped into those streams.
5:00
We also have a lot of Hydro power.
5:03
This is the Rocky Reach Dam on the Columbia River
5:06
in Eastern Washington.
5:08
We also have small dams that are monitored by our dam safety
5:14
unit.
5:15
This is the Hofer diversion dam over in Walla Walla Basin.
5:19
It's on the Touchet River over by wine country.
5:23
These diversions, even though it's a dam, it's also got a fish passage associated with
5:30
it, it's got two water diversion associated with
5:32
it, and information about screening to protect fish.
5:39
Then finally salmon.
5:40
This is a picture of the Skykomish system and anglers out fishing
5:44
for salmon on the west side of the state.
5:48
Salmon also migrate up through the Columbia River, all along here, up into ...this is
5:54
a picture of the Yakima system.
5:56
That has salmon in it, and also is used as a major irrigation
6:00
source.
6:03
Having these separate GIS hydrography layers is OK when you doing separate
6:08
management, but they're expensive to maintain, and we have a lot of data in common.
6:12
We had a lot of problems we wanted to solve, like having trying to get our data on the
6:18
same hydrography database set.
6:20
In January of 2011, a bunch of agencies got together, and we adopted a national
6:29
hydrography data set as a state standard.
6:31
We're still moving towards there.
6:34
Not everybody has been able to get all of the way there,
6:38
because it's expensive.
6:39
The idea is we're trying to get to maintaining one copy for the state
6:44
and be attaching individual agency business needs through linear referencing.
6:51
Today, I wanted to touch on three of our areas water diversions, fish distribution and
6:59
stream order.
7:02
Everyone wants to know where water's diverted, so that's one of the things
7:04
we did first.
7:07
Washington has been moving water rights, points of diversion, and places of
7:10
use information from paper documents to digital map form for many years.
7:14
If you look over on the left, here, that's what that looks like.
7:18
These were needed especially for court cases, adjudications,
7:22
and to evaluate new water rights and transfers.
7:26
These were all on a map with the polygons being where water was used, and all of these
7:32
little triangles being diversion points.
7:34
They were not associated with the NHD the diversion points and many of them were
7:41
only located to the centroid of a quarter section.
7:44
If you wanted to know which rights diverted from a particular stream network,
7:50
for example, you couldn't do that.
7:52
If you go over to the right side, this picture is the
7:59
NHD.
8:00
These little red dots are the older system, our GWIS system.
8:04
You can see some of those red dots are on the stream and some are just located like
8:09
this, a little quarter section that has a whole bunch
8:11
of dots on it.
8:12
If I was interested in knowing, "What are all the water rights diverted from
8:17
maybe this stream network here?"
8:21
I wouldn't be able to do it.
8:23
I could try to select all of those, but I don't know, of these, if it's really
8:27
going on this river system or this river system.
8:30
Although the legal documents, a lot of them, had stream names, lots of times those were
8:36
spelled different ways or they were missing, and there was just really no way to get all
8:41
the diversions on a particular stream.
8:46
We got a grant from the USGS to go and import those to the NHD.
8:58
We use the Hydro Event Management Software available through
9:02
USGS, and this comes as a tool bar.
9:07
We imported all of those surface water points
9:10
of diversion in 25 foot increments.
9:14
We created a feature class from our old points of diversion
9:20
which was named this, the [?] SDE point.
9:24
We had a link field, our unique identifier, We had our NHD data, our network data here.
9:31
Then we set a search tolerance.
9:32
This says 25 meters, but we actually used 25 feet.
9:36
Then we pulled in everything that was within 25
9:39
feet, snapped it to the stream.
9:42
If the stream name from NHD matched the one on our original record, then this is good
9:51
and we're fine to go.
9:53
If they didn't, that was a manual check.
9:56
Then we went and save that 25 feet as an attribute on that database,
10:01
and then went to 50 feet and pulled the next set in.
10:05
We had a measure of how close that was at the beginning.
10:11
We manually check all diversion that didn't have a name match and any diversion that
10:16
were over a thousand feet away.
10:18
We also had to manually check all lakes diversions that
10:21
didn't have a name match and any diversions that were over a thousand feet away and we
10:22
also had to manually check all lake diversions.
10:23
We had problems with springs.
10:25
Some of the springs were just little dots, mixed with
10:31
streams.
10:32
A lot of those, if they were close enough, those diversions were snapped the to
10:36
the end of the closest stream network.
10:39
It was a lot of research by Brad Carlson in a our
10:44
water resources program to go through and look at the legal documentation to find out
10:49
where those were.
10:51
In the end, we have 37,000 of these located.
10:57
This is a piece of data that is associated them.
11:00
Each of those point features has, of course, a reach code and a measure.
11:07
They also have a URL that links into a web map that
11:09
gives you a lot more information about that diversion.
11:12
It has a quantity on it down here, the cubic feet per second quantity.
11:21
Most of you in the West probably know our water law is what's
11:25
allowed when it was permitted, and it's not the actual amount withdrawn.
11:29
You have to know something about our water law in order
11:32
to use those quantities.
11:35
A portion of our diversions have quantity meters on the them, and that's what this field
11:42
this here, reporting status.
11:43
There's no reporting, or it's metered.
11:46
Ecology requires metering as a condition for all new surface water rights
11:50
now it does.
11:52
Originally, it used to be just our larger surface water diversions and diversions
11:57
from areas that have fish stocks that were classified as critical or depressed.
12:03
I'm going to show, this the webmap that it goes to.
12:08
If you click that link, you get popped into this, which is called Water Rights Explore.
12:13
It shows you where the particular location is, gives you some more information
12:19
about it, and it also usually gives a list of
12:23
documents that you can click on.
12:25
I can go here, click on the certificate, and get the
12:29
original document that comes with that water right.
12:33
We are uploading a portion of these to the national map, into the NHD point event feature
12:40
class layer.
12:42
We decided to just the largest ones, because a lot of them are pretty small.
12:47
On national scale, that was more important.
12:49
We chose ones that had a water quantity greater than 10 cubic feet per second, or the quantity
12:57
is greater than 5 cubic feet per second and metering is required.
13:01
We removed claims that were not metered.
13:06
Moving on to fish distribution.
13:10
Salmon and steelhead fisheries in Washington are
13:12
important for both commercial and recreation users.
13:18
These fish are co managed by Washington State Department of Fish and Wildlife
13:22
and treaty tribes in Washington.
13:27
This SalmonScape web map, which released last year and shows fish distributions that
13:34
are all located on NHD through linear events.
13:37
This was a huge deal.
13:39
Prior to this project, the State Department of Fish and Wildlife had its own fish
13:43
distribution on their own hydrography layer called str24.
13:49
Northwest Indian Fish Commission had their own fish distribution
13:52
on another hydrolayer called CHEOPs.
13:55
Though a grant with EPA, a team was put together to jointly map this distribution onto
14:00
the NHD.
14:01
You can see there's different distributions, depending on which species of salmon you
14:07
have.
14:08
Under this map right now is fall Chinook streams.
14:12
If we click on spring Chinook streams, it's a totally different type of
14:17
map. there's more of them in Eastern Washington.
14:20
Where these species live, along with timing of spawning and rearing, affects not only
14:32
the fishing seasons, but it affects even the logging
14:35
regulations, temperature and dissolved oxygen limits on point source discharges to
14:40
the stream, and also timing of construction projects near those streams.
14:48
They've got their distribution, a bunch of attributes.
14:51
You can get NHD reach code measures for those.
14:56
They also continue to store an LLID code, which is a whole stream
15:02
identifier that's important for them to link back to their historical data.
15:09
One of the things that we were able to do, since we had NHD and fisheries on the same
15:13
map this is just an example of something that we could do really fast last year was to
15:20
be able to produce a web map for water quality grant applicants.
15:25
There was a project where we were soliciting folks that wanted to get grants, and there
15:31
was a particular buffer requirement for those to go through.
15:36
I just kept this one in here for documentation that you guys can read later
15:41
if you want.
15:42
Essentially what it was is we needed to put out a map with four different groups of buffer
15:48
requirements.
15:49
If you were going to apply for grants, this is how big your buffer was going
15:54
to need to be.
15:55
It needed to be something easy that we put up on our GIS, online for folks
16:01
to get.
16:02
All of these categories the 35 minimum buffer, the 50, the 100 could all be
16:10
derived from NHD and from fish distribution.
16:13
These pieces of it, category A, constructed ditches, intermittent streams and ephemeral
16:24
streams.
16:25
Those were all in the FCode, FType in NHD.
16:29
Perennial waters are too.
16:31
With salmon information, we needed this third category
16:36
with the wider one, for the perennial, intermittent and ephemeral waters that also
16:41
had fish attached to it.
16:43
This probably took just a few weeks.
16:46
They guy, Dustin Bilhimer in our water quality program, put this together.
16:52
This was a map with just NHD streams, salmon only, NHD
16:58
with no salmonids.
17:01
He combined it together and put it out into an ArcGIS online map
17:06
with instructions for grant applicants.
17:11
Those grant applicants could go in, zoom in, had different color codes for the different
17:16
riparian buffers.
17:17
They could go into their own area and find out, "If I'm going to apply for
17:22
something in this area, that's what it needs to be."
17:27
It was a real successful collaboration between our agencies to put this out.
17:31
The other thing, we had kind of a side benefit from this project.
17:38
Especially the canal ditch features and making sure those were right,
17:42
became really important, so we've doing a lot
17:44
of irrigation district mapping and recoding.
17:48
If you were on a canal or ditch, that buffer requirement was smaller, and so that's led
17:55
to really improving a lot of our FCode and FType information.
18:02
For stream order, the Strahler stream order, the states of Washington and Oregon
18:10
calculate Strahler stream order on the high resolution NHD.
18:15
We provide that to our state users and to our USGS point of contact to
18:21
be loaded into the NHD flowline value added attribute table.
18:29
People wonder, "How did this come about?"
18:31
There was two main things.
18:32
We had a need for stream order internally, and, in reality,
18:38
was a self defense mechanism for me.
18:41
I was being faced with the questions on this slide,
18:44
and I was a new steward, and actually I was surprised that I was getting these.
18:49
If we look up on the fifth area here, this was a slide that I got from the US Forest
18:56
Service.
18:58
The US Forest Service does all of the NHD mapping on federal lands, and I do it on state
19:06
and private.
19:08
There's areas that we call the checkerboard regions, where its ownership goes
19:13
in and out of federal ownership.
19:17
They generally have less streams on their maps.
19:21
They said, "Can we delete all of these little black lines?
19:26
Those aren't really streams."
19:31
That was interesting.
19:32
At the same time, the USGS was going through its network improvement project, which
19:37
was doing a lot of quality control on flow direction across the country, to prepare for
19:50
a new NHDPlus.
19:51
This is one that I got from them, "Can we delete all this with red Xs over,
19:56
because these aren't real streams."
20:00
For this one I looked at the aerial photos looked like and it was like, "Well, there's
20:04
all these green areas there.
20:05
Actually they might not be super big streams but they're
20:08
definitely aquatic habitat.
20:10
This little streams originally were imported from our
20:15
department of natural resources, our logging...and they do protection of other aquatic
20:21
species.
20:22
We pulled all those in, because they had said, "We only want to be part of this if you
20:26
have our streams," so we couldn't get rid of those.
20:29
At the same time, when I had people trying to remove streams, I had other folks...this
20:35
is a picture from Clallam County, up the Elwha River Basin.
20:40
They've done a good job of generating streams from LiDAR.
20:45
In this one, the red streams were existing NHD, and the blue were LiDAR
20:52
generated streams that they wanted to add.
20:55
One of my fears was that I didn't want to be deleting the streams, and then have
21:02
somebody add the same streams in later.
21:04
I needed to do this.
21:06
I looked at this.
21:07
How do we code NHD Flowline to accommodate users needs to see different levels, different
21:15
density levels, and to incorporate LiDAR?
21:18
I wasn't sure what to do, so I went and took
21:23
this to our Pacific Northwest Hydro Framework meeting.
21:28
In Washington and Oregon, the state and federal partners meet once or twice a year to go
21:32
over NHD issues and help each other figure out what to do.
21:38
I made this slide and I looked at five different ways of coding those lines
21:43
so that people could choose to see more or less.
21:46
I had one that I called density independent on this side, and I had the density
21:52
dependent one on this side.
21:53
What I mean by that, if you look at this picture and you all know this when you go across
21:59
lengths from one county or one township to another, one state to another, people map
22:05
things at different densities.
22:07
You can go and have an artificial line right down here, where one side is dense and one
22:11
side is not dense.
22:13
Ideally, we'd have something that would get the same code, no matter
22:17
what your density was.
22:19
First I looked at those, and one value I thought it would be great, because of my former
22:25
work doing water modeling stuff, was mean annual flow.
22:28
This was a value that was available on NHDPlus dataset, but it was only
22:34
available on the medium resolution, the 1:100K data.
22:37
It looked good, but it looked like it was going to be years before that came to the
22:44
high resolution dataset, and we needed in the high
22:47
resolution dataset.
22:48
I also looked at periodicity.
22:50
There's a code at NHD for perennial, intermittent and
22:54
ephemeral, but in Washington, we've only used perennial and intermittent.
22:59
We don't have good rules for what's ephemeral and what's
23:04
not ephemeral.
23:05
There's also been some legal issues around the use of the word "ephemeral,"
23:11
so we didn't have that.
23:14
The other thing I looked at was there was a group at USGS, Larry Stanislawski's group,
23:21
that was going through and generalizing, picking streams that would be displayed on the
23:26
1:24k National Map.
23:29
I thought, "Well, that would be great.
23:31
If they're going to select the ones would appear on a 1:24k Map, if I could
23:37
go and select those and run stream order on just those, that would be great."
23:42
But, they weren't really selecting them and then flagging those.
23:46
They were actually doing a generalization process, and selecting and
23:49
removing some vertices, and so it wasn't really something I could actually select from.
23:55
I ended up looking at the density dependent side.
23:58
I looked at stream level, which was a value in the NHD data model, in the value
24:06
added attribute table, but it had been set up for
24:09
NHDPlus processing and pretty much everyone said not to use it.
24:15
We ended up with stream order.
24:17
This was one which was requested by the most users.
24:21
It was already in the in the NHD Data Model.
24:28
Jay Stevens, who works for BLM Oregon, already had a process in place and had run
24:34
stream order on about half of the State of Oregon.
24:39
We just went for it.
24:41
I said, "Well let's just do it," and I did.
24:44
I was smart enough to ask Jay first, "Wow, since you've done half of Oregon,
24:49
do you wanna just do Washington while you're at it?"
24:53
He said, "I'll help you get it set up there, so you can do it yourself."
24:59
[laughs] So this is what it looks before NHD, and then
25:03
this is what it looks like with stream order on it.
25:09
It might not be perfect, but it sure works for 90 percent of the problem.
25:14
This is the NHD Flowline value attribute table with the
25:18
permanent identifiers and filled out stream order.
25:23
The way we did this, the process is we run stream order by four sub regions.
25:31
We will go and download a copy from a pre stage sub region
25:38
from USGS.
25:40
It comes with the NHD flow table, and it's all based on this.
25:45
We copy that over to our server, and I have a little
25:50
stream order toolbox.
25:51
I'll run a QAQC on that to make sure that all the network ends and pour points are valid.
25:57
Then I run a stream order script that goes and generates this table here, which has stream
26:04
orders and permanent identifiers.
26:07
Then I can join my NHD flowline using on permanent identifier and draw it up.
26:17
For some basins that is all that has to be done.
26:20
In some basins with a lot of irrigated areas, when that canals cross each other, lots of
26:27
those can artificially make the streams too large.
26:31
These are obvious errors.
26:32
In that case, we go and we make a copy of this geo database
26:38
that we can edit it on, and go through and delete the flowlines that cause these man
26:43
made canals to create incorrect stream orders.
26:46
We'll delete those, and then USGS also provides a group of NHD utilities, and I'll re run
26:54
this build flow utility and rebuild the flow table.
26:59
When I've done that I repeat from this above.
27:01
I'll go and copy that flow table over to our server and rerun it.
27:06
When we're satisfied that it's complete, I run final Python script to copy to stream
27:13
order as the new attribute under flowline and also
27:16
put it on to the VAA table.
27:19
Then I share those with Oregon and USGS.
27:26
That is the end of the Washington's presentation.
27:29
Are there any questions?
27:32
Jeff Simley: One of the things that we'll do, Anita...thanks a lot for going through
27:36
that, very interesting.
27:37
For the questions we should have people taping questions into the
27:41
Q&A tab.
27:42
Al Rea and Susan Buto are monitoring that.
27:47
Al or Susan, do you have any questions that have come up yet?
27:51
Al Rea: None yet.
27:54
Has everyone found the Q&A tab?
28:01
If you maximized the screen to see Anita's slides, then you need to put
28:09
your mouse to the top of the screen and a little
28:11
pull down thing will show up.
28:13
There's a little Q&A thing there.
28:17
Anita: While we're waiting for Q &A, I put some acknowledgements on the last
28:23
page there.
28:24
There's a list of folks that helped out with the different pieces.
28:29
Otherwise, this probably wouldn't have...this definitely wouldn't
28:35
have happened.
28:36
Al: Anita, we still haven't gotten any questions in but this is Al.
28:43
I'll just go ahead and ask you a little bit about the web map that you
28:47
put on ArcGIS Online.
28:50
I think you mentioned that in your newsletter article a couple months
28:58
ago, but maybe we could share the URL for that.
29:03
Could you just talk a little bit about how people are using that?
29:08
Anita: There's was one I mentioned in the newsletter and that was a different one.
29:13
The one in the newsletter that I mentioned is
29:17
our feature service that we put out.
29:18
We do have an NHD map cache for the State of Washington
29:24
that's out there for folks.
29:26
If you're using ArcGIS Online, you can just pull back to again
29:30
get any maps you want to use.
29:34
This one that I showed here is a separate web map that was just used for that one project.
29:44
We have different web maps for different uses.
29:45
That one, for that water quality buffer was a separate one, but we do have what I
29:52
mentioned in the newsletters.
29:53
We have a cache, which is really helpful.
29:56
Many users can pull that into any kind of web
30:00
mapping software they want to.
30:02
We have a hydro and labels for that separately.
30:06
Al: Looks like Sue's having a little trouble getting un muted, so I'll go ahead.
30:18
We have a question from David Anderson who asks, "Can
30:22
you share the toolbox that you used for stream order?"
30:28
Anita: Yes, I could.
30:32
You would just like the toolbox and the associated Python code for
30:37
that?
30:40
Al: Mm hmm.
30:49
Anita: That Python code...this is kind of interesting.
30:55
Jay Stevens had gone through and written the original Python code for the stream order.
31:03
In Oregon, they use the Oracle system for their SDE database, and so he had done it
31:09
with that.
31:10
When he transferred the code up to us, we use a SQL Server SDE database, so one
31:16
of the folks on our staff here, Darby Veeck, rewrote that code on something that worked
31:22
on our system.
31:25
Al: OK, thanks.
31:33
Any more questions?
31:34
Jeff: This is Jeff Simley, Anita.
31:43
I was just following up on the stream order.
31:50
How do you account for divergences in the network with
31:54
the Strahler stream order?
31:56
Anita: The divergences carry that same stream order.
32:02
The stream goes down and it's a seven, it carries through those.
32:06
Braided streams end up having the higher stream order.
32:12
The braids in the stream, when they diverge and come together, they carry that same
32:18
stream order.
32:20
Jeff: Are there any other questions, Al?
32:26
Susan Buto: I have a question for you.
32:31
Can you briefly elaborate on legal issues that you
32:35
mentioned with the use of the term "ephemeral?"
32:37
Anita: I was just told not to do it, and it had something to do with water quality
32:44
regulations in our state law.
32:49
I was told not to use it about a year back, so I just didn't.
32:59
I think we would start to use it if we had some
33:02
good rules for figuring out what is ephemeral and what's not.
33:06
If we could go through and have some automated process to say, "This group is a
33:12
ephemeral, would probably go back and say, "This is, this is what we'll do."
33:19
I think the
33:25
definition of ephemeral had something to do with how many days of rain.
33:31
It wasn't a map based criteria at all.
33:37
You had to use rainfall over a certain number of weeks.
33:41
I don't know.
33:42
It wasn't going to work, and they didn't want me to go there.
33:45
Susan Buto: Fair enough.
33:46
I thank you.
33:49
Al: Another question that has come up is, "Would the presentation be available online?"
33:57
We will post the presentation on the website for the seminars, which is on the main NHD
34:06
website.
34:07
Near the bottom, on the left hand side, there are links.
34:13
Near the bottom, there's one for the Hydro Seminars Series.
34:17
We will be posting the presentation there.
34:24
We're also trying to get recordings posted, but that's taking us a while.
34:31
I know we promised earlier to get the earlier seminars
34:37
posted, but we have to comply with Section 508, making them accessible and closed captions.
34:50
We're having trouble getting all of that done, so it's been a bit of a delay on that.
34:57
We will hope the recordings up there pretty soon.
35:02
Jeff: Any more questions come in?
35:06
Al: No.
35:08
Jeff: OK, good.
35:11
Anita, thanks a lot.
35:13
Once again, as Al just point it out, this material will
35:16
be available to you through our website.
35:18
Be sure to go to nhd.usgs.gov, look for Hydro Seminars Series, and you'll find information
35:25
posted over the next few weeks on this presentation that Anita gave.
35:29
You can learn more about it.
35:30
I'm sure, Anita, that you'd be happy if people contacted you personally if they had
35:34
questions about your work in Washington.
35:36
Anita: Yeah, that'd be just fine.
35:39
Jeff: Next, we're going to move on to what we call a lightning talk, and this is going
35:43
to be a brief five minute presentation.
35:46
The first one is by Dave Holtschlag.
35:48
He's a surface water specialist from the USGS Michigan Water Science Center.
35:53
He holds a bachelor's degree in forestry from the
35:55
University of Missouri and master's degrees in forest hydrology from the University of
36:00
Minnesota, and systems science engineering from Michigan State University.
36:04
Dave is an accredited professional statistician by the American Statistical Association.
36:08
As part of his professional and principle development,
36:11
Dave has successfully completed 40 courses through Stanford online and Coursera.
36:16
He began his career with USGS in 1976 studying floods and established 45 technical
36:23
reports on the survey.
36:25
Dave's talk is about UFINCH, a method for simulating and adjusting unit flows in
36:31
networks of channels described by the NHDPlus geospatial framework, using continuous
36:38
daily flow data at USGS streamgages.
36:41
Dave, go ahead.
36:44
Al: Dave, are you muted?
36:53
Al: Dave, we're not hearing you.
37:00
Jeff: All right, if we're not getting Dave on, we can go ahead with Susan Phelps to talk
37:12
about her talk.
37:14
Going once, going twice, Dave are you on?
37:18
Susan, how about you?
37:24
Al: I'll switch it over to Susan.
37:28
Dave, if you can try and figure out your audio problem
37:34
while we do Susan's.
37:37
Anita: Are we hearing Susan?
37:45
Jeff: Susan, are you on the line?
37:52
Susan Phelps: I don't need the lecture mode.
37:53
That might get it back.
37:54
Al: Want to hit *5?
37:55
Recording: The conference is no longer in lecture mode.
37:56
Woman: Are Susan and Dave on now?
37:59
Dave Holtschlag: Yes, we're on.
38:01
I'm on.
38:02
Woman: Everybody, we had to take the conference off of muting of everyone, so if
38:05
people can please mute your telephone lines we'd really appreciate it.
38:09
It cuts down on feedback and accidental coughs, dog barks,
38:16
and hold music.
38:17
Please don't put us on hold if you have hold music, and mute your phone lines.
38:18
If you can't mute with your phone you can dial *6
38:21
into your phone, and that will mute it on this
38:23
conference line.
38:24
You want to go back to David or stay with Susan?
38:28
Jeff: We'll go with Dave, since we've introduced Dave, got him all set up, and
38:32
everybody's all excited to hear this.
38:34
We'll go ahead with Dave, as soon as we get this first
38:37
slide ready to go here.
38:38
Al: Dave, I just made you presenter again.
38:42
Dave: Can you see my presentation and hear OK?
38:53
Jeff: Yes.
38:54
Dave: That's great.
38:56
UFINCH is a standalone computer application intended to run on
39:01
windows PC.
39:02
It's written in a Matlab programming environment, but does not require
39:05
Matlab on your local computer to use it.
39:08
I am developing a report.
39:10
It's currently in colleague review.
39:12
I expect to release it sometime early next year, which will provide
39:16
the software, as well as providing documentation.
39:20
UFINCH is intended to be used for streamflow record extension of daily unit values from
39:26
a base gauge at the outlet of a basin to the upstream flowline described in NHDPlus.
39:30
Also could be use for hydrograph comparison and
39:34
record analysis.
39:35
Flow at the outlets is expected to be representative of water yields throughout the basin.
39:40
If we have estuary flows, that would probably be a problem, or if it were heavily
39:46
regulated, that would also be a problem.
39:48
Testing so far, it's been on basins that have a
39:52
3000 square miles or less drainage area.
39:54
I'd like to provide an overview of the functionality, graphical user interfaces, and user
39:59
options to UFINCH.
40:01
This is the main graphical user interface.
40:06
The user would select the two digit hydrologic regions from this drop
40:13
down menu.
40:15
UFINCH would then create the map.
40:19
If you didn't know exactly which region you wanted to use, you can display a map of
40:23
those regions.
40:25
You can display the flowlines and streamgages on the same map, specify a
40:31
water year to highlight the streamgages as they were active in that water year on the
40:36
map.
40:37
Both the flowlines and the streamgages are in active coverage, depending on selection
40:42
of this radio button.
40:44
If you select streamgages, it'll pertinent information to that streamgage.
40:47
If you click on it, the gaging number, name, user record, some other information you
40:54
might need.
40:55
Otherwise, the flow attributes will be displayed.
40:58
When you select base streamgage, it will highlight that entire network up at the
41:04
streamgage that's going to be modeled and indicate the number of flowlines.
41:08
This area you would read 15 minutes flow values.
41:12
If flow value [indecipherable 00:36:56.15] did
41:14
not exist on your system, UFINCH would go out and retrieve an inventory of daily values
41:20
at the station that you selected for the base gage.
41:22
It will then interpolate that to unit values.
41:27
Unit is in 15 minute values.
41:31
That particular time increment was chosen because flowlines
41:36
and velocities in NHD, median resolution, usually accommodate at least one time step
41:42
in the interval.
41:43
Woman: Can people please mute your phone lines?
41:46
We're hearing conversations in the background.
41:48
Thank you.
41:49
Dave: You can systematically adjust the velocity and compute travel time within that
41:55
network to specify a simulation period, and then simulate the flow for that interval.
42:02
You can select, using the same map interface and
42:04
streamgages, say upstream, for a comparison.
42:08
Then another interface can be launched for a streamflow comparison.
42:14
Just a quick comparison.
42:15
This is some of the graphs that you'll see when you highlight it.
42:18
This is streamflow HUC4, that they can be selected from the two digit HUC the map of
42:25
that HUC4 base gage and some of the other things we've been discussing.
42:30
This is a map that shows the comparison, hydrographs.
42:34
The measure flows in blue, simulator flows in red.
42:36
There is a statistical procedure you can use to adjust the flows to
42:42
more closely match measured flows.
42:44
This shows the effect of that correction on the
42:46
empirical cumulative distribution function.
42:50
Summary, UFINCH is highly automated for simulating flows, retrieves information that
42:57
you're going to need, computes travel times, simulates flows, and provides a mechanism
43:04
for adjusting.
43:05
Potential for quality assurance streamflow records and extending
43:11
streamflow data.
43:13
Any requests for information or questions to follow up, I have contact
43:17
information below.
43:19
Thank you.
43:20
Jeff: Thanks, a lot.
43:21
We'll just hold this slide up for second, so people can take a look at
43:25
Dave's email address.
43:26
If you have any questions for him, contact him directly or contact
43:29
us here at the USGS.
43:31
We can forward that information off to Dave, and you can learn
43:34
more about it.
43:35
We'll also have Dave's presentation posted at the website.
43:38
Look for that and you can review the material he just presented.
43:43
Dave: Thanks a lot.
43:44
Jeff: Thanks, Dave.
43:46
Next we are going to turn our attention to LiDAR derived
43:50
hydrography from Susan Phelps.
43:51
Susan Phelps is a geographic information system manager at AECOM's Raleigh, North Carolina
43:58
office.
43:59
She is certified geographic information systems professional, as well
44:02
as a certified flow plan manager with over 15
44:06
years of experience in GIS and water resources.
44:08
Over the last nine years, Ms. Phelps has served as the NHD technical discipline lead and
44:14
assistant project manager for local resolution NHD project in several states, including
44:19
Indiana, Mississippi, and North Carolina.
44:21
Susan is going to talk about local resolution NHD stream delineation from LiDAR based terrain
44:27
sources.
44:28
Susan, go ahead.
44:30
Susan Phelps: All right, thank you Jeff.
44:32
As Jeff mentioned, I'm going to talk about how
44:36
we've been using LiDAR to create local resolution NHD.
44:39
First, I want to talk really briefly about why local resolution NHD is
44:45
important.
44:46
What are some of the drivers behind it?
44:49
First of all, enhance quality and content of hydro data.
44:52
It's especially needed at the local level.
44:55
Also, uniform mapping to support resources and policy decision making across
45:01
large jurisdictions.
45:03
Also, we have a lot more capability with hardware and software to
45:10
help process and analyze the large hydro datasets, and then the websites to help distribute
45:17
and maintain that data.
45:18
Lastly, we have more accurate framework layers like LiDAR and Orthos to help support
45:22
the creation of local res NHD.
45:24
We talked a little a bit about why it's important.
45:29
Now I want to talk a little bit about the approach that AECOM has used for LiDAR based
45:34
local resolution mapping of NHD in North Carolina, Mississippi, and Indiana.
45:40
First, obviously, we needed to collect all the base data that plan to use for the project.
45:48
If the LiDAR has not already been processed and
45:51
hydro corrected, then we will import that data into our proprietary software program
45:56
called WISE.
45:58
That gives us the ability to blend different terrain sources and create
46:03
seamless elevation products from the back end.
46:06
We'll import that LiDAR data into WISE, build our TINs, and hydro correct the elevation
46:13
data, at which point we can start to generate a reference files for local res NHD.
46:20
Reference files are going to include the hydro corrected DEMs and hillshades.
46:25
We're also able to generate six acre basins and guide streams.
46:32
We use those to help with determining the upstream limits and general
46:37
stream locations, basically making sure that we have complete coverage for a basin.
46:41
One thing I want to mention here is that the six acre limit is not set in stone.
46:48
What works in one state may not work in another, so that
46:52
upstream limit can be customized to meet whatever the stakeholders needs are.
46:54
There's a quick example under here.
47:01
This is just your DEMs and hillshades, and then I've got
47:08
six acre basins and guide streams here.
47:10
Some other products that we can generate from the hydro corrected terrain data are flow
47:15
accumulation grids and flow vectors.
47:17
We don't typically use those for digitizing local res
47:21
NHD, but we do have clients that have found this helpful for modeling purposes on the
47:26
back end.
47:27
This is just a quick example of a flow accumulation grid that's generated from
47:33
the hydro corrected data.
47:37
We have all of base data process for the project, and we're ready to start digitizing the
47:44
local res NHD.
47:45
In doing that, we're using the imagery, the hydro corrected DEMs and the
47:50
hillshades as the primary data source for the horizontal stream locations.
47:55
We are also using those LiDAR automated guide streams and the 24K to help indicate
48:02
where the stream should be digitized and how far up into the basin we should digitize
48:07
features.
48:08
The basic process is we start at the upstream end point of the guiding streams
48:16
and work our way down to the next confluence.
48:19
We work from confluence to confluence, basically until all of those guide streams are
48:25
represented in the local res NHD.
48:26
If we do have local hydro data, if it's accurate enough,
48:31
we will use that as a basis for local res NHD flowlines, and then just extend those
48:37
reaches up to the upstream limit of our guide stream.
48:41
Also, we want to reference the 24K to make sure that we're capturing all those streams
48:47
that are still visible in the imagery and the
48:50
terrain sources.
48:53
What are some of the challenges that we've seen with LiDAR based NHD?
48:57
One of the biggest ones we've seen are the areas where
49:01
the streamflow has been altered.
49:03
These are particularly prevalent in the urban areas
49:05
and agricultural areas.
49:08
We found that the guide streams are typically not as accurate in these areas, so we do
49:12
have to rely more on the imagery and the base DEMs, hillshades, and local data.
49:20
The good thing about if you have newer LiDAR,
49:23
your man made canal ditches will show up a lot better in the LiDAR.
49:29
If you have new construction, like highways or neighborhood, they also going to be more
49:34
visible.
49:35
You still may not be able to see where the pipelines are.
49:39
In those instances, the local stormwater data can be very helpful.
49:45
That was all I have for today.
49:46
I have my contact information here.
49:49
If anyone have any question or want any more information, feel
49:53
free to contact me.
49:54
Thank you.
49:55
Jeff: Susan, thanks a lot.
49:58
That was a great presentation, and I'm sure that people are going
50:02
to learn a lot more about that.
50:03
By the way, in case you're interested in seeing the direct
50:05
result of this work, you can download NHD data over Southern Indiana.
50:11
It reflects hydrography that AECOM added to the NHD on
50:14
behalf of the state of Indiana.
50:16
You can directly look at some of those results that
50:19
way.
50:20
If you'd like to contact Susan, or contact us and we'll get you in touch with Susan,
50:24
you want to learn more about local resolution
50:27
NHD derived from LiDAR based terrain data.
50:30
Those were our presentations for today.
50:35
Before we depart, we want to have you take a
50:38
quick poll as to how you viewed this presentation today and suggestions to the future.
50:46
There are three things that we want you to address here.
50:51
One is which part of the session was most valuable to you, which of parts of
50:55
the session were least valuable to you, and what topics are you interested in learning
50:58
about more in the future.
51:00
Speaking of the future, our next seminar is going to be on September 24th, also a
51:06
Thursday at same time, two o'clock Eastern time.
51:09
Our plan is to be talking about SPARROW modeling.
51:12
This involves transport of nutrients, particularly nitrogen and
51:16
phosphorus, through the nation's waterways.
51:20
How can we model that transport of nutrients using those SPARROW modeling systems?
51:25
Look forward to that.
51:26
We hope to have a couple of more lightning talks just to add to the variety of information
51:31
we're presenting.
51:32
I ask that you stay tuned for more information about that.
51:36
You can find out about it through our website.
51:38
You'll also be receiving an email from us.
51:40
I'm reminding you that there's an upcoming seminar, and
51:43
also information about this past seminar and how to access all the materials that we're
51:48
posting online.
51:49
Anything else to add from the team here?
51:52
I want to thank Allison, Susan and Al.
51:56
You guys have anything else to add?
52:00
AL: The polling questions should be showing up as a tab on your meeting there on the
52:09
right hand side.
52:14
Hopefully, you'll see those and you can answer those.
52:22
It doesn't look quite...
52:26
Woman: We have seven people finished already, so I think it's worked OK.
52:31
Jeff: We're going to leave those questions up, to allow people to take time to fill out
52:38
the survey here.
52:39
We'll give you a little bit of time.
52:41
Other than that, we'll close it for today.
52:46
Appreciate everybody joined this call.
52:47
Hopefully, you've learned a lot.
52:49
We've all learned a lot and appreciate the speakers and all the great
52:52
work that they've done.
52:53
Are very dedicated to the NHD, to WBD, and to mapping in the
52:58
United States.
52:59
We appreciate all that good work.
53:01
Thank you and goodbye.