NASA ARSET_ Overview of GEOGLOWS for Monitoring and Predicting Flood Risk
The Story
Welcome to another crucial episode of the NASA Live Video Podcast: "NASA ARSET: Overview of GEOGLOWS for Monitoring and Predicting Flood Risk."In this episode, we focus our attention on global water challenges and disaster management. We explore GEOGLOWS (Geo-Global Water Sustainability), a powerful initiative that bridges the gap between complex water data and actionable decision-making. As climate change increases the frequency and severity of extreme weather events, understanding how to monitor and predict flood risks globally has never been more vital.
Through the framework of NASA’s Applied Remote Sensing Training (ARSET) program, we provide a comprehensive overview of how GEOGLOWS utilizes advanced hydrologic modeling, satellite observations, and cloud computing to deliver real-time streamflow forecasts. We discuss how these open-access tools enable local and international water management agencies to anticipate flooding, plan emergency responses, and protect vulnerable communities before disaster strikes.
Whether you are a hydrologist, a disaster management professional, an environmental scientist, or someone deeply interested in how space technology protects lives on Earth, this episode offers essential insights into modern water intelligence. Subscribe to the NASA Live Video Podcast to stay updated on the frontier of earth science, satellite data applications, and global exploration!
Speaker 1: Hello everyone, Welcome back to this final session of the
Speaker 1: training on Monitoring and Predicting Floods using Earth Observations for
Speaker 1: Planning and Preparedness. Part three today is going to focus
Speaker 1: on overview of Group of Earth Observations Global Water Sustainability
Speaker 1: tool that is GEOGLOS for monitoring and predicting flood risk.
Speaker 1: Our guest speakers today are Rachel Megoffin from Aquaveo LLC
Speaker 1: and Riley Hales from Brigham Young University. We'll start with
Speaker 1: a brief review of what we saw in Part two.
Speaker 1: We had doctor Renito Franso. We provided an overview of
Speaker 1: Opera Dynamic Surface Extent or DSWX products which are derived
Speaker 1: from harmonized Lancet and Sentinel two optical imagery and Sentinel
Speaker 1: one synthetic aperture radar imagery. These products are DSWX HLS
Speaker 1: and DSWXS one. The products are near global and are
Speaker 1: available at thirty meter resolution. The temporal coverage or that
Speaker 1: TSWXHLS is from April twenty twenty three to present with
Speaker 1: approximately three day resolution and DSWXS one started in December
Speaker 1: twenty twenty three extend to present with six to resolution.
Speaker 1: We also saw how to select access and composite DSWXHLS
Speaker 1: and DSWXS one products. DSWX data products can be visualized
Speaker 1: using NASA Worldview and data can be accessed using nasal Data.
Speaker 1: We saw that multiday composite of these two products are
Speaker 1: recommended when there are persistent clouds. Flood detection more accurate
Speaker 1: with DSWXHLS for airy region, while DSWXS one for inundated
Speaker 1: vegetation and multiple DSWX data layers merged using QGIS can
Speaker 1: improve flood detection capability. Doctor Fransov demonstrated that so today
Speaker 1: in the final part will have overview of geoglows for
Speaker 1: Monitoring and Predicting flood risk. There will be one homework
Speaker 1: posted on twenty fifth June, that is today, and it
Speaker 1: will be due on ninth of July. The homework will
Speaker 1: be posted on the training webpage. A certificate of completion
Speaker 1: will be awarded to those who attend all live sessions
Speaker 1: and complete the homework assignment before the two date. So
Speaker 1: we'll start with today's session overview of geoglows for Monitoring
Speaker 1: and Predicting flood risk. Overall objectives for Part three are
Speaker 1: that by the end of this part participants will be
Speaker 1: able to identify the capabilities of Geogloss River Forecast System
Speaker 1: or RFS for global stream flow prediction and use Geoglose
Speaker 1: Hydroviewer to access globally available retrospective and predicted stream flow
Speaker 1: for selected reverse Our outline today is that Rachel and
Speaker 1: Riley they will be talking about Geoglows. They will provide
Speaker 1: an overview of Geoglows River Forecast System which is based
Speaker 1: on meteorology model, hydrology model, stream flow routing model and
Speaker 1: stream analysis for bias estimation and reduction. Then we'll talk
Speaker 1: about Geoglows RFS data access and there will be a
Speaker 1: demonstration of how to use Geoglose Hydroviewer. Once again, Please
Speaker 1: put your questions in the question box and we will
Speaker 1: address them at the end of the webinar. Feel free
Speaker 1: to enter your questions as we go and we will
Speaker 1: try to get all of the questions during the question
Speaker 1: and answer session. After the webinar, the remainder of the
Speaker 1: questions will be answered in the Q and a document
Speaker 1: which will be posted on the training website about a
Speaker 1: week after the training. With that, I want to introduce
Speaker 1: our speakers for today. Rachel Hooper macaffin is a hydrologic
Speaker 1: data scientist at Aquaveayo with a master's degree from Brigham University.
Speaker 1: She specializes in GIS and hydrologic modeling. For the past
Speaker 1: five years, she has contributed to the Geogloss River Forecasting System,
Speaker 1: starting as a student at Brigham Young University and continuing
Speaker 1: in her role at Aquaveyo. Through projects with Surveer and
Speaker 1: the World Meteorological Organization, she has helped lead workshops designed
Speaker 1: to build capacity for data management and flood preparedness across
Speaker 1: Central America, South America, and Africa. Doctor Riley Hills is
Speaker 1: a hydrology and river hydrolic researcher at Brigham Young University.
Speaker 1: He is the technical director of the Geogloss program, where
Speaker 1: he builds and operates a global coverage hydrological model called
Speaker 1: the River Forecast System. He has provided hydrologic capacity building
Speaker 1: and training in more than a dozen countries in Central
Speaker 1: and South America, Africa, the Middle East, and South Asia.
Speaker 1: RFS data is used by water and disaster management agencies
Speaker 1: in these areas for flood preparedness, early warning systems, agricultural planning,
Speaker 1: water quality monitoring, and other applications. So with that, we
Speaker 1: invite Rachel and Riley to talk about geoglows.
Speaker 2: Okay, thank you, Amita for that wonderful introduction. As she said,
Speaker 2: my name is Rachel Hubert macgoffin. I work for AQUAVEO
Speaker 2: and I've been working with the Geoglos Initiative for a
Speaker 2: couple of years now, and I'm really excited to share
Speaker 2: a little bit about our river forecast system, our hydrologic model.
Speaker 2: And so as I begin, you may be familiar with GEO,
Speaker 2: but if you're not, that's a group on Earth observations
Speaker 2: and it is a partnership of more than one hundred
Speaker 2: national governments in participating organizations that envisions a future in
Speaker 2: which decisions and actions for humanities benefits are based on coordinated,
Speaker 2: comprehensive and sustained Earth observations. And so this is a
Speaker 2: large partnership in geoglows kind falls under the umbrella of GEOO,
Speaker 2: and geoglows is focused on global water sustainability, and so
Speaker 2: GEOGLOWS leverages partnerships, data and resources to deliver accurate, open
Speaker 2: and accessible hydrological predictions on a global scale, playing a
Speaker 2: vital role in addressing the complex challenges of water resource management.
Speaker 2: And so I wanted to begin with this introduction, so
Speaker 2: you kind of understand that geoglows itself is a larger organization. Today,
Speaker 2: we're going to focus just on our hydrological model, and
Speaker 2: we're going to focus specifically on streamflow and so on
Speaker 2: the hydrologic global scale. We're going to focus on kind
Speaker 2: of what Geoglow's main flagship thing is is our river
Speaker 2: forecast system, our hydrologic model that produces streamflow. But if
Speaker 2: you want to learn more about geogos in general, you
Speaker 2: can visit our website www dot geoglows dot org. And
Speaker 2: so also, as I'm getting started, this hydrologic model, the
Speaker 2: River Forecast System RFS, as you will hear me refer
Speaker 2: to it, is slightly a paradigm shift from what you
Speaker 2: may normally see in hydrologic models. We often see these
Speaker 2: global entities providing dem data, land use data, meteorology data,
Speaker 2: and we're used to seeing those on global scales, and
Speaker 2: often what happens is those meteorology data sets are taken
Speaker 2: and then a lot of funding, resources and trainings are
Speaker 2: given to local organizations and then it becomes their responsibility
Speaker 2: to do the hydrologic modeling. And so each place may
Speaker 2: build their own hydrologic model based on these global data
Speaker 2: sets and then from there they take their hydrologic model
Speaker 2: and use it to do things like agriculture planning, water
Speaker 2: supply management, disaster preparedness. And so they're both doing the
Speaker 2: modeling and doing the local decision making. And this makes sense.
Speaker 2: They're getting to make their own local model. Until when
Speaker 2: some of that funding, some of those resources, some of
Speaker 2: those trainings go away, maybe the person who was trained
Speaker 2: to leave the organization, and suddenly we find that those
Speaker 2: hydrologic models may not be up kept, they may not
Speaker 2: be sustainable, and this approach may end up breaking. And
Speaker 2: so Geoglows seeks to solve this problem by shifting it
Speaker 2: and instead we take in our River Forecast system, we
Speaker 2: take this global dem land data, meteorology data, and we
Speaker 2: provide our own global hydrologic model. And so this is
Speaker 2: done on a global scale, and then we focus the
Speaker 2: trainings and the resources on specifically taking the hydrology data
Speaker 2: sets and applying them to local applications of things like
Speaker 2: agriculture planning, water supply management, disaster preparedness. And so as
Speaker 2: I talk about the River Forecast system, it's going to
Speaker 2: be a little different because instead of giving you links
Speaker 2: to GitHub or to code where you're going to go
Speaker 2: run the model yourself. We are going to focus on
Speaker 2: giving you the results from the model, giving you the
Speaker 2: time series, giving you the products, giving you the visualizations.
Speaker 2: So then hopefully if you are in a situation where
Speaker 2: you work for a national hydrologic service or for a
Speaker 2: local government, you can just focus on doing what you're
Speaker 2: mandated to do, where you take that data and apply
Speaker 2: it to the situations that you need. And so with
Speaker 2: that in mind, our global hydrologic model, as I've said,
Speaker 2: is the River Forecast System, and so this contains streamflow
Speaker 2: data for rivers globally. It has both a forecast and
Speaker 2: a retrospective component to it, and we have used this
Speaker 2: model to address hydrologic needs in countries around the world
Speaker 2: by providing global data and allowing for local bias correction.
Speaker 2: And so we have worked in Central and South America,
Speaker 2: We've done projects in Africa and the Hinalayan region, and
Speaker 2: so we've really focused on this idea of global modeling
Speaker 2: but then taking it to specific locations and having local applications.
Speaker 2: And I just wanted to mention if you have worked
Speaker 2: with Geoglows RFS before it has been upgraded to a
Speaker 2: new version in the last couple of years, and so
Speaker 2: it has new file formats, more streams, and a longer
Speaker 2: retrospective simulation. So even if you've worked with this before,
Speaker 2: you should listen because you may still learn something new.
Speaker 2: And again, all the information on this and everything I'm
Speaker 2: going to go over in this presentation are on our
Speaker 2: training site training dot geoglows dot org, and I'm going
Speaker 2: to put a plug in for that over and over
Speaker 2: again because I know it's really hard to learn all
Speaker 2: this information from one presentation, and so that's a really
Speaker 2: good resource to go to get more information. So before
Speaker 2: we get into how to access this data, I want
Speaker 2: to go a little into the nuts and bolts of
Speaker 2: our model. So this is going to be a bit
Speaker 2: of a tangent, and we will then go into how
Speaker 2: to actually access the data. But I kind of wanted
Speaker 2: to tie into the remote sensing theme and kind of
Speaker 2: explain the origins of how the river forecast system operates.
Speaker 2: And so we know that good meteorology modeling or good
Speaker 2: hydrologic modeling is based on good meteorology, and so without
Speaker 2: the meteorology, we're not going to be able to figure
Speaker 2: out the hydrology.
Speaker 3: And so a.
Speaker 2: Meteorology model is basically an energy balanced calculations driven mainly
Speaker 2: by solar radiation, and so we see three D grid
Speaker 2: of varying grids cell heights with many layers. These grids
Speaker 2: are a coarse resolution, so think like a quarter degree
Speaker 2: twenty five kilometers. So these are a bigger resolution. We're
Speaker 2: going to use smaller resolution on our streams when we
Speaker 2: get to our stream catchments, and I'll go over that.
Speaker 2: But the meteorology model has a courser resolution. And then
Speaker 2: there's energy transfers happening horizontally in columns and also vertically
Speaker 2: in layers, and so these type of models are going
Speaker 2: to be calibrated for atmospheric variables, usually not precipitation or
Speaker 2: water variables, and so you may be familiar with some
Speaker 2: of these models. We have the Global Forecast System GFS,
Speaker 2: which is the American model, and then we have ACMWF
Speaker 2: their Integrated Forecast System IFS is the European model. This
Speaker 2: is what we use for the River Forecast System. RFS
Speaker 2: is based on IFS the ECMWS data, and these models
Speaker 2: when they produce forecasts, they don't just produce one value
Speaker 2: to make a guess into the future. Rather, they do
Speaker 2: ensemble prediction, where they predict a range of values of
Speaker 2: different different possibilities of things that could happen, and they'll
Speaker 2: often produce different a short range forecast, a medium range forecast,
Speaker 2: the long range forecast, and so generally the best models
Speaker 2: are going to be medium range, and they're going to
Speaker 2: be good for twelve ish days in advance, depending on
Speaker 2: your location and a lot of different factors. And so
Speaker 2: Geoglows RFS uses the ECMWF one, We use the medium range,
Speaker 2: the fifteen day forecast, which is why our streamflow is
Speaker 2: also fifteen days. And we use the ERA five data
Speaker 2: for our retrospective data and the IFS data for our
Speaker 2: forecast data. And I just wanted to mention that while
Speaker 2: the data we take in is runoff data from EERA five,
Speaker 2: this does not come from a satellite, but EA five
Speaker 2: is a global atmospheric or analysis from ECMWF, and so
Speaker 2: satellites provide many of the real world observations blended into
Speaker 2: EERA five, including temperature, humidity, precipitation, soil moisture, and so
Speaker 2: even if the runoff isn't measured by satellite, there are
Speaker 2: satellite values and observations that are going in to improve
Speaker 2: the model as a whole, which should then hopefully improve
Speaker 2: the runoff values. And that's what we take in for RFS,
Speaker 2: and so some satellites including Noah fifteen through nineteen, Agua Aqua,
Speaker 2: and so if you want to learn more about it,
Speaker 2: go read the EI five observations documentations. But that's kind
Speaker 2: of how we tie into remote sensing.
Speaker 3: And so now that we've.
Speaker 2: Talked about meteorology data, I'm going to move to talk
Speaker 2: about hydrology models. And so we know that in hydrology
Speaker 2: we're going to treat everything as if it's happening in
Speaker 2: a bucket. So precipitation is coming down, evaporation is going up,
Speaker 2: we have groundwater discharge, we have infiltration, we have snow melt.
Speaker 2: It's all happening, but it's all happening in this bucket.
Speaker 2: And this is happening as calculations. So we get you know,
Speaker 2: precipitation plus soil moisture, but then we take away the
Speaker 2: of appo transpiration and whatever we have left is what
Speaker 2: our runoff is. And so water is happening only in
Speaker 2: a bucket traveling vertically, but then the water is going
Speaker 2: to leave the bucket as runoff, and we're going to
Speaker 2: need to route it to put it into channels and
Speaker 2: move it along the channels into our rivers. And so
Speaker 2: we're going to start and we're going to take those
Speaker 2: those weather forecast grids and then in a bucket is
Speaker 2: happening all our hydrology and we're left with runoff and
Speaker 2: we can convert that into runoff depths, so we end
Speaker 2: up with a grid of run runoff depths. And then
Speaker 2: we're going to take streams and catchments because we know
Speaker 2: that we're modeling streamflow. We want to get the amount
Speaker 2: of water in the stream and we can figure out.
Speaker 3: Where the streams are using.
Speaker 2: Elevation because we know that water is going to travel downhill,
Speaker 2: and we can use these runoff grits in these streams
Speaker 2: and catchments to create a basin runoff volume these tables
Speaker 2: with kind series, and from there we're going to be
Speaker 2: able to route the water through our streams to create
Speaker 2: an overall hydrograph which will represent our time series of
Speaker 2: our data in our stream. And so again, this runoff
Speaker 2: depth is happening on grids, but we have no flow
Speaker 2: between the grids, and instead we have these streams, and
Speaker 2: so our little stream catchments don't follow the grids, so
Speaker 2: we need to convert our runoff depth into the basin
Speaker 2: runoff vout volumes. So we take the grid lines and
Speaker 2: we intersect the basins and we can get the percentage
Speaker 2: of the basin that's in each of the different grids,
Speaker 2: and we can sum them all together, and so we
Speaker 2: end up with the depth over that polygon. Then we're
Speaker 2: able to take that and repeat it for every basin,
Speaker 2: for every timestep. So now we have the volume of
Speaker 2: water in every basin at every time step, and we're
Speaker 2: going to be able to use that in our routing process.
Speaker 2: And so next comes the computations where we have to
Speaker 2: figure out, based on this timestep, based on these volumes,
Speaker 2: how is how's my water actually moving through my river?
Speaker 2: And so we know runoff is going to follow a
Speaker 2: terrain slope until it enters a river channel, and then
Speaker 2: river channels concentrate the runoff into an open channel flow
Speaker 2: and we assume no losses once in this channel flow,
Speaker 2: and then we can put the water and calculate how
Speaker 2: fast it moves.
Speaker 3: And now there's lots.
Speaker 2: Of different hydrologic routing methods. The one we use in
Speaker 2: our model is most similar to Muskigum routing and so
Speaker 2: kind of to go over our model, we start with
Speaker 2: our satellite data and that gets meteorology and land surface
Speaker 2: model data, and then we have our digital elevation model
Speaker 2: which turns into streams and catchments. And now using these
Speaker 2: two things, we can get our runoff per basin. Those
Speaker 2: are our volumes on our little basins. Then we need
Speaker 2: to route our water through our stream. We actually use
Speaker 2: a Python package. It was actually written by Riley Hales
Speaker 2: who's going to be showing the High Reviewer later, and
Speaker 2: we use that to calculate how the water is moving
Speaker 2: through the street the streams and add in the different
Speaker 2: volumes as they enter into the stream beds. But then
Speaker 2: we don't stop there, so then we get river discharged.
Speaker 2: But we also as part of our process, make data
Speaker 2: distribution a high priority and so we take our outputs
Speaker 2: and we put it on web services, We make bulk
Speaker 2: downloads available, We put it in long term archives on AWS,
Speaker 2: so all this data that we have collected through the
Speaker 2: sprouting process is now available for distribution. We also create visualizations.
Speaker 2: In partnership with EZRI, we have a living outless layer.
Speaker 2: We also produce plots and maps, reports, all of these
Speaker 2: and then hopefully people can take all these things we've
Speaker 2: provided to do local applications. And so the goal is
Speaker 2: that while it is a global model, that by providing
Speaker 2: the data to distribution tools and the visualizations, that this
Speaker 2: can then be taken and applied locally as people need it.
Speaker 2: So there's three main products I'm going to talk about
Speaker 2: from RFS today. There's the retrospective stream flow data, which
Speaker 2: goes back to nineteen forty. There's the fifteen day stream
Speaker 2: flow forecast data, which is an ensemble of data available
Speaker 2: daily for fifteen days in the forecast. And then we
Speaker 2: also have our hydrography data all available for download as well,
Speaker 2: including our streamlines and catchments and some other products I.
Speaker 3: Will talk about as well.
Speaker 2: So to start with, the retrospective data is based on
Speaker 2: the E five data set. I kind of mentioned that earlier.
Speaker 2: We use the runoff value as the value that we
Speaker 2: wrote in and this is a deterministic result and so
Speaker 2: there's just one value, it's not a range of value.
Speaker 2: The retrospect is deterministic and we have about six point
Speaker 2: eight million stream segments and so this is available on
Speaker 2: an hourly timestep eighty five years of data on six
Speaker 2: point eight million streams globally, and it updates with a
Speaker 2: five day lag from present, so it's pretty up to
Speaker 2: date in terms of how recently it's available and also
Speaker 2: from the retrospective data. We use all these tools to
Speaker 2: create derivative products, so that way, if someone doesn't want
Speaker 2: to download the whole time series and do the computations themselves,
Speaker 2: we do have derivative products already available for download. And
Speaker 2: so this includes return periods like the two year, five year,
Speaker 2: ten year, twenty five year, and fifty twenty five year,
Speaker 2: fifty and one hundred year return periods calculated using the
Speaker 2: Gumbele distribution and the log Pierson Type three distribution, and
Speaker 2: so this is like your one hundred what the value
Speaker 2: of your one hundred year flood is, your fifty year flood,
Speaker 2: your ten year flood. We also pre compute all the
Speaker 2: monthly averages, the yearly averages, the daily averages, which this
Speaker 2: is really nice if you're doing projects where you need
Speaker 2: to access all this information. It can save on a
Speaker 2: lot of streams. It can save you time for me
Speaker 2: to download all the data and compute those yourself. We
Speaker 2: also have flowdoration curves both available, like the overall flow
Speaker 2: duration curve for the river, but we also have the
Speaker 2: monthly floatation curve available for each month for each river.
Speaker 2: And so these are some examples. Riley's going to show
Speaker 2: the hydro viewer after and he will show that there's
Speaker 2: also a lot of other plots in charge that can
Speaker 2: be made using the retrospective data, and you're able to
Speaker 2: compute those and download those. But this is just some
Speaker 2: examples of some of the derivative products that we have
Speaker 2: available for download. We also have our forecast data and
Speaker 2: so this is a fifteen day ensemble forecast. So I
Speaker 2: mentioned earlier that the IFS data is produced in an ensemble.
Speaker 2: They produce several different possibilities, and we take each of
Speaker 2: their ensemble values for their runoff and we route each
Speaker 2: one of them. So therefore we end up having ensemble
Speaker 2: of forecast members as well. And so this is a
Speaker 2: fifteen day forecast. It's available every day, there's a new forecast.
Speaker 2: It's at three hour time steps, and there's one control
Speaker 2: forecast and fifty ensemble members, so you will see fifty
Speaker 2: one different possibilities. And we also have forecast statistics available
Speaker 2: and that will help provide the uncertainty bounds. You can
Speaker 2: kind of see your range of possible answers you could
Speaker 2: get as well as what is considered to be.
Speaker 3: The most likely.
Speaker 2: I also want to mention that all our forecast data
Speaker 2: we save, and so we have about two years at
Speaker 2: this point worth of old retrospective data old forecast data available,
Speaker 2: and so if you want to go look at your
Speaker 2: forecast data from about a year ago, you could go
Speaker 2: look at that. And so for some reason you need
Speaker 2: old forecast data that is available as well. And then
Speaker 2: I also mentioned that we have our hydrography data available.
Speaker 2: So as a background, the RFS hydrography data is based
Speaker 2: on TEDx hydro which is from the Tandem satellite and
Speaker 2: it's delineated using taodem, and so we took the TEDx
Speaker 2: hydro stream delineations, but we did make some improvements to
Speaker 2: it to help our model run smoother and to fix
Speaker 2: some of the errors that were present. And so some
Speaker 2: of these will be applicable to everyone, and some of
Speaker 2: the improvements we made any will be applicable to anyone
Speaker 2: who wants to use the hydrography data. But also some
Speaker 2: of it was specifically for our model and what we
Speaker 2: needed to happen. So we combined some of the headwaters,
Speaker 2: like to order one streams we might combine with their
Speaker 2: order to stream to be one single basin. We combined
Speaker 2: some of the really tiny short streams as well as
Speaker 2: we're moving some water sheds and flat deserts where we're
Speaker 2: not seeing any flow ever in them. And so we
Speaker 2: did these things to help the model run smoother and
Speaker 2: to help make our numbers more accurate in the model
Speaker 2: overall better. And so the version that we ended up
Speaker 2: with of our hydrography is what we have available now
Speaker 2: for other people to download. And so this data, the
Speaker 2: hydrography data, is all the into VPUs, and a VPU
Speaker 2: is a vector processing unit which is basically just a
Speaker 2: collection of watersheds that we bundled together to make more
Speaker 2: efficient processing and data management. And so if you know
Speaker 2: your VPU, you can download just that VPU instead of
Speaker 2: needing to download globally all the streams. Because with six
Speaker 2: point eight million streams, that sends up to.
Speaker 3: Be a lot of data.
Speaker 2: So being able to download just your VPU of data
Speaker 2: is a way to make it a lot more efficient,
Speaker 2: and so ours is one hundred and twenty five globally,
Speaker 2: and you'll see that in the a US buckets. They're
Speaker 2: split into VPUs and that's how we manage the data.
Speaker 2: So you can download the actual stream center lines, and
Speaker 2: these are the center lines representing the flow path for
Speaker 2: a river segment, and every stream has a unique nine
Speaker 2: digit river idea. You might also hear this referred to
Speaker 2: as a link number, and this is what's going to
Speaker 2: be on the hydrography data. It's also the link number
Speaker 2: you'll use when you want to query the retrospective data
Speaker 2: or the forecast data. This is its identifying number. And
Speaker 2: so in the hydrography data you can see what the
Speaker 2: link numbers are. You'll also see that on the hydro
Speaker 2: viewer as well. And we also in our stream data
Speaker 2: have some additional attributes that might be useful to some people.
Speaker 2: So we have the stream order, we have the upstream area,
Speaker 2: we have what region it came from in TDX hydro
Speaker 2: and so, and like what the terminal link is the
Speaker 2: output for that stream.
Speaker 3: So that is all available in the stream package.
Speaker 2: And then we also have nexus points and lakes and
Speaker 2: so nex's points are just the points where the streams connect,
Speaker 2: so you can see all the points where we have
Speaker 2: the segments connecting with each other, and it'll mark and
Speaker 2: it'll tell you what the upstream and downstream rivers are
Speaker 2: at that point. And then we have the basins that
Speaker 2: we consider lakes in our model, and well these are
Speaker 2: all available on the AWS buckets that I'll show you
Speaker 2: how to access in a minute. And lastly, if you're
Speaker 2: looking at our hydrography data we do, if you are
Speaker 2: looking to put it in some sore of GIS software,
Speaker 2: the easiest way to do it is to take to
Speaker 2: use the EZRE webmap, and so in collaboration with EZRE,
Speaker 2: there's a publicly hosted Living Atlas layer. And so this
Speaker 2: layer is nice because it is done so that the
Speaker 2: thickness of the streams matches the amount of water in
Speaker 2: the streams, and then the colors represent if it's exceeding
Speaker 2: a certain return period. So you can see here that
Speaker 2: that little area where it's purple there that stream flow
Speaker 2: is at this point exceeding fifty years. And this is
Speaker 2: a ten day animated map, and so you can actually
Speaker 2: see those flow period those flow return period colors are
Speaker 2: representing what is currently happening because of this living outless layer,
Speaker 2: and so this is a really nice option to have
Speaker 2: for GIS. And so we start with our geoglows version
Speaker 2: two data and that is delivering AWS open data and
Speaker 2: web service sources. And so this is what I've talked.
Speaker 2: We've talked about the daily historical data, the daily animated maps,
Speaker 2: the daily new forecast. We also have our and this
Speaker 2: is all happening on a supercomputer. And then we're delivering
Speaker 2: all these products and they're being stored on AWS. They're
Speaker 2: being done stored as the Living Atlas layer with Ezer,
Speaker 2: there's an API, and so these are all stored. But
Speaker 2: then the hope is that all these stored data sets
Speaker 2: are then taken and powering local adaptable open source code
Speaker 2: and web applications. So the goal is that all this
Speaker 2: global data that we've provided can then be taken and
Speaker 2: applied locally. And so I now want to show you
Speaker 2: and tell you about how you can take all these
Speaker 2: things I've told you are available and use them.
Speaker 3: And so in order to do that, you will need.
Speaker 2: To access the Geoglosse data. Now, the easiest way to
Speaker 2: access the data is in the hydrid viewer, and this
Speaker 2: is going to be demoed in the second half of
Speaker 2: this workshop, and this is a web application that you're
Speaker 2: going to again it'll be demoed, but use you open
Speaker 2: it up, there's a map, you zoom into your stream,
Speaker 2: you click on your stream, and a bunch of charts
Speaker 2: and information and things you can download just pop up
Speaker 2: right there for you. And so it's really nice, it's
Speaker 2: really easy, and it's also generally easiest for that one
Speaker 2: if you only have one specific stream. And so let's
Speaker 2: say you have a whole series of streams and you're
Speaker 2: trying to query them every every day. The hydro viewer,
Speaker 2: where you have to click on every single one of
Speaker 2: the streams if you have two hundred streams, might not
Speaker 2: be the best option for you anymore. And so there
Speaker 2: is an option where you can query data yourself from
Speaker 2: the AWUS bucket. And so this means that you can
Speaker 2: write Python code to directly access the data and then
Speaker 2: it'll read into your Python code, which makes it easy
Speaker 2: from there to be able to manipulate it, include it
Speaker 2: in web applications, use it for what you need, analyzes, report,
Speaker 2: it's all available for you. And to help make that
Speaker 2: one step easier, we have the geoglows Python package that
Speaker 2: makes it super easy to query the data. And you
Speaker 2: don't even have to create the a to us bucket directly.
Speaker 2: You can just align a code to query everything using the.
Speaker 3: Googles Python package.
Speaker 2: And this queering the data is generally going to be
Speaker 2: the fastest way to download the data, especially if you're
Speaker 2: looking at a large quantity of data. Again, if you're
Speaker 2: looking at say one hundred different river segments, this is
Speaker 2: probably going to be your best way. And then of
Speaker 2: course we have our webmap that I've talked about that's
Speaker 2: the ten day animated streams layer showing forecast results. And
Speaker 2: this is free to use or view in any website
Speaker 2: or GIS, So if you're doing something with GIS software,
Speaker 2: this is a really easy way to integrate RFS. And again,
Speaker 2: I know this is a lot of information, and as
Speaker 2: I go through this, all all of this information is
Speaker 2: on training that geoglos dot org. So go ahead and
Speaker 2: take a look at that website to kind of refresh
Speaker 2: yourself on everything I've talked about. So I've mentioned that
Speaker 2: all our data is available on AWS buckets and they
Speaker 2: are available for open use, and this is going to
Speaker 2: be a really fast way to download large sets of data,
Speaker 2: and on our AWS buckets we have everything available. So
Speaker 2: we have metadata, routing, configuration files, we have the hydrography
Speaker 2: data I talked about, we have forecast data, we have
Speaker 2: retrospective data. We have some of those derivative products to
Speaker 2: the retrospective data with different averages, and so these are
Speaker 2: all available on AWS. And so you can go to
Speaker 2: the actual AWS bucket like you see here on my screen,
Speaker 2: and you can click on the subset that you want
Speaker 2: and you can click through and you can download the file. Now,
Speaker 2: I will say you will download a lot of data
Speaker 2: doing this because you're gonna have to download the whole file.
Speaker 2: So generally it is better to use the geoglos python
Speaker 2: package or to query it programmatically and then you can
Speaker 2: query specifically for the rivers you're interested in.
Speaker 3: And so the geoglows python.
Speaker 2: Package is a Python package that allows for data to
Speaker 2: be easily queried, and it defaults to querying the AWS
Speaker 2: buckets as its source, and so the retrospective and forecast
Speaker 2: values can be queried there if you want to use this.
Speaker 2: I'm not going to be able to go over all
Speaker 2: the options with the geogloss python package, but we do
Speaker 2: have documentation on how to use it and what commands
Speaker 2: are available.
Speaker 3: And one highlight of.
Speaker 2: The Geoglos Python package is that multiple rivers can be
Speaker 2: requested at once. You can request all of your rivers
Speaker 2: and it's also easy to write code to be able
Speaker 2: to check it again in a couple of days if
Speaker 2: you need to update it. And so I have a
Speaker 2: little code snippet here, I just want to show that
Speaker 2: it actually is like one line of code to get
Speaker 2: it all. And so you just import the package, you
Speaker 2: give it all the river ideas you want, and then
Speaker 2: it's as easy as geoglows dot data dot forecast ensembles
Speaker 2: with your river list or geoglows dot data dot retrospective
Speaker 2: with your river list, and that's going to spit you
Speaker 2: out a data frame with the daytime index and a
Speaker 2: column per river id, and so again it's a really
Speaker 2: fast and easy way to be able to get data
Speaker 2: for a lot of rivers. You also, if you are
Speaker 2: more comfortable with queering aid to bas directly instead of
Speaker 2: using the Python package, you can create aws bucket programmatically
Speaker 2: or use the command line if you are already familiar
Speaker 2: with this. And there's more examples of this on training
Speaker 2: dot geoglows dot org, so you can get the URI
Speaker 2: for the AWS bucket and using x ray you can
Speaker 2: just open that data set and select the rivers you
Speaker 2: want and get the data that way. You do need
Speaker 2: to make sure if you do this option that you
Speaker 2: need to make sure you create anonymously or it will
Speaker 2: throw an error.
Speaker 3: It is open for.
Speaker 2: Everyone, but if you don't queerate anonymously, it'll say you
Speaker 2: don't have permission. But as long as you create anonymously,
Speaker 2: you will have permission to access the data. I generally
Speaker 2: think the Python package is easier, but if you are
Speaker 2: more familiar with this way, or you have specific applications
Speaker 2: where you need to use the AWS buckets directly, this
Speaker 2: is an option of something you can do. And then again,
Speaker 2: our other way to access data, probably the easiest, most
Speaker 2: user friendly is the RFS version two hydro viewer. It
Speaker 2: has a ton of visualizations available for your river. It
Speaker 2: will it can do lots of things. You zoom in,
Speaker 2: you click on your river, you can see old forecast data,
Speaker 2: current forecast data, retrospective data, a bunch of different graphs.
Speaker 2: You can see the streams colored and Riley will talk
Speaker 2: more about this later, but this is a really cool
Speaker 2: tool we have for data visualization and for data accessibility
Speaker 2: because you can just download the data straight from there.
Speaker 2: And now I've kind of talked about our data, I've
Speaker 2: talked about how to access it, but I wanted to
Speaker 2: mention one more thing as I kind of start to
Speaker 2: wrap up this part of the presentation before Riley does
Speaker 2: the demonstration, and that is I've talked a little a
Speaker 2: lot about how the goal of geoglows is that well,
Speaker 2: it is a global model, we hope that it can
Speaker 2: go to local applications. And now, as a global model,
Speaker 2: often is bias exists on a local scale when you're
Speaker 2: going to be using a global model, and some of
Speaker 2: that bias comes from the runoff data that we input
Speaker 2: as the input into it arefs, is going to be
Speaker 2: other sources a bias that may occur based on your
Speaker 2: specific conditions of where you live. And so we are
Speaker 2: always working on ways to improve our model to get
Speaker 2: better numbers, better answers out. However, one of the ways
Speaker 2: you can get better numbers is a bias correction option,
Speaker 2: and so there is an option for local bias correction,
Speaker 2: which then enables better local.
Speaker 3: Results for the model.
Speaker 2: So this does require observed data at the stream segment,
Speaker 2: but then it will give you both forecasts and retrospective data,
Speaker 2: and it'll be corrected to match the volume of water
Speaker 2: we're seeing in the observed data. So if we tend
Speaker 2: to in the simulated data often over predict by bias correcting,
Speaker 2: we can correct the volume and our range of values
Speaker 2: will be more similar to what you may see in
Speaker 2: your observed value. And this is available to use in
Speaker 2: the Geoglows Python package. And we just have some functions
Speaker 2: geoglos dot bias dot correct historical and Geoglows dot bias
Speaker 2: dot correct forecast, and those are available for you to
Speaker 2: use and to perform your own local bias correction on
Speaker 2: your own data with your own data on the global data.
Speaker 2: And so the way this method works is so we
Speaker 2: take the simulated hydrograph that we are getting out of
Speaker 2: the RFS, and we're going to get the floatation curve
Speaker 2: for that simulation data, and then we're going to get
Speaker 2: the observed floatation curve from the observe data that you
Speaker 2: upload as part of the function, and we're going to
Speaker 2: use that observed data to correct the values of a hydrograph.
Speaker 2: So then the values of the hydrograph, the volume of
Speaker 2: it matches more similar to what we were seeing in
Speaker 2: the flowtation curve of the observed data. And so we
Speaker 2: also acknowledge that observed data, which is necessary to do
Speaker 2: bias correction, is not available for every river, and we
Speaker 2: have been working on ways to then try to improve
Speaker 2: the bias in areas.
Speaker 3: That may not have the subserved data.
Speaker 2: And one experimental process we have right now is called
Speaker 2: Saber stream analysis for Bias Estimation and Reduction. And what
Speaker 2: this does is it takes the bias correction methods that
Speaker 2: we have locally and it works to apply them globally.
Speaker 2: And so we've taken the data that has been given
Speaker 2: to us, whether and we have permission to use, whether
Speaker 2: from GRDC USGS, specific organizations or countries, and this is
Speaker 2: then included in the model. And we've taken the basins
Speaker 2: globally and they've been clustered and so like basins are
Speaker 2: similar to each other and so they have similar patterns.
Speaker 2: And then we're able to take flow duration curves from
Speaker 2: the gauged networks and the corrections we perform we're able
Speaker 2: to apply to other gauges, whether in a similar region
Speaker 2: or in a similar cluster in the same cluster, and
Speaker 2: so I won't go into the whole algorithm for it,
Speaker 2: but it's a way to apply the bias correction using
Speaker 2: regionalized base and data, and so all the streams can
Speaker 2: benefit from the bias correction happening in some of the streams.
Speaker 2: And so this data, the global bias corrected data, is
Speaker 2: available on the hydro viewer and all those time series
Speaker 2: and things, both for forecast and for retrospective data that
Speaker 2: we have available for our with our normal data is
Speaker 2: available for the global bias correction. But I do want
Speaker 2: to mention that this data is experimental. We are still
Speaker 2: evaluating it and working on lots of improvements in our
Speaker 2: model as always, and so just use this data at
Speaker 2: your own risk. It may improve some of your numbers,
Speaker 2: but it may make some of your numbers worse. And
Speaker 2: so just make sure you understand what you are using
Speaker 2: when you choose to use this data. And so that
Speaker 2: is going to conclude my presentation. That's kind of overviewing
Speaker 2: all of the river forecast system. Again, I know it's
Speaker 2: kind of a lot to take in all at once,
Speaker 2: and so I encourage you to go check out our
Speaker 2: way website, our training website at training dot geoglows dot org,
Speaker 2: where it's going to have all the information I talked
Speaker 2: about and more in addition to examples and code snippets
Speaker 2: to help you work through, and you can go look
Speaker 2: at the parts that specifically interest you. And then I'm
Speaker 2: going to let Riley take over and he's going to
Speaker 2: show you in real time how to use the hydro
Speaker 2: viewer and some of these tools I've talked about so
Speaker 2: that hopefully you feel a little more comfortable taking them
Speaker 2: and using.
Speaker 3: Them for yourselves.
Speaker 4: Well, thank you Rachel for that introduction to everything there
Speaker 4: is to know how geoglows RFS.
Speaker 5: I know that was a lot.
Speaker 4: I'm going to do my best to provide some concrete
Speaker 4: examples of everything that we just learned about. I'm going
Speaker 4: to start by giving another plug for the training sites.
Speaker 4: This is training dot geoglows dot org. And when you
Speaker 4: first land here on the left, you'll see and a
Speaker 4: column of about all the headings and there's River Forecasts
Speaker 4: system is one of your options. Part one about model
Speaker 4: formulation is a simplified version of what we just went over,
Speaker 4: but it does have a lot of extra links to
Speaker 4: other places where you can read more about the different
Speaker 4: components and journal articles and things like that. I'd love
Speaker 4: to draw your attention there if you have further questions,
Speaker 4: and I'd be happy to take them in the Q
Speaker 4: and A part as well. However, moving down to two
Speaker 4: available data where I'm starting to pick up on this
Speaker 4: this first entry data catalog.
Speaker 3: Has.
Speaker 4: If I scroll down just a little bit, there's this
Speaker 4: table of data sets, section and on.
Speaker 5: To highlight a couple of things here.
Speaker 4: First, all of this data is on an AWSS three buckets.
Speaker 4: There's a ABS has this program that makes it such
Speaker 4: that you do not need to have a user account.
Speaker 4: There's no tokens, no put in your credit card, no
Speaker 4: user name or password, nothing like that is required to
Speaker 4: access any of the data I'm about to show you.
Speaker 4: And that second is that there are two locations to
Speaker 4: find all of this data. So if you're the kind
Speaker 4: of person that wants to write code that obtain this,
Speaker 4: if you want to go brows what's there and refresh
Speaker 4: your memory, this table will give you an entry for
Speaker 4: every row.
Speaker 5: Is one of the things that I can provide you
Speaker 5: what file.
Speaker 4: Format it's in, what's the URL for you to go
Speaker 4: find it? The AWS region. If you're using it within
Speaker 4: the AWS ecosystem. So if if you're interested in obtaining
Speaker 4: the daily forecasts, you'll see this is in a ZAR
Speaker 4: formats and that's where you go looking for it. If
Speaker 4: you're interested in the hourly average flow historical simulation, this
Speaker 4: is the same thing comes in ZAR formats.
Speaker 5: Here's the URL to go looking for it.
Speaker 4: When you go to one of these buckets, all of
Speaker 4: these links will take you to well zoomed into the
Speaker 4: correct subdirectory within the buckets, but you'll end up on
Speaker 4: a page that looks like this. This farthest less column
Speaker 4: will be the different headings, and these headings will all
Speaker 4: correspond to something that is in the table on the
Speaker 4: data catalog portion of the training sites.
Speaker 5: So feel free to browse these as well.
Speaker 4: If you're a AWS guru, there should be old hats
Speaker 4: and feel free to go access this. No tokens or
Speaker 4: log in or anything like that is required. Moving on
Speaker 4: to the Hydroviewer. This is hydroviewer dot googlows dot org.
Speaker 4: There's a two main purposes of the hydro Viewer that
Speaker 4: I'm going to try to cover with you today. First,
Speaker 4: it's a visualization tool. We've got a lot of features
Speaker 4: in here to help you explore data graphically and through
Speaker 4: maps and all sorts of visual means. And second, it's
Speaker 4: a way to retrieve data and look at plots for
Speaker 4: those that are not native English speakers. You're of course
Speaker 4: welcome to use automatic Translate anywhere you want, but I'll
Speaker 4: start by up on the top right, we've got official
Speaker 4: human translated and verified translations in Spanish and in French,
Speaker 4: so if those that if you speak one of those
Speaker 4: language and have that preference, we do have a human
Speaker 4: translated version already available, so that the graphs and the
Speaker 4: map labels and anything that can be translated will be translated.
Speaker 4: Next is right next to that is there's this gear
Speaker 4: icon for settings. Now, this tool is definitely targeting a
Speaker 4: more scientific user, but even given all of the wealth
Speaker 4: of the charts and maps and everything that's available, there's
Speaker 4: some of those things are not on by defaults, So
Speaker 4: I'll draw your attention to First, we'll be looking at
Speaker 4: a simplified view of the forecast. By defaults, that's the
Speaker 4: recommended place I would start. However, there's this option that's
Speaker 4: off by defaults, which says show additional plots if you
Speaker 4: want to see the extra feel free to toggle that on,
Speaker 4: and as well as for bias correction, Rachel mentioned how
Speaker 4: we've done a lot of analysis to understand that bias
Speaker 4: is the primary error, and that is that it's correctable
Speaker 4: using gauge data, where it's a experimental method to make
Speaker 4: that apply to all river segments in the model, not
Speaker 4: just the ones where we have gauge data. Feel free
Speaker 4: to toggle us on, and I suggests the further reading
Speaker 4: and journal articles on the training sites.
Speaker 5: If you're going to try experimenting with this option, all.
Speaker 4: Right, let's start by looking at the visualization options. I'll
Speaker 4: frust drate your attention to the base map that we're
Speaker 4: looking at here. This is called the environment map, and
Speaker 4: it's got a couple of things that helped clarify looking
Speaker 4: at rivers. The blue lines are the rivers from TDX
Speaker 4: hydro that we've revise to do hydrologic modeling on. But
Speaker 4: these brown lines are watershed boundaries from hydro basins. And
Speaker 4: as you zoom in you'll see more those divisions appear,
Speaker 4: and there'll be other blue lined references and those all
Speaker 4: come from hydro sheds. However, if you have a preference
Speaker 4: for any others, you can of course change to imagery
Speaker 4: or topographic or any of the other options to be
Speaker 4: most friendly for all audiences, I'm going to keep it
Speaker 4: on a simple gray one so that there's the maximum
Speaker 4: amount of contrast for some of these streams. The first
Speaker 4: thing I'll point out about the streams themselves is that
Speaker 4: there's both different thicknesses and different colors that are apparents.
Speaker 4: As I zoom in and out, will see more streams.
Speaker 4: That's called a multi scale map. So I'll start by
Speaker 4: zooming in to this north part of South America, where
Speaker 4: I see some streams and a few different countries that
Speaker 4: are colored differently. The legend on the bottom left reminds
Speaker 4: me that those colors correspond to that's exceeding a return period,
Speaker 4: or in other words, that the yellow is the beginning
Speaker 4: of you should be worried about flooding occurring, And the
Speaker 4: farther you go down this list to exceeding fifty years,
Speaker 4: the more likely is this is a bigger floods covering.
Speaker 5: More area, and it is more rare in how big
Speaker 5: that event is.
Speaker 4: So I'll zoom in and we'll notice that once I
Speaker 4: zoom in here more lines where are parents here compared
Speaker 4: to zoomed out, I'll do that one more time to
Speaker 4: draw attention. From this level, I can see just the
Speaker 4: main stems, the biggest portions of the rivers, and when
Speaker 4: I zoom in, these streams densify. That'll happen two times
Speaker 4: until you get all the way zoomed in. The Next
Speaker 4: thing to look at is that this map layer is animated.
Speaker 4: If I come to the top left, there's a clock icon.
Speaker 4: That's why of our controls. If I toggle that on,
Speaker 4: a time slider appears on the bottom. Forecasts are generated
Speaker 4: every day at midnight, and so that by default you'll
Speaker 4: see that first time step that corresponding to midnight UTC
Speaker 4: time zone. Regardless of where you are in the world,
Speaker 4: it's always going to be midnight UTC is the first
Speaker 4: time step. Feel free to slide this by hands, or
Speaker 4: you can use the There's a play button and every
Speaker 4: couple seconds it will slide through the timesteps. And if
Speaker 4: I zoom in far enough, we'll see that the thickness
Speaker 4: and the coloring of the rivers is going to change
Speaker 4: as the slider progresses down the line. So for here,
Speaker 4: for instance, if I pick out just one spot at
Speaker 4: the headwater, there's some yellow here, but as time progresses,
Speaker 4: the flood is receding, so there's it's leaving that warning
Speaker 4: threshold and going back to the standard blue, which is
Speaker 4: within normal flow ranges. If I now pause this and
Speaker 4: jump ahead, the animation goes out for ten days, and
Speaker 4: jumping ten days into the future, you can see most
Speaker 4: of the yellow has disappeared and the thicknesses for some
Speaker 4: of those segments have gotten narrower.
Speaker 5: Maybe there's less water in them.
Speaker 4: Next thing that I will draw attention to on the
Speaker 4: maps is again on the top left, there's a there's
Speaker 4: controls to manipulate what streams are visible. This filter icon
Speaker 4: will prompt you to filter the streams that are visible.
Speaker 4: Rachel mentions that the one of the intended applications of
Speaker 4: all of this hydrology data is to support custom applications
Speaker 4: by country or by watershed, so the map is capable
Speaker 4: of having filters applied. There's a few that are the
Speaker 4: most common that I provide you some dropdowns for like
Speaker 4: for instance, this one river country means if I type
Speaker 4: in the name of a country like United States or
Speaker 4: let's say Brazil, I'm closer to Brazil.
Speaker 5: If I check that box and hit apply.
Speaker 4: The map will reduce itself to only showing me the
Speaker 4: river segments that intersect the boundaries of the country. Now
Speaker 4: you might say, well, if this is in the Amazon,
Speaker 4: that crosses into some other country boundaries. So if I
Speaker 4: go back to the filter menu, I might say, show
Speaker 4: me countries that are either in Brazil or who outlet
Speaker 4: outlets in Brazil. I hit apply, Then some more of
Speaker 4: the Amazon becomes visible, even though those segments are outside
Speaker 4: of Brazil, but they flow into that. Between those two
Speaker 4: controls you have a lot of ability to display rivers
Speaker 4: that are trans boundary. So if your application area is
Speaker 4: in a country that's as most are, where the rivers
Speaker 4: has trans boundary flow, those two controls here help you
Speaker 4: create targeted visualizations for whatever application area you have. I'll
Speaker 4: clear for now to restore that. However, you'll see that
Speaker 4: there's this enter custom sequel. This is an EZRI web
Speaker 4: map layer, and I've left you a link to documentation
Speaker 4: if you are familiar with writing sequel. I won't cover
Speaker 4: that here, But there are other attributes, like you could
Speaker 4: provide a bounding box on latitude longitude. You can provide
Speaker 4: specific river numbers that you want to be filtered this
Speaker 4: site's the visit the Ezraelving Atlas link here will direct
Speaker 4: you to the pages with information about what all the
Speaker 4: attributes are, and you can build your own filters here.
Speaker 4: The other main components of visualization, we offer some supplementary
Speaker 4: layers that provide additional context to this.
Speaker 5: Up on the top.
Speaker 4: Right of the map area, there's a layer selector and
Speaker 4: from the most of these come from the Noah twenty
Speaker 4: satellites veers. You can get the most recent imagery on
Speaker 4: thermal anomalies. You can get true color reflectants. One that
Speaker 4: I'll toggle on is this Veer's flood composits. This is
Speaker 4: using the most recently available Vier's imagery running through a
Speaker 4: classification algorithm, and the colors corresponds to different land use
Speaker 4: types or there's.
Speaker 5: Blue for water, for instance.
Speaker 4: And use this as an example to say if while
Speaker 4: looking at anything on this app including in most common
Speaker 4: perhaps even these supplementary layers like the flood composite. On
Speaker 4: the top rights there's a question mark icon which will
Speaker 4: provide you links to both the geoglows RFS data and
Speaker 4: our various websites for instructions, but also for instance, the
Speaker 4: Vier's flood composite layer. There's this link to a un
Speaker 4: University of Wisconsin websites that has the explanation for.
Speaker 5: What the colors mean on that layer.
Speaker 4: Another one worth drawing your attention to is hydro SOS
Speaker 4: Monthly Status. Hydro SOS is the WMO World Meteorological Organization Activity.
Speaker 4: These polygons that you're seeing correspond to hydro shed's basins,
Speaker 4: and there's a yellowish hand ish color which represents normal
Speaker 4: and for that the month that's being visualized, it was drier,
Speaker 4: slightly drier, or much drier than normal, it gets one
Speaker 4: of these shades of red, or if it's slightly wetter
Speaker 4: or much wetter, it gets the lighter blue or dark blue. Correspondingly,
Speaker 4: These maps are available for every monthly average going back
Speaker 4: for thirty years, so I see it or sorry. If
Speaker 4: I direct your attention to the top left, there's a
Speaker 4: control labeled SOS for hydro SOOS controls, and this one
Speaker 4: also will animate. It's not quite as responsive as the
Speaker 4: streams if you animate those, but the slider here can
Speaker 4: be manually dragged to whatever time period you're looking at,
Speaker 4: like for instance, I happen to stop on July nineteen
Speaker 4: ninety nine, and this is what the map.
Speaker 5: Looked like at this point.
Speaker 4: That concludes the main components of our visualization parts. I'm
Speaker 4: going to refresh the page and get back to the
Speaker 4: defaults view. So if I refresh the page and get
Speaker 4: back to the default view, we'll start looking at how
Speaker 4: you use the hydro viewer to extract data and get
Speaker 4: plots and look at things numerically. But I mentioned already
Speaker 4: that this map is multi scale, meaning that there's more
Speaker 4: rivers become visible as you zoom in. So if I
Speaker 4: start really zoomed out and I try and click in
Speaker 4: South America, the map is going to drag me into
Speaker 4: a much higher resolution or a much higher zoom so
Speaker 4: that I can see the rivers at their full detail
Speaker 4: being presented to me. And only when you're this far
Speaker 4: zoomed in will I be able to click on a
Speaker 4: stream and it will start pulling data for me. After
Speaker 4: you've clicked on a stream, you're going to see this
Speaker 4: modal appear. And there's two options at the top right
Speaker 4: for you to toggle between forecast data, which we're looking
Speaker 4: at now, and the other button takes me to look
Speaker 4: at the retrospective simulation data. I will start on the
Speaker 4: forecasts our main chart here. The top plot this hydrograph
Speaker 4: shows the predicted flow for the fifteen day period that
Speaker 4: forecast covers. I'm going to toggle off the return period
Speaker 4: by clicking on them for a minute so I can
Speaker 4: comment on the two main lines here, the black one
Speaker 4: labeled predicted flow, and this blue region labeled uncertainty. So
Speaker 4: the black line that's called predicted flow. If someone needs
Speaker 4: just a single number for what flow did we predict
Speaker 4: for a deterministic application, or you need to put this
Speaker 4: into an equation somewhere, this black line is labeled predicted flow.
Speaker 5: Is the median of the ensemble.
Speaker 4: As Rachel already mentions, this is a fifty one member
Speaker 4: ensemble and at every time step, so every three hours
Speaker 4: across the fifteen days, there's going to be fifty one
Speaker 4: different numbers, and this black line is the median at.
Speaker 5: Each of the time steps.
Speaker 4: It's the representative value that we would suggest you use.
Speaker 4: You can try averaging, you can use other means to
Speaker 4: reduce the ensemble down, but the black line that we
Speaker 4: put out is a good starting place is the median.
Speaker 4: The blue region labeled uncertainty. It corresponds to the twentieth
Speaker 4: percentile and the eightieth percentile at each time step, so
Speaker 4: that's sixty percent. So it's sixty percent of the data
Speaker 4: fall fell within that range. So it's more likely than not,
Speaker 4: according to our predictions, that the actual flow that will
Speaker 4: occur at whatever the lead time is will be within
Speaker 4: that boundary this blue shaded region. It's normal for the
Speaker 4: blue shaded region to get smaller as if you're looking
Speaker 4: at bigger watersheds, so there's more upstream drainage area. And
Speaker 4: that's because the for instance, at this flow right now,
Speaker 4: we're predicting seven thousand meters per seconds. This may or
Speaker 4: may not be biased to remember, we haven't done biased
Speaker 4: correction yet, but we're predicting seven thousand cubic meters per
Speaker 4: second on June sixteenth at three am. According to this
Speaker 4: and that, it's hard for there to be a very
Speaker 4: large window of uncertainty relative to larger and larger flows.
Speaker 4: But if you use this tool instead to look at
Speaker 4: a smaller tributary with a much smaller drainage area, it's
Speaker 4: normal for this blue area to become bigger because there's
Speaker 4: less certainty, and smaller uncertainties propagate into a larger relative
Speaker 4: amount of error that might be predicted. I'll turn the
Speaker 4: return periods back on. Now.
Speaker 5: These are the same colors that we're used for the
Speaker 5: map this.
Speaker 4: They go from yellow to orange, red all the way
Speaker 4: up to purple. The map stops coloring at fifty, but
Speaker 4: the chart shows a one hundred year return period as well.
Speaker 4: The return periods help provide context for how big the
Speaker 4: flow is. If you don't have a strong concept already
Speaker 4: of what's normal in a given river, you might look
Speaker 4: at four thousand cubic meters per second and say is
Speaker 4: that a lot or a little? And these return periods
Speaker 4: help you understands. At a two year return period, so theoretically,
Speaker 4: every other year, perhaps you might expect this river to
Speaker 4: reach this flow. So it's pretty common, but it's hydrologically
Speaker 4: we start to think of that as the beginning of
Speaker 4: If it happens just every other year, that's as a
Speaker 4: random guess, not knowing specifics about the river, that's when
Speaker 4: flooding would start to occur. The five, ten, twenty five
Speaker 4: and as they go up these larger return period values,
Speaker 4: as the flow is predicted to cross into one of those,
Speaker 4: it's more likely that the flow is going to cause flooding,
Speaker 4: and that the extent of how wide the flood will
Speaker 4: be will get bigger. Another way to look at that
Speaker 4: same information is in the table just below this. For
Speaker 4: each of the fifteen days in the prediction, you'll see
Speaker 4: the line up until about June eighteenth and on the
Speaker 4: graph is entirely within the Orange region. And this tables
Speaker 4: tells you specifically the percentage there are more ensemble members
Speaker 4: being plotted that are rather not being plotted, And this
Speaker 4: table tells you the percentage that are within each of
Speaker 4: these thresholds during each of the days in the fifteen columns.
Speaker 4: The last thing the comment on for the forecast is
Speaker 4: if you want to go back in time and look
Speaker 4: at what we projected in the future rather in the past.
Speaker 4: There's a date picker at the top. Rachel mentioned already
Speaker 4: that we have or the old forecast. We're in June
Speaker 4: twenty twenty sixth right now as of the day that
Speaker 4: we're presenting, the first forecast that we have is July
Speaker 4: one of twenty twenty four, so we're about to hit
Speaker 4: two full years of forecasts being stored. And I want
Speaker 4: to comment on refecasts. The record that you can go
Speaker 4: back and obtain is whatever we forecasted on that day
Speaker 4: with no deviations. Even if we found an error in
Speaker 4: the model later or going back, we determined that the
Speaker 4: model didn't do very well, and we could have adjusted
Speaker 4: certain parameters to make it perform better. We have not
Speaker 4: gone back and done reforecasts, so this past archive perhaps
Speaker 4: the farther back in time you go. There might be
Speaker 4: errors in your specific watershed which later we've discovered and addressed,
Speaker 4: but the forecast that you obtain for those dates in
Speaker 4: the past will not reflect those edits.
Speaker 5: There's no refecasting that happened.
Speaker 4: Last thing that I'll show on the charts is there's
Speaker 4: a tab to toggle over to the retrospective. Rachel mentioned
Speaker 4: that there's hourly average is the native resolution, and you
Speaker 4: can obtain that still. To keep the plot simpler, we
Speaker 4: just show the daily average and the monthly averages here.
Speaker 4: You can click on these to toggle them, and it's
Speaker 4: by default zooms into. Only a few years of data
Speaker 4: are visible. The slider on the bottom, you can drag
Speaker 4: the ends to shrink or grow the window that's visible. Normally,
Speaker 4: I'd suggest you keep this shrunk down to five or
Speaker 4: ten years if you want to be able to see
Speaker 4: what's really going on in the data, otherwise it becomes
Speaker 4: really spiky as it's all visible. There are some other
Speaker 4: plots here, and there's several more of these that are
Speaker 4: available if you go back to the settings and toggle
Speaker 4: on the additional plots. The only other one that's on
Speaker 4: by defaults at least at the time that we're in
Speaker 4: our workshop today, as this plots that shows the Hydross categories,
Speaker 4: and if I toggle on each of the individual categories here,
Speaker 4: these shades of blue and red correspond to the same
Speaker 4: thing that the maps show if we toggle on the
Speaker 4: Hydross layer, and by default, just whatever year you're in
Speaker 4: is visible. So that's twenty twenty six currently. But if
Speaker 4: you're studying this watershed and you're using remote sensing from
Speaker 4: twenty years ago or something, you might say two thousand
Speaker 4: and nine is the year i'm interested in, so you
Speaker 4: can scroll down finds that year on the legend entries
Speaker 4: over here, and that will appear on the map. Last
Speaker 4: thing to help you obtain data is on the top right.
Speaker 4: There's a download icon which will prompt you to download
Speaker 4: the CSBS. You can click on that and download either
Speaker 4: of the forecast data or the retrospective data or both
Speaker 4: and if you like the style of plots and you
Speaker 4: want to just borrow the plots that we provide in
Speaker 4: the viewer, every single one of the plots on the
Speaker 4: top rights of when you hover your mouse over, it
Speaker 4: will prompt you to download this plot as a p
Speaker 4: ANDNG and that's for all of them.
Speaker 5: A few other.
Speaker 4: Sort of informational items about the Hydro viewer is up
Speaker 4: on the top right. We have the ability for you
Speaker 4: to save rivers. This bookmark icon will show you by default,
Speaker 4: it's just a dozen or so of the biggest rivers
Speaker 4: in the worlds and you'll see the ID number that
Speaker 4: corresponds to that river and the name, and you can
Speaker 4: shortcut having to browse through the map to find that
Speaker 4: river by just hitting this chart icon and it will
Speaker 4: go load the information for that river, and you'll see
Speaker 4: that when opening up one of the rivers from that menu,
Speaker 4: the heart is is toggled here.
Speaker 5: If for.
Speaker 4: Your application, there's a river that you're gonna want to
Speaker 4: visit all the time, perhaps it corresponds to a gauged location,
Speaker 4: or it's a monitoring point, an infload, or a reservoir,
Speaker 4: something like that. I just clipped on another new river
Speaker 4: and I can hit the heart icon and it will
Speaker 4: auto populate the river ID and give me the chance
Speaker 4: to save it with a name, so I could say,
Speaker 4: maybe this corresponds to gauge one, two.
Speaker 5: Three, four, of course that's the name.
Speaker 4: Can be anything that's that's meaningful to you here and
Speaker 4: I hit add bookmark and the heart turns red. And
Speaker 4: now that's something that I can frequently go back and
Speaker 4: find without needing to browse through the map. If there's
Speaker 4: just a list of, you know, twelve rivers that you
Speaker 4: always want to check on, or that you're going to
Speaker 4: visit a couple times throughout the frequency of your projects,
Speaker 4: this is a good way to convenience yourself on not
Speaker 4: needing to browse the maps as many times and speed
Speaker 4: things up. That concludes my presentation on the Hydroviewer. Thank
Speaker 4: you so much for being with us. I'm looking forward
Speaker 4: to taking your questions and I'll turn the time back
Speaker 4: over to our hosts.
Speaker 1: Thank you so very much Rachel and doctor Hale's for
Speaker 1: your presentations and demonstration of Hydroviewer. This is going to
Speaker 1: be an extremely useful tool for flood prediction and preparedness.
Speaker 1: This brings us to the end of today's session. Just
Speaker 1: to summarize what we saw today, we learned about geoglows.
Speaker 1: It's a partnership initiative among one hundred plus national government
Speaker 1: and organizations to deliver accurate, open and accessible hydrological predictions
Speaker 1: on a global scale based on the ECMWF ERA five
Speaker 1: and integrated for class system data. The ERA five models
Speaker 1: include insitute and multiple satellite data assimilation. Geogloss uses a
Speaker 1: hydrologic model with inputs from models, gages and satellites to
Speaker 1: calculate runoff. Distributed vertically uses a river routing model to
Speaker 1: get river discharge and provides retrospective and forecast hydrographs for
Speaker 1: global river segments. Geoglose provides written periods, monthly and annual
Speaker 1: averages and maximums and flow duration curves from the retrospective data.
Speaker 1: Geoglos data visualization can be done through hydro Viewer and
Speaker 1: RGIS webmap and query and download data from Amazon Web service.
Speaker 1: This brings us to the conclusion of this training on
Speaker 1: monitoring and predicting floods using our third durations for planning
Speaker 1: and preparedness. Just to summarize this training, this was a
Speaker 1: three part training that focused on flood detection on land
Speaker 1: from remotely sensed optical and microwave data, imagery and flood modeling,
Speaker 1: and we were discharge prediction using weather, hydrology and river
Speaker 1: routing models. In part one we talked about global flood product.
Speaker 1: Second part focused on operodynamic surface water extent and today
Speaker 1: we talked about geogloss river forecasts system. So part one
Speaker 1: Global flood product was summarized by doctor Dance. LABA was
Speaker 1: based on Terra and aquamdis and Noah twenty and twenty
Speaker 1: one vers optical data. It uses red infrared and shortwave
Speaker 1: infrared reflectancies to detect water. Identification of recurring floods is
Speaker 1: based on twenty two year flood mask historical data. Also
Speaker 1: its global two hundred and fifty meters respecial resolution and
Speaker 1: near real time and twenty three years of archived data
Speaker 1: are available from Terra and AQUA multilook composites of one,
Speaker 1: two and three day to assign threshold based water detection
Speaker 1: is used. Terrent shadow and cloud shadow corrections are applied
Speaker 1: to remove false positive in water detection and composite product
Speaker 1: recommended by PERSIST for persistent cloudiness and longer lasting larger floods.
Speaker 1: We saw an example or several examples of how to
Speaker 1: look at worldview for data visualization of global flood product
Speaker 1: from different composites, and also how to access data from
Speaker 1: NASA Earth Data and Large Deck, as we reviewed earlier. Today,
Speaker 1: Part two was about opera dynamic surface what extent, presented
Speaker 1: by doctor Renato Franso. He described how operodynamic surface water
Speaker 1: Extent or DSWX has two products, one from optical imagery
Speaker 1: harmonized land set and Sentinel two data and based on
Speaker 1: SAR Centinel one sr set. So these two are DSWXHLS
Speaker 1: and DSWXS one products. Both have relatively high resolution thirty
Speaker 1: meters their near global Both DSWXHLS and S one products
Speaker 1: are available from twenty twenty three to present, HLS from
Speaker 1: April and S one from December. Temporal resolutions are also
Speaker 1: given here a three day for HLS and six to
Speaker 1: twelve for S one. We saw that DSWXHLS data should
Speaker 1: be composited over multiple days or combined with DSWXS one
Speaker 1: data when there are persistent clouds, and we also saw
Speaker 1: how to merge DSWX data layers in GIS for improved
Speaker 1: flood detection capability. There was a demonstration of how to
Speaker 1: visualize DSWX data in NASA Worldview and data Access to data. Finally,
Speaker 1: we had presentation and demonstration from Rachel Megafin and Riley Hales.
Speaker 1: They talked about GEOGLOWS, which is based on the acmw
Speaker 1: ERA five and Integrated Forecast System, uses in situ and
Speaker 1: multiple satellite data assimilation in these models and also uses
Speaker 1: hydrologic model and a river routing model. GEOGLOWS combines models,
Speaker 1: gauge data and satellite data and provides retrospective and forecasts.
Speaker 1: Hydrographs for fifteen day forecasts, written periods, monthly and annual
Speaker 1: averages and maximums and flow duration curves from the retrospective
Speaker 1: data also available from a hydro viewer. There's an example
Speaker 1: I've picked up. This is the cares in Ukraine. This
Speaker 1: is the same flood that we saw in Global Flood
Speaker 1: Product and this is the hydrograph or discharged time series
Speaker 1: for that and you can see from hydro viewer that
Speaker 1: you do see increased discharge during that period when we
Speaker 1: saw flooding in this Careson area. We also found out
Speaker 1: that RTIs webmap can also be used for visualizing this
Speaker 1: data and data can be accessed through Amazon Web Service. Overall,
Speaker 1: there are several benefits and limitations to what we learn
Speaker 1: in this training. For example, combining multiple satellite and incituo
Speaker 1: observations with models provides predictive capability for stream flow enabling
Speaker 1: risk assessment, planning and preparedness for floods, such as using
Speaker 1: weather forecast, ideology and river outing models. In geoglows in
Speaker 1: which multiple observations are used, then remote sensing observations both
Speaker 1: active microwave and passive optical from multiple satellites and sensors
Speaker 1: such as Terra and Aqua Modis twenty twenty one years,
Speaker 1: lands At eight and nine only Sentinel to MSI and
Speaker 1: sentinel ones are These are satellites and sensors used in
Speaker 1: Global Flood Product and Opera DSWX. They enable the detection
Speaker 1: of inundation and water logging during and after flood events,
Speaker 1: supporting response and recovery activities. SAR observations provide all weather
Speaker 1: capability to detect surface water, while optical observations cannot see
Speaker 1: through clouds and are therefore unable to detect surface water
Speaker 1: in overcast conditions. The special and temporal resolutions of these
Speaker 1: flood products vary by satellites and sensors, such as we
Speaker 1: saw that opera products are thirty meters, global flood product
Speaker 1: are two one hundred and fifty meters and resolution Temporal
Speaker 1: resolution varies from one to twelve days, and they carry
Speaker 1: uncerties due to various factors such as orange shadow, cloud shadow,
Speaker 1: and surface types. Monitoring flood potential using jeoglos alongside merged
Speaker 1: flood products from multiple optical inside data sets would greatly
Speaker 1: enhance flood related decision making activities. So the message is
Speaker 1: that we can use beneficial information from different satellites and
Speaker 1: sensors and models and combine them to be better prepared
Speaker 1: for flood related decision making. The homework assignment is posted
Speaker 1: today on our training web page and answers must be
Speaker 1: submitted via Google Forms and the homework is due on
Speaker 1: ninth of July and you will receive a certificate of
Speaker 1: completion approximately two months after the completion of this course
Speaker 1: if you attended all live webinars and if you complete
Speaker 1: the homework assignment by the due date. So we did
Speaker 1: exercise one and two after our previous sessions. Today the
Speaker 1: exercise will focus on using geoglows outfestream flow prediction using
Speaker 1: hydro Viewer. We will be looking at the same flood
Speaker 1: caase in South Sudan between fifteenth of May and thirty
Speaker 1: first of May, so you will be looking at streamflow
Speaker 1: or discharge using geoglows RFS. So about the homework exercises,
Speaker 1: we had three exercises counting today's exercise, first one on
Speaker 1: global flood product then a dynamic surface water extent. Both
Speaker 1: these were through NASA Worldview and today you'll be using
Speaker 1: hydro viheer to look at this South Sudan floodcase and
Speaker 1: some of the homework questions you will find based on
Speaker 1: these exercises. Once again, we want to thank all our
Speaker 1: guest speakers for their excellent presentations, demonstrations and contribution to
Speaker 1: this training and doctor Daniel Slayback, Doctor Renetto Frasso, Rachel
Speaker 1: mcaffin and doctor Riley Hales. We thank you all for
Speaker 1: your contribution to this training. It's the contact information for
Speaker 1: Rachel and Riley if you have any specific questions about Geoglows,
Speaker 1: and you can always contact us at our set with
Speaker 1: any questions that you have. Here is our set website
Speaker 1: with a lot of information you can find about different
Speaker 1: trainings and our set YouTube has recordings of all our trainings.
Speaker 1: For questions, comments, or to share how you have applied
Speaker 1: our trainings to your work or studies, please email NASA
Speaker 1: dot r SET at gmail dot com and join our
Speaker 1: mailing list to stay up to date on our latest trainings,
Speaker 1: and visit our contact page to subscribe. These are the
Speaker 1: resources we used in this training and share your thoughts.
Speaker 1: Within the day or two, we will send you an
Speaker 1: invitation to complete a short online survey and your feedback
Speaker 1: helps us improve the RSET program. Participation is optional and
Speaker 1: all responses are confidential. Survey data are crucial to helping
Speaker 1: us understand how to better meet your needs, and we
Speaker 1: want to help you use our observation data more effectively.
Speaker 1: We read every survey comment, so please share your thoughts.
Speaker 1: The survey will come from no Reply at Alchemera dot com,
Speaker 1: so this is not a spam email that you will
Speaker 1: receive from this address, so please we request that you
Speaker 1: complete the survey and your feedback is very important to us.
Speaker 1: With that, we want to thank you all for attending
Speaker 1: this training session and now we will go to our
Speaker 1: question and answer session with Rachel and Riley for geoglows. Yeah,
Speaker 1: thank you everyone for attending this training series and also
Speaker 1: our speakers for today, Rachel Meguffin and Riley Hale. We'll
Speaker 1: go to the question and answer session now, I'll read
Speaker 1: the questions and our guest speakers will help. So the
Speaker 1: first question is does you close provide data in coastal
Speaker 1: area areas or island nations and you can unmute and
Speaker 1: answer the question, thank you.
Speaker 4: Yes, we do have coverage on some islands, not all.
Speaker 4: The question or the answer that's visible here is that
Speaker 4: some of the foreseeings and data sets we use have
Speaker 4: varying resolutions. One additional clarification I can add on to
Speaker 4: that is that the dem products, the elevation products and
Speaker 4: things that are used to derive where the catchment boundaries
Speaker 4: are just we're not available on all islands. It is
Speaker 4: most places, but not all of them. I direct you
Speaker 4: to look around on the web viewer to see if
Speaker 4: the islands that you're interested in is covered.
Speaker 1: Great, thank you. A second question is can this geoglosse
Speaker 1: modeling be applied to a single basin.
Speaker 4: Yes, it can. The products that we use are all
Speaker 4: open source. The streams we provide the net forcings are
Speaker 4: from ECMWF and those don't require a license to obtain.
Speaker 4: You can either take our pre computed answer using these methods,
Speaker 4: or if you want to use the if you have
Speaker 4: some reason you need to run that yourself, or you
Speaker 4: want to apply some modification to any of the steps,
Speaker 4: then that you can just download the data from the
Speaker 4: relevant places. You'll have to do some additional work on
Speaker 4: your own to modify that odes to work on your
Speaker 4: area of interest, but everything you would need is open
Speaker 4: source to do that.
Speaker 1: Great, thank you. Question three is I'm wondering about the
Speaker 1: hydrological model used in geoglows WIF hydro lease flood.
Speaker 4: Yeah, so this question is asking, I believe about how
Speaker 4: we calculate the runoff volumes from the meteorology. This we
Speaker 4: use products from ECMWFS Integrated Forecast System i f S,
Speaker 4: and the land surface component of that is done with
Speaker 4: the model called h TESSEL and that is we take
Speaker 4: the answer straight from that. We apply modeling downstream of it,
Speaker 4: but our main source of truth for what the runoff
Speaker 4: depth is comes from that h TESLIL model.
Speaker 1: Next question is where we can download the hydrography shape file.
Speaker 4: Yeah, so there are several questions asking about where defines
Speaker 4: data for this one in particular, but also the others.
Speaker 4: I'll direct you to our training websites. That's training dot
Speaker 4: gogos dot org, and that's that'll be in this answer documents,
Speaker 4: and it's in the slides and in various places, and
Speaker 4: you'll find tables that direct you for whichever product you're
Speaker 4: looking for. We'll give you a description of the name
Speaker 4: and what file formats and so on and so forth
Speaker 4: for where you can download.
Speaker 1: That question file. Is there any bias correction too available?
Speaker 4: Yeah, So this can happen in two different ways. One,
Speaker 4: we provide code, and we've have papers describing a method
Speaker 4: where if you have your you want to bring your
Speaker 4: own gauge data, you can apply the method that we
Speaker 4: use to get our model data and your gauge data
Speaker 4: that you provide and calculate what the bias corrected flow
Speaker 4: would be. Alternatively, option two, there are some restrictions on
Speaker 4: what data we are and are not allowed to use
Speaker 4: for a broad global application, but we do have in
Speaker 4: the hydro viewer there's an option to toggle turning on
Speaker 4: using bias correction. This is also available in code, but
Speaker 4: go to the hydrid viewer and in the settings you
Speaker 4: can toggle on that you want to use the experimental
Speaker 4: bias correction and we will do our best guess of
Speaker 4: what the bias corrected flow is everywhere, using what gauge
Speaker 4: data we do have that is appropriately licensed and so on.
Speaker 1: Thank you. Question six, can you download the data from
Speaker 1: the living at last or is it just a visualizer?
Speaker 4: Yeah, so the living atless layer is really meant to
Speaker 4: just be for visualization. You can go browse all the
Speaker 4: attributes that are applied to the streams that's used for
Speaker 4: the styling and animation, but really it's meant just for visualization.
Speaker 4: There are plenty of other code tools and notebooks other
Speaker 4: things in the training to help you download if you
Speaker 4: need to get large volumes of data downloaded.
Speaker 1: Question seven, is there any approach in this method that
Speaker 1: estimates regulated basins?
Speaker 4: So this question also, I think has kind of two answers.
Speaker 4: Some of the most impactful regulations could be extracting water
Speaker 4: for irrigation or running a canal or something. It's really
Speaker 4: difficult to get information about what volumes of water are
Speaker 4: used there. We do not have a way to to
Speaker 4: make that, but there are other ways, like how lakes
Speaker 4: are managed or reservoirs or dams, those are sometimes able
Speaker 4: to or do have the information that we would need
Speaker 4: to make an estimate on that. The current model version
Speaker 4: does not do an especially good job of accounting for
Speaker 4: all those things, but Rachel and I are collaborating on
Speaker 4: doing better in the next model version. How will make
Speaker 4: the model accounts for the effects of reservoirs? So that's
Speaker 4: some some yes, and some know that we that we
Speaker 4: whether or not we're able to account for regulations.
Speaker 1: Great question eight is, since the ensemble forecasting model generates
Speaker 1: multiple possible forecast outcomes, is there a mechanism for incorporating
Speaker 1: subsequent observational data to update and define earlier forecasts, thereby
Speaker 1: improving prediction accuracy over time.
Speaker 4: Yeah, this is a really good question. That this is
Speaker 4: getting a data assimilation essentially. The biggest problem is that
Speaker 4: countries that have often the greatest need for this kind
Speaker 4: of supplemental global hydrology modeling often don't have very many gauges,
Speaker 4: and those that do typically don't have their data publicly
Speaker 4: accessible on the Internet, so that the lag time between
Speaker 4: when the measurement is made and when it would be
Speaker 4: accessible to me to try to do some sort of
Speaker 4: ingestion run A common filter or something like that is
Speaker 4: pretty long, so we don't primarily because it's just not
Speaker 4: feasible the computationally, the data doesn't become accessible on a
Speaker 4: short enough lead time to try doing that. However, as
Speaker 4: I said before, the code and data sets and everything
Speaker 4: you would need to go back in time and do
Speaker 4: a re forecast is all open source and available, So
Speaker 4: even though we don't do that at the global scale,
Speaker 4: that is possible, and you can check out our code
Speaker 4: and send some emails to chat more about that if
Speaker 4: you would like.
Speaker 3: Nice.
Speaker 1: Question nine is has geo gloves been evaluated or benchmarked
Speaker 1: against other operational flood forecasting platforms such as IFAs or
Speaker 1: Google flood up.
Speaker 5: Yes we have.
Speaker 4: Sometimes those are published, and I gave you a link
Speaker 4: to the publications there. That's again on trading that geobos
Speaker 4: you'll find a publication section.
Speaker 5: Also.
Speaker 4: We do similar kinds of benchmarkings and comparisons whenever we're
Speaker 4: participating in w MOO activities, including some that are ongoing
Speaker 4: right now, so I'll direct you to those publications to
Speaker 4: see if that gives you the answer that you're looking for.
Speaker 1: Question ten is does geoglows aim to serve as a
Speaker 1: flood forecasting tool or stream flow stetus and forecasting data provider.
Speaker 4: Primarily our use cases and that we've collaborated with country
Speaker 4: hydromed agencies has been for flooterly warning applications. We do
Speaker 4: have examples of applying this data and building tools or
Speaker 4: apps or other things around other applications such as water
Speaker 4: quality or irrigation or reservoir management, but those have are
Speaker 4: more in the minority to the majority of our collaborations
Speaker 4: have revolved around flood forecasting. We are looking to expand
Speaker 4: the number of pre made things that we provide on
Speaker 4: that on those other application areas. Though.
Speaker 1: Interesting elemon is how are the RFS simulations validated? Are
Speaker 1: the calibrator or validated using hydrometric stations?
Speaker 4: Yeah, so we have I've already alluded to this slightly
Speaker 4: that we have a lot of gauge data. It's growing.
Speaker 4: But the some of the problems in publishing about all
Speaker 4: of those gauge measurements is that they're not all permissively
Speaker 4: licensed for us to publish validation against that, that would
Speaker 4: necessarily mean we're giving away some of those gauge measurements
Speaker 4: and they're being put on plots and things, and that's
Speaker 4: not always allowed, So we do validate against a very
Speaker 4: large set of inciti measurements. Not all of them make
Speaker 4: it into publications, and not all of them can be shared,
Speaker 4: so there's some difficulty in how those gets share or
Speaker 4: how we're able to share that with other people.
Speaker 1: Question twelve, is there any thought to creating our library
Speaker 1: for jyo glows?
Speaker 4: Yeah? This I get this question occasionally. The geoglows main
Speaker 4: team does not have any our developers on it, so
Speaker 4: we're not in a great position to create that ourselves.
Speaker 4: We have a Python a job script job excuse me,
Speaker 4: job a script version. If you would like to take
Speaker 4: the lead in creating in our version, I'm definitely open
Speaker 4: to having that conversation.
Speaker 1: Question thirteen, is there any opportunity to get hand to
Speaker 1: hand training on setting the geoglows model model?
Speaker 4: So I would say yes, the I would direct you
Speaker 4: first to training dot geoglows, and there's some links here
Speaker 4: to a Google group and we have a YouTube channel
Speaker 4: with some webinars, So I'd hope that this covers a
Speaker 4: lot of the the questions and upfronts kind a direction
Speaker 4: that you're looking for, but you would need to reach
Speaker 4: out to us to discuss if you're looking for live
Speaker 4: trainings and things like that.
Speaker 1: Thank you. Question fourteen, how does geoglows differ from glow fasts?
Speaker 4: So this is a really good question, getting right to
Speaker 4: the core of how our model operates. What Rachel was
Speaker 4: presenting at at the beginning. We in rfs and glow
Speaker 4: fasts share the same ECMWF MET predictions that ensemble prediction
Speaker 4: the core. We're both built on the same meteorology predictions.
Speaker 4: As the farther you go down the line, though, we
Speaker 4: start to diverge on the different additional modeling steps that
Speaker 4: are applied. Because of that, that are met forcings at
Speaker 4: the core are the same, so we'll often show very
Speaker 4: similar signals. It's sometimes called or shapes on the graphs.
Speaker 4: If glow fast predicts it, we will probably also predict it,
Speaker 4: and vice versa because we share that same core, but
Speaker 4: because we use different modeling methods downstream of the mets
Speaker 4: and the land surface parts, they won't be identical, but
Speaker 4: they'll often be very complimentary.
Speaker 1: Question fifteen, incheoglows? Can we searched for a river by name?
Speaker 4: Yeah, this is another really common question we get. There's
Speaker 4: some difficulty in getting a really good authoritative source for
Speaker 4: what river names are. So in general, I would say no,
Speaker 4: you should use the ID numbers because that is guaranteed
Speaker 4: to be unique everywhere. For instance, there could be multiple
Speaker 4: rivers names the Colorado River or the fill in the blank.
Speaker 4: There's probably multiple rivers' names are sharing the same name.
Speaker 4: We are exploring ways to try to get some river
Speaker 4: name attributes applied to the streams so that you could
Speaker 4: do some searching and filtering, but that's not available just yet.
Speaker 1: Question sixteen Real Geo Clowse hydro Viewer and the Hissory
Speaker 1: Living Atlas eventually visualized trout conditions or below normal flows.
Speaker 1: I assume that pulling the data and Python would allow
Speaker 1: for this type of visualization in addition to flooding in
Speaker 1: local applications.
Speaker 4: So I think the answer is probably yes eventually. This
Speaker 4: is an ongoing area we're exploring right now. Actually, so
Speaker 4: I don't have an ability to promise specifically wet maps
Speaker 4: or charts or the timeline or anything like that, but
Speaker 4: I would say yes, we do want to have more
Speaker 4: on that front for now, though you'll have to download
Speaker 4: the data yourself and generate the visualization you're looking for.
Speaker 1: Wonderful, We'll take one more question, because we are almost
Speaker 1: at the at the end of our session time, how
Speaker 1: is the uncertainty computed?
Speaker 4: So the statistics for meteorology can get kind of complicated.
Speaker 4: The main thing for you to know is that the
Speaker 4: meteorologists would advise you to view the fifty one different predictions,
Speaker 4: which in turn we use to make fifty one different
Speaker 4: discharge predictions. Those should be treated as if they're equally probable,
Speaker 4: so that you can then do many many directions on
Speaker 4: how you want to analyze that and how you calculate uncertainty.
Speaker 4: I think this question is getting more at when on
Speaker 4: the graphs that we present, what's the blue shaded region?
Speaker 4: How is that uncertainty estimated? This is very unsophisticated, but
Speaker 4: it was done this way intentionally, so it's very simple
Speaker 4: and most readily understood by a big, wide array of
Speaker 4: audiences that have sometimes a great deal of statistical training
Speaker 4: and sometimes not very much at all. We take on
Speaker 4: every kid step, the values are sorted from max to minimum,
Speaker 4: high to low, and the middle sixty percents is that
Speaker 4: considered the uncertainty and that that checks out because the
Speaker 4: most extreme values tend to have very few of the
Speaker 4: members predicting that they happen, and the most common range
Speaker 4: of values sit in the middle. There are, of course,
Speaker 4: many other ways that you could go about estimating certainties.
Speaker 4: This one has chosen specifically because it's simple and it's
Speaker 4: understandable by a wide range of people.
Speaker 5: And the hydro viewer.
Speaker 4: Remove that option and not view the simplified forecast and
Speaker 4: view all the ensemble members and see different ways that
Speaker 4: uncertainty you can be presented. That's just not the default
Speaker 4: for the communication reasons.
Speaker 1: Great, thank you so much. So we have a few
Speaker 1: questions that we will be posting. We will be answering
Speaker 1: and then this question answered document will be posted on
Speaker 1: our training website in a week or so. With that,
Speaker 1: we want to thank our speakers once again, Rachel Megafwin, Ralei,
Speaker 1: thank you so much for your contribution, excellent presentations and demonstrations.
Speaker 1: This is going to be a very useful tool. So
Speaker 1: this brings us to the end of this training and
Speaker 1: we hope to see you at future our set training.
Speaker 1: So please subscribe to our listener or just go through
Speaker 1: the link and you will can subscribe to all the
Speaker 1: future upcoming trainings and stay up to date. At this point,
Speaker 1: I also want to thank our our set team, my
Speaker 1: colleague Sean McCartney, coordinator Natasha Johnson Griffin, and editor Maria Marabito.
Speaker 1: We also have instructional designer Kevin Fuel and our other
Speaker 1: coordinators brock Levin, Salvon, Salvin Hudson or Doy We thank
Speaker 1: you all and Sharry Morris so thank you for your
Speaker 1: help and thank you all for attending this training and
Speaker 1: we hope to see you soon. One last reminder, we
Speaker 1: have an exercise posted today using geoglows height of viewer
Speaker 1: and then some of the questions will.
Speaker 3: Be based on that.
Speaker 1: So you will have free question three exercises and one
Speaker 1: homework assignment and once you finish that and submit the
Speaker 1: homework by dud it, you will receive certificate in about
Speaker 1: eight weeks or so after the after today. So thank
Speaker 1: you all, and please do not forget to take the
Speaker 1: survey when you receive a survey link. We really look
Speaker 1: forward to your comments and thoughts for our future trainings,
Speaker 1: so thanks all once more,
Podbean