You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This chapter needs updating, the lists are not complete

A.1 GeoDatum

DELFT-FEWS may use a number of national coordinate system as geo-datum. These are referenced by all configurations requiring a definition of geodatum.

All coordinates are handled internally as WGS 1984 (longitude-latitude). To add a new coordinate system to DELFT-FEWS, the transformation between WGS-1984 and that system will need to added as Java class to DELFT-FEWS

The lists of GeoDatum supported are:

+ WGS 1984 (Geographic projection; longitude-latitude)
+ Ordnance Survey Great Britain 1936 (Great Britain)
+ Rijks Driehoekstelsel (The Netherlands)
+ Gauss Krueger Austria M34 (Austria)
+ Gauss Krueger Meridian3 (Germany)
+ TWD 1967 (Taiwan)

A.2 Time Zones

DELFT-FEWS supports a number of time zones:

+ GMT Greenwich Mean Time (UTC+0.00)
+ CET Central European Time (UTC+1.00)
+ EET Eastern European Time (UTC+2.00)
+ WET Western European Time (UTC+1.00)

A.3 Units

DELFT-FEWS supports a list of units. Most of these are SI units.

Unit

Description

m

Metres

mm

Millimetres

m3/s

Cubic meters per second

oC

Degrees Centigraed

mm/hr

Millimetres per hour

%

Percentage

g

 

s

 

degrees

Degrees (directional)

Bft

Beaufort

m/s

Metres per second

-

Dimensionless

W/m2

Watts per metre squared

A.4 Data quality flags

Quality flags are constructed on a philosophy of two qualifiers. The first describes the origin of the data and the second the quality.

Possible origins of data are:

+ Original: This entails the data value is the original value. It has not been amended by DELFT-FEWS
+ Completed: This entails the original value was missing and was replaced by a non-missing value.
+ Corrected: This entails the original value was replaced with another non-missing value.

Possible qualifiers are:

+ Reliable: Data is reliable and valid
+ Doubtful: The validity of the data value is uncertain
+ Unreliable: The data value is unreliable and cannot be used.

Following this specification, the table below gives an overview of quality flag enumerations

Table 1                   Enumeration of quality flags

Enumeration

Description

0

Original/Reliable
The data value is the original value retrieved from an external source and it successfully passes all validation criteria set.

1

Corrected/Reliable
The original value was removed and corrected. Correction may be through interpolation or manual editing.

2

Completed/Reliable
Original value was missing. Value has been filled in through interpolation, transformation (e.g. stage discharge) or a model.

3

Original/Doubtful
Observed value retrieved from external data source. Value is valid, but marked as suspect due to soft validation limits being exceeded.

4

Corrected/Doubtful
The original value was removed and corrected. However, the corrected value is doubtful due to validation limits.

5

Completed/Doubtful
Original value was missing. Value has been filled in as above, but resulting value is doubtful due to limits in transformation/interpolation or input value used for transformation being doubtful.

6

Missing/Unreliable
Observed value retrieved from external data source. Value is invalid due to validation limits set. Value is removed

7

Corrected/Unreliable
The original value was removed and corrected. However, corrected value is unreliable

8

Completed/Unreliable
Original value was missing. Value has been filled in as above, but resulting value is unreliable,

9

Missing value in originally observed series. Note this is a special form of  both Original/Unreliable and Original/Reliable.

Notes:

  • No difference is made between historic and forecast data. This is not considered a quality flag. The data model of DELFT-FEWS is constructed such that this difference is inherent to the time series type definition.

A.5 Synchronisation Levels

To allow optimisation of Data flows in DELFT-FEWS when set-up in a distributed environment, synchronisation levels can be defined. These synchronisation levels are integers. There is no requirement on these integers, and when required additional synchronisation levels can be added to further refine the synchronisation process. The current convention is;

  •         synchLevel = 0; Default synchLevel. Used for all data from forecasting modules.
  •         synchLevel = 1; used to identify import data.
  •         synchLevel = 2; used to identify simulated forecast time series of grid type, like floodmaps.
  •         synchLevel = 3; used to identify input time series with a large volume (may be excluded from synchronisation using a minimum profile).
  •         synchLevel = 4; used to identify import time series data imported incidentally (e.g. Astronomical time series).
  •         synchLevel = 5; used to identify manually edited time series data. This synchlevel is normally used to upload time series from the Operator Client to the Central Database.
  •         synchLevel = 6; used to identify imported external forecast grids that are synchronised from the central database to the Operator Client.
  •         synchLevel = 7; used to identify imported external forecast grids that are NOT synchronised from the central database to the Operator Client. These grids are normally only used as input to FEWS modules only.
  •         synchLevel = 8; used to identify performance indicator time series. These are time series that do not need to be synchronised with a short synchronisation interval or when a forecaster logs in with a minimum profile.
  •         synchLevel = 9; used to identify temporary time series not requiring synchronisation.
  • No labels