Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

page under construction ------------------------------

Are there any differences in the remapping process for EFAS & GloFAS? Which information can be merged into a general description? 

...

Image Added

As we cannot trust that the location of a station in the model is completely representative of the location of the station in the 'real world' (based

...

on provided coordinates alone), the following protocol to map the stations on the river network should be followed. The overall concept of mapping locations onto the river networks is the same for both EFAS and GloFAS.

This page describes the protocol of mapping new locations onto the river network, using the example of GloFAS. In this context, ‘new locations’ are usually river discharge observation stations provided by GloFAS users. The locations represent the catchment of the river at their outlet points. During the process of mapping, the ‘best-fit’ of location in the GloFAS model river network is found, that corresponds with the location of the station on the river in the ‘real world’, based on the coordinates of the station from the data provider.

...

Users should rely on this protocol as a guideline in case they have to extract point time series. To extract point time series, the locations must be mapped onto the GloFAS river

...

network

Tools to use

  1. Go to Settings/Options/Network and click on "Use proxy for web access".
  2. Go to plugins and choose QuickMapServices and click install.
  3. Maps will be available in the Web tab

Step-1: Verify station metadata

  • Make sure the station metadata is correctly provided, identify if any metadata are missing. These should be

...

  • the geographic coordinates (lat/lon in degrees), station and river names, and upstream area (if available).
  • Search for the station location on Google Maps or Google Earth
  • Download the GloFAS upstream area map and load it into QGIS or some other GIS software. It can also be useful be helpful to add a high detail vector river shapefile which can help to identify the real rivers. Alternatively, you can also load the Google Maps/Earth into the GIS software and analyse all layers together.
  • Analyse the location of the stations with the other provided metadata and check if they appear to match with the location in Google Earth/Maps.
  • Check how the user-provided metadata compares with the maps and the GloFAS river network (represented by the upstream area map). Analyse the upstream area values of the GloFAS river network in the vicinity of the provided river point location.
  • This step is a manual

...

  • and subjective process.

Step-2: Identify river network match and find the right river channel

  • Use the GIS software and the loaded upstream area maps, river shapefile, and Google Maps (Earth) (or if the Google products are not available in the GIS software then open in a separate website).
  • First, check how well the GloFAS river network represents the real rivers in the area.
    • Check if the rivers, the main channel(s), and tributaries compare perfectly, well, or if there are minor/major discrepancies.
    • Maybe the rivers are not represented at all (e.g. rivers are so close in reality which cannot be resolved in GloFAS), or in some cases, the GloFAS network is simply wrong for some reason (e.g. rivers flow into each other incorrectly, etc.), or the provided station drains only a very small area (i.e. below 1000 km2 or even maybe only few hundred km2) which GloFAS cannot accurately represent.
    • Alternatively in some areas of the world real rivers can be difficult to locate even on Google Maps/Earth (i.e. in very dry areas where ephemeral rivers flow only intermittently, or where rivers can change their channels like in big deltas), so in such cases, the GloFAS river network will more likely be incorrect or incomplete.
  • Then locate the right GloFAS river channel.
    • As an ideal scenario, the provided coordinates allow

...

    • the identification of the river section without uncertainty on Google Maps/Earth.
    • The provided upstream area (if available), and thus the match between the provided and modelled areas will often help to increase the confidence, or in some cases, where the location is not so clear on Google Maps (e.g. the point is right at the confluence, and it is not clear which channel it is gauging), the provided upstream area will most likely help to decide about the correct channel (i.e. whether it is the main channel, or the tributary, etc.).
    • In some rare cases, the right channel cannot be identified due to problems with the GloFAS river network or uncertainties on the provided location (maybe erroneous coordinates, or uncertain position of real rivers in the area), or simply as a consequence of too small catchment area (i.e. below 1000 km2 or even maybe only few hundred km2) of the provided station.
  • To help increase the confidence of the river channel match, if possible, also compare the observation time

...

  • series (if it is available simply plot the time series) with the GloFAS reanalysis time series from the most likely GloFAS river pixel.
    • The GloFAS-ERA5 reanalysis can be downloaded from the Copernicus Climate Data Store (https://cds.climate.copernicus.eu/cdsapp#!/dataset/cems-glofas-historical) and the reanalysis data extracted for the selected GloFAS river location.
    • Especially, if there is still some uncertainty about the river match, then moving the selected GloFAS point around, and comparing the reanalysis time series from those points with the observation time series, can highlight problems, wrong provided location, incorrect provided upstream area, etc.
    • This step can be especially helpful if the mapping seems problematic and the best model point is ambiguous.
  • This step is a manual

...

  • and subjective process.

Step-3: Compare the observed river flow time series with nearby stations, if possible

  • If the station has

...

  • an observed time series associated with it and there are nearby observing stations in the same catchment, compare the data

...

  • against the nearby stations to check if the time series can be trusted or if it requires further investigation. Ideally, they should srelate well, downstream points showing (upstream area) proportionally higher discharge, etc.
  • In QGIS,

...

  • analyse the locations and alignment of all nearby upstream/downstream stations.
  • Plot the time series using tsview, excel, python, or whichever software can allow you to plot multiple time series
  • In case the comparison gives ambiguous results,

...

  • be aware that the station

...

  • might be in the wrong location.

Step-4: Map

...

the station or discard the station from your analysis

  • Based on Step-2 and Step-3, the best river pixel should be chosen on the selected GloFAS river channel

...

  • ,

...

  • the

...

  • coordinates

...

  • of

...

Station metadata is misleading and the station is mapped with Low/no confidence.

In the comment is specified which metadata does not allow to map the station with higher confidence.

The station is a duplicate, specified in the comment.

...

The station was mapped with low/no confidence and it should not be trusted as it is.

The station is a duplicate. It should not be used and should be possibly removed.

...

wrong ldd/ ldd not able to represent network

...

The station is in the correct place but the ldd does not represent the river system. 

...

The station seems to be in the right position but the observed discharge vs GLOFAS discharge plot seems very different.

Possible issues:

Wrong time series assigned to the station?

Wrong metadata?

Issues with GLOFAS for that catchment?

...

Station seems to be in the correct position with the correct metadata, but unsure of position.

In this case, there were no time series associated with the station or the time series is not helpful in locating the station.

...

Even if the metadata provided is partially misleading the station could be mapped on GloFAS. In this case, is very important to add a comment about the mapping situation and the nature of the problems or difficulties.

Possible examples

i.e. the station name and the coordinates are correct but the upstream area provided is completely misleading.

i.e. the station coordinates are incorrect but the upstream area provided, station name, river name, time series allow the user to place the station in the correct GloFAS position.

moderate confidence. The station can be used by the modeller.

...

  • the chosen pixel will be used to extract the modelled river discharge. If in the previous steps too many discrepancies occurred, the location is very uncertain, observed data does not seem to be fitting into nearby stations, etc., then the station should be discarded.