WEBVTT

00:00:00.420 --> 00:00:02.969
Al ReaYeah, so today, we're
going to talk about something

00:00:03.990 --> 00:00:07.670
that we struggled a long time
about what to call this,

00:00:09.430 --> 00:00:13.200
and we finally decided
on the term

00:00:13.200 --> 00:00:16.460
National Hydrographic
Infrastructure,

00:00:16.460 --> 00:00:23.190
or NHI, and that's because
it really

00:00:23.190 --> 00:00:25.290
is what we are envisioning

00:00:25.290 --> 00:00:28.690
this as, really,
in the infrastructure

00:00:28.690 --> 00:00:33.370
that people will use sort of
like the road network

00:00:33.370 --> 00:00:36.010
just to tie things to.

00:00:36.010 --> 00:00:37.800
It's an information
infrastructure,

00:00:37.800 --> 00:00:39.440
not a physical
infrastructure,

00:00:41.960 --> 00:00:50.740
so think of it a lot like
the underpinnings of Google Maps

00:00:50.740 --> 00:00:54.520
or a GPS
that has embedded maps.

00:00:55.130 --> 00:00:57.610
That's what we're envisioning

00:00:57.610 --> 00:01:00.180
as this National Hydrographic
Infrastructure,

00:01:00.780 --> 00:01:03.700
so basically,
we're trying to combine

00:01:04.250 --> 00:01:08.010
this foundational
hydrography data

00:01:08.010 --> 00:01:12.320
sets that we have
with the capabilities

00:01:12.320 --> 00:01:14.200
that they have of addressing

00:01:14.850 --> 00:01:20.210
and then also building
a search engine in a catalog

00:01:20.210 --> 00:01:23.990
so that people can use
the intelligence

00:01:23.990 --> 00:01:26.400
of the hydrography network

00:01:29.660 --> 00:01:31.920
as part of
a search functionality,

00:01:32.520 --> 00:01:35.130
so kind of building
a search engine

00:01:35.130 --> 00:01:39.210
that understands
the hydro network,

00:01:41.290 --> 00:01:44.650
so our concept here is to
provide this infrastructure

00:01:45.540 --> 00:01:47.490
for sharing data,

00:01:47.490 --> 00:01:50.840
any kind of water,
surface-water-related data,

00:01:53.360 --> 00:01:57.210
and that would basically
be kind of

00:01:57.210 --> 00:02:02.710
underpinning
all different agency efforts

00:02:02.710 --> 00:02:08.570
that have hydro observations
and modeling

00:02:08.570 --> 00:02:12.810
and just basically trying
to account for all the water

00:02:14.570 --> 00:02:20.790
in the hydrologic cycle
going from when we get water

00:02:21.610 --> 00:02:23.620
falling out of the atmosphere
onto land

00:02:24.280 --> 00:02:27.280
and where it goes out
into the ocean again,

00:02:28.030 --> 00:02:31.740
so all of the land part
of that water cycle,

00:02:35.210 --> 00:02:37.080
so I will ...

00:02:38.320 --> 00:02:40.770
There's this diagram,
which is kind of complicated.

00:02:40.770 --> 00:02:44.740
I'm going to talk about it
in very general terms,

00:02:45.550 --> 00:02:47.470
and I'll show you ...
On the next slide,

00:02:47.470 --> 00:02:51.400
I'll show you this more so you
can read what's under here,

00:02:51.400 --> 00:02:53.400
but basically,
we're going to talk about

00:02:54.000 --> 00:02:55.600
this hydrographic framework,

00:02:57.200 --> 00:03:00.710
the hydrographic
addressing tools,

00:03:02.330 --> 00:03:04.550
how that relates
to a community

00:03:04.550 --> 00:03:07.010
and how the community
can make use of this

00:03:07.010 --> 00:03:12.200
and, finally, these tools for
catalog search and discovery,

00:03:13.030 --> 00:03:19.730
so here's that figure
a little bit more enlarged,

00:03:19.730 --> 00:03:23.170
and that first category
down there in the center

00:03:23.170 --> 00:03:27.920
is the framework,
the hydrographic framework,

00:03:27.920 --> 00:03:30.100
and that basically consists
of the data sets

00:03:30.100 --> 00:03:35.910
that we've used for many years:
the NHD, the WBD and the 3DEP.

00:03:35.910 --> 00:03:37.500
Now we're combining
those together

00:03:37.500 --> 00:03:39.200
into the NHDPlus High Res.

00:03:40.630 --> 00:03:45.040
Excuse me.
So that's our basic framework,

00:03:46.500 --> 00:03:49.550
and then we are going to spend
quite a bit of time today

00:03:49.550 --> 00:03:51.630
talking about addressing,

00:03:52.280 --> 00:03:54.930
so the term that
we've used in the past,

00:03:54.930 --> 00:03:57.110
which is kind of jargon,

00:03:57.110 --> 00:04:02.410
a GIS jargon term of 'events'
in linear referencing,

00:04:02.410 --> 00:04:04.150
we found that people
just didn't understand

00:04:04.150 --> 00:04:06.910
what that meant
if they're not a GIS expert.

00:04:08.430 --> 00:04:10.530
They didn't understand
what we're talking about,

00:04:10.530 --> 00:04:12.890
but we can talk in terms
of addressing

00:04:12.890 --> 00:04:18.030
as a verb and addressing
things to the network,

00:04:18.030 --> 00:04:19.430
and people understand

00:04:19.430 --> 00:04:22.040
intuitively what
we're talking about,

00:04:22.040 --> 00:04:25.170
so we're talking about
these addressing tools,

00:04:25.170 --> 00:04:31.390
and we have some web services
and this engine,

00:04:31.390 --> 00:04:35.330
addressing engine,
underlying those tools,

00:04:35.330 --> 00:04:38.280
so we're going to talk quite
a bit about those tools today,

00:04:39.240 --> 00:04:41.170
so that's hydrographic
addressing.

00:04:41.170 --> 00:04:45.420
Next, once you've
addressed your data

00:04:45.420 --> 00:04:51.980
or your point of interest
to the hydrographic network,

00:04:51.980 --> 00:04:57.040
you can publish your data
as a web-feature service,

00:04:57.810 --> 00:05:00.190
and then the concept here

00:05:00.190 --> 00:05:02.540
is that we have out
in the community,

00:05:02.540 --> 00:05:05.860
everybody still maintains
control of their own data set.

00:05:06.390 --> 00:05:08.100
They're not making copies.

00:05:08.100 --> 00:05:10.080
We're not storing copies
of your data

00:05:11.290 --> 00:05:15.480
in our database or anything.
You would control your data.

00:05:16.210 --> 00:05:19.900
You would have your data itself,
but you would just serve it

00:05:19.900 --> 00:05:23.070
as a standard
OGC web-feature service

00:05:23.620 --> 00:05:28.160
with particular fields in there.

00:05:28.160 --> 00:05:31.260
There's a minimum set of fields

00:05:31.260 --> 00:05:34.360
that you would need to have
in those data sets,

00:05:34.360 --> 00:05:38.010
and then you could participate
in this NHI framework,

00:05:39.670 --> 00:05:42.070
and so you would have
all your different data

00:05:42.070 --> 00:05:44.340
sets shared out here,

00:05:45.820 --> 00:05:49.510
and then those would feed
into a catalog,

00:05:50.560 --> 00:05:52.820
and then based
on that catalog,

00:05:52.820 --> 00:05:56.990
we'll have
search-and-discovery tools

00:05:56.990 --> 00:06:00.250
and, again, web services,

00:06:00.250 --> 00:06:04.550
so this whole structure
is a web-based structure,

00:06:05.500 --> 00:06:10.210
so moving from the desktop where
we've had similar functionality

00:06:10.750 --> 00:06:14.390
for a long,
long time on a GIS desktop

00:06:16.230 --> 00:06:20.770
primarily in our HEM tools,
working inside ArcGIS.

00:06:20.770 --> 00:06:24.150
This is opening
that whole tower up

00:06:24.690 --> 00:06:30.090
to a web-based infrastructure,
a web-based paradigm,

00:06:30.090 --> 00:06:34.250
so people don't have to have
software installed or anything.

00:06:34.250 --> 00:06:36.110
It works in
the standard web browser.

00:06:38.530 --> 00:06:40.260
So let's see.

00:06:41.430 --> 00:06:45.930
Becci Anderson is going to talk
a little bit about governance

00:06:45.930 --> 00:06:48.480
as it relates to the National
Hydrography Infrastructure.

00:06:48.480 --> 00:06:50.080
Becci, are you on?

