...
To support the validation status, it is possible since PI timeseries version 1.19 to define flagSourceColumns and (custom)flagSources in the PI-XML timeseries format. For example a flag source column named 'V3' that has a custom flag source value 'OK' will result in an attribute
fs:V3="OK"
<
TimeSeries
Code Block |
---|
|
<TimeSeries xmlns="http://www.wldelft.nl/fews/PI" |
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
xsi:schemaLocation="http://www.wldelft.nl/fews/PI |
http://fews.wldelft.nl/schemas/version1.0/pi-schemas/pi_timeseries.xsd" |
xmlns:fs="http://www.wldelft.nl/fews/fs"> |
<
timeZone
>1.0</
timeZone
>
<
series
>
<
header
>
<
type
>instantaneous</
type
>
<
moduleInstanceId
>WerkFilter</
moduleInstanceId
>
<
locationId
>140-w_Leidsche Rijn</
locationId
>
<
parameterId
>HGTE_METING_15M</
parameterId
>
<
timeStep
unit
=
"second"
<timeZone>1.0</timeZone>
<series>
<header>
<type>instantaneous</type>
<moduleInstanceId>WerkFilter</moduleInstanceId>
<locationId>140-w_Leidsche Rijn</locationId>
<parameterId>HGTE_METING_15M</parameterId>
<timeStep unit="second" multiplier="900"/> |
<
startDate
<startDate date="2012-06-25" |
<
endDate
<endDate date="2012-06-25" |
<
missVal
>NaN</
missVal
>
<
stationName
>AANVOERDER
<missVal>NaN</missVal>
<stationName>AANVOERDER_140-w_Leidsche |
Rijn</stationName
>
<
lat
>52.082416488309036</
lat
>
<
lon
>5.075337740730613</
lon
>
<
x
>133623.0</
x
>
<
y
>454951.0</
y
>
<
z
>-9999.0</
z
>
<
units
>mNAP</
units
>
</
header
>
<
event
Rijn</stationName>
<lat>52.082416488309036</lat>
<lon>5.075337740730613</lon>
<x>133623.0</x>
<y>454951.0</y>
<z>-9999.0</z>
<units>mNAP</units>
</header>
<event date="2012-06-25" |
<
event
series
>