Time series data represent data collected over a given period of time at a specific location Time series data represent data collected over a given period of time at a specific location Time series data represent data collected over a given period of time at a specific location The version of the published interface schemas Time series data represent data collected over a given period of time at a specific location The header is used to specify the link to the location and the contents Since 2014.01. Properties that are applicable to the events following Since 2015.01. Defines the domain axis values for the specified parameter unlimited number of events with a constant timeStep. The date, time and value attributes are required, the quality flag is optional. When no events exists the event values are stored in a bin file. The binary file has the same name as the xml file only the extension is "bin" instead of "xml". The bin file contains only IEEE 32 bit reals. The length of the bin file is 4 times the number of events for all time series in the file. The byte order in the bin file is always Intel x86. The bin file is only allowed for equidistant time steps. use this field as a notebook to add comments, suggestions description of data entered etc. The header is used to specify the link to the location and the contents Type of data, either accumulative or instantaneous. For accumulative data the time/date of the event is the moment at which the data was gathered. Since 2015.02 pi version 1.17 Since 2015.01. Eg. when the parameter is wave variance density spectrum specify the the domain parameter frequency and direction. Since version 1.4 Further clarification of the time series, when the parameter, location and time step are not enough to identify a time series. Multiple qualifiers are allowed, the order of the qualifiers is insignificant. A different order of the qualifier ids should not map to the an other time series. Since version 1.4 An ensemble forecast consists of a number of simulations made by making small changes to the estimate of the current state used to initialize the simulation. These small changes are designed to reflect the uncertainty in the estimate. Every simulation has it's own ensembleMemberIndex When specified the ensembleMemberIndex is required Since version 1.4 An ensemble forecast consists of a number of simulations made by making small changes to the estimate of the current state used to initialize the simulation. These small changes are designed to reflect the uncertainty in the estimate. Every simulation has it's own ensembleMemberIndex. Ensemble id is not required when the ensembleMemberIndex is specified Since version 1.10 An ensemble forecast consists of a number of simulations made by making small changes to the estimate of the current state used to initialize the simulation. These small changes are designed to reflect the uncertainty in the estimate. Every simulation has it's own ensembleMemberId. Ensemble id is not required when the ensembleMemberId is specified The timeStep element provides three choices date/time of the first event date/time of the last event Since version 1.5 date/time of the forecast. By default the forecastDate equals the start time Since version 1.20. Returns the time that simulated forecast was made current. In case of no longer current then the original approved time is returned. Missing value definition for this TimeSeries. Defaults to NaN if left empty Optional long (descriptive) name Station name Latitude of station Longitude of station X coordinate of station Y coordinate of station Z coordinate of station. From version 1.16 this optional element is only written when available. In 1.15 and earlier z=0.0 is used when z is not defined Optional string that identifies the units used Since 2015.01. Used for spectra and other 1D or 2D variables. e.g. frequency and direction. Additional axis to the time axis Description of (the content of) this file Optional element that maybe used by third parties. The element is not used by FEWS. It is neither written nor read. Optional element that maybe used by third parties. The element is not used by FEWS. It is neither written nor read. code/description of the region. Needed if the id's can be the same in different regions. Since 2019.02. Show product and product info that has been added to the timeSeries. Since 2019.02. Id of the product Since 2019.02. Name of the product Since 2019.02. Id of the product category Since 2019.02. Name of the product category Since 2019.02. User that created the product Since 2019.02. Confidence level of the product Since 2019.02. Classification of the product Since 2019.02. Comment given on the product Since 2015.01. Domain parameter id Since 2015.01. Unit for domain variable Since 2015.01. One of the domain axis parameter ids specified in the header Since version 1.22 Since version 1.27 Since version 1.27 unlimited number of events with a constant timeStep. Each TimeSeries should contain at least one element (records). The date, time and value attributes are required, the quality flag is optional. ISO 8601 (yyyy-mm-dd) ISO 8601 (hh:mm:ss.dsec e.g. 16:30:0.001) Since version 1.23, ISO 8601 (yyyy-mm-dd) Since version 1.23, ISO 8601 (yyyy-mm-dd) Since version 1.23, ISO 8601 (yyyy-mm-dd) Since version 1.23, ISO 8601 (yyyy-mm-dd) Since version 1.31, Value source, only MAN (manual) is recognized Since version 1.31, normal, dried, inundated and ice is recognized Since version 1.29, will be set if the value is not inside the detection range. Since version 1.11, validation rule, default codes are MAN (manual), MOD (modifier), SN (soft min), HN (hard min), SX (soft max), HX (hard max), ROR (rate of rise), ROF (rate of fall), SR (same reading), TS (time shift), OSC (oscillation), SVS (secondary validation series), SVF (secondary validation flags) Since version 1.3 Since version 1.10 Since version 1.19. Used for flag source column names and their custom flag source values. For example a flag source column named 'A' that has a custom flag source value 'OK' will result in an attribute: fs:A="OK"