00:06:50.660 --> 00:06:51.940
Becci AndersonYep. Excuse me.

00:06:51.940 --> 00:06:54.440
Yes, I'm here, and just a note
for the other presenters,

00:06:54.440 --> 00:06:56.460
it seems like there
might quite a lag

00:06:56.460 --> 00:06:59.620
in especially animations
in the presentation,

00:06:59.620 --> 00:07:04.170
but also maybe even just
switching slides, just a note.

00:07:04.810 --> 00:07:08.840
So the National
Hydrography Infrastructure

00:07:08.840 --> 00:07:10.480
working group
was started up ...

00:07:10.480 --> 00:07:14.940
I believe it was
in the fall of 2018,

00:07:15.800 --> 00:07:25.200
and this group is primarily
focused on moving forward

00:07:25.200 --> 00:07:27.210
with the National Hydrography
Infrastructure,

00:07:27.210 --> 00:07:28.810
all the parts and pieces.

00:07:29.540 --> 00:07:33.730
Right now, it consists of all
of the Federal agencies

00:07:33.730 --> 00:07:35.370
that you can see
in the list there.

00:07:35.370 --> 00:07:39.290
USGS Co-chairs to group.
We've been meeting quarterly,

00:07:39.290 --> 00:07:41.760
but we are moving to meeting
every other month

00:07:42.310 --> 00:07:44.140
as we move forward
to develop goals.

00:07:44.900 --> 00:07:47.890
This group really acts
as a hub.

00:07:47.890 --> 00:07:52.480
There are not only the different
agencies that participate in it,

00:07:52.480 --> 00:07:54.950
but there's also programmatic
and technical advisors,

00:07:54.950 --> 00:07:56.380
especially from the USGS.

00:07:56.380 --> 00:07:57.910
These are people
specifically from

00:07:57.910 --> 00:07:59.660
especially
National Geospatial Program

00:07:59.660 --> 00:08:01.660
but also
Water Mission Area,

00:08:01.660 --> 00:08:04.970
who help to advise
since so much of the NHI

00:08:04.970 --> 00:08:08.260
is being developed
at USGS right now.

00:08:09.570 --> 00:08:12.590
We also have at least
one subcommittee.

00:08:12.590 --> 00:08:13.920
It's a subgroup.

00:08:13.920 --> 00:08:18.050
It's what we call a subworking
group on addressing,

00:08:18.050 --> 00:08:21.510
so we'll hear a little bit more
about addressing in a minute,

00:08:21.510 --> 00:08:28.080
and that group is composed
of technical people

00:08:28.080 --> 00:08:30.679
from the agencies that are part
of the larger group,

00:08:31.210 --> 00:08:35.400
and they're focused
right now on looking at ...

00:08:36.050 --> 00:08:37.450
I don't want to use
the word standards,

00:08:37.450 --> 00:08:40.010
but standard ways
of doing things and models

00:08:40.010 --> 00:08:43.000
so that we're all doing
addressing in similar ways.

00:08:43.000 --> 00:08:46.610
We're all figuring out
how to attach the information

00:08:46.610 --> 00:08:48.290
to the hydrographic framework

00:08:49.080 --> 00:08:51.530
using similar methodologies
that are,

00:08:52.070 --> 00:08:54.140
in particular,
interoperable.

00:08:55.360 --> 00:08:58.010
We also coordinate out
with other governance groups.

00:08:59.090 --> 00:09:03.200
SSWD right now isn't meeting,
but we also meet with ...

00:09:03.760 --> 00:09:07.060
we would coordinate
with the 3DEP Working Group

00:09:07.060 --> 00:09:12.810
and the FGDC National Geospatial
Data Asset groups,

00:09:14.570 --> 00:09:20.160
so right now, as I mentioned,
we're really looking at goals,

00:09:20.160 --> 00:09:24.780
and I think the next
pieces of work

00:09:24.780 --> 00:09:29.430
we'll focus on
are the next steps in NHDPlus

00:09:29.430 --> 00:09:34.990
High Resolution production,
the structure for that as well

00:09:34.990 --> 00:09:37.720
as elevation-derived
hydrography,

00:09:37.720 --> 00:09:41.240
how to get the streamlines
from the elevation data

00:09:41.240 --> 00:09:45.410
and move that into the NHD
to get a more robust network

00:09:45.410 --> 00:09:48.100
that's better aligned
with elevation data

00:09:48.100 --> 00:09:51.320
as well as moving
forward further

00:09:51.320 --> 00:09:53.370
with hydrographic addressing,

00:09:53.370 --> 00:09:55.060
so, Al,
I'll hand it back to you.

00:09:56.910 --> 00:09:58.510
Al ReaAll right. Great.
Thanks, Becci.

00:10:00.100 --> 00:10:04.050
So this is hopefully a review
for most folks on this call,

00:10:04.050 --> 00:10:09.530
but you all know that
we have linear referencing.

00:10:09.530 --> 00:10:13.990
Hopefully, you know we have
a linear referencing system

00:10:13.990 --> 00:10:17.260
built on top of the NHD
of reach codes

00:10:17.260 --> 00:10:19.230
and measures along
those reaches,

00:10:19.230 --> 00:10:23.880
starting at zero at the bottom,
the downstream end of the reach,

00:10:23.880 --> 00:10:27.230
going up to 100
at the top of the reach.

00:10:28.700 --> 00:10:29.950
These really are ...

00:10:29.950 --> 00:10:34.320
You can think of these as
analogous to a street address,

00:10:34.320 --> 00:10:37.400
so if you have
your street address

00:10:37.400 --> 00:10:40.800
on a map of
showing the streets,

00:10:42.630 --> 00:10:44.820
then we also have the watershed
boundaries data set,

00:10:44.820 --> 00:10:47.960
which sort of provides
more of a larger ...

00:10:48.850 --> 00:10:52.930
They're really used as reporting
units for the most part,

00:10:54.170 --> 00:10:59.910
and it's a hierarchical
structure of nested data

00:10:59.910 --> 00:11:01.160
sets, polygons,

00:11:01.160 --> 00:11:03.709
and you can think of those,
really, like zip codes.

00:11:05.230 --> 00:11:07.130
The analogy breaks
down a little bit

00:11:07.130 --> 00:11:13.060
if you get into the super
detailed analysis of it,

00:11:13.060 --> 00:11:15.380
but it's a good way
just sort of in general

00:11:15.380 --> 00:11:16.580
to think of these things,

00:11:16.580 --> 00:11:18.920
especially if you're trying
to talk to people

00:11:18.920 --> 00:11:21.570
who aren't already familiar
with these data sets,

00:11:23.270 --> 00:11:27.490
so that's one way
to think about it,

00:11:28.780 --> 00:11:31.450
so a little bit more about
the linear referencing,

00:11:31.450 --> 00:11:34.190
so we'll have something
that we want to reference

00:11:34.190 --> 00:11:37.580
to or address to the data set,

00:11:37.580 --> 00:11:40.460
to the NHD, so we've got,
for example,

00:11:40.460 --> 00:11:42.580
we have this streamgage
that sits right here,

00:11:42.580 --> 00:11:44.629
and it's maybe
on the bank of the stream,

00:11:46.350 --> 00:11:51.220
and it doesn't sit
exactly on the network,

00:11:51.830 --> 00:11:53.810
so the first thing we have to do
is sort of snap

00:11:53.810 --> 00:12:00.090
that over onto the flow-line
network of the NHD.

00:12:01.620 --> 00:12:03.770
This process can actually be ...

00:12:03.770 --> 00:12:07.420
The snapping distance
can actually be quite a bit,

00:12:07.420 --> 00:12:11.350
quite long, if, for example,
you have a wide river,

00:12:15.470 --> 00:12:19.170
but the important thing is,
we want to know where this gage

00:12:19.170 --> 00:12:21.380
sits functionally
on the network,

00:12:21.380 --> 00:12:23.380
so what's it measuring,

00:12:23.380 --> 00:12:27.840
and how does that relate
to the stream network itself?

00:12:28.800 --> 00:12:30.370
So then we're ...
In essence,

00:12:30.370 --> 00:12:34.090
we're converting from
latitude-longitude coordinates

00:12:34.090 --> 00:12:39.670
to a reach-code measure pair
of coordinates on the network,

00:12:42.970 --> 00:12:45.390
so that gives us
sort of locational

00:12:45.390 --> 00:12:48.780
or geospatial context
to the data.

00:12:48.780 --> 00:12:53.130
So if you have this data
here from the gauge,

00:12:53.130 --> 00:12:56.290
and you're wondering,
"What's going on here?

00:12:56.290 --> 00:12:59.030
Why does the data
look the way it does?"

