Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_cells.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_cells.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_cells.xsd (revision 5924)
@@ -0,0 +1,38 @@
+
+
+
+
+
+
+ Each point specifies a cell centre point location.
+
+
+
+
+
+
+
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+
+ Points are read in the order in which they occur and
+ allocating starts in the upper left corner.
+ i.e. the first points is the upper left corner,
+ the last points is the lower right corner. The
+ number of points should match rows*columns
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_importmods.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_importmods.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_importmods.xsd (revision 5924)
@@ -0,0 +1,70 @@
+
+
+
+
+
+ Defines meta data associated with external provided Mods.
+
+
+
+
+
+
+
+ Defines meta data associated with external provided Mods.
+
+
+
+
+ Defines pi_timeseries or pi_parameters file with MOD values.
+
+
+
+
+
+
+ Defines meta data associated with external provided Mods.
+
+
+
+
+ MOD ID e.g. RAINSNOW
+
+
+
+
+ optional name
+
+
+
+
+ start time of MOD, i.e. moment MOD kicks in
+
+
+
+
+ end time of MOD
+
+
+
+
+ MOD validDate, if validDate larger or equal to Now use the MOD for the entire period, elseif validDate smaller then Now set end date to valid date
+
+
+
+
+
+
+
+
+ file containing MOD time series. Units can be specified inside the time series file, no file naming convention applies
+
+
+
+
+ file containing parameter MOD. Note: parameter MODS need to be provided in Metric units. The naming convention for the file name has to be OPERATION_SEGMENTNAME_OPERATIONID
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_configupdatescript.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_configupdatescript.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_configupdatescript.xsd (revision 5924)
@@ -0,0 +1,246 @@
+
+
+
+
+
+
+ List of configuration updates.
+
+The order in which commands are executed is as follows:
+
+- All RemoveLocationSetItem commands
+- All AddLocation commands
+- All EditLocation commands.
+- All AddLocationSetItem commands
+- All EditLocationSetItem commands
+
+
+
+
+ Collections of Configuration update commands.
+
+
+
+
+
+
+ The version attribute is required.
+ This is the version of this specific file.
+ The version number of the entire interface is
+ embedded in the namespace.
+
+
+
+
+
+
+
+ Add location to the Locations file.
+
+
+
+
+ Add an existing location to a location set. Also adds location information to linked IdMaps and ValidationRuleSets.
+
+
+
+
+ Remove a location from a location set. The location information is also removed from linked IdMaps and ValidationRuleSets.
+
+
+
+
+ Edit an already existing location in the Locations file.
+
+
+
+
+ Edit linked information for a location that is already present in the locationSet.
+
+
+
+
+ Import rating curves from xml file(s) in the FEWS rating curves format. The imported rating curves are added to the ratingCurves xml file in the RegionConfigFiles directory. If a rating curve with the same ratingCurveId as an existing rating curve is imported, then the existing rating curve will be replaced.
+
+
+
+
+ Import dbf and/or csv files that contain location attributes. The imported files are put into the mapLayerFiles configuration directory. This only works for dbf or csv files for which an older version is already present in the configuration. If the files to import would make the configuration invalid, then an error is logged and none of the files will be imported.
+
+
+
+
+
+
+ Add / Edit location information.
+
+
+
+
+
+
+ If 'true' existing attributes will be set to null if they are not configured here.
+If 'false' existing attributes will remain unchanged when not configured here.
+
+
+
+
+
+ Add / Edit LocationSet information. Depending on the references of the LocationSet additional information must be provided for linked IdMaps and ValidationRuleSets.
+
+
+
+
+
+
+
+
+
+ If 'true' existing attributes will be set to null if they are not configured here.
+If 'false' existing attributes will remain unchanged when not configured here.
+
+
+
+
+
+
+ Information required to remove a location from a location set.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ points which a times series can exists.
+ The point is represented by X, Y and Z coordinates. Each location element of a time
+ series location file corresponds to a time series data file and consist of four elements.
+
+
+
+
+ Long (descriptive) name of location (tool tip) or description
+
+
+
+
+ Short name of location for chart legend
+
+
+
+
+ Tooltip to be displayed in the FewsExplorer.
+ You can use use \n or CDATA or HTML when you need multiple lines.
+ Besides the global properties you can use the following tags
+ %ID%, %NAME%, %DESCRIPTION%, %LAST_VALUE%, %LAST_VALUE_TIME%,
+ %FORECAST_START_TIME%, %MAXIMUM_VALUE%, %MAXIMUM_VALUE_TIME%
+ The tooltip supports html including images and hyperlinks.
+ The url in the hyper link can be an internet url, an executable file, a document file, or a folder.
+ Use the CDATA xml tag to include html in a xml file.
+ By default the following tool tip is used.
+
+ ID: %ID%\n
+ Name: %NAME%\n
+ Desc: " + "%DESCRIPTION%\n
+ Last value [%LAST_VALUE%] Time [%LAST_VALUE_TIME%]\n
+ Forecast Start Time [%FORECAST_START_TIME%]\n
+ Maximum [%MAXIMUM_VALUE%] Time [%MAXIMUM_VALUE_TIME%]
+
+
+
+
+
+
+ When a location has a parent id it is an invisible child location.
+ All the children of a location are automatically selected in the fews explorer
+
+
+
+
+ X coordinate of the point (Easting)
+
+
+
+
+ Y coordinate of the point (Northing)
+
+
+
+
+ Z coordinate of the point (altitude)
+
+
+
+
+
+
+
+
+
+
+ This can be the path and name of either a file or a directory. This path has to be either absolute or relative to the current working directory. If a file is specified, then the rating curves in the specified file will be imported. If a directory is specified, then the rating curves in all files in the specified directory will be imported.
+
+
+
+
+ Optional id of IdMap to be used for locationId mapping during import. External locationIds will be mapped to internal locationIds.
+
+
+
+
+ Optional. If true, then for each rating curve the locationId is prefixed to the ratingCurveId. This can be used to ensure that all ratingCurveIds are unique. The locationIds are prefixed after locationId mapping takes place, but before the rating curve is imported. Default is false. E.g. for locationId "Delft" and ratingCurveId "224" the new ratingCurveId would become "Delft_224".
+
+
+
+
+
+
+
+
+ This can be the path and name of either a file or a directory. This path has to be either absolute or relative to the directory of this script file. If a file is specified, then that file will be imported. If a directory is specified, then all dbf and csv files in the specified directory will be imported. If any .shp, .shx and .sll files, that correspond to dbf files, are present, then those files will also be imported. If no .shp, .shx and .sll files are present, then the required .shp, .shx and .sll files will be generated from the dbf files and the generated files will also be imported. It is assumed that for each file the Charset is the same as the Charset for the corresponding file in the existing configuration (as defined in the locationSets configuration file).
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_table.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_table.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_table.xsd (revision 5924)
@@ -0,0 +1,106 @@
+
+
+
+
+
+
+ To relate 2 or three parameters (e.g. stage height to discharge) lookup tables are used.
+
+ This can be used also to describe level-area curves for off-line storage areas
+
+
+
+
+ To relate 2 or three parameters (e.g. stage height to discharge) lookup tables are used.
+ This can be used also to describe level-area curves for off-line storage areas
+
+
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+
+
+
+
+ Number of rows
+
+
+
+
+ Number of columns
+
+
+
+
+
+
+
+
+
+ start date and time from which the relation is valid.
+
+
+
+
+ end date and time until which the relation is valid.
+ If not present the relation is assumed to be valid indefinitely
+
+
+
+
+ type of extrapolation if outside the range:
+ non = not allowed, critical stop
+ maxmin = stays fixed at max (or) min level in table
+ linear = linear extrapolation
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The type attribute determines how the data is interpreted: double, long or string.
+ The total number of items MUST match rows*cols. Items are processes from top left to bottom right, row by row
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_sharedtypes.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_sharedtypes.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_sharedtypes.xsd (revision 5924)
@@ -0,0 +1,1136 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Integer that allows (global) properties
+
+
+
+
+
+
+
+ Boolean that allows (global) properties
+
+
+
+
+
+
+
+ Double that allows use of location attributes
+
+
+
+
+
+
+
+
+
+
+ initial version.
+
+
+
+
+
+
+ comment added to pi_timeseries.xsd
+
+
+
+
+
+
+ qualifierId, ensembleId, ensembleMemberIndex added to pi_timeseries.xsd
+
+
+
+
+
+
+ forecastTime added to pi_timeseries.xsd
+
+
+
+
+
+
+ forecastTime added to pi_profiles.xsd
+
+
+
+
+
+
+ location coordinates added to pi_timeseries.xsd
+
+
+
+
+
+
+ log level to pi_run.xsd
+
+
+
+
+
+
+ added pi_timeseriesparameters.xsd, pi_filters.xsd included pi_locations.xsd in build. altered pi_locations.xsd
+
+
+
+
+
+
+ added user and ensembleMemberId to pi_timeseries.xsd
+
+
+
+
+
+
+ added flag source to pi_timeseries.xsd
+
+
+
+
+
+
+ added comments and flags to pi_ratingcurves.xsd
+
+
+
+
+
+
+ Since 2014.01 added header properties to pi_timeseries.xsd
+
+
+
+
+
+
+ Since 2014.02 added header threshold group info to pi_timeseries.xsd
+
+
+
+
+
+ Since 2015.01 added parent location id to pi_locations.xsd
+
+
+
+
+ Since 2015.01 added statistics to pi_timeseries.xsd
+
+
+
+
+ Since 2015.02 added moduleInstanceId to pi_timeseries.xsd
+
+
+
+
+ Since 2015.02 added times attribute to time step
+
+
+
+
+ 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"
+
+
+
+
+
+ Since 2015.02 added approved time to header
+
+
+
+
+ Since 2016.01 added samples support
+
+
+
+
+ Since 2016.02 added threshold labels to pi_timeseries.xsd
+
+
+
+
+ Since 2016.02 a time / value range to event to pi_timeseries.xsd
+
+
+
+
+ Since 2017.02 added minutes attribute to time step
+
+
+
+
+ Since 2018.01 added parameter group to pi_timeseriesparameter.xsd
+
+
+
+
+ Since 2019.02 added product to pi_timeseries.xsd
+
+
+
+
+ Since 2020.02 added threshold description and threshold comment
+
+
+
+
+ Since 2020.02 added timeZone and date,time to pi_diag.xsd
+
+
+
+
+ Since 2021.01 added detection
+
+
+
+
+ Since 2021.02 added parameter attributes
+
+
+
+
+ Since 2021.02 added pi time series value source, state, use milliseconds time format when needed.
+
+
+
+
+ Since 2022.02 added parameterGroupName to timeSeries parameters.
+
+
+
+
+ Since 2023.01 added properties to pi_ratingcurves.xsd.
+
+
+
+
+ Since 2023.02 split sample and value properties for pi_samples.xsd
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The time unit element has three attributes, unit and divider and multiplier. the unit is second, minute, hour, week, month year. The divider attribute is optional (default = 1).
+
+
+
+
+
+
+ Defines the time step by a list of times without dates, e.g. "10:00 23:00". In this case it is not allowed to specify a unit, divider and multiplier
+
+
+
+
+ Since 2017.02. Defines the time step by a list of minutes (with prefix 0 for single digits), e.g. "05 25". In this case it is not allowed to specify a unit, divider and multiplier
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The time unit element has two attributes, unit and divider. the unit is required and can be 1, 2, 3, or 4 meaning: year, month, day and hour. The divider attribute is optional (default = 1).
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Example: to construct timeSteps op 5 seconds use unit 4 (hours) and a divider of 720. For daily timeSteps use unit 2 (day) and divider 1.
+
+
+
+
+
+
+ The geographical datum for the location data. Presently only WGS-1984, OS 1936 and LOCAL are recognised. LOCAL indicates a local grid.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Location ID, defined by the model
+
+
+
+
+
+
+ Content of the data (Discharge, Precipitation, VPD); defined by the model
+
+
+
+
+
+
+
+
+ The timeZone (in decimal hours shift from GMT) e.g. -1.0 or 3.5. If not present the default timezone configured in the general adapter or import module is used. Always written when exported from FEWS
+
+
+
+
+ Id of atime zone that is observing daylight saving time
+
+
+
+
+
+
+
+ The timeZone (in decimal hours shift from GMT) e.g. -1.0 or 3.5. If not present the default timezone configured in the general adapter or import module is used. Always written when exported from FEWS
+
+
+
+
+
+
+ time zones that use day light saving in summer
+
+
+
+
+ Alaska Standard Time, winter:GMT-9 summer:GMT-8
+
+
+
+
+ Pacific Standard Time, winter:GMT-8 summer:GMT-7
+
+
+
+
+ Mountain Standard Time, winter and summer:GMT-7
+
+
+
+
+ Central Standard Time, winter:GMT-6 summer:GMT-5
+
+
+
+
+ Eastern Standard Time, winter:GMT-5 summer:GMT-4
+
+
+
+
+ Newfoundland Standard Time, winter:GMT-3:30 summer:GMT-2:30
+
+
+
+
+ Argentine Time, winter:GMT-3 summer:GMT-2
+
+
+
+
+ Brasilia Time, winter:GMT-3 summer:GMT-2
+
+
+
+
+ Western European Time, winter:GMT+0 summer:GMT+1
+
+
+
+
+ Central European Time, winter:GMT+1 summer:GMT+2
+
+
+
+
+ Middle Europe Time, winter:GMT+1 summer:GMT+2
+
+
+
+
+ Eastern European Time, winter:GMT+2 summer:GMT+3
+
+
+
+
+ Azerbaijan Time, winter:GMT+4 summer:GMT+5
+
+
+
+
+ Armenia Time, winter:GMT+4 summer:GMT+5
+
+
+
+
+ Australia Eastern Time (New South Wales), winter:GMT+10 summer:GMT+11
+
+
+
+
+ Since 2013.01. Australia Western Time, winter:GMT+8 summer:GMT+9
+
+
+
+
+ New Zealand Standard Time, winter:GMT+12 summer:GMT+13
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 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 2014.01
+
+
+
+
+
+ Since 2014.01
+
+
+
+
+
+
+
+
+
+ Custom attributes, used in locations.
+
+
+
+
+
+
+
+
+
+ Describes where and why this attribute is used
+
+
+
+
+ Available since 2019.02.
+
+
+
+
+ Available since 2019.02.
+
+
+
+
+
+ Location attribute of the type text.
+
+
+
+
+
+ Location attribute of the type number.
+
+
+
+
+
+ Location attribute of the type boolean.
+
+
+
+
+
+ Location attribute of type datetime.
+
+
+
+
+
+
+ Id of the attribute
+
+
+
+
+
+ name of the attribute
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A period condition. If a date is specified without a timezone, e.g. 2002-10-10T12:00:00, then it is assumed to be in UTC.
+
+
+
+
+ Timezone
+
+
+
+
+
+ Start and end date time
+
+
+
+ Start date and time for this period.
+
+
+
+
+ End date and time for this period.
+
+
+
+
+
+ Valid for entire period prior to this date and time.
+
+
+
+
+ Valid for entire period after this date and time.
+
+
+
+
+ A seasonal period that is repeated every year.
+
+
+
+ Start month and day of this season.
+
+
+
+
+ End month and day of this season.
+
+
+
+
+
+ Day of the year (e.g. third of May) that is repeated every year
+
+
+
+
+ Month that is repeated every year
+
+
+
+
+ Day of the month such as the 5th of the month that is repeated every year
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Intended for the configuration of any table
+
+
+
+
+
+
+
+
+
+
+
+ Column names for columns A through Z.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Value-types in the columns A through Z. If no type specified, type 'String' is assumed.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Values in the columns A through Z. The values are entered as strings, however the value-type in each column should match the type as specified with columnTypes for this column. This wil be checked while reading the xml-file. If no column-type specified, 'String' type is assumed.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Id that references an qualifier listed in the regionConfigFiles/Qualifiers.xsd
+
+
+
+
+
+
+
+
+
+
+
+ The value at a time represents the aggregated value over the aggregation period
+ e.g when the aggregation period is -6 to 0 hour the value at 13:00 represents
+ an aggregation (e.g. moving average) from 7:00 till 13:00 (including)
+
+
+
+
+
+ Optional field for running ensembles. Ensemble id's in a time series set will override ensemble id's defined in the workflow.
+
+
+
+
+
+
+
+ Defines a moving period in time. The start and end time are relative time to a certain
+ time.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Any number of parameters > 0
+
+
+
+
+ Optional field to describe the parameter. May be used as notebook for comments annotations etc
+
+
+
+
+ Actual value/content of the parameter.
+
+
+
+ Holds one floating point value
+
+
+
+
+ Holds one integer value
+
+
+
+
+ Holds one boolean value
+
+
+
+
+ Holds one string
+
+
+
+
+ Holds one dateTime value.
+
+
+
+
+ Holds one table. The values are entered as strings, however the value-type in each column should match the type as specified with columnTypes for this column.
+ This will be checked while reading the xml-file. If no column-type specified, 'String' type is assumed. Use columnId for entering column name.
+
+
+
+
+
+
+
+ Id of the parameter
+
+
+
+
+ Optional name of the parameter.
+
+
+
+
+
+ Model parameters , grouped
+
+
+
+
+
+ A group of parameters. e.g. default, catchmentOne, catchmentTwo, summer, winter etc.
+
+
+
+
+
+
+
+ Group of parameters
+
+
+
+
+ Used to describe this group of parameters
+
+
+
+
+ Optional location id for this group of parameters. If used externally this is the external locationId
+
+
+
+
+ Optional element to identify the model (algorithm) the parameters are configured for
+
+
+
+
+ Period the parameters are valid in.
+
+
+
+
+
+ Any number of parameters > 0
+
+
+
+
+ Any number of ensembles > 0
+
+
+
+
+
+
+ Unique id for for this group. Id is required and must be used to retrieve the group of parameters.
+
+
+
+
+ Optional name for this group of parameters
+
+
+
+
+ Optional Attribute to indicate that this group may not be changed (e.g. by a GUI) Default = false.
+
+
+
+
+ When set to True it means at least one parameter from the the group has been modified from the original version. Default = false
+
+
+
+
+
+ Defines ensemble of model parameters
+
+
+
+
+
+ Optional field to specify one particular ensemble member the parameters are configured for
+
+
+
+
+ Optional field to specify a particular range of ensemble members the parameters are configured for.
+
+
+
+
+
+ Parameters for this ensemble
+
+
+
+
+
+ Id of ensemble the parameters are specified for
+
+
+
+
+
+
+
+
+
+
+
+ Since 2020.02: value to mark if a value was out of bound of the detection range.
+
+
+
+
+
+ Below detection limit
+
+
+
+
+
+
+ Above detection limit
+
+
+
+
+
+
+ Approximate
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_modelparameters.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_modelparameters.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_modelparameters.xsd (revision 5924)
@@ -0,0 +1,20 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_state.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_state.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_state.xsd (revision 5924)
@@ -0,0 +1,83 @@
+
+
+
+
+
+
+ A state consists of a number of locations.
+ from which FFS reads and writes the model state data.
+ A such reading is reading by the FFS and writing is writing by the FFS.
+
+
+
+
+ A state consists of a number of locations.
+ from which FFS reads and writes the model state data.
+ A such reading is reading by the FFS and writing is writing by the FFS.
+
+
+
+
+ id of this state, defined by the module
+
+
+
+
+ optional descriptive name of this state
+
+
+
+
+ the time zone of the pi input files is assumed when the time zone in a pi output file is missing
+
+
+
+
+ date and time this state is valid for/was taken
+
+
+
+
+ Each state location consists of a read and a write location.
+ The type attribute indicates whether this points to a file or a directory.
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+
+ Each state location consists of a read and a write location.
+ The type attribute indicates whether this points to a file or a directory.
+
+
+
+
+ The name of the input state of the model. The write location is imported by the general adapter. This imported file is renamed to the read location internally
+
+
+
+
+ The name of the output state of the model. The write location is imported by the general adapter. This imported file is renamed to the read location internally
+
+
+
+
+
+ type: either file or directory
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_version.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_version.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_version.xsd (revision 5924)
@@ -0,0 +1,37 @@
+
+
+
+
+
+
+ Delft-FEWS version information.
+
+
+
+
+ Version info.
+
+
+
+
+ Implementation version, e.g. 2020.02
+
+
+
+
+ Build type, e.g. stable, development
+
+
+
+
+ Build number (also known as patch number), e.g.: 123456
+
+
+
+
+ Time the build was made, e.g.: 2002-05-30T09:00:00Z
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_diag.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_diag.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_diag.xsd (revision 5924)
@@ -0,0 +1,70 @@
+
+
+
+
+
+
+ All model diagnostics output that is generated during and at the end of a run by a module should go in this file.
+
+
+
+
+ All model diagnostics output that is generated during and at the end of a run by a module should go in this file.
+
+
+
+
+
+ Each line/mesasage contains the actual text and a warning level.
+ each message/line has a level attached to it
+ 3 = info (information, all is well, e,g, :"SOBEK: program ended")
+ 2 = warn (warning information.
+ e.g. "SOBEK: high number of iterations")
+ 1 = error (critical problems. e.g. "SOBEK: no convergence")
+ 0 = fatal (full module crash. e.g. "SOBEK: ooops, what now?")
+ All levels higher than 3 are regarded as non-essential (debug) information
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+
+ Each line/mesasage contains the actual text and a warning level.
+ each message/line has a level attached to it
+ 3 = info (information, all is well, e,g, :"SOBEK: program ended")
+ 2 = warn (warning information.
+ e.g. "SOBEK: high number of iterations")
+ 1 = error (critical problems. e.g. "SOBEK: no convergence")
+ 0 = fatal (full module crash. e.g. "SOBEK: ooops, what now?")
+ All levels higher than 3 are regarded as non-essential (debug) information
+
+
+
+ Since 2020.02 date this message has been issued ISO 8601 (yyyy-mm-dd)
+
+
+
+
+ Since 2020.02 time this message has been issued ISO 8601 (hh:mm:ss.dsec e.g. 16:30:0.001)
+
+
+
+
+
+
+
+
+
+ Since 2014.01. event code used when this message is stored in the FEWS log entries table
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_samples.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_samples.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_samples.xsd (revision 5924)
@@ -0,0 +1,196 @@
+
+
+
+
+
+
+ Samples data represent data collected at a specific time at a specific location
+
+
+
+
+ Samples data represent data collected at a specific time at a specific location
+
+
+
+
+
+ Samples data represent data collected at a specific time at a specific location
+
+
+
+
+
+
+ The version of the published interface schemas
+
+
+
+
+
+ Samples data represent data collected at a specific time at a specific location
+
+
+
+
+
+
+ The header is used to specify the link to the location
+ and the contents
+
+
+
+
+
+
+ Properties that are applicable to the sample following
+
+
+
+
+
+
+
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+
+
+ The sample header is used to specify the link the sample location and the contents
+
+
+
+
+
+ Since 2019.02
+
+
+
+
+
+ date of the sample
+
+
+
+
+ Missing value definition for this Sample. Defaults to NaN if left empty
+
+
+
+
+ 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
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+ A sample table can contain an unlimited number of sample rows.
+
+
+
+
+
+ Properties that are applicable to the value following
+
+
+
+
+ unlimited number of sample rows. A table should contain at least 1 row.
+ 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.
+
+
+
+
+
+
+
+
+
+ For each row the parameter, value and qualifiers are required.
+
+
+
+
+
+
+ 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), SVS (secondary validation series), SVF (secondary validation flags)
+
+
+
+
+
+
+
+
+
+ Since version 1.21. Used for sample qualifiers.
+ qualifierId:a="AC_1"
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_tables.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_tables.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_tables.xsd (revision 5924)
@@ -0,0 +1,195 @@
+
+
+
+
+
+
+
+ Collection of tables
+
+
+
+
+ Collection of tables.
+
+
+
+
+
+ Table definition and table data
+
+
+
+
+
+ The version of the published interface schemas
+
+
+
+
+
+ Table definition and table data
+
+
+
+
+
+ The header is used to specify the link to the location
+ and the contents
+
+
+
+
+
+
+
+
+
+
+
+
+ The header is used to specify the link to the location
+ and the contents
+
+
+
+
+
+ Further clarification of the table, when the parameters and location are not enough to identify the table Multiple qualifiers are allowed, the order of the qualifiers is not significant.
+
+
+
+
+ Specifies parameter stored in table column 'a' . This parameter represents domain parameter in Fews. Values in column 'a' should be ascending.
+
+
+
+
+ Specified parameter stored in column 'b' . Columns from 'b' to 'z' correspond to a separate time series set in FEWS. All the time series sets should share the same domainParameter.
+
+
+
+
+ Columns from 'c' to 'z' are optional and specify parameters stored in these table columns
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Date this table is valid for
+
+
+
+
+
+
+
+
+ Description of (the content of) this file
+
+
+
+
+ use this field as a notebook to add comments
+
+
+
+
+ Date on which this table was
+created
+
+
+
+
+ Time on which this table was created
+
+
+
+
+ code/description of the region. Needed if the id's
+ can be the same in different regions.
+
+
+
+
+
+
+ Table column definition. Specifies which parameter is stored in a column
+
+
+
+ Parameter Id
+
+
+
+
+ Optional string that identifies the units used
+
+
+
+
+
+ Table data. At least one row must be present
+
+
+
+
+ table rows
+
+
+
+
+
+
+ Values in the columns a through z. Row must have at least columns a and b
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_timeseries.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_timeseries.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_timeseries.xsd (revision 5924)
@@ -0,0 +1,461 @@
+
+
+
+
+
+
+ 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"
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_qualifiers.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_qualifiers.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_qualifiers.xsd (revision 5924)
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Since 2019.02. Qualifier attributes
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_archive_attributes.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_archive_attributes.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_archive_attributes.xsd (revision 5924)
@@ -0,0 +1,15 @@
+
+
+
+
+
+ Defines meta data records for the archive
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_polygons.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_polygons.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_polygons.xsd (revision 5924)
@@ -0,0 +1,132 @@
+
+
+
+
+
+
+ (dynamic) polygons
+
+
+
+
+ (dynamic) polygons
+
+
+
+
+ The geographical datum for the location data.
+ Presently only WGS-1984, OS 1936 and LOCAL are recognised.
+ LOCAL indicates a local grid.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ date/time of the first event
+
+
+
+
+ date/time of the last event
+
+
+
+
+ optional descriptive name
+
+
+
+
+ ID of the upstream polygon.
+ If no id is given, this catchment is either on
+ its own or the topmost catchment in a series.
+
+
+
+
+ ID of the downstream polygon.
+ If no id is given, this polygon is either on
+ its own or the last catchment in a series.
+
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+
+
+
+
+ Optional mark identifying special points(i.e.):
+ 1 = catchment outlet
+ 2 = saddle
+ 3 = high-point
+
+
+
+
+
+ Areal weighted polygon centroid
+
+
+
+
+ X coordinate of the point (Easting)
+
+
+
+
+ Y coordinate of the point (Northing)
+
+
+
+
+ Z coordinate of the point (altitude)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Areal weighted polygon centroid
+
+
+
+
+ Optional uniform value for the area covered by this polygon for this event
+
+
+
+
+ optional polygon area
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_parameter_nodes.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_parameter_nodes.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_parameter_nodes.xsd (revision 5924)
@@ -0,0 +1,46 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Short name of parameter
+
+
+
+
+ Long descriptive name of parameter node (tooltip) Description or description
+
+
+
+
+ List of parameters that are part of this node
+
+
+
+
+ parent of this node.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_workflows.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_workflows.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_workflows.xsd (revision 5924)
@@ -0,0 +1,41 @@
+
+
+
+
+
+
+
+
+
+ Since 2015.01.
+
+
+
+
+ Since 2015.01.
+
+
+
+
+
+
+
+
+
+
+ Since 2015.01.
+
+
+
+
+ Since 2015.01.
+
+
+
+
+
+ Since 2015.01.
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/Delft_PI.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/Delft_PI.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/Delft_PI.xsd (revision 5924)
@@ -0,0 +1,37 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_filters.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_filters.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_filters.xsd (revision 5924)
@@ -0,0 +1,22 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_locations.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_locations.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_locations.xsd (revision 5924)
@@ -0,0 +1,118 @@
+
+
+
+
+
+
+ Time series location data files identify points at which specific times series exist.
+ The point is represented by X, Y and Z coordinates. Each location element of a time
+ series location file corresponds to a time series data file and consist of four elements.
+
+
+
+
+ Time series location data files identify points at which specific times series exist.
+ The point is represented by X, Y and Z coordinates. Each location element of a time
+ series location file corresponds to a time series data file and consist of four elements.
+
+
+
+
+
+
+
+
+
+
+
+ Long (descriptive) name of location (tool tip) or description
+
+
+
+
+ Short name of location for chart legend
+
+
+
+
+ Available since 2019.02.
+
+
+
+
+ Available since 2019.02.
+
+
+
+
+ Latitude of station
+
+
+
+
+ Longitude of station
+
+
+
+
+ X coordinate of station
+
+
+
+
+ Y coordinate of station
+
+
+
+
+ Z coordinate of station
+
+
+
+
+ Since 2015.01. Location Id of parent location
+
+
+
+
+ Available since 2019.02
+
+
+
+
+ Since 2017.02. Location attributes
+
+
+
+
+
+
+
+
+
+
+ Available since 2019.02
+
+
+
+
+
+
+ Available since 2019.02
+
+
+
+
+
+ Describes where and why this attribute is used
+
+
+
+
+ Describes where and why this attribute is used
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_taskruns.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_taskruns.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_taskruns.xsd (revision 5924)
@@ -0,0 +1,131 @@
+
+
+
+
+
+
+ List of task runs.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Forecast task run or regular.
+
+
+
+
+ Forecast task run is current or not. Only applies to forecasts
+
+
+
+
+ Status of run.
+
+
+
+
+ Type of state used by run.
+
+
+
+
+ Workflow identifier of forecast task run.
+
+
+
+
+ Time of execution
+
+
+
+
+ Time task run completed
+
+
+
+
+ This is the start of a forecast for a forecast run.
+ This is the time 0 of a FEWS task run.
+
+
+
+
+
+ Start time of output timeseries
+
+
+
+
+ End time of output timeseries
+
+
+
+
+ Identifier of shell server on which task was run
+
+
+
+
+ Optional: WhatIfScenario identifier used for run
+
+
+
+
+ Optional: Identifier of user that executed run
+
+
+
+
+ Descriptive text relating to taskrun
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Cold state selected and used
+
+
+ Warm state selected but not found. Cold state used
+
+
+ Warm state selected and used.
+
+
+ No state selected. Default warm state not found so default cold state used.
+
+
+ No state selected. Default state found and used. Can be either cold or warm
+
+
+ Warm state selected but not found. Cold state used
+
+
+
+
\ No newline at end of file
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_branches.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_branches.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_branches.xsd (revision 5924)
@@ -0,0 +1,103 @@
+
+
+
+
+
+
+ Branch data is used to represent linear futures such as rivers, streams and canals.
+ Each branch has an unique identifier , a name, a start and end-chainage field, a link to an upper
+ node and a link to a downstream node. A series of X, Y points
+ defines the actual branch, the first point being the upstream node,
+ the last point the downstream node.
+
+
+
+
+
+
+
+ Each branch element has a number of required elements
+ These are:
+
+ -BranchID
+ -BranchName
+ -StartChainage
+ -EndChainage
+ -UpNode
+ -DownNode
+ This definition is modified from the EUROTAS format
+
+
+
+
+
+
+
+ Each branch element has a number of required elements
+ These are:
+
+ -BranchID
+ -BranchName
+ -StartChainage
+ -EndChainage
+ -UpNode
+ -DownNode
+ This definition is modified from the EUROTAS format
+
+
+
+
+ Name of the branch
+
+
+
+
+ Chainage at the start of the branch
+
+
+
+
+ Chainage at the end of the branch
+
+
+
+
+ Upstream node id (string)
+
+
+
+
+ Downstream node ID (string)
+
+
+
+
+ Each branch must hold at least two pt (point/node) elements.
+ The maximum number of points is not limited. Each pt
+ element has two required attributes, X and Y that
+ point to a geographical location.
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+
+ Each branch must hold at least two pt (point/node) elements.
+ The maximum number of points is not limited. Each pt
+ element has two required attributes, X and Y that
+ point to a geographical location.
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_timeseriesparameters.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_timeseriesparameters.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_timeseriesparameters.xsd (revision 5924)
@@ -0,0 +1,88 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The unit of the values internally stored in the data store. By specifying a display unit you can use another unit seen by the user
+
+
+
+
+
+ Specify when the unit seen by the user is not the same as the unit of the values internally stored in the data store. Also specify
+ displayUnitConversionsId above as first element in this config file. In this unit conversions the conversion from (internal) unit to display unit should be available
+
+
+
+
+
+
+ Since 2021.02. Parameter attributes
+
+
+
+
+
+
+ Since 2018.01 parameterGroup added as attribute to parameter element
+
+
+
+
+ Since 2022.02 parameterGroupName added as attribute to parameter element
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_moduleruntimes.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_moduleruntimes.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_moduleruntimes.xsd (revision 5924)
@@ -0,0 +1,54 @@
+
+
+
+
+
+
+ List of module run times
+
+
+
+
+
+
+
+
+
+
+
+ MC ID of the module run.
+
+
+
+
+ WorkFlow ID of the module run.
+
+
+
+
+ ModuleInstance ID of the module run.
+
+
+
+
+ Expected start time of the module run execution
+
+
+
+
+ Expected completion time of the module run
+
+
+
+
+ Expected duration the module run will be in the pending state
+
+
+
+
+ Expected duration the module run will take
+
+
+
+
+
\ No newline at end of file
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_parameters.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_parameters.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_parameters.xsd (revision 5924)
@@ -0,0 +1,132 @@
+
+
+
+
+
+
+ module parameters
+
+
+
+
+ module parameters
+
+
+
+
+
+ Any number of parameters > 0
+
+
+
+
+
+
+
+ Any number of parameters > 0
+
+
+
+
+ name of the parameter
+
+
+
+
+ Actual value/content of the parameter.
+ Four data types can be used.
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+
+ Actual value/content of the parameter.
+ Four data types can be used.
+
+
+
+
+
+
+
+
+ if this is set to true the NFFS is allowed to adjust
+ this parameter.
+
+
+
+
+
+
+
+
+
+
+
+
+ maximum value allowed for this parameter
+
+
+
+
+ minimum value allowed for this parameter
+
+
+
+
+ if this is set to true the NFFS is allowed to adjust
+ this parameter.
+
+
+
+
+ Optional step size hint for model calibration.
+ Only used if allowAdjust = 1
+
+
+
+
+
+
+
+
+
+
+
+
+ maximum value allowed for this parameter
+
+
+
+
+ minimum value allowed for this parameter
+
+
+
+
+ if this is set to true the NFFS is allowed to adjust
+ this parameter.
+
+
+
+
+ Optional step size hint for model calibration.
+ Only used if allowAdjust = 1
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_importstatus.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_importstatus.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_importstatus.xsd (revision 5924)
@@ -0,0 +1,27 @@
+
+
+
+
+
+
+ List of module run times
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_modifiers.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_modifiers.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_modifiers.xsd (revision 5924)
@@ -0,0 +1,213 @@
+
+
+
+
+
+
+
+ module parameters
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Since 2015.01. Additional user defined properties for Modifier Type. An example of a standard (non user defined) propperty would be the name
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ISO 8601 (yyyy-mm-dd)
+
+
+
+
+ ISO 8601 (hh:mm:ss.dsec e.g. 16:30:0.001)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ISO 8601 (yyyy-mm-dd)
+
+
+
+
+ ISO 8601 (hh:mm:ss.dsec e.g. 16:30:0.001)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Since 2015.01. Unique id for for this group. Id is required and must be used to retrieve the group of parameters.
+
+
+
+
+
+
+
+
+
+
+
+
+ Since 2015.01
+
+
+
+
+ Since 2015.01.
+
+
+
+
+
+
+
+
+ Since 2015.01.
+
+
+
+
+ Since 2015.01
+
+
+
+
+ Since 2015.01.
+
+
+
+
+
+
+
+
+
+
+
+ date should comply with ISO 8601 (yyyy-mm-dd) , time should comply with ISO 8601 (hh:mm:ss.dsec e.g. 16:30:0.001)
+
+
+
+
+
\ No newline at end of file
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_archive_simulatedmetadata.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_archive_simulatedmetadata.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_archive_simulatedmetadata.xsd (revision 5924)
@@ -0,0 +1,15 @@
+
+
+
+
+
+ Defines meta data records for the archive
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_mapstacks.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_mapstacks.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_mapstacks.xsd (revision 5924)
@@ -0,0 +1,145 @@
+
+
+
+
+
+
+
+
+
+ Maps stacks are time series of grid data
+
+ Three data formats are supported:
+ - usgs bil, bip
+ - pcraster native format
+ - ascii format
+
+ In the usgs format all timeSteps are in a single file. In the other two formats
+ each time step is stored in a separate file. The order of the maps is determined
+ by the file extension and the last two characters of the first part of the filename:
+
+ (e.g. evap0000.001, evap0000.002 …. evap0000.999, evap0001.000).
+
+ This limits the size of a stack of maps to 9999999.
+
+
+
+
+
+
+ Maps stacks are time series of grid data
+
+ Three data formats are supported:
+ - usgs bil, bip
+ - pcraster native format
+ - ascii format
+
+ In the usgs format all timeSteps are in a single file. In the other two formats
+ each time step is stored in a separate file. In this case it is required to indicate the position of the file number
+ by a ??? pattern. Only one pattern may exists. The number of question marks in the pattern is user defined.
+
+ e.g. pattern is evap.??? results to evap.001 …. evap.999
+ e.g. pattern is evap????.asc results to evap0001.asc …. evap9999.asc
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ If non equidistant map stacks are used the date time elements are required
+
+
+
+
+ date/time of the first event
+
+
+
+
+ date/time of the last event
+
+
+
+
+ Link to one of the three
+ supported file formats.
+ For each file another file
+ with the positions of the cell
+ centre points most be present.
+ See cells.xsd
+
+
+
+
+ Date and time of each event in the stack. This is needed for non equidistant data. The number of event elements MUST match the number of maps/profile etc
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+ Link to one of the three
+ supported file formats.
+ For each file another file
+ with the positions of the cell
+ centre points most be present.
+ See cells.xsd
+
+
+
+
+
+
+
+
+
+
+
+
+ eg:
+ temp????.???
+ See map stack description
+
+
+
+
+
+
+
+
+
+
+
+ eg:
+ temp????.???
+ See map stack description
+
+
+
+
+
+
+
+ Required file with xyz co-ordinates(lat-long) for each centre-point
+ of the grid. the format of the file is described
+ in cells.xsd
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_run.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_run.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_run.xsd (revision 5924)
@@ -0,0 +1,215 @@
+
+
+
+
+
+
+ Since 2008.03. General information about the run executed by the general adapter that is used by the pre and post adapter
+ This file generated on the fly during a pi run file export activity from the General Adapter. This file is read only for the pre and post adapters.
+ A pre or post adapter that supports pi run files only needs this pi run file at the command line argument to find all the pi files it needs to read and write.
+ Other options can be passed to the pre or post adapter by adding extra properties to the generated pi run file during export.
+
+
+
+
+
+
+
+ since 1.8, Log level compatible with log4j.
+
+
+
+
+
+ Time zone used in the exported pi files. This is also the default time zone used by the general adapter
+
+
+
+
+ Start of the run. The time of the of the state exported by the General Adapter. When there is no state exported the earliest time in any time series exported by the General Adapter will be used
+
+
+
+
+ End of the run. The latest time exported by the General Adapter
+
+
+
+
+
+ This is the start of a forecast for a forecast run
+ This is the time 0 of a FEWS task run.
+
+
+
+
+
+
+ Last time of non missing observation based on observed time series sets configured in the General Adapter.
+
+
+
+
+
+ Fully qualified path to the current working directory.
+ This is also the startup directory of an non java executable launched by the general adapter.
+
+
+
+
+ Fully qualified path to the pi parameter file exported by the
+ General Adapter before the run.
+ An active modifier is already applied to this file
+
+
+
+
+
+ Fully qualified path to the location attributes CSV file exported by the
+ General Adapter before the run.
+
+
+
+
+
+ Fully qualified path to the pi state file that describes the state exported by the General Adapter before the run.
+ In this file you can also find the state time and the paths to the actual state files
+
+
+
+
+ Fully qualified path to a pi time series file exported by the General Adapter before the run
+
+
+
+
+ Fully qualified path to a map stack file exported by the General Adapter before the run.
+ A map stack is a list of raster files for each time step.
+
+
+
+
+
+ Fully qualified path to a pi netcdf file exported by the General Adapter before the run
+
+
+
+
+
+ Fully qualified path to a pi longitudinal profiles file exported by the General before the run
+
+
+
+
+ Since 2016.01 Fully qualified path to a pi_tables file exported by the General Adapter before the model run
+
+
+
+
+ Fully qualified path to a pi_ratingcurves file exported by the General Adapter before the model run
+
+
+
+
+ Fully qualified path to a pi diagnostic file that that will be imported by the General
+ Adapter after the run . It is deleted by the general adapter before the run.
+
+
+
+
+
+ Fully qualified path to the pi state file that describes the state that will be imported by the General Adapter
+ adapter after the run
+
+
+
+
+
+ Fully qualified path to a pi time series file that will be imported by the General Adapter after the run
+
+
+
+
+
+ Fully qualified path to a pi map stack file that will be imported by the General
+ Adapter after the run. A map stack is a list of raster files for each time step.
+
+
+
+
+
+ Fully qualified path to a pi netcdf file that will be imported by the General
+ Adapter after the run
+
+
+
+
+
+ Fully qualified path to a pi longitudinal profiles file that will be imported by the GeneralAdapter after the run
+
+
+
+
+ Since 2015.01. Fully qualified path to a csv module run table file that will be imported by the General Adapter after the run
+
+
+
+
+ Kind of an extra command line argument for the pre and post adapter. This is also a
+ convenient way way to pass global properties to a pre or post adapter. An adapter is not allowed to access the
+ FEWS global.properties directly.
+ These extra options makes an additional pre or post adapter configuration file unnecessary.
+ See the documentation of the used pre and post adapter for the supported property keys with their allowed values
+
+
+
+
+
+
+
+
+
+
+
+ level designates very severe error events that will presumably lead the application to abort.
+
+
+
+
+
+
+ level designates error events that might still allow the application to continue running
+
+
+
+
+
+
+ level designates potentially harmful situations
+
+
+
+
+
+
+ level designates informational messages that highlight the progress of the application at coarse-grained
+
+
+
+
+
+
+ level designates informational messages that highlight the progress of the application at coarse-grained
+
+
+
+
+
+
+ Level designates finer-grained informational events than the debug
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_profiles.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_profiles.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_profiles.xsd (revision 5924)
@@ -0,0 +1,80 @@
+
+
+
+
+
+
+ Longitudinal profiles
+
+
+
+
+ Longitudinal profiles
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ date/time of the first event
+
+
+
+
+ date/time of the last event
+
+
+
+
+
+ since version 1.6
+ date/time of the profile. By default the forecastDate equals the startDate
+
+
+
+
+ Each profile can hold one or more events). A single profile just holds one event. A date and time attribute must be specified
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+ Each profile can hold an (unlimited) number of
+ X, Y, and Z points representing the surveyed location and elevation
+
+
+
+ chainage along the branch
+
+
+
+
+
+
+
+
+ Each profile can hold an (unlimited) number of
+ X, Y, and Z points representing the surveyed location and elevation
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_crosssections.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_crosssections.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_crosssections.xsd (revision 5924)
@@ -0,0 +1,136 @@
+
+
+
+
+
+
+ Cross sections are measured locations along a branch,
+ where a surveyed cross section is located. This data type includes
+ a unique identifier, the branchID it is associated with,
+ and the chainage or location along the branch.
+
+
+
+
+ Cross sections are measured locations along a branch,
+ where a surveyed cross section is located. This data type includes
+ a unique identifier, the branchID it is associated with,
+ and the chainage or location along the branch.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Label of cross section - this links to the branch and also to the longitudinal profile
+
+
+
+
+ Geographic coordinate (Easting) of cross section
+
+
+
+
+ Geographic coordinate (Northing) of cross section
+
+
+
+
+ Coordinate of the left bank point (cross section coordinate)
+
+
+
+
+ Coordinate of the right bank point (cross section coordinate)
+
+
+
+
+ Coordinate of the thalweg point (cross section coordinate)
+
+
+
+
+ Elevation of the left bank point
+
+
+
+
+ Elevation of the right bank point
+
+
+
+
+
+
+ Each cross section can hold an (unlimited) umber of
+ X and Z point representing the surveyed location and elevation
+ along the cross section and two attributes describing the
+ resistance and mark
+
+
+
+
+ use this field as a notebook to add comments, suggestions
+ description of data entered etc.
+
+
+
+
+
+
+ Each cross section can hold an (unlimited) umber of
+ X and Z point representing the surveyed location and elevation
+ along the cross section and two attributes describing the
+ resistance and mark
+
+
+
+ cross section point distance co-ordinate
+
+
+
+
+ cross section point elevation
+
+
+
+
+ This assigns roughness to each point
+ in the cross section.
+
+
+
+
+ Indicators used to define points of interest
+ (i.e. thalweg, left bank)
+
+
+
+
+ geographical X co-ordinate
+
+
+
+
+ geographical Y co-ordinate
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_ratingcurves.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_ratingcurves.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_ratingcurves.xsd (revision 5924)
@@ -0,0 +1,276 @@
+
+
+
+
+
+
+
+ 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
+
+
+
+
+
+ Rating curve applicable form start date to end date
+
+
+
+
+
+ The version of the published interface schemas
+
+
+
+
+
+ Rating curve
+
+
+
+
+
+ The header is used to specify the link to the location
+ and the contents
+
+
+
+
+
+
+
+
+
+
+
+ Since 2017.02 Power type equation Discharge = cr ( stage - a )^beta
+
+
+
+
+ Since 2019.02. A rating curve which is only available during a period (season) of the year
+
+
+
+
+
+
+
+
+
+ Start month and day of this season.
+
+
+
+
+ End month and day of this season.
+
+
+
+
+
+ Since 2017.02 Power type equation Discharge = cr ( stage - a )^beta
+
+
+
+
+
+
+
+ the name of the season
+
+
+
+
+
+ The header is used to specify the link to the location
+ and the contents
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+ Date this rating curve becomes active
+
+
+
+
+ Date this rating curve is replaced by a new one
+
+
+
+
+ Optional long (descriptive) name
+
+
+
+
+ Station name
+
+
+
+
+ String that identifies the stage unit used
+
+
+
+
+ String that identifies the stage units used
+
+
+
+
+
+
+ Description of (the content of)
+ this file
+
+
+
+
+ use this field as a notebook to add comments
+
+
+
+
+ Date on which this rating curve was
+ created
+
+
+
+
+ Time on which this rating curve was created
+
+
+
+
+ code/description of the region. Needed if the id's
+ can be the same in different regions.
+
+
+
+
+ Since 2023.01 Properties applicable to this rating curve
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Minimum allowable stage to which Rating Curve may be extended at the lower end;
+
+
+
+
+
+
+ Maximum allowable stage to which Rating Curve may be extended at the upper end;
+
+
+
+
+
+
+ stage/ discharge pair
+
+
+
+
+
+
+
+
+
+
+
+ Stage value.
+
+
+
+
+ Discharge value.
+
+
+
+
+ Offsets to shift the Rating Curve so that it is a straight line on a logarithmic plot. By default the offset for the previous row is used
+
+
+
+
+ Quality flag assigned to converted value. 3 = doubtful, 6 = unreliable
+
+
+
+
+
+ Power type equation.
+ Discharge = cr ( stage - a )^beta + Q0
+ Stage = (discharge/cr)^(1/beta) + alpha
+
+
+
+ Minimum stage for which this equation is valid
+
+
+
+
+ Maximum stage for which this equation is valid.
+
+
+
+
+ Quality flag assigned to results of this equation 3 = doubtful, 6 = unreliable
+
+
+
+
+ Stage corresponding to zero discharge
+
+
+
+
+ Coefficient
+
+
+
+
+ Coefficient
+
+
+
+
+ Q0 in units specified with dischargeUnit. If no dischargeUnit is configured, in m3/s. The default value is 0
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_archive_externalnetcdfstorageforecasts.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_archive_externalnetcdfstorageforecasts.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_archive_externalnetcdfstorageforecasts.xsd (revision 5924)
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Defines meta data records for the archive
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_latinputs.xsd
===================================================================
diff -u
--- DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_latinputs.xsd (revision 0)
+++ DamClients/DamLive/trunk/xsd/fews-pi-schemas/pi_latinputs.xsd (revision 5924)
@@ -0,0 +1,66 @@
+
+
+
+
+
+
+ Lateral (or BranchBoundary inputs)
+
+
+
+
+ Lateral (or BranchBoundary inputs)
+
+
+
+
+
+
+
+
+
+
+
+ A constant value for the lateral discharge
+
+
+
+
+ A key combination to link to a TimeSeries
+
+
+
+
+
+
+
+
+
+
+
+ ID of this lateral input
+
+
+
+
+ Geographical co-ordinate (Easting)
+
+
+
+
+ Geographical co-ordinate (Northing)
+
+
+
+
+ ID of the branch this lateral input
+ is located on
+
+
+
+
+ The chainage of the lateral discharge
+
+
+
+