Skip to main content

Surface water hydrology: a reach based approach

In surface watershed hydrology, stream network is usually represented by a number of connected stream segments. Outflow from a upstream is then routed to its downstream as inflow at certain time step.

One of the important parameters to determine how long the outflow will arrive the next segment is defined using the travel time. The manning equation is usually used to calculate the open channel flow velocity and rate.

In a typical surface hydrology model such as SWAT or PRMS, these parameters are either prepared or calculated for the model. However, there may be great uncertainty for high-spatial resolution simulations.

For example, a segment travel time may be far less than one hour and a daily time step simulation cannot accurately capture the peak flow at all.

In some scenarios, we are interested in the spatial distribution of flow rate, flow velocity, and other dissolved components (DOC/DIC) in the stream, therefore, a segment based approach is inappropriate.

An alternative way to simulate this process is using a reach-based approach instead of segment-based.
In this scenario, each segment is further broken into a number of stream reaches.

Similar to segment, we can define the travel time for each reach. However, in this case, the travel time is much shorter. For example, for a reach length of 100m simulation, the travel time is approximately within 5 minutes (Imagine you are sitting in a kayak down the stream without paddling).

Therefore, we need a much high temporal resolution to simulate the flow dynamics for each stream reach. Depending on the local elevation variations, the travel time varies significantly, which requires further consideration of different paces in stream routing.


Popular posts from this blog

Spatial datasets operations: mask raster using region of interest

Climate change related studies usually involve spatial datasets extraction from a larger domain.
In this article, I will briefly discuss some potential issues and solutions.

In the most common scenario, we need to extract a raster file using a polygon based shapefile. And I will focus as an example.

In a typical desktop application such as ArcMap or ENVI, this is usually done with a tool called clip or extract using mask or ROI.

Before any analysis can be done, it is the best practice to project all datasets into the same projection.

If you are lucky enough, you may find that the polygon you will use actually matches up with the raster grid perfectly. But it rarely happens unless you created the shapefile using "fishnet" or other approaches.

What if luck is not with you? The algorithm within these tool usually will make the best estimate of the value based on the location. The nearest re-sample, but not limited to, will be used to calculate the value. But what about the outp…

Numerical simulation: ode/pde solver and spin-up

For Earth Science model development, I inevitably have to deal with ODE and PDE equations. I also have come across some discussion related to this topic, i.e.,

In an attempt to answer this question, as well as redefine the problem I am dealing with, I decided to organize some materials to illustrate our current state on this topic.

Models are essentially equations. In Earth Science, these equations are usually ODE or PDE. So I want to discuss this from a mathematical perspective.

Ideally, we want to solve these ODE/PDE with initial condition (IC) and boundary condition (BC) using various numerical methods.

Because of the nature of geology, everything is similar to its neighbors. So we can construct a system of equations which may have multiple equation for each single grid cell. Now we have an array of equation…

Lessons I have learnt during E3SM development

I have been involved with the E3SM development since I joined PNNL as a postdoc. Over the course of time, I have learnt a lot from the E3SM model. I also found many issues within the model, which reflects lots of similar struggles in the lifespan of software engineering.

Here I list a few major ones that we all dislike but they are around in almost every project we have worked on.

Excessive usage of existing framework even it is not meant to Working in a large project means that you should NOT re-invent the wheels if they are already there. But more often, developers tend to use existing data types and functions even when they were not designed to do so. The reason is simple: it is easier to use existing ones than to create new ones. For example, in E3SM, there was not a data type to transfer data between river and land. Instead, developers use the data type designed for atmosphere and land to do the job. While it is ok to do so, it added unnecessary confusion for future development a…