00:12:59.030 --> 00:13:01.790
Well, a big part of that
is probably because

00:13:01.790 --> 00:13:06.680
we're sitting just downstream
of a large reservoir, right?

00:13:06.680 --> 00:13:12.570
So it's a regulated flow here,
so all of that information about

00:13:12.570 --> 00:13:18.460
where you sit on the network
really enriches the information,

00:13:18.460 --> 00:13:23.260
the data that you may collect at
that place because now you know,

00:13:23.260 --> 00:13:26.050
"Okay, I'm downstream
of this large reservoir.

00:13:26.050 --> 00:13:29.320
Maybe there are withdrawals
coming from the reservoir.

00:13:29.320 --> 00:13:31.219
There's regulated flow,"
and so forth,

00:13:34.150 --> 00:13:37.930
so really kind of underlying
all of this

00:13:37.930 --> 00:13:41.780
is the ability to do navigation
on the stream network,

00:13:42.950 --> 00:13:50.790
and traditionally, we've enabled
this function in the GIS desktop

00:13:50.790 --> 00:13:53.790
using the geometric network,
ESRI geometric network,

00:13:55.290 --> 00:13:59.720
and I'll do just a quick
little sidebar here.

00:13:59.720 --> 00:14:01.290
I don't want to spend
a lot of time on it,

00:14:01.290 --> 00:14:06.350
but the geometric network
does not work in ArcGIS Pro.

00:14:06.870 --> 00:14:10.110
However, there is
a new data structure

00:14:10.110 --> 00:14:11.330
that ESRI has developed

00:14:11.330 --> 00:14:13.280
that they're calling
the trace network,

00:14:14.210 --> 00:14:17.250
which provides all the same
kind of functionality

00:14:17.250 --> 00:14:20.230
that we have with
the geometric network,

00:14:20.740 --> 00:14:23.840
and that is out
in beta right now.

00:14:23.840 --> 00:14:29.090
We have tested it, and it will
be released in the summer

00:14:30.290 --> 00:14:35.740
when ESRI releases
the 2.6 version of ArcGIS Pro,

00:14:36.370 --> 00:14:38.310
so we've done
some testing on that,

00:14:38.310 --> 00:14:42.340
and it all seems to be working
really well,

00:14:42.340 --> 00:14:45.930
and it works very much like
a geometric network

00:14:45.930 --> 00:14:50.790
does in ArcMap,
but the thing about that

00:14:50.790 --> 00:14:54.500
is it's relying
on a proprietary data structure.

00:14:55.470 --> 00:15:00.000
It requires that you have
GIS desktop software

00:15:00.000 --> 00:15:02.190
basically in order
to to use it directly,

00:15:02.700 --> 00:15:06.990
so what are some other ways that
we can do network navigation?

00:15:08.400 --> 00:15:12.980
And we've developed this set
of attributes called valued

00:15:12.980 --> 00:15:17.620
added attributes, or VAAs,
that are part of the NHDPlus.

00:15:17.620 --> 00:15:20.360
They're part of NHDPlus
Medium Resolution

00:15:20.360 --> 00:15:22.410
that's been around
for a long time

00:15:22.410 --> 00:15:25.050
and are also part of the NHDPlus
High Resolution,

00:15:25.990 --> 00:15:29.840
and this set of attributes
here over on the right

00:15:29.840 --> 00:15:33.390
are all involved in one way
or another in network

00:15:33.390 --> 00:15:36.420
navigation tasks
of one type or another.

00:15:38.490 --> 00:15:40.770
The nice thing about being able
to do navigation

00:15:40.770 --> 00:15:41.990
using attributes

00:15:41.990 --> 00:15:45.910
is that it basically boils down
to a database query,

00:15:46.740 --> 00:15:48.340
something that's very easy to do

00:15:48.340 --> 00:15:51.020
over
a web-service kind of thing,

00:15:51.020 --> 00:15:58.790
and it's not reliant
on proprietary data structures,

00:15:58.790 --> 00:16:03.380
so that's a big advantage
of being able to do network

00:16:03.380 --> 00:16:08.270
navigation with the VAAs.
Here are some resources,

00:16:08.270 --> 00:16:10.640
and I'll make
this PowerPoint available

00:16:11.390 --> 00:16:16.620
afterwards with these links.
We have a web page on VAAs

00:16:16.620 --> 00:16:19.090
that explains them
much more completely.

00:16:20.170 --> 00:16:23.730
Our user guide, if you haven't
seen it yet for the NHDPlus

00:16:23.730 --> 00:16:27.350
High Res, we published that
just a couple of months ago,

00:16:27.350 --> 00:16:30.820
actually sort of
over the holidays.

00:16:32.540 --> 00:16:34.439
In that time frame,
we published that.

00:16:35.220 --> 00:16:38.890
It's got a lot of information
in there about VAAs

00:16:38.890 --> 00:16:43.850
and how to do certain tasks like
network navigation and so forth.

00:16:44.400 --> 00:16:49.230
We also have a kind of tutorial

00:16:49.840 --> 00:16:53.010
and a workshop
that we put together.

00:16:53.010 --> 00:16:55.880
We have that out on GitHub,

00:16:56.600 --> 00:17:02.090
so it's got a network navigator,
a VAA network navigator.

00:17:02.090 --> 00:17:04.650
It currently runs
just for ArcMap.

00:17:05.320 --> 00:17:08.210
It's an executable
that you can download.

00:17:08.210 --> 00:17:11.690
It does upstream main stem,
upstream with tributaries,

00:17:11.690 --> 00:17:15.600
downstream main stem
and downstream with divergences.

00:17:16.230 --> 00:17:19.040
It does all those four types
of navigations.

00:17:19.040 --> 00:17:22.170
We also have source code
in that GitHub repository.

00:17:23.180 --> 00:17:26.010
There's a toolbox
with an ArcPy module

00:17:26.840 --> 00:17:29.960
that does upstream
with tributaries,

00:17:29.960 --> 00:17:32.620
I think, for ArcGIS Pro,

00:17:33.240 --> 00:17:36.230
so we don't have a complete
set of tools yet for Pro,

00:17:37.120 --> 00:17:39.680
but we do have some
of the tools here,

00:17:42.280 --> 00:17:44.350
and then there's more
information on our web page,

00:17:44.350 --> 00:17:48.730
of course,
so I wanted to also show ...

00:17:48.730 --> 00:17:52.430
This is a prototype that is
actually a functioning prototype

00:17:53.040 --> 00:17:55.510
of the web-based services

00:17:55.510 --> 00:17:59.610
that we are trying to enable
for the NHI.

00:17:59.610 --> 00:18:02.830
This is all based on
NHDPlus Version 2,

00:18:04.340 --> 00:18:06.080
and this is live right now.

00:18:06.080 --> 00:18:09.360
You can use the URL
that you see up there at the top

00:18:09.360 --> 00:18:14.570
and then add to it navigate
upstream main stem, UM,

00:18:15.450 --> 00:18:19.670
and you'll get returned
the feature that are upstream

00:18:19.670 --> 00:18:22.850
of that point that
was specified here in the URL,

00:18:22.850 --> 00:18:26.760
which is a HUC12 pour point,
the outlet of a HUC12,

00:18:28.290 --> 00:18:31.290
and this is the HUC12
that we're looking at,

00:18:31.290 --> 00:18:32.890
which is in Central Florida.

00:18:33.890 --> 00:18:36.690
You can do a navigate upstream
with tributaries,

00:18:36.690 --> 00:18:39.690
and you get all of
the flow lines upstream of it.

00:18:41.510 --> 00:18:45.530
You can also do a downstream
with divergences.

00:18:46.280 --> 00:18:47.510
Here is that zoomed in.

00:18:47.510 --> 00:18:49.620
You can also do downstream
main stem.

00:18:50.380 --> 00:18:54.660
All of these things work.
Basically, you can ...

00:18:56.080 --> 00:19:00.810
They're restful.
It's a restful API.

00:19:00.810 --> 00:19:05.640
You can go to these services
and execute

00:19:05.640 --> 00:19:09.000
these things directly
if you want to.

00:19:09.000 --> 00:19:12.700
Again, this is based on that
NHDPlus Version 2.

00:19:12.700 --> 00:19:14.300
We hope to build this out

00:19:14.300 --> 00:19:17.720
based on NHDPlus High Res
in the near future,

00:19:21.820 --> 00:19:25.730
but the real power of this

00:19:25.730 --> 00:19:29.690
is not just being able
to see the hydro network,

00:19:31.760 --> 00:19:34.950
navigation on the hydro network.
It's actually finding things

00:19:34.950 --> 00:19:36.840
that have been
tied to that network,

00:19:37.710 --> 00:19:41.420
linked to it or addressed to it,
so here,

00:19:41.420 --> 00:19:46.530
we have an example where we do
an upstream with tributaries

00:19:46.530 --> 00:19:49.900
from that same place
that I showed earlier,

00:19:49.900 --> 00:19:51.580
and we looked for
the NWIS sites,

00:19:51.580 --> 00:19:54.070
so the USGS NWIS database,

00:19:56.090 --> 00:19:59.750
so not all of the NWIS sites
are indexed

00:19:59.750 --> 00:20:03.720
or in this data set yet,
in this catalog,

00:20:04.330 --> 00:20:07.420
but most of the gages are,

00:20:08.480 --> 00:20:12.270
and then here we have sites
with water quality,

00:20:12.270 --> 00:20:14.890
so there is something called
the Water Quality Portal

00:20:14.890 --> 00:20:16.490
that this is embedded in.

00:20:17.130 --> 00:20:21.830
The Water Quality Portal
basically aggregates data

00:20:21.830 --> 00:20:24.470
from about
400 different databases,

00:20:24.470 --> 00:20:28.140
including USGS' NWIS database,

00:20:28.140 --> 00:20:33.230
EPA's STORET database
and a whole bunch of databases

00:20:33.230 --> 00:20:38.250
from other agencies and State
and local agencies as well,

00:20:38.840 --> 00:20:42.510
so this is already working
in the Water Quality Portal,

00:20:43.100 --> 00:20:44.900
and just to give you an example

00:20:44.900 --> 00:20:47.660
of how this can
really empower things,

00:20:48.350 --> 00:20:52.070
we had an example
back in August of 2015

00:20:53.040 --> 00:20:55.920
where there was a spill called
the Gold King Mine spill.

00:20:55.920 --> 00:20:58.800
It spilled mine waste
into the Animas River,

00:20:59.330 --> 00:21:01.010
and what you're seeing here

00:21:01.010 --> 00:21:06.000
is a model that was used
to estimate travel time

00:21:06.000 --> 00:21:07.650
of the plume going downstream.

00:21:08.430 --> 00:21:11.030
Each of the different
color segments are 1 day,

00:21:12.230 --> 00:21:15.080
going downstream
on the Animas River,

00:21:17.160 --> 00:21:20.200
so we had a request from EPA

00:21:20.200 --> 00:21:24.580
to get all of the historical
water-quality data downstream

00:21:24.580 --> 00:21:26.100
of that spill.

00:21:26.100 --> 00:21:28.480
Well, our databases
were not set up for that,

00:21:29.370 --> 00:21:31.100
and it took us
a couple of weeks

00:21:31.100 --> 00:21:35.670
and several conference calls
for a team

00:21:35.670 --> 00:21:40.710
to actually compile
all of that data.

00:21:40.710 --> 00:21:44.980
You can do that same query now
using the Water Quality Portal

00:21:44.980 --> 00:21:47.770
and this sort of thing
in a couple of minutes.

00:21:48.490 --> 00:21:50.290
Actually, if you were
to click on this,

00:21:50.290 --> 00:21:53.090
it would go actually way
less than 2 minutes,

00:21:54.710 --> 00:21:59.240
so that's the power of having
this sort of infrastructure.

00:21:59.240 --> 00:22:01.570
This really is an implementation

00:22:02.080 --> 00:22:04.070
of the National Hydrography
Infrastructure,

00:22:04.070 --> 00:22:12.140
so it's the stuff here over
in the corner of the catalog,

00:22:12.140 --> 00:22:15.640
the addressing
search-and-discover data sets,

00:22:16.320 --> 00:22:17.900
search-and-discovery engine,

00:22:17.900 --> 00:22:22.630
so the next couple of segments
of this are going to focus

00:22:22.630 --> 00:22:27.610
on the addressing,
hydrographic addressing,

00:22:27.610 --> 00:22:30.700
and focus on tools
that we have available

00:22:30.700 --> 00:22:33.060
now or in the near future

00:22:33.920 --> 00:22:37.740
for you to use
to address data to the NHD,

00:22:39.090 --> 00:22:43.070
and with that, I'm going to turn
it over to Daniel Wieferich.

00:22:43.760 --> 00:22:46.080
Daniel, can you kind of
introduce yourself

00:22:46.080 --> 00:22:48.110
and talk about
the HydroLink tool?

00:22:49.120 --> 00:22:51.030
Daniel WieferichCan you
hear me all right?

00:22:51.030 --> 00:22:52.330
Al ReaYes.

00:22:52.330 --> 00:22:53.830
Daniel WieferichOkay.

00:22:53.830 --> 00:22:56.380
As Al mentioned,
I'm Daniel Wieferich.

00:22:56.380 --> 00:22:58.640
I'm with the Science Analytics

00:22:58.640 --> 00:23:01.100
and Synthesis program
within USGS,

00:23:01.100 --> 00:23:06.930
and I've been collaborating
with NGP and NGTOC.

00:23:07.960 --> 00:23:13.060
I'm on the NHI
and linear referencing concepts

00:23:13.630 --> 00:23:15.230
over the last few years.

00:23:15.830 --> 00:23:19.580
Today, I'll be talking
about the HydroLink tool

00:23:19.580 --> 00:23:22.220
that my program developed
with support

00:23:22.220 --> 00:23:28.620
of the USGS Fisheries program,
and I'd like to note right away

00:23:28.620 --> 00:23:30.630
that throughout
the presentation,

00:23:30.630 --> 00:23:33.800
I'll be providing
some direct URLs,

00:23:34.490 --> 00:23:38.540
but the URL on this
initial slide here

00:23:39.500 --> 00:23:43.050
will actually get you
to all the other URLs

00:23:43.050 --> 00:23:45.260
and everything that
I'm talking about,

00:23:46.320 --> 00:23:49.800
actually sharing that
in the chat right now as well.

00:23:50.990 --> 00:23:52.590
Next slide.

00:23:56.630 --> 00:23:59.570
So one of the main drivers
of the HydroLink tool

00:23:59.570 --> 00:24:02.500
was to help encourage
USGS scientists

00:24:02.500 --> 00:24:05.160
and our partners
to linear reference

00:24:05.160 --> 00:24:10.250
and/or address their data
to two commonly used versions

00:24:10.250 --> 00:24:12.050
of the National Hydrography data

00:24:12.050 --> 00:24:16.420
set and then to share that
information as a common resource

00:24:16.420 --> 00:24:20.190
to start building up
our collective knowledge

00:24:20.190 --> 00:24:21.790
of the stream networks.

00:24:22.840 --> 00:24:25.730
I won't go into
a lot of details here,

00:24:26.890 --> 00:24:32.760
but on this slide, we have some
of the specific national efforts

00:24:33.340 --> 00:24:36.560
from my work
that contribute to this concept

00:24:36.560 --> 00:24:39.500
and also illustrate the power

00:24:39.500 --> 00:24:42.460
of having many habitat
and fisheries data

00:24:42.460 --> 00:24:45.700
sets addressed
to the same stream network,

00:24:46.680 --> 00:24:50.600
allowing us to better
model species distributions

00:24:50.600 --> 00:24:54.510
and habitat conditions
at large spatial scales or,

00:24:54.510 --> 00:24:56.830
in my case,
at the national scale.

00:24:58.340 --> 00:24:59.940
Next slide.

00:25:06.970 --> 00:25:10.700
So to build off my last slide,
the HydroLink tool

00:25:10.700 --> 00:25:14.750
was built to support researchers
in the verification

00:25:14.750 --> 00:25:19.140
and point data location
and to support them in linear

00:25:19.840 --> 00:25:24.370
referencing for addressing
of those points

00:25:24.370 --> 00:25:28.500
to the NHDPlus
Version 2 Medium Resolution

00:25:28.500 --> 00:25:32.150
and the High-Resolution NHD
as well,

00:25:33.080 --> 00:25:37.580
which are, in my field of work,
two very commonly

00:25:37.580 --> 00:25:40.170
used hydrography
networks at this point.

00:25:41.270 --> 00:25:45.500
Although this was supported
by the fisheries effort,

00:25:45.500 --> 00:25:48.530
it can be leveraged
for any sample-site data

00:25:48.530 --> 00:25:53.130
or spatial-feature
locations related to streams

00:25:54.050 --> 00:25:58.350
and is available to most
ArcGIS Online account holders.

00:26:00.190 --> 00:26:04.320
The tool was built to require
a point-by-point editing,

00:26:05.360 --> 00:26:07.480
and this was
to encourage scientists

00:26:07.480 --> 00:26:11.990
to evaluate site locations
and the NHD quality,

00:26:12.810 --> 00:26:16.200
and on the NHD-quality
end of things,

00:26:17.970 --> 00:26:22.890
our scientists across the agency
are out in the field.

00:26:24.420 --> 00:26:28.150
They've got a pretty
good understanding

00:26:28.150 --> 00:26:29.780
of the hydrography,

00:26:29.780 --> 00:26:33.740
and we're hoping that with
a little bit of encouragement

00:26:33.740 --> 00:26:37.440
that we could bring
that knowledge back to the NHD

00:26:37.440 --> 00:26:42.350
through the markup tool
or by having folks go through

00:26:42.350 --> 00:26:47.850
and look at one point at a time
as an address that brings up ...

00:26:48.810 --> 00:26:55.230
It shows potential
different issues with NHD

00:26:55.230 --> 00:26:57.710
that can be updated
through time,

00:26:57.710 --> 00:27:00.820
and then we're improving
on the network

00:27:00.820 --> 00:27:05.860
and the quality
or the capability

00:27:05.860 --> 00:27:08.310
of using this information
through time.

00:27:08.310 --> 00:27:09.910
Next slide.

00:27:12.660 --> 00:27:16.910
The HydroLink tool allows users
to upload point data

00:27:16.910 --> 00:27:20.320
from a shapefile,
CSV or Excel spreadsheet,

00:27:21.340 --> 00:27:28.000
so this is to help remove
a heavy lift

00:27:28.610 --> 00:27:30.240
for those scientists

00:27:30.240 --> 00:27:32.840
that don't really have
that geospatial background.

00:27:33.850 --> 00:27:36.330
The tool then converts
this information

00:27:36.330 --> 00:27:39.120
into an ArcGIS
Online feature service,

00:27:39.880 --> 00:27:44.860
which does all of the
back-end data management

00:27:44.860 --> 00:27:48.810
throughout editing,
and during this step,

00:27:48.810 --> 00:27:52.440
the tool adds eight fields
that are shown here.

00:27:53.800 --> 00:27:57.520
The eight fields capture three
different groups of information.

00:27:58.050 --> 00:28:01.030
On the left,
you can see the fields

00:28:01.030 --> 00:28:04.770
that show the verified
location of the point.

00:28:06.520 --> 00:28:12.390
Then you have a few fields that
represent the hi-res address

00:28:12.390 --> 00:28:17.210
and then a few fields
for the NHDPlus

00:28:17.210 --> 00:28:18.810
Medium Resolution as well.

00:28:19.790 --> 00:28:22.450
When a user is done
with the tool,

00:28:22.450 --> 00:28:25.390
they can then export
to a shapefile,

00:28:26.310 --> 00:28:30.050
but, really, that data
exists in ArcGIS Online,

00:28:30.050 --> 00:28:33.500
so if you're savvy
in using that,

00:28:33.500 --> 00:28:36.810
you can then export the data
into a variety of formats

00:28:36.810 --> 00:28:39.530
or keep it right there
in the feature service

00:28:40.330 --> 00:28:43.790
and hopefully share out
to the NHI

00:28:43.790 --> 00:28:47.700
concept that Al mentioned
previously. Next slide.

00:28:52.520 --> 00:28:54.850
So I'll be going through
a few quick slides

00:28:55.370 --> 00:28:58.920
just to show a few basics
of the tool,

00:28:58.920 --> 00:29:03.090
but I highly recommend using
our 6-minute training video

00:29:04.280 --> 00:29:08.170
to get all the details
needed to get up

00:29:08.170 --> 00:29:10.530
and running
with the HydroLink tool.

00:29:10.530 --> 00:29:17.960
Next slide.
Here is a general screenshot

00:29:17.960 --> 00:29:20.560
of what the tool looks like
in editing mode.

00:29:21.170 --> 00:29:25.160
This can be accessed
right after upload of your data.

00:29:26.200 --> 00:29:31.190
Notice the fields that I just
mentioned are populated

00:29:31.730 --> 00:29:34.290
and showing as a default,

00:29:34.980 --> 00:29:40.490
but you can also add in and
display fields from your data

00:29:40.490 --> 00:29:44.120
as well to help you navigate
your different sites.

00:29:44.820 --> 00:29:46.420
Next slide.

00:29:48.330 --> 00:29:50.500
As mentioned,
the tool allows the user

00:29:50.500 --> 00:29:54.330
to verify the location
of the point and edit

00:29:54.330 --> 00:29:55.780
that if necessary.

00:29:55.780 --> 00:29:59.280
Here on the left,
it shows a screenshot of data

00:29:59.280 --> 00:30:01.450
as it is uploaded by a user.

00:30:02.470 --> 00:30:04.910
You can see the point
is off the stream,

00:30:05.600 --> 00:30:11.890
either bad GPS coordinates or
the example I like to mention.

00:30:11.890 --> 00:30:14.300
I remember when I was
doing field work,

00:30:16.240 --> 00:30:18.470
maybe you forget
to take that point

00:30:18.470 --> 00:30:23.160
while you're in the stream,
but you take it back at a place

00:30:23.160 --> 00:30:27.310
where you're recording
information or back

00:30:27.310 --> 00:30:29.090
at the vehicle location,

00:30:29.090 --> 00:30:32.740
so this gives users
an opportunity

00:30:33.560 --> 00:30:35.810
to correct the accuracy
of that point,

00:30:37.530 --> 00:30:39.530
and on the right-hand side here,

00:30:39.530 --> 00:30:43.470
you can see just with a general
drag-and-drop method

00:30:44.090 --> 00:30:47.830
the user can move that point
and then get some immediate back

00:30:48.920 --> 00:30:51.930
to ensure that point is
in the proper location.

00:30:52.620 --> 00:30:54.220
Next slide.

00:30:57.560 --> 00:31:00.760
And then the addressing
component of the tool

00:31:02.090 --> 00:31:04.640
allows the user
to get visual feedback

00:31:04.640 --> 00:31:07.360
to help evaluate
a linear reference,

00:31:08.100 --> 00:31:11.440
so the tool works
by allowing the user

00:31:12.070 --> 00:31:16.120
to click on the NHD networks.

00:31:16.120 --> 00:31:19.100
Both of them would be
showing as default,

00:31:20.020 --> 00:31:22.260
but the user can click
on the network,

00:31:22.260 --> 00:31:26.870
and he'll drop a little square,
as you can see in that image,

00:31:28.230 --> 00:31:32.530
to let them know where that
point is being referenced.

00:31:33.070 --> 00:31:36.640
You can also do both
of these simultaneously,

00:31:36.640 --> 00:31:37.910
so you drop one point,

00:31:37.910 --> 00:31:46.810
and it'll try to get the address
for both of the NHD networks,

00:31:47.720 --> 00:31:51.060
but you also have the option
to unselect one of the layers

00:31:51.060 --> 00:31:54.420
and just work one NHD layer
at the time.

00:31:55.100 --> 00:31:58.260
This is helpful
when you have two versions

00:31:58.260 --> 00:32:01.470
or when the two different
versions of the NHD

00:32:01.470 --> 00:32:03.420
have some high variability,

00:32:03.420 --> 00:32:08.680
or maybe one of the versions
has a flow line

00:32:09.310 --> 00:32:11.620
where the other does not.
Next slide.

00:32:15.610 --> 00:32:17.650
Alongside the web application,

00:32:18.330 --> 00:32:21.080
I've been developing
a Python package to assist

00:32:21.080 --> 00:32:26.710
in addressing large sets of data
to both versions of the NHD.

00:32:27.670 --> 00:32:29.890
This code is being developed
in GitHub,

00:32:29.890 --> 00:32:35.800
and I encourage those that
do you use Python to help test

00:32:35.800 --> 00:32:41.130
and/or develop these efforts.
It's in an open space right now,

00:32:41.770 --> 00:32:45.530
and we also use fully
open-source methods,

00:32:46.690 --> 00:32:51.980
so there's no need for an
ESRI license to use this code,

00:32:52.850 --> 00:32:55.100
currently working
on some updates

00:32:55.100 --> 00:33:00.290
to help make the code easier
to use and to expand methods

00:33:00.290 --> 00:33:05.130
and get better documentation
and things like that instated,

00:33:05.700 --> 00:33:08.530
so if you do jump on there,

00:33:09.170 --> 00:33:13.300
expect to see some changes
pushed into that repo soon,

00:33:14.600 --> 00:33:19.020
and the code also returns data
to the users

00:33:20.330 --> 00:33:25.170
to identify how certain we are
of a point being addressed

00:33:25.170 --> 00:33:30.920
to the right reach
just based on stream name,

00:33:32.750 --> 00:33:36.690
snapping distance
and some efforts we're looking

00:33:36.690 --> 00:33:40.700
into using distances
that confluences too.

00:33:42.320 --> 00:33:43.920
Next slide.

00:33:46.960 --> 00:33:49.540
So at this point,
I just wanted to remind everyone

00:33:49.540 --> 00:33:57.180
that everything HydroLink
can be found at this URL here,

00:33:57.760 --> 00:33:59.620
so the link to the tool itself,

00:34:00.780 --> 00:34:05.340
the Python code and much more
can be found at that URL.

00:34:05.880 --> 00:34:10.490
In addition in this space,
when you go to that URL,

00:34:10.490 --> 00:34:14.610
it encourages users of the tool
to share their information

00:34:14.610 --> 00:34:17.420
to help it
become more accessible

00:34:17.420 --> 00:34:22.410
and to help build
on some of these NHI concepts

00:34:22.410 --> 00:34:24.010
that Al had mentioned.

00:34:25.890 --> 00:34:28.170
With that, I'll wrap up
by noting

00:34:28.170 --> 00:34:29.650
that we've been working closely

00:34:29.650 --> 00:34:35.230
with the National
Geospatial Program and NGTOC

00:34:35.230 --> 00:34:38.410
as well throughout
the development of this tool.

00:34:39.500 --> 00:34:41.030
With those conversations,

00:34:41.030 --> 00:34:45.180
we are starting
a longer-term strategy with them

00:34:45.180 --> 00:34:51.010
to eventually transition
our users to the HydroAdd tool,

00:34:51.010 --> 00:34:53.670
which Mike Tinker
will be talking about next.

00:34:54.520 --> 00:34:57.330
This will allow us
to collaborate

00:34:57.330 --> 00:34:58.860
and support a common,

00:34:58.860 --> 00:35:01.160
more powerful tool
moving forward.

00:35:02.020 --> 00:35:04.770
With that being said, those
conversations just started,

00:35:06.470 --> 00:35:13.020
and what we'll do is probably
note that at this URL here

00:35:13.020 --> 00:35:17.230
as we know more kind of what
that transition might look like,

00:35:17.230 --> 00:35:19.650
so it's still a ways out,

00:35:20.680 --> 00:35:24.120
but just wanted to make sure
that folks were aware of that,

00:35:24.120 --> 00:35:28.340
and with that, I'll go ahead
and pass things off to Mike.

00:35:36.180 --> 00:35:38.400
Al ReaOkay, Mike,
are you unmuted?

00:35:38.400 --> 00:35:39.660
I'm not hearing you.

00:35:39.660 --> 00:35:41.420
Mike TinkerYes, can you hear me?

00:35:41.420 --> 00:35:43.130
Al ReaYes, we can hear you.
Great.

00:35:43.130 --> 00:35:45.470
Mike TinkerVery good.
Hello, everybody.

00:35:46.240 --> 00:35:48.900
I'm going to talk about
the HydroAdd tool today,

00:35:49.630 --> 00:35:51.279
the hydrographic
addressing tool.

00:35:53.110 --> 00:35:55.660
I'll show you
a little bit about

00:35:57.300 --> 00:35:58.650
some of the thinking
that went into it,

00:35:58.650 --> 00:36:00.890
and then I'll show you
some screenshots

00:36:00.890 --> 00:36:03.770
to explain
how it works so far.

00:36:07.100 --> 00:36:08.700
Next slide, please.

00:36:10.300 --> 00:36:11.980
So the overview
of the HydroAdd tool

00:36:11.980 --> 00:36:13.810
is that this is a tool
that allows users

00:36:13.810 --> 00:36:16.240
to address
their NHD High Res

00:36:17.160 --> 00:36:19.720
or maintain their existing
HydroAdd data,

00:36:20.710 --> 00:36:22.380
what we know and love
as events.

00:36:23.840 --> 00:36:26.440
The user,
as Al mentioned earlier,

00:36:27.550 --> 00:36:28.930
and also with
the HydroLink tool,

00:36:28.930 --> 00:36:30.729
you have to make
your data available

00:36:31.350 --> 00:36:33.650
as a web feature layer
from ArcGIS Online

00:36:34.650 --> 00:36:36.250
in the HydroAdd schema.

00:36:37.680 --> 00:36:40.310
Once you've got your data
up there in the right schema,

00:36:40.310 --> 00:36:43.640
then the HydroAdd tool
allows editing of that layer.

00:36:44.850 --> 00:36:48.580
The user interacts with their
data via an editing queue,

00:36:49.710 --> 00:36:54.620
and the editing queue
drives the user

00:36:54.620 --> 00:36:57.690
to what are unapproved items.

00:37:00.440 --> 00:37:03.970
Queues, an editing queue is
associated with a service layer,

00:37:05.470 --> 00:37:08.640
and one of the important
selling points of this tool

00:37:08.640 --> 00:37:11.960
is that multiple queues
can be associated

00:37:11.960 --> 00:37:13.430
with any one service layer,

00:37:13.430 --> 00:37:16.580
and multiple people can work on
a service layer simultaneously.

00:37:17.570 --> 00:37:19.270
Editing permissions
for those service layers

00:37:19.270 --> 00:37:21.480
are set in ArcGIS Online,

00:37:23.120 --> 00:37:26.810
so the user can search
their service layer

00:37:27.500 --> 00:37:29.420
and select things
to add to the queue,

00:37:30.070 --> 00:37:34.270
an editing queue,
or they can direct,

00:37:34.970 --> 00:37:39.400
select and map just by drawing
a box and selecting features,

00:37:40.780 --> 00:37:44.140
or they can select
by hydrologic unit code.

00:37:44.710 --> 00:37:50.230
You can even search
for your data by source ID,

00:37:50.970 --> 00:37:54.480
for example a National
Water Information site number,

00:37:54.480 --> 00:37:57.100
an NWIS site number
or a streamgage site number.

00:37:59.710 --> 00:38:01.800
Using the interface, you can
also search for a reach code

00:38:01.800 --> 00:38:04.690
or for a WBD hydrologic unit.

00:38:08.060 --> 00:38:10.980
QC of a queue
or an entire service layer

00:38:10.980 --> 00:38:13.680
is something that is
also planned for this tool.

00:38:14.780 --> 00:38:16.380
Next slide, please.

00:38:18.900 --> 00:38:23.070
So the top use cases
there are on top.

00:38:23.070 --> 00:38:25.800
First, users who have events

00:38:26.420 --> 00:38:30.280
that are already
linked to NHDPlus V2

00:38:32.370 --> 00:38:35.290
or to the High Res already
have existing reach codes,

00:38:35.290 --> 00:38:37.550
so especially
if you've got stuff

00:38:37.550 --> 00:38:40.790
that's been indexed
to NHDPlus V2

00:38:40.790 --> 00:38:43.230
and you want to migrate
those to the High Res,

00:38:43.230 --> 00:38:46.520
that's one of the main reasons
this tool is designed.

00:38:47.760 --> 00:38:52.750
Secondly, the national map has
hundreds of thousands of point

00:38:52.750 --> 00:38:55.510
events,
dams, flow alterations,

00:38:55.510 --> 00:38:58.430
streamgages, WBD hydrologic unit

00:38:58.430 --> 00:39:00.700
pour points that
we need to maintain,

00:39:00.700 --> 00:39:04.580
and so that's the other
main driver for this tool,

00:39:07.460 --> 00:39:09.400
but there are other use cases,

00:39:09.400 --> 00:39:11.850
maintaining streamgages
for StreamStats database,

00:39:13.030 --> 00:39:17.710
addressing NWIS streamgages so
that you can attach reach codes

00:39:17.710 --> 00:39:20.059
to your streamgages
or any other NWIS holdings,

00:39:20.760 --> 00:39:24.660
to be able to attach any other
kind of data to the High Res,

00:39:25.290 --> 00:39:27.930
such as fish passage
barriers or waterfalls

00:39:27.930 --> 00:39:29.730
like Daniel was mentioning.

00:39:29.730 --> 00:39:31.850
Culverts will be important
as we move

00:39:31.850 --> 00:39:33.790
towards
elevation-derived hydro,

00:39:35.960 --> 00:39:38.170
so Daniel and I
speak frequently.

00:39:38.170 --> 00:39:39.510
SAS and NGTOC

00:39:39.510 --> 00:39:42.770
will continue to collaborate
on future use cases.

00:39:44.730 --> 00:39:46.330
Next slide, please.

00:39:49.720 --> 00:39:52.630
So here's a general overview
of what's been going on.

00:39:52.630 --> 00:39:56.270
In FY20, we've been building
the editing queue for points,

00:39:56.270 --> 00:39:57.880
which is nearly complete,

00:39:57.880 --> 00:40:03.470
and we'd like to in FY20
be able to QC people's points,

00:40:04.390 --> 00:40:06.470
and this is in progress now.

00:40:06.470 --> 00:40:10.410
In the future, these are
essentially in priority order.

00:40:10.410 --> 00:40:12.330
In the future,
it's important for us

00:40:12.330 --> 00:40:15.440
to be able to address lines
and polygons.

00:40:16.540 --> 00:40:18.470
We'd like to be able
to link the Markup tool

00:40:18.470 --> 00:40:22.800
and the WBD tools
to the HydroAdd tool,

00:40:22.800 --> 00:40:25.470
so for example,
if you're a WBD editor

00:40:25.470 --> 00:40:27.970
and you need to make sure that
your hydrologic unit pour point

00:40:27.970 --> 00:40:29.530
is in the correct place,

00:40:29.530 --> 00:40:32.960
zip on over to the HydroAdd,
fix your WBD pour point,

00:40:32.960 --> 00:40:35.360
and then go back
in the WBD editing,

00:40:35.360 --> 00:40:37.880
or similar,
if you see an issue in NHD

00:40:37.880 --> 00:40:39.730
that you think needs
to be addressed,

00:40:40.790 --> 00:40:42.710
zoom on over to the Markup tool,

00:40:43.500 --> 00:40:45.750
put a markup in
and then go back to HydroAdd.

00:40:47.450 --> 00:40:51.180
Longer term as part of the NHI
that AI was talking about,

00:40:51.180 --> 00:40:53.470
we'd like to be able to make
all of our national map holdings

00:40:53.470 --> 00:40:57.410
available
as read-only service layers

00:40:57.410 --> 00:41:00.259
and in-house as edit layers
so that we can maintain them,

00:41:01.630 --> 00:41:03.130
and the NHDPlus
High Res is coming.

00:41:03.130 --> 00:41:05.830
We want out tool to be able
to address the catchments.

00:41:07.750 --> 00:41:09.140
Ultimately, it'd be nice
to be able

00:41:09.140 --> 00:41:12.830
to actually share your service
layers directly from HydroAdd

00:41:12.830 --> 00:41:15.890
for search and discovery.
Again, the whole idea with NHI

00:41:16.400 --> 00:41:19.690
is for search
and discovery of events,

00:41:19.690 --> 00:41:23.990
and that's what these tools
are all about.

00:41:23.990 --> 00:41:25.590
Next slide, please.

00:41:27.510 --> 00:41:30.530
So I'll give you
some screenshots here

00:41:30.530 --> 00:41:33.260
and sort of tell you
how the tool is coming along.

00:41:33.260 --> 00:41:36.890
On the left-hand side, you see
I've got a service layer,

00:41:36.890 --> 00:41:38.270
a couple service layers
actually,

00:41:38.270 --> 00:41:41.210
shared out on ArcGIS Online.

00:41:41.210 --> 00:41:44.390
You can see the map in the
center image of the points

00:41:44.390 --> 00:41:46.670
as they live in ArcGIS Online,

00:41:46.670 --> 00:41:49.930
and then a lower image
is the HydroAdd tool

00:41:51.750 --> 00:41:55.380
shows the same service layer
as it lives in ArcGIS Online,

00:41:55.380 --> 00:41:57.760
but now it's being consumed
by the HydroAdd tool,

00:41:57.760 --> 00:42:00.170
and it's ready for editing.
Next slide.

00:42:03.540 --> 00:42:06.690
So here I've got the dark-gray
background turned on.

00:42:06.690 --> 00:42:08.880
I've got the contours,
National Map contours,

00:42:08.880 --> 00:42:12.010
turned on, and I'm zoomed
into a particular point here.

00:42:12.010 --> 00:42:14.250
That's the NWIS site number,
the source ID,

00:42:14.990 --> 00:42:16.630
641 is the NWIS site number,

00:42:17.350 --> 00:42:20.520
and so what we're showing here
is the search-and-select,

00:42:20.520 --> 00:42:24.250
so you can search
for in NWIS or any ...

00:42:25.580 --> 00:42:28.480
whatever your unique identifier
is, the source ID,

00:42:29.240 --> 00:42:32.200
and I've just put in 641,
and it zoomed to 641.

00:42:34.030 --> 00:42:35.630
Next slide, please.

00:42:37.460 --> 00:42:40.060
You can also do a direct
selection right in the map

00:42:40.060 --> 00:42:43.730
just by drawing an extent,
and here I've drawn a big box,

00:42:44.250 --> 00:42:46.100
and I've selected
all these features.

00:42:46.100 --> 00:42:48.460
The features are listed
in the left-hand pane

00:42:48.460 --> 00:42:49.970
there that I've selected,

00:42:49.970 --> 00:42:54.560
and you can see the source ID,
4, 13, 14, 74 all the way down.

00:42:54.560 --> 00:42:58.280
You can also see
that these are thumbs-down.

00:42:58.280 --> 00:43:00.130
In other words,
these are unapproved.

00:43:01.520 --> 00:43:06.960
These haven't been examined yet.
Next slide, please.

00:43:10.120 --> 00:43:12.700
So once you've got
a bunch of stuff selected,

00:43:12.700 --> 00:43:14.060
and I have select all here

00:43:14.060 --> 00:43:16.960
because I have a little checkbox
at the top of the list,

00:43:16.960 --> 00:43:18.600
once you've got
a bunch of stuff selected,

00:43:18.600 --> 00:43:20.060
you can create
a new editing queue,

00:43:20.060 --> 00:43:21.330
and that's what's
happening here.

00:43:21.330 --> 00:43:23.580
I'm creating a new queue.
Next slide, please.

00:43:26.040 --> 00:43:28.740
And it asks you to name
your edited queue,

00:43:28.740 --> 00:43:31.010
and it asks you to select
your service layer.

00:43:32.500 --> 00:43:34.100
Next slide.

00:43:36.040 --> 00:43:39.580
And so now I've got
a bunch of dots

00:43:39.580 --> 00:43:41.810
that shows rows per page
right now is 500,

00:43:42.370 --> 00:43:45.360
and so you can see
all the dots that I have.

00:43:45.360 --> 00:43:49.160
There's 340, and they're
all available in this list,

00:43:49.810 --> 00:43:51.380
and I've added them
to this queue,

00:43:51.380 --> 00:43:53.770
which I've called
the Four Corners State Queue,

00:43:55.590 --> 00:43:57.190
and you've got
the label there,

00:43:57.970 --> 00:43:59.620
but this is still
just search and select.

00:43:59.620 --> 00:44:02.220
We just added these too a queue.
The next thing would be

00:44:02.220 --> 00:44:04.320
to actually start
editing this queue,

00:44:04.320 --> 00:44:06.290
and you can see
the queue is listed there.

00:44:06.290 --> 00:44:09.170
Edit queues, Four Corners State.
Next slide, please.

00:44:11.980 --> 00:44:15.170
So if we were now to go to the
editing queue itself and select,

00:44:15.170 --> 00:44:16.850
and you can have
as many queues as you want,

00:44:16.850 --> 00:44:18.100
so you'd have your queue.

00:44:18.100 --> 00:44:20.820
The whole idea here
is to drive the user

00:44:21.380 --> 00:44:23.420
to what is unapproved
in your queue.

00:44:25.240 --> 00:44:29.800
If you mouse over a row in your
queue, you'll get these buttons.

00:44:30.410 --> 00:44:31.750
The buttons light up.

00:44:31.750 --> 00:44:34.550
You've got the edit button
on the left-hand side there.

00:44:34.550 --> 00:44:36.910
You've got the add
or remove to queue button,

00:44:36.910 --> 00:44:38.680
and you've also got
the delete-from-service data.

00:44:38.680 --> 00:44:39.940
That's a rather powerful button.

00:44:39.940 --> 00:44:42.040
You can delete directly
from your service layer,

00:44:42.040 --> 00:44:43.750
and then, of course,
on the far left,

00:44:43.750 --> 00:44:45.640
you've got the approve,
unapprove,

00:44:45.640 --> 00:44:47.240
thumbs-up
or thumbs-down button,

00:44:48.820 --> 00:44:51.360
and so you can click
the row directly to zoom

00:44:51.360 --> 00:44:53.459
to that feature
and examine it in the map,

00:44:54.970 --> 00:44:58.330
or you could hit
the edit button itself to zoom

00:44:58.330 --> 00:45:00.730
to the feature
and go directly to edit mode.

00:45:00.730 --> 00:45:02.330
Next slide, please.

00:45:04.430 --> 00:45:07.580
So here we are in edit mode,
and you see the attributes.

00:45:07.580 --> 00:45:11.490
This is the HydroAdd schema,
and this is a ...

00:45:12.120 --> 00:45:15.420
You see important fields
such as the source ID.

00:45:17.770 --> 00:45:19.430
The source ID
is number 13 there.

00:45:19.430 --> 00:45:21.360
It's in the second row
down there,

00:45:21.360 --> 00:45:23.410
and then you've got a reach code
and a measure,

00:45:23.410 --> 00:45:24.890
which is in the fourth row down.

00:45:24.890 --> 00:45:27.490
This has not been indexed yet,
but as soon as we do,

00:45:27.490 --> 00:45:28.910
it's going to have
a reach code

00:45:28.910 --> 00:45:30.910
and a measure reach
spatial modify date.

00:45:31.490 --> 00:45:33.760
What you see in the map view
is the cursor,

00:45:35.860 --> 00:45:38.770
and you see the snapping cursor,
the cyan crosshairs,

00:45:39.280 --> 00:45:41.470
so wherever you mouse
around in the map,

00:45:42.030 --> 00:45:45.270
the cyan crosshairs
follow your mouse around,

00:45:45.270 --> 00:45:48.850
but the cyan cursor
is always snapping

00:45:48.850 --> 00:45:51.160
the nearest flow line
in all cases,

00:45:51.160 --> 00:45:55.100
so if I were to click right now
wherever that crosshair is,

00:45:55.100 --> 00:45:56.590
I get a reach code
and a measure,

00:45:56.590 --> 00:46:00.800
and it would fill in
over the attributes there.

00:46:00.800 --> 00:46:02.930
Then the user
can go save their edits.

00:46:02.930 --> 00:46:04.530
The save button is up top.

00:46:05.440 --> 00:46:08.490
The only thing that
you must have before you save

00:46:08.490 --> 00:46:12.490
is a source ID,
a unique identifier.

00:46:13.090 --> 00:46:15.300
Once you save,
next slide, please,

00:46:18.660 --> 00:46:21.150
the interface will drop you
back into the queue,

00:46:22.160 --> 00:46:23.580
and once you've gone
through the trouble

00:46:23.580 --> 00:46:25.520
to actually edit something
and snap it

00:46:25.520 --> 00:46:27.400
and give it a reach code
and a measure,

00:46:27.400 --> 00:46:31.480
the point is approved.
As you can see, item 13 here,

00:46:31.480 --> 00:46:33.360
source ID 13
at the bottom of the list,

00:46:33.360 --> 00:46:34.960
now has a thumbs-up,

00:46:35.540 --> 00:46:40.270
so the idea is click a row,
take a look at the point.

00:46:40.270 --> 00:46:42.600
If it's where it needs to be,
approve it.

00:46:42.600 --> 00:46:44.850
If it's not, fix it,
and it will be approved.

00:46:45.430 --> 00:46:47.250
Again, the whole idea
with this editing queue

00:46:47.250 --> 00:46:49.870
is to drive the user
to what is unapproved.

00:46:49.870 --> 00:46:53.880
Everything is about search
and discovery with the NHI,

00:46:53.880 --> 00:46:57.010
and if the point is
in the right place on the line

00:46:57.010 --> 00:46:58.850
with a reach code and a measure,

00:46:58.850 --> 00:47:03.760
then it will be discoverable
by a stream trace.

00:47:05.380 --> 00:47:06.980
Next slide, please.

00:47:09.150 --> 00:47:12.249
Other thing I wanted to point
out to you is the identify tool.

00:47:12.960 --> 00:47:16.590
Here I've drawn a box
to identify NHD features.

00:47:16.590 --> 00:47:18.150
Actually, it will
identify NHD features

00:47:18.150 --> 00:47:20.050
and features
in your service layer,

00:47:20.910 --> 00:47:23.060
so here I've got
hill shade turned on,

00:47:23.060 --> 00:47:26.080
and I'm drawing a box around
some of these NHD features

00:47:26.080 --> 00:47:27.750
on the flank of
Mount St. Helens.

00:47:27.750 --> 00:47:29.350
Next slide, please.

00:47:30.840 --> 00:47:34.660
And an attribute table opens
at the lower part of the screen.

00:47:34.660 --> 00:47:39.310
This attribute table is
broken out by NHD feature type,

00:47:39.310 --> 00:47:42.400
so I've got 23 flow lines
selected in this box

00:47:42.400 --> 00:47:43.760
and a couple of different
water bodies.

00:47:43.760 --> 00:47:46.690
If you mouse over the row
in the attribute tables,

00:47:46.690 --> 00:47:48.890
the item is highlighted
in the map.

00:47:49.540 --> 00:47:51.140
Next slide, please.

00:47:53.200 --> 00:47:56.280
Same thing, I'm mousing over
a couple of NHD water bodies

00:47:56.280 --> 00:48:01.340
that are shown on the map there.
Next slide, please.

00:48:02.840 --> 00:48:06.480
Okay. That's it.
Tool is still in development.

00:48:07.630 --> 00:48:09.410
Eventually, we're going
to need beta testers.

00:48:09.410 --> 00:48:11.370
Please contact me
if you're interested.

00:48:11.370 --> 00:48:12.970
Questions?

00:48:15.990 --> 00:48:17.190
Al ReaOkay, thanks, Mike.

00:48:17.190 --> 00:48:18.790
Mike TinkerYou're welcome.

00:48:20.060 --> 00:48:22.310
Al ReaI'll just kind
of reiterate that

00:48:23.120 --> 00:48:28.390
if you need to work
on addressing data right now,

00:48:28.390 --> 00:48:32.630
you have two choices
available to you.

00:48:32.630 --> 00:48:34.550
You have the HEM tool,
which still works.

00:48:34.550 --> 00:48:37.440
It's a desktop, GIS-based tool,

00:48:38.580 --> 00:48:40.580
and Mike is our support
person for that,

00:48:42.260 --> 00:48:44.200
and you have the HydroLink tool

00:48:44.200 --> 00:48:46.210
that Daniel showed
a few minutes ago,

00:48:48.100 --> 00:48:51.250
and then in the near future,
hopefully,

00:48:51.250 --> 00:48:53.860
we'll be able to release
this tool

00:48:53.860 --> 00:48:57.730
to the public
that Mike was just showing,

00:48:57.730 --> 00:49:00.030
and you'd be able to use
the HydroAdd tool,

00:49:01.020 --> 00:49:06.530
so I'm going to go ahead
and turn off mute for everyone.

00:49:06.530 --> 00:49:08.460
Hopefully, it's not too noisy,

00:49:11.460 --> 00:49:14.470
and we have just
a couple of minutes here

00:49:14.470 --> 00:49:24.760
if we have any questions.
Does anyone have questions?

00:49:26.810 --> 00:49:28.650
AttendeeSo this is Ana
from Missouri,

00:49:28.650 --> 00:49:31.840
and I was wondering,
the HydroAdd tool,

00:49:31.840 --> 00:49:35.020
is that strictly for points,
and is it going to be updated

00:49:35.020 --> 00:49:36.870
for lines and polygons
in the future?

00:49:37.390 --> 00:49:39.820
AttendeeHe just said it was.

00:49:39.820 --> 00:49:43.600
Mike TinkerYeah.
We would like to make lines.

00:49:44.380 --> 00:49:46.530
Lines is a big part
of what HydroAdd is ...

00:49:48.930 --> 00:49:52.420
That's for future development.
We're starting with points,

00:49:52.420 --> 00:49:54.650
but we'll get to lines
and polygons too.

00:49:56.470 --> 00:49:58.320
AttendeeOkay.
Sorry that I missed that point.

00:50:01.800 --> 00:50:03.400
Al ReaAny other questions?

00:50:15.240 --> 00:50:19.490
Well, okay, so that's great.

00:50:21.040 --> 00:50:24.610
I think we will
conclude with this.

00:50:26.920 --> 00:50:28.790
Thanks, everybody,
for joining us.

00:50:28.790 --> 00:50:35.690
I hope everybody stays safe,
and we'll have another advisory

00:50:35.690 --> 00:50:38.780
call next month
at our regular time.

00:50:40.190 --> 00:50:44.310
Thanks again, everybody,
and we'll see you next month.

00:50:44.310 --> 00:50:45.540
AttendeeThank you.

00:50:45.540 --> 00:50:47.140
AttendeeBye, now.