Page tree
Skip to end of metadata
Go to start of metadata

Release Remarks

 

Delft-FEWS 2017.02 New Features
KeyComponent/sSummaryRelease Note TextRelease Note Text DescriptionConfig ExampleLink to DocumentationCustomer name
FEWS-17763App - Admin Web User InterfaceFEWS-16767 Test AI functionality with new database schema changes Deltares
FEWS-17115App - Admin Web User InterfaceAI should check jdbc driver versionThe system status page provides a warning when an older jdbc driver is used and provides a tooltip when all is well.There have been some problems with older jdbc drivers, and they have been replaced in the master-controller. However the jdbc drivers in the admin interface might also need updating. The migration update procedure now also includes a version check of the jdbc driver in tomcat where the admin interface is running. The system status page now warns if this step was not executed properly as a precaution. Jdbc driver versions postgres 42 and oracle 12.2 are now required (included in master-controller lib directory). Deltares
FEWS-16904App - Admin Web User InterfaceFEWS-16887 NWS: #24695 AI scheduled tasks should be MC-specificAllow downloading tasks for the current MC onlyThe admin interface has been extended to support downoading tasks for the current MC only. The following scheduled tasks actions are now available: Download Scheduled Tasks: All Current MC NWS
FEWS-18268App - Admin Web User InterfaceFEWS-16767 AI: additional functionalitiesAdmin Interface displays status for synchronization, rolling barrel, system alerter and task runsAdmin Interface displays status for synchronization, rolling barrel, system alerter and task runs Deltares - Roadmaps
FEWS-18523App - Admin Web User InterfaceFEWS-16767 AI: Add button to update schema modification time to force rebuilding cache files.AI: Add button to update schema modification time to force rebuilding cache files.SystemControl now has a button to force clear cache on FSSs. Deltares - Roadmaps
FEWS-17527App - ArchiveVerify that the export to the archive is successful Deltares - Roadmaps
FEWS-17660App - Archiveremove dependency from tomcat for archive backendthe architecture of the archive is simplifiedTo make it easier to write unit tests for the archive the architecture is now simplfiied. It is now possible to start the core of the archive server without tomcat. This will make it easier to write unit tests and develop new functionality. Deltares - Roadmaps
FEWS-17385App - ArchiveFEWS-17266 TVA: webservice request for checkbox to allow filtering on data typeonlyForecasts can be used to only get forecast time series from the pi serviceonlyForecasts can be used to only get forecast time series from the pi service TVA
FEWS-17477App - ArchiveCache elastic search queries only for the requesting threadcode improvement for the seamless integrationTo improve the performance of the seamless integration requests are cached. The results are now stored in cache specific for the requesting thread. Deltares
FEWS-18018App - ArchiveFEWS-14334 Verify exported metadata file for simulated datasetsadditional check in archive exportTo ensure that the data is exported correctly to the archive an additional check is added. The export will now verify that all exported netcdf-files are listend in the metaData.xml file. Deltares
FEWS-16882App - ArchiveFEWS-15003 make it possible to access elastic catalogue by the piwebserviceaccess the elastic catalogue by the pi webserviceIn the future it will be possible to access the elastic catalogue by the pi webservice. In this release a temporary version is available. It is mainly used for demo and evaluating purposes and will be extended later to final production version. BPA
FEWS-18364App - Archive, Plugin - Gui - System MonitorFEWS-14334 Open Archive status in SystemMonitorArchive Server Status in SystemMonitorWhen Fews is connected to Archive version 2017.02 or higher, then the status of the Archive is shown in a separate tab “Archive Server Status” in SystemMonitor. The picture ArchiveStatus.png shows an example of this tab.
FEWS-17898App - Configuration Manager Gui, DatabaseFEWS-16767 Migrate default config tables to default config synch levelDatabaseInitialization tool migrates default config tablesThe DatabaseInitialization tool will migrates default config tables by setting synchlevel 11 for the corresponding table. After completion the default config tables will be deleted. https://publicwiki.deltares.nl/display/FEWS2020/Database+InitializationToolDeltares - Roadmaps
FEWS-16447App - Data Conversion ModuleDCM Export: MeteoAlarm RWS
FEWS-14305App - Delft-FEWSFEWS-16767 Remove JMS from OC Deltares - Roadmaps
FEWS-18702App - Master Controller Server, DatabaseFEWS-16767 Reduce number of database connections per OC/FSS/PI to 4 Deltares - Roadmaps
FEWS-17355App - Master Controller Server, DatabaseFEWS-16767 Create MC datasource Deltares - Roadmaps
FEWS-17900App - Master Controller ServerFEWS-16767 Remove populater Deltares - Roadmaps
FEWS-17516App - Master Controller ServerFEWS-16767 Implement Delft_SQL.jar in MC code Deltares - Roadmaps
FEWS-17764App - Master Controller ServerFEWS-16767 MC initialisation Deltares - Roadmaps
FEWS-18240App - Master Controller ServerFEWS-16767 System Alerter and Log Processor Deltares - Roadmaps
FEWS-17560App - Master Controller ServerFEWS-16663 Quebec - Eliminate plain-text database password in fews.master.mc.confMake it possible to use encryptedPassword in fews.master.mc.confConfigurator can now generate a fews.master.mc.conf with a encryptedPassword for the database connection{code} <dbServer> <!-- The central database server type (oracle, postgresql, sqlserver (=sqlserverjtds), sqlserverjtds (SQL Server using the jtds jdbc driver) or sqlserverms (SQL Server using the Microsoft jdbc driver)) --> <dbServerType>postgresql</dbServerType> <!-- The server name or IP address of the central database server. --> <dbServerName>dbserver01.deltares.nl</dbServerName> <!-- Optional database port if non-standard. Assumed are 1521 for Oracle, 5432 for PostgreSQL, 1433 for SQL Server. --> <!-- <dbServerPort>5432</dbServerPort> --> <!-- The database instance ID. --> <dbInstanceName>nlwl00</dbInstanceName> <!-- The database user name. --> <dbInstanceUser>nlwl00</dbInstanceUser> <!-- The database user's password. --> <dbInstancePassword>password</dbInstancePassword> <!-- Option to produce encrypted password --> <dbEncryptPassword>true</dbEncryptPassword> </dbServer> {code} Quebec
FEWS-17899App - Master Controller Server, DatabaseFEWS-16767 Implement deletion of rows using DeletedRows and ProcessedDeletedRows tables (replace marked record manager)Distributed deletion of rows has been implemented using the new DeletedRows and ProcessedDeletedRows tables. see also section on RollingBarrel in https://publicwiki.deltares.nl/display/FEWS2020/Implementation+process Deltares - Roadmaps
FEWS-16299App - Operator Client Gui (Explorer)FEWS-17266 TVA: ability to minimize undocked windows TVA
FEWS-16897App - Operator Client Gui (Explorer)FEWS-17266 TVA: F12 option to remove cache files without having to restart client manually TVA
FEWS-17057App - Operator Client Gui (Explorer)Add re-scale option while using expression filter GO-FEWS (Selection of Dutch Waterboards)
FEWS-18313App - Operator Client Gui (Explorer)FEWS-16767 Rolling Barrel Implementations SA / OC Deltares - Roadmaps
FEWS-18269App - Operator Client Gui (Explorer)FEWS-16767 OC System Monitor: add mc-mc synch metrics Deltares - Roadmaps
FEWS-18242App - Operator Client Gui (Explorer), DatabaseFEWS-16767 Remove on demand blob download Deltares - Roadmaps
FEWS-17848App - Operator Client Gui (Explorer)FEWS-16132 HERMES: Today Button Zoom to System Cardinal Time in SA BPA
FEWS-17600App - Operator Client Gui (Explorer)FEWS-17202 Smart labeling for polylinessmart labeling for line shapelayersInstead of a single fixed label location, labels for line shapelayers are now displayed at the line and will move along the line when the view window is adjusted. Note: FEWS-17802 allows for this new behavior to be turned off through the layer configuration. APP
FEWS-17599App - Operator Client Gui (Explorer)FEWS-17202 Option to make labels invisibleoption to make labels invisible in layer selection panel (moved color change options)When you right-click a layer in the layer selection panel, an option will be available to turn off/on the labels for that label (when applicable). The already present functionality to change the fill and line color of layers was moved from the double-click menu to this new right-click menu. APP
FEWS-17598App - Operator Client Gui (Explorer)FEWS-17202 Option to show legend for background layer (eg DTM)layer selection panel is displayed as legend next to map and contains legend images for wms layersThe layer selection panel was moved from a separate pop-up menu to a panel displayed to the right of the map when toggled. For WMS layers a legend image is downloaded and displayed in this panel (when available), similar to how it already contained a legend for layers with classbreaks. APP
FEWS-16969App - Operator Client Gui (Explorer)FEWS 64 bit OC starts really slowknown issue: 64b JRE does not contain client caching. Might take longer to startup OC using 64b Deltares
FEWS-17821App - Operator Client Gui (Explorer)FEWS-17521 Expand/shrink selection functionality unclearclearer expand/shrink selection windowMore text was added to the expand/shrink selection box, to make the possible entries clearer. Deltares
FEWS-17556App - Operator Client Gui (Explorer)FEWS-17202 Add button to show last value in exploreradded button to change location labels to map displayAdded a drop-down button to the map display to allow selecting whether the last value should be displayed in the labels. The functionality is similar to the label button already present in the spatial / grid display. APP
FEWS-17654App - Operator Client Gui (Explorer)FEWS language: add Vietnamese as user language (GUI)add Vietnamese to language optionsLanguage files for Vietnamese were added to FEWS. Provinces Vietnam
FEWS-18435App - Operator Client Gui (Explorer)Store system time in user_settings.ini for SAStore system time in user settings for Stand AloneThe system time of a stand alone is now stored in and read from the user settings, if and only if <adjustSystemTimeAutomatically> is set to false. Note that this is the default for stand alone environments. Set this element (found in explorer.xml -> <dateTime>) to true for a stand-alone environment in which the system time should be adjusted to the actual time automatically. For stand alone environments in which this is not configured, the new default behavior will be that the system time is only changed when adjusted manually, and no longer updated to the current time on start-up. Note that the value stored in the user settings will be overruled if a T0 is configured in the global properties. https://publicwiki.deltares.nl/display/FEWSDOC/01+FEWS+Explorer#id-01FEWSExplorer-adjustSystemTimeAutomaticallyDeltares
FEWS-18416App - Operator Client Gui (Explorer)Split location counter (data viewer) in main and sublocationsLocation counter in data viewer is split between parent and child locationsWhen the time navigator toolbar is enabled in the explorer, a location count is shown in the data viewer. This count has now been split in two separate counts: the number of parent locations and the number of child locations. HDSR
FEWS-17281App - Operator Client Gui (Explorer)Embedded PDF viewer default print format A4Embedded PDF print changed default format from Letter to A4
FEWS-18385ConfigurationFEWS-14299 IdMap. Allow multi value attributes for parameterIdFunction
FEWS-18147ConfigurationCustom hourly timestep at half hours (e.g. 00:30, 01:30, 02:30)new timestep at specified minutes of each hourA new possibility for defining a <timeStep> was added. The minutes attribute can be used to specify minute offsets for each hour. For example <timeStep minutes="15 50"/> will result in steps at 0:15, 0:50, 1:15, 1:50, etc.{code:xml} <timeStep minutes="15 50"/> <!-- 0:15, 0:50, 1:15, 1:50, etc. --> {code}https://publicwiki.deltares.nl/display/FEWSDOC/26+TimeSteps#id-26TimeSteps-Otherexamples
FEWS-16983Configurationclient.truststore improvementsclient.truststore can be configured in the clientConfig.xmlThe clientConfig.xml can now be used to explicitly configure the client.truststore and client.keystore using a custom name and location. If the configured files are not found, a config error will be logged. For backwards compatability the client.truststore and client.keystore will still be used if no clientConfig.xml configuration was found.{code} <?xml version="1.0" encoding="UTF-8"?> <clientConfiguration xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/clientConfig.xsd"> <localDataStoreFormat>Derby</localDataStoreFormat> <clientStore> <trustStoreFile>%REGION_HOME%/client.truststore</trustStoreFile> <keyStoreFile>%REGION_HOME%/client.keystore</keyStoreFile> </clientStore> </clientConfiguration> {code}https://publicwiki.deltares.nl/display/FEWSDOC/How+to+configure+secure+https+connection+to+MatroosDeltares
FEWS-16883DatabaseFEWS-16887 NWS: #28627 Sequence table incorrect after database rebuild and initial MC_synchronisation NWS
FEWS-18365DatabaseExpand the taskTag column in the Tasks table to 146 characters so workflowId and taskTag do not need to be chopped anymore Deltares - Roadmaps
FEWS-17353DatabaseFEWS-16767 Create new table ForecastingShells Deltares - Roadmaps
FEWS-16876DatabaseFEWS-16767 Add globalRowId column to all tables Deltares - Roadmaps
FEWS-17647DatabaseFEWS-16767 Database time provider in extended datasource Deltares - Roadmaps
FEWS-18237DatabaseFEWS-16767 Add integer build number column to log entries table Deltares - Roadmaps
FEWS-17575DatabaseOptimize Snapshot / Replicate functionality {code:xml} <?xml version="1.0" encoding="UTF-8"?> <exportArchiveModule xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/exportArchiveModule.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews"> <exportSnapShot> <general> <archiveFolder>$ARCHIVE_DIR$</archiveFolder> </general> <activities> <exportSnapShot> <areaId>test</areaId> <filter id="only time series"> <xmlConfig enabled="false" name="Default xml config" synchLevel="11"/> <coldStates enabled="false" name="Default cold states" synchLevel="11"/> <moduleDataSets enabled="false" name="Default module data sets" synchLevel="11"/> <mapLayers enabled="false" name="Default map layers" synchLevel="11"/> <icons enabled="false" name="Default icons" synchLevel="11"/> <reportTemplates enabled="false" name="Default report templates" synchLevel="11"/> <reportImages enabled="false" name="Default report images" synchLevel="11"/> <continuousTimeSeries enabled="true" name="Simulated" synchLevel="0" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Telemetry" synchLevel="1" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Manual" synchLevel="5" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Astronomical and climatological" synchLevel="4" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Small external forecast grids" synchLevel="6" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Large external forecast grids" synchLevel="16" maxAge="10000" unit="week"/> <warmStates enabled="false" name="Warm states" maxAge="10" unit="week"/> <logEntries enabled="false" name="Log Entries" maxAge="1" unit="week"/> <thresholdEvents enabled="false" name="Threshold Events" maxAge="1" unit="week"/> </filter> </exportSnapShot> </activities> </exportSnapShot> </exportArchiveModule> {code} Deltares
FEWS-18432DatabaseFEWS-16767 Always use sequences when inserting system activities Deltares - Roadmaps
FEWS-17885DatabaseIndexing TaskRunCompletion table is slow D-USA
FEWS-18411DatabaseFEWS-16767 Connection namingname all database connections based on component namename all database connections based on component name Deltares - Roadmaps
FEWS-17175DatabaseFEWS-16315 Add nullable exportTime column to ThresholdEvent tableThe ThresholdEvents table has a new exportTime column. BoM
FEWS-17354DatabaseFEWS-16767 Replace Sequences table with 4 database sequencesSequence tables replaced by actual database sequences which are simpler and more efficientSequence tables replaced by actual database sequences which are simpler and more efficient Deltares - Roadmaps
FEWS-18051DatabaseFEWS-14299 FFFS: Add power function to time series rating curvesRating curve with stageToDischargePowerEquationstageToDischargePowerEquation represents the equations discharge = cr * (stage - alpha)^ beta where ‘cr’ and ‘beta’ are rating curve constants, and ‘alpha’ is a constant which represents the stage corresponding to zero discharge. To show the stageToDischargePowerEquation rating curves in the TimeSeriesDisplay, a table is generated on the fly from the power equations. For each equation ten stage values are generated using increment (max stage – min stage) /10 , and for each stage a discharge is computed. Please note that this table is only used in the display and not in TransformationModule computations. Example from pi_ratingcurves.xml {code:xml} <ratingCurve> <header> <locationId>LocA</locationId> <startDate date="2011-01-01" time="00:00:00"/> <stationName>LoccationA</stationName> <stageUnit>m</stageUnit> <dischargeUnit>m3/s</dischargeUnit> </header> <stageToDischargePowerEquation minStage="0.02757" maxStage="0.5" cr="8.8605" alpha="0.02757" beta="1.8032"/> <stageToDischargePowerEquation minStage="0.5" maxStage="10.0" cr="8.8605" alpha="0.02757" beta="1.8032"/> <stageToDischargePowerEquation minStage="10.0" maxStage="999.0" flag="3" cr="17.7210" alpha="0.02757" beta="1.8032"/> </ratingCurve> {code} EA
FEWS-18238DatabaseFEWS-16767 Implement Maintenance ModeMaintenance mode supportFrom the admin interface maintenance mode can be started or stopped. When in mainenance mode other FEWS components aren't allowed to write to the database. Deltares - Roadmaps
FEWS-17101Debug Tool - Workflow NavigatorWFN should check if all referenced properties are availableWFN check of transformation module expressionsWFN checks to see if the variables and coefficients, referenced in the expressions , are defined. When any expression variable or coefficient is not defined , then the transformation module node is marked with a red cross . Using menu “Show messages” the popup can be opened that shows the undefined variables and/or coefficients. See picture WFN.png Deltares
FEWS-18635DocumentationFEWS-17521 Check with ICT-OS what Database recovery mode means
FEWS-18633DocumentationFEWS-17521 Check how OC logging is written to, read from and acknowledged from central database
FEWS-17399Module Adapter - AllUpgrade wanda adapter with new dll-s Deltares
FEWS-18247Module Adapter - AllFEWS-16663 Québec: Hydrotel AdapterCreated pre and post adapter for Hydrotel model https://publicwiki.deltares.nl/pages/viewpage.action?pageId=132449418MDDELCC (Quebec)
FEWS-17003Module Adapter - CalibrationFEWS-16887 NWS: #34172 (b) CHPS Calibration: MapLayers CSV Compatibility for model parametersModified location attribute parameters can be visualized in the tabular config file displayModified location attribute parameters can be visualized in the tabular config file display. Marking the the "Show modified values" checkbox will show the changed values and highlight the background in blue. The modified values can be exported to CSV> NWS
FEWS-17504Plugin - Gui - Forecast ManagerForecast management dialog: add extra column with runtime of workflow Nationaal Water Model
FEWS-17883Plugin - Gui - Grid DisplayFEWS-17145 GridDisplay - Mask (or erase) coarse model results in areas with detailed model results {code:xml} <locationSet id="wave_EAM_clipper.shp"> <esriShapeFile> <file>wave_EAM_clipper.shp</file> <id>EAM.Wave</id> <x>0</x> <y>0</y> </esriShapeFile> </locationSet> {code} remove the EAM.Wave from the locations.xml
FEWS-16905Plugin - Gui - Grid DisplayFEWS-16887 NWS: #24896 Spatial Display time-slider snapped to moving accumulation time step {code:xml} </dataLayer> <accumulationTimeStep unit="minute" multiplier="30"/> <accumulationTimeStep unit="hour" multiplier="1"/> <accumulationTimeStep unit="hour" multiplier="3" timeZone="CST"/> <accumulationTimeStep unit="hour" multiplier="6" timeZone="CST"/> <accumulationTimeStep id="12Z"/> <classBreaks> {code} NWS
FEWS-17462Plugin - Gui - Grid DisplayShow time series set locations instead of related in spatial display FEWS Sava
FEWS-17149Plugin - Gui - Grid DisplayFunctionality to show a fixed logo at grid product, like EUMETSAT H-SAF The image file should be placed in the MaplayerFiles directory{code:xml} <gridPlot id="Precipitation"> <timeSeriesSet> <moduleInstanceId>Import_NWP</moduleInstanceId> <valueType>grid</valueType> <parameterId>P.fc</parameterId> <qualifierId>aladin_hr</qualifierId> <locationId>NWP_ALADIN_HR</locationId> <timeSeriesType>external forecasting</timeSeriesType> <timeStep unit="hour"/> <relativeViewPeriod unit="day" start="-5" end="10"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> <logo> <imageFile>logo.png</imageFile> <position>topRight</position> </logo> <classBreaksId>Precipitation_1h</classBreaksId> <contourLinesColor>gray</contourLinesColor> </gridPlot> {code}https://publicwiki.deltares.nl/display/FEWSDOC/01+Grid+DisplayFEWS Sava
FEWS-17837Plugin - Gui - Grid DisplayLastValue checkbox in spatial display default settingstore "last value" checkbox status from spatial display in the user settingsThe status of the "last value" checkbox in the spatial display is now stored in the user settings. When FEWS is restarted, the checkbox will still be checked/unchecked like it was when FEWS was exited. APP
FEWS-17208Plugin - Gui - Grid DisplayFEWS-17202 Make labels of background layers configurablenew label formatting options for shape-layersFor shape-layers (esriShapeLayer and serverShapeLayer), several new elements are available to format the labels: * labelFontSize * labelFontColor * labelBackgroundColor * labelOpaqueness (opaqueness of the background color) * labelBorderColor * labelAtLine (controls whether smart labeling is used for lines, see FEWS-17600) * labelXAttribute & labelYAttribute (allow defining label coordinates in the shape files){code:xml} <esriShapeLayer id="myPrettyLabelLayer"> <file>layerFile</file> <label>%labelColumn%</label> <labelFontSize>15</labelFontSize> <labelFontColor>blue</labelFontColor> <labelBackgroundColor>red</labelBackgroundColor> <labelOpaqueness>20</labelOpaqueness> <labelBorderColor>black</labelBorderColor> <labelXAttribute>labelXColumn</labelXAttribute> <labelYAttribute>labelYColumn</labelYAttribute> <lineColor>gray90</lineColor> <fillColor>yellow</fillColor> <opaquenessPercentage>25</opaquenessPercentage> </esriShapeLayer> {code} {code:xml} <esriShapeLayer id="noSmartLineLabels"> <file>Contour</file> <label>%CONTOUR%</label> <labelAtLine>false</labelAtLine> <lineColor>light goldenrod yellow</lineColor> <lineWidth value="2"/> </esriShapeLayer> {code}https://publicwiki.deltares.nl/display/FEWSDOC/GeoMap#GeoMap-CommonShapeLayerElementsAPP
FEWS-17845Plugin - Gui - Grid DisplayMousepointer does not show calculation symbol when hovering on mapmouse pointer shows hourglass symbol when hovering over mapThe mouse pointer will now show an hourglass symbol when hovering over the map when FEWS is still calculating, similar to how the hourglass symbol was already shown when hovering outside of the map. Deltares
FEWS-17990Plugin - Gui - Grid DisplayFEWS-17202 Enable classification of point layers in geoMapenable classification for point layers in geoMapIt is now possible to configure a classification for point shapelayers using icons.{code:xml} <esriShapeLayer id="VenH Lozingspunten" name="VenH Lozingspunten"> <file>VenH_lozingspunten.shp</file> <pointIconId>meteo_site_data.gif</pointIconId> <classBreaksAttributeName>OWA_OWA_ID</classBreaksAttributeName> <classBreaks> <break lowerValue="0" label="red" icon="meteo_site_data.gif"/> <break lowerValue="1000" label="blue" icon="meteo_site_data_blue.gif"/> </classBreaks> </esriShapeLayer> {code}https://publicwiki.deltares.nl/display/FEWSDOC/GeoMap#GeoMap-CommonShapeLayerElementsAPP
FEWS-17986Plugin - Gui - Grid DisplayFEWS-17202 Add MapExtentId to Gridplotcouple zoom extent to grid plotIt is now possible to configure a mapExtentId for grid plots, the map will then automatically select the configured zoom extent when the grid plot is selected in the spatial display. The mapExtentId can be coupled to specific grid plots or defaults can be used to configure the same mapExtentId for several grid plots at once.{code:xml} <defaults> <plotGroupId>Rainfall_obs</plotGroupId> <mapExtentId>New South Wales</mapExtentId> </defaults> {code} {code:xml} <gridPlot id="Peilschaal" name="Peilschaal"> <mapExtentId>Jambi</mapExtentId> <dataLayer> <circleBorderSize>1</circleBorderSize> <timeSeriesSet> <moduleInstanceId>Process_WMMS_auto</moduleInstanceId> <valueType>scalar</valueType> <parameterId>WL.obs</parameterId> <locationSetId>WaterLevel_RiauSMF</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep id="Week"/> <relativeViewPeriod unit="week" start="-4" end="0" startOverrulable="true"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </dataLayer> <classBreaksId>WaterLevel</classBreaksId> </gridPlot> {code} https://publicwiki.deltares.nl/display/FEWSDOC/01+Grid+DisplayAPP
FEWS-17850Plugin - Gui - Grid DisplayFEWS-17145 GridDisplay configuration optimization using multiple grid partitionsWhen DFlow FM model results have been imported for multiple computational domains, the 2D or 3D data can be displayed in Grids.xml by making use of a LocationSet containing all partition locationIds.When 2D or 3D data is imported using multiple domain partitions, this data can be displayed in Grids.xml making use of LocationSets. Create a LocationSet including the LocationId for all partitions. This LocationSet can be used consistently throughout the gridDisplay configuration, like when displaying: * 2D data, e.g. water level * 3D data, e.g. a combination of uTimeSeriesSet, VTimeSeriesSet and sigmaScaleReferenceTimeSeriesSet * 3D data, e.g. a combination of timeSeriesSet (e.g. temperature) and sigmaScaleReferenceTimeSeriesSet<gridPlot id="3D_data" name="3D data display"> <dataLayer> <arrowColor>white</arrowColor> <arrowSymbol>flow</arrowSymbol> <multipleArrowsPerValue>false</multipleArrowsPerValue> <uTimeSeriesSet> <moduleInstanceId>DFlowFM_FC</moduleInstanceId> <valueType>grid</valueType> <parameterId>C.simulated.u</parameterId> <locationSetId>DFlowFM_0_####</locationSetId> <timeSeriesType>simulated forecasting</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read complete forecast</readWriteMode> </uTimeSeriesSet> <vTimeSeriesSet> <moduleInstanceId>DFlowFM_FC</moduleInstanceId> <valueType>grid</valueType> <parameterId>C.simulated.v</parameterId> <locationSetId>DFlowFM_0_####</locationSetId> <timeSeriesType>simulated forecasting</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read complete forecast</readWriteMode> </vTimeSeriesSet> <uvAmplitudeParameterId>C.simulated.speed</uvAmplitudeParameterId> <uvDirectionParameterId>C.simulated.dir</uvDirectionParameterId> <sigmaScaleReferenceTimeSeriesSet> <moduleInstanceId>DFlowFM_FC</moduleInstanceId> <valueType>grid</valueType> <parameterId>WD.simulated</parameterId> <locationSetId>DFlowFM.merged</locationSetId> <timeSeriesType>simulated forecasting</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read complete forecast</readWriteMode> </sigmaScaleReferenceTimeSeriesSet> </dataLayer> <barLegend> <position>right</position> <width>50</width> <length>400</length> <labelsInside>true</labelsInside> </barLegend> <classBreaksId>Class.Currents</classBreaksId> <contourLinesColor>antique white</contourLinesColor> </gridPlot> Deltares
FEWS-18289Plugin - Gui - Grid DisplayFEWS-17145 Hide "Last Value" box in grid display when not applicableAdded configuration option to hide the last value checkbox in the GridDisplayThe last value checkbox in the GridDisplay can now be hidden through configuration. Documentation on the new configuration option and the functionality of the last value checkbox was added to the wiki. https://publicwiki.deltares.nl/display/FEWSDOC/01+Grid+Display#id-01GridDisplay-Accumulation/MovingAveragesliderorLastValueCheckbox
FEWS-17973Plugin - GUI - IFD - Forecaster HelpList of 'Product' doesn't refresh after a task/node has finished runningForecaster help selection panel selection panel is improvedThe forecaster help selection panel gives an overview of the files which are available for a certain topology node to help the forecaster. After selection of a file the content will be displayed in the forecaster documentation panel. It is possible to show the content of multiple folders for each separate node. If the content of these folders is changed the selection panel will now always refresh its content. RWS
FEWS-12981Plugin - Gui - MapFEWS-14893 FOEN-DEV: Add feature to disable threshold icons in Filters and Map displaynew button in the map display which can disable threshold iconsA new button was added to the map display to turn the threshold icons for the locations on and off. Turning the threshold icons off allows the validation icons to become visible. FOEN
FEWS-18286Plugin - Gui - Map, Plugin - Module - ReportsFEWS-17145 Link location-specific reports to Map viewerAdded option to link a report to locationsLocations can now be linked to a specific report. When configured, if the location is selected, the linked report will be automatically selected in the ForecasterAidSelectionPanel. Note that the report must already be present in the list of reports in this panel. Information on the configuration of these feature is available on the wiki. https://publicwiki.deltares.nl/display/FEWSDOC/27+Forecaster+Aid+Selection+Panel
FEWS-18214Plugin - Gui - Schematic Status DisplayFEWS-17521 Context menu - save as - error when extension not entered Deltares
FEWS-16812Plugin - Gui - Schematic Status DisplaySSD, switching between panels with different timestep causes loss of time definitionTime slider activation button can be configured to toggle between active and inactive timesliderTime navigator toolbar activation button can be configured to toggle between active and inactive time navigator. When the time navigator is set to inactive, the behaviour is equal to the case where no navigator toolbar was configured at all.{code} <showTimeNavigatorToolbar> <timeNavigatorRelativePeriod unit="day" start="-30" end="0"/> <activate>false</activate> <showTimeNavigatorActivationToggle>true</showTimeNavigatorActivationToggle> </showTimeNavigatorToolbar> {code}https://publicwiki.deltares.nl/pages/viewpage.action?pageId=8684020RWS (NL)
FEWS-17490Plugin - Gui - Schematic Status DisplayConfigurable schematic status display backgroundSchematic Status Display can have a custom background colorA Schematic Status Display can have a custom background color. The colors can be colorScheme dependent. A background color can be define on the display level, that will apply to all panels in the display. On the panel level a color can be defined as well to overrule the color on the displaylevel.Example of background color for a display. {code} <displayName>Scada Display Twenthekanalen</displayName> <showTimeNavigatorToolbar> <timeNavigatorRelativePeriod unit="day" start="-30" end="0"/> <activate>true</activate> <showTimeNavigatorActivationToggle>true</showTimeNavigatorActivationToggle> </showTimeNavigatorToolbar> <backgroundColor>[HLH_blue]</backgroundColor> {code} Example of a panel specific color: {code} <scadaPanel id="TK" name="Twenthekanalen 10 min"> <svgFile>TK_Twentekanalen_10min.svg</svgFile> <overrulingTimeNavigatorTimeStep multiplier="10" unit="minute"/> <backgroundColor>yellow</backgroundColor> {code} https://publicwiki.deltares.nl/pages/viewpage.action?pageId=8684020IWP
FEWS-18373Plugin - Gui - Schematic Status DisplayUse of attributes in SSD the 'title' of the 'leftSingleClickAction'PARAMETER tag and LOCATIONATTRIBUTE tag SSD improvementsPARAMETER tag and LOCATIONATTRIBUTE tag SSD improvements. https://publicwiki.deltares.nl/pages/viewpage.action?pageId=8684020RWS - IWP
FEWS-18080Plugin - Gui - System MonitorFEWS-14730 System Monitor Display, Import status tab - highlight selected rowSystem Monitor Display, Import status tab - highlight selected rowIf rows are selected in the table of the import status tab in the System Monitor Display, they are now highlighted. MDBA
FEWS-18418Plugin - Gui - Schematic Status Display, Plugin - Gui - Threshold DisplaySet transparency of svg elements based on a timeseriesopaquenessPercentage available for ThresholdWarningLevelsIn the ThresholdWarningLevels.xml it is now possible to configure a opaquenessPercentage. Default a value is set to 100%. {code} <thresholdWarningLevel id="4" name="Afvoer is positief, overschot"> <color>green</color> <opaquenessPercentage>20</opaquenessPercentage> {code} RWS
FEWS-16092Plugin - Gui - Threshold DisplayFEWS-17266 System wide threshold crossing display with action acknowledge functionalityDisplay that shows table like overview of all Threshold EventsUser manual is documented under link: https://publicwiki.deltares.nl/display/FEWSDOC/29+System+Wide+Thresholds+Display{code} <explorerTask name="Events"> <iconFile>table.png</iconFile> <mnemonic>T</mnemonic> <taskClass>nl.wldelft.fews.gui.plugin.thresholdeventsviewer.ThresholdEventsTableViewer</taskClass> <toolbarTask>true</toolbarTask> <menubarTask>true</menubarTask> <allowMultipleInstances>false</allowMultipleInstances> <accelerator>ctrl T</accelerator> <loadAtStartup>false</loadAtStartup> </explorerTask> {code}https://publicwiki.deltares.nl/display/FEWSDOC/29+System+Wide+Thresholds+DisplayTVA
FEWS-17028Plugin - Gui - Time SeriesFEWS-17266 TVA: ability to auto-sort times when editing nonequidistant data TVA
FEWS-16981Plugin - Gui - Time SeriesHKV: Timeseries Marker as icon (for displaying wind direction as arrow) {code:xml} <parameterDisplayOptions id="WS.15"> <preferredColor>purple</preferredColor> <lineStyle>solid</lineStyle> <markerRotationParameterId>WR.15</markerRotationParameterId> <!--<markerIcon>arrow_icon_test.png</markerIcon>--> </parameterDisplayOptions> {code} HHS Delfland
FEWS-17193Plugin - Gui - Time SeriesFEWS-16132 HERMES: show single day (0-23hr) in the 24N display irrespective of hour of the day FB97 BPA HERMES
FEWS-17364Plugin - Gui - Time SeriesFEWS-16132 ability to configure colors of table headers for specific timeseriestable column header background colorIt's now possible to configure a tableHeaderBackgroundColor in the parameterDisplayOptions of the timeSeriesDisplay.xml to have a custom background color. It's also possible to use a color that has been defined in the color schemes. {code} <parameterDisplayOptions id="Q_Obs"> <preferredColor>green</preferredColor> <lineStyle>solid</lineStyle> <markerStyle>triangledown</markerStyle> <markerSize>3</markerSize> <precision>1</precision> <scaleUnit>1</scaleUnit> <tableHeaderBackgroundColor>[HLH_blue]</tableHeaderBackgroundColor> </parameterDisplayOptions> {code} In the CustomColors.xml the HLH_Blue color has been defined: {code} <customColorKey key="HLH_blue" color="light blue"/> {code} BPA HERMES
FEWS-12984Plugin - Gui - Time SeriesFEWS-14893 FOEN-DEV: Add a second icon to the icons of the shortcuts to know if thresholds are crossed before or after the system timeshow threshold warnings in time series display only based on values before / after display timeThe show threshold warnings button in the time series display (graph display) could already be used to turn on/off the threshold icons in the shortcuts menu. A drop-down menu was added to this button with options to only use values before, or only use value after the display time, when deciding what icon to display. FOEN
FEWS-17059Plugin - Gui - Grid Display, Plugin - Gui - Time SeriesAdd pixel information to pasted timeseries (from grid-display)add pixel information to pasted timeseries (from grid display)When you double click on a grid cell in the grid display, the time series for this point is shown in a graph. The coordinates of the grid cell are now shown in the title of this graph. GO-FEWS (Selection of Dutch Waterboards)
FEWS-17029Plugin - Gui - Time SeriesFEWS-17266 TVA: default last row in nonequidistant table to T0When a new time step in added at the end of the period in the data editor let the new time default to T0 if possible.When a new time step in added at the end of the period in the data editor let the new time default to T0 if possible. TVA
FEWS-17025Plugin - Gui - Time SeriesFEWS-10616 TVA: Data editing of nonequidistant time series (remove time)Remove time in the time series editor now removes the whole row TVA
FEWS-16936Plugin - Gui - Time SeriesFEWS-16887 NWS: #25016 Distance reduced of cursor (tooltip) readout showing nearest timeseries valueOption toolTipMargin to configure radius (in pixels) round the time series value the tool tip starts appearingAn example from TimeSeriesDisplayConfig.xml : <generalDisplayConfig> <thresholdLabelFontSize>9</thresholdLabelFontSize> <barMarginPercentage>20</barMarginPercentage> *<toolTipMargin>10</toolTipMargin>* <convertDatum>false</convertDatum> </generalDisplayConfig> NWS
FEWS-17315Plugin - Gui - Time SeriesAdd functionality to scatter plot to show multiple parameters for single locationOption to show "ShowAsScatterPlot" for the displayGroups is extendedIt is possible to define a scatterplot for a certain node in the display groups. This was already possible in the previous releases by using the showAsScatterPlot optie. However the timeseries were always paired my matching the parameter. This means that if a set of time series were defined for a certain node that two time series with the same parameter were always compared in the scatter plot. Since the 201702 release it is now also possible to create pairs by matching the location. This can be done by setting the option creatPairsByMatchingParameter to false.<displayGroup name="Verification_parameters_scatter"> <display name="Rotterdam parameters scatter"> <nrOfRecentForecasts>2</nrOfRecentForecasts> <locationId>rotterdam</locationId> <plotId>Scatterplot_parameters</plotId> <showAsScatterPlot> <chartTitle>My scatter plot</chartTitle> <referencePoints> <point> <x>-1</x> <y>-1</y> </point> <point> <x>0</x> <y>0</y> </point> <point> <x>2</x> <y>2</y> </point> </referencePoints> <xAxisRange> <min>-1</min> <max>2</max> </xAxisRange> <yAxisRange> <min>-1</min> <max>2</max> </yAxisRange> <createPairsByMatchingParameter>false</createPairsByMatchingParameter> </showAsScatterPlot> </display> RWS
FEWS-17862Plugin - Gui - Time SeriesButton "return to default"Explorer File menu option "Reload default user settings"The user may modify the preferences in the OC Gui. For example changing colors or switching TimeSeriesDislay toolbar buttons on/off. These preferences are stored in user_settings.ini. File menu option "Reload default user settings" restarts Fews with the default settings again. The previously entered user preferences are removed. RWS
FEWS-15730Plugin - Gui - Time SeriesAdd option to use identical vertical scales in timeseries viewer in 'multi-panel' modeAdded option to use identical vertical scales in graphsThe time series display already contained the option "Toggle graph" to display each time series in a separate graph. A second option "Toggle graph with equal scaling" was added. When this button is used, time series which were shown in the same graph originally, will use the same scale on the y-axis. Office of Public Works, Ireland
FEWS-17926Plugin - Gui - Time SeriesAdd configuration option for whitespace between (sub)plotsAdd configuration option for whitespace between (sub)plotsThe subplot element in displayGroups.xml now has an element <plotSeparatorWeight> (in addition to the <plotWeight> element) which controls the amount of whitespace above the subplot. For example, if two subplots are configured and the first subplot, second subplot and separator of the second subplot are all given equal weight, each will occupy 1/3 of the screen. HHS Delfland
FEWS-18223Plugin - Gui - Time Series Modifier, System - WorkflowFEWS-18222 HyFS: Dynamic selection of catchmentsWorkflow activity option “enabled”If the option “enabled” is present and the location attribute, specified with attributeId, has value FALSE, then the activity will be excluded from the workflow run. AttributeId should refer to the boolean attribute. To change interactively the attribute value, use location attribute modifiers.An example from Workflow.xml : {code:xml} <activity> <properties> <string key="CATCHMENT" value="goulburn"/> </properties> <enabled locationId="hunter_goulburn" attributeId="INCLUDE_IN_WORKFLOW"/> <runIndependent>true</runIndependent> <moduleInstanceId>goulburn_Rainfall_Multi_Scen_Forecast</moduleInstanceId> <moduleConfigFileName>Rainfall_1h_Multi_Scen_Forecast</moduleConfigFileName> </activity> <activity> <properties> <string key="CATCHMENT" value="goulburn"/> </properties> <enabled locationId="hunter_goulburn" attributeId="INCLUDE_IN_WORKFLOW"/> <runIndependent>true</runIndependent> <workflowId>goulburn_URBS_Catchment_Forecast</workflowId> </activity> {code} BoM
FEWS-16937Plugin - Gui - Time Series ModifierFEWS-16887 NWS: #23388 Order of available time series types in the Create mod menu's sub-menu should be configurableThe order of the parameters in the submenu of the "create modifier"-button dropdownlist is now configurableWhen a time series modifier can be applied to multiple parameters the parameter can be selected from a sub menu in the drop down list of the "create modifier"-button. The parameters are sorted alphabetically. It is now possible to configure the order of the parameters in the modifierDisplayConfig.xml<dropDownMenuDisplayOrder> <modifier id="rrichng"/> <modifier id="tschng"> <parameterId>SQIN</parameterId> <parameterId>STG</parameterId> </modifier> </dropDownMenuDisplayOrder> NWS
FEWS-16902Plugin - Gui - Time Series ModifierFEWS-16887 NWS: #23387 Order of mods in drop-down menu should be configurableOrder of the modifiers in the drop down list of the "create modifier" button is now configurableBy default the list of modifiers in the drop down menu of the "create modifier" button are sorted alphabetically. It is now possible to configure this order in the modifierDisplay.xml. It is not necessary to configure the order for all modifiers. These modifiers will added to the list alphabetically.<dropDownMenuDisplayOrder> <modifier id="wechng"/> <modifier id="weadd"/> </dropDownMenuDisplayOrder> NWS
FEWS-14443Plugin - Gui - Time Series ModifierFEWS-14471 Add modifier for "Staumatrix fullen" (p2)New Modifier added using referenceColumns Example from ModifierTypes.xml {code:xml} <highLowSurgeSelectionModifier id="staumatrix1" name="StauMatrix1"> <modifierColumn name="Modifier"> <timeSeries> <moduleInstanceId>ImportStauMatrix</moduleInstanceId> <parameterId>Surge</parameterId> <qualifierId>Default</qualifierId> </timeSeries> </modifierColumn> <referenceColumn name="ModelA"> <timeSeries> <moduleInstanceId>ImportStauMatrix</moduleInstanceId> <parameterId>Surge</parameterId> <qualifierId>ModelA</qualifierId> </timeSeries> </referenceColumn> <referenceColumn name="ModelB"> <timeSeries> <moduleInstanceId>ImportStauMatrix</moduleInstanceId> <parameterId>Surge</parameterId> <qualifierId>ModelB</qualifierId> </timeSeries> </referenceColumn> <referenceColumn name="ModelC"> <timeSeries> <moduleInstanceId>ImportStauMatrix</moduleInstanceId> <parameterId>Surge</parameterId> <qualifierId>ModelC</qualifierId> </timeSeries> </referenceColumn> <astronomicalNumberSelection> <timeSeriesFilter> <moduleInstanceId>ImportStauMatrix</moduleInstanceId> <parameterId>Surge</parameterId> <qualifierId>ModelA</qualifierId> <locationId>LocA</locationId> </timeSeriesFilter> <relativePeriod unit="hour" start="0" end="48"/> </astronomicalNumberSelection> <correctionTimeLocationAttributeId>MHWI</correctionTimeLocationAttributeId> <defaultStartTime>start run</defaultStartTime> <defaultEndTime>end run</defaultEndTime> <defaultValidTime/> <onlyApplyLastModifier>true</onlyApplyLastModifier> <resolveInWorkflow>true</resolveInWorkflow> <resolveInPlots>true</resolveInPlots> </highLowSurgeSelectionModifier> {code} BSH
FEWS-16655Plugin - Gui - Time Series ModifierFEWS-17266 TVA: ability to combine MAP modifiers when editing in plotsMerge multiple small time series modifiers into a single modifiersNormally when a forecaster makes multiple small changes to a time series then this will result in multiple modifiers. With this new option it is possible to merge these small mods automatically into 1 single large mod. The automated merging will only be done for new uncommitted time series modifiers which edit the same time series.{code}<timeSeriesModifier id="my mod" name="my modifier"> <timeSeries> <parameterId>my parameter</parameterId> </timeSeries> <mergeUnCommittedModifiers>true</mergeUnCommittedModifiers> <defaultStartTime>start run</defaultStartTime> <defaultEndTime>end run</defaultEndTime> <resolveInWorkflow>true</resolveInWorkflow> <resolveInPlots>true</resolveInPlots> </timeSeriesModifier> {code} TVA
FEWS-17503Plugin - Gui - What-if Scenario, Plugin - Module - Archiveuse custom properties in archive export for what-if nameApplied what-if scenarios are now stored in the archiveWhen a forecast is exported to the archive and a what-if scenario was applied to one of the time series which is part of the exported data set the applied what-if scenario(s) will be added to the runinfo.xml in the archive. The harvester of geonetwork will also add this information to the geonetwork archive. Nationaal Water Model
FEWS-16241Plugin - Module - AmalgamateFEWS-10616 TVA. maintain edit meta data in tss data history after amalgamating TVA
FEWS-18406Plugin - Module - ArchiveFEWS-17145 Archive 3D Scalar profile data to NetCDF
FEWS-17144Plugin - Module - ArchiveFEWS-17145 On-the-fly generation of regular NetCDF-GRID file based on bbox and viewperiod from Archive
FEWS-17289Plugin - Module - Data ExportFEWS-12539 Add to generalCSV export option to deal with enumeration values {code:xml} <general> <exportType>generalCsv</exportType> <folder>$EXPORT_DIR$</folder> <exportFileName> <name>ExportGeneralCsv.csv</name> </exportFileName> <table> <dateTimeColumn name="DateTime" pattern="yyyy-MM-dd HH:mm"/> <locationColumn name="Location"/> <parameterColumn name="Parameter"/> <valueColumn name="ValueOnly" ignoreForEnumerationParameters="true"/> <valueColumn name="LabelOnly" ignoreForNumericalParameters="true"/> <unitColumn name="Unit" /> </table> <idMapId>GeneralCsv</idMapId> <exportMissingValueString/> <convertValuesToEnumerationLabels>true</convertValuesToEnumerationLabels> </general> {code}https://publicwiki.deltares.nl/display/FEWSDOC/General+CSV+ExportNZV
FEWS-17546Plugin - Module - Data ExportFEWS-17145 Export 3D Z-Layer to NetCDF (GA export)NETCDF-CF_ZLAYERS time series exportNETCDF-CF_ZLAYERS exports scalar time series as Z-layers. Scalar time series at the same geo point Z but different X,Y are considered to be a Z-layer. All available Z’s are used to create a Z-axis (layer axis) in the NetCdf file, and the time series values are written to the associated Z element. An example: float salinity(time=5, node=26, z=40); Values of Z-axis are stored in meters. Per parameter only one Z-axis is allowed. Different parameters may have different Z-axis Z-axis values are sorted in ascending order. The number of stations in the nc file equals to the number of unique X,Y that are available in the scalar time series. The location id’s/names associated with the first (lowest) Z are written to the nc file as station id’s/names. If there are parent locations configured, then the IdMap can be used to write the parent locations id’s to the nc file (see config example) The long_name attribute of the parameters is equal to the parameter id by default. To override the default long_name, configure parameter description in Parameters.xml. The parameter description will be then written to the nc file as long_name. Usage NETCDF-CF_ZLAYERS in GeneralAdapter: To export scalar time series as Z_layers in GA, use option <exportZLayers>true</exportZLayers> in <exportNetcdfActivity> In GA the default missing value for time series is -999. You can overwrite it in GA using <missVal>, for example <missVal>NaN</missVal>
FEWS-17154Plugin - Module - Data ExportFEWS-16887 NWS: #35088 FEWS HEC DSS Export/ImportImport and export for time series data from files in Hydrologic Engineering Center Data StorageImport and export for time series data from files in Hydrologic Engineering Center Data Storage System format: http://www.hec.usace.army.mil/software/hec-dss/ These files were already used in HEC-XXX models and their FEWS adapters.Config for Hec Dss export {code:xml} <timeSeriesExportRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/timeSeriesExportRun.xsd"> <export> <general> <exportType>HecDss</exportType> <folder>$EXPORT_FOLDER$</folder> <exportFileName> <name>equidistant.dss</name> </exportFileName> </general> <timeSeriesSet> <moduleInstanceId>Hec</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H_max</parameterId> <locationId>Dummy</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="10"/> <relativeViewPeriod unit="week" start="-100" end="0"></relativeViewPeriod> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </export> </timeSeriesExportRun> {code} WIKI: https://publicwiki.deltares.nl/pages/viewpage.action?pageId=130383980 Config for Hec Dss import IdMap is needed for import when location and/or parameter id in FEWS is not in capitol letters. HecDss always uses Capitol letters. {code:xml} <timeSeriesImportRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/timeSeriesImportRun.xsd"> <import> <general> <importType>HecDss</importType> <folder>$REGION_HOME$/import/dss</folder> <idMapId>IdMapDssImport</idMapId> </general> </import> </timeSeriesImportRun> {code} Example id map for import config above and attached [^H_MAX-DUMMY-10MIN.dss] {code:xml} <idMap version="1.1" xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/idMap.xsd"> <parameter internal="H_max" external="H_MAX"/> <location internal="Dummy" external="DUMMY"/> </idMap> {code} WIKI: https://publicwiki.deltares.nl/display/FEWSDOC/HecDsshttps://publicwiki.deltares.nl/display/FEWSDOC/HecDssNWS
FEWS-17758Plugin - Module - Data ImportFeature to apply locationSelection also on import modules. https://publicwiki.deltares.nl/display/FEWSDOC/06+Configuring+WorkFlows#id-06ConfiguringWorkFlows-loopLocationSetIdWIS WaterschapsBedrijf Limburg (WBL)
FEWS-17530Plugin - Module - Data ImportFEWS-17145 Improve Netcdf-CF_Grid so it can read .nc files without time coordinate
FEWS-18201Plugin - Module - Data ImportFEWS-16663 Québec: generalCSV parser supporting daylight savings time with separate date and time columns Quebec
FEWS-17039Plugin - Module - Data ImportFEWS-17145 Import Profile Data with varied domain parameter (z layer or sigma layer) Panama
FEWS-18531Plugin - Module - Data ImportFEWS-16464 FOEN: Update SHD parser with new locationID mapping https://publicwiki.deltares.nl/display/FEWSDOC/SHD+-+Swiss+Hydro+DataFOEN
FEWS-17092Plugin - Module - Data ImportFEWS-14337 nc4 import for NOAA GPM radar data BMT-WBM
FEWS-17594Plugin - Module - Data ImportFEWS-17202 Import user information from database table {code:xml} <table> <dateTimeColumn name="Datum/Tijd" pattern="dd-MM-yy HH:mm"/> <parameterColumn name="Parameter"/> <valueColumn name="Waarde"/> <locationColumn name="Locatie"/> <userColumn name="Gebruiker"/> </table> {code}https://publicwiki.deltares.nl/display/FEWSDOC/General+Csv#GeneralCsv-userColumnAPP
FEWS-17802Plugin - Module - Data ImportAPI Import TAHMOimport TAHMOAdded a new import type TAHMO. https://publicwiki.deltares.nl/display/FEWSDOC/TAHMO+importTanzania
FEWS-17484Plugin - Module - Data ImportFEWS-17202 New Import type: In-Situ Rugged TrollTimeseries import supports gotoLineWhichStartsWith option to skip lines until configured starts with string is foundTimeseries import supports gotoLineWhichStartsWith option to skip lines until configured starts with string is found. Usefull in case the start of CSV headers is variable. https://publicwiki.deltares.nl/display/FEWSDOC/General+Csv#GeneralCsv-ExamplegotoLineWhichStartsWith(Since2016.02)APP
FEWS-18532Plugin - Module - Data ImportFEWS-17145 Add fileNameObservationDateTimePattern to NETCDF-CF_GRID import from OpenDAPTimeSeriesImport from OpenDAP can use fileNameObservationDateTimePatternWhen OpenDAP NC datasets does not contain any event time, and the date and time are available in the Url , then fileNameObservationDateTimePattern can be used to obtain date and time from this Url. Symbol ? can be used if the part of Url is variable, however the number of ? must match the actual number of characters in the Url. This is useful if the configured URL is a catalog. Please note that catalog should be a XML document. An example from TimeSeriesImport.xml {code:xml} <general> <importType>NETCDF-CF_GRID</importType> <serverUrl>http://tl-tc068.xtr.deltares.nl:8080/thredds/dodsC/Ganga/S3A_SR_2_WAT____20180406T010052_20180406T011037_20180406T033003_0585_029_359______MAR_O_NR_003.nc</serverUrl> <fileNameObservationDateTimePattern>'?????????????????????????????????????????????????????????????????????????'yyyyMMdd'T'HHmmss'??????????????????????????????????????????????????????????????????'</fileNameObservationDateTimePattern> <idMapId>IdMapGrid</idMapId> </general> {code}
FEWS-16898Plugin - Module - Data ImportFEWS-16887 NWS: #32624 Enhancement request for updates to SHEF importsSHEF import supports multiparameter lines and continuationsThe SHEF import now has support for multiple parameters on one line using the .A code. The continuations (.A1, .A2 etc.) are supported as well. https://publicwiki.deltares.nl/display/FEWSDOC/SHEF+-+Standard+Hydrometeorological+Exchange+FormatNWS
FEWS-17865Plugin - Module - Data ImportImport for FEWS BoliviaSENAMHI importA new SENAMHI import module was added to FEWS. https://publicwiki.deltares.nl/display/FEWSDOC/SENAMHI+importSENAMHI
FEWS-16857Plugin - Module - Data ImportImport json CoVadem data via http GETNew import (COVADEM) is available in FEWS.The covadem webservice provides measurements of the water depth by ships. A new data import is available in FEWS to consume this data. The import is available with the tag "Covadem". RWS
FEWS-18212Plugin - Module - Data ImportFEWS-17145 NetCDF irregular grid import - Automate geometry detectionNetCDF irregular grid import - Automate geometry detection for temporary time seriesThe existing NETCDF-CF_GRID import was expanded. When the time series being imported has a timeSeriesType set to "temporary" or "temporary external forecast", the import no longer requires the grid to be configured in the grids.xml, but can automatically detect the grid geometry instead. The irregular grid geometry will be stored along with the imported data, to be used later (within the same workflow). This is currently only available for grids that do not have z-values / z-layers. https://publicwiki.deltares.nl/display/FEWSDOC/NETCDF-CF_GRID
FEWS-16899Plugin - Module - Data ImportFEWS-16887 NWS: #23704 Import reservoir storage curves to allow display capabilities similar to rating curvesLookupTablesStorage curves and any other curves can be stored in region config file LookupTables.xml , according to the pi_tables format. Similar to the rating curves, the LookupTable curves can be displayed in TSD and can be used to create the right axis in the plots. ConfigExampleLookupTables.zip contains very simple example configuration with imaginary data, to demonstrate the functionality (import scalar series first, see ImportBackup\scalar). The lookup tables can be referenced using domain parameter Id, Parameter Id, optionally qualifier Id’s and optionally location Id. An example from DisplayGroups: {code:xml} <subplot> <lookupAxis> <inputColumnParameterId>Stage</inputColumnParameterId> <outputColumnParameterId>Storage</outputColumnParameterId> </lookupAxis> <timeSeriesSet> …………………………………. {code} Picture LookupTablesAndRightAxis2 and LookupTablesAndRightAxis2 shows the displays created with the example LookupTables.xml and DisplayGroups.xml The LookupTables can be displayed in the same way as rating curves, see RatingCurveAndLookupTablesDisplay1 and RatingCurveAndLookupTablesDisplay2 All available curves for the selected location(s) appear in the list box. The LookupTables curves are indicated as ‘parameter column a’ - ‘parameter column x’ If there are multiple locations selected, each curve name contains also location name . In the list box we select a curve to display. The list box only appears if there are multiple curves for the selected location. NWS
FEWS-16916Plugin - Module - Data ImportFEWS-16663 Import of bespoke Hydro Québec .prn filesImport type added: HydroQuebecPRNImport for specific Quebec format, containing flow for 3 Quebec locations<importType>HydroQuebecPRN</importType>https://publicwiki.deltares.nl/display/FEWSDOC/HydroQuebecPRNMDDELCC
FEWS-18525Plugin - Module - Data ImportFEWS-16464 FOEN: Add separate year, month, day columns to generalcsv importAdd separate year, month, day, hour, minute and second columns to generalCsv importThe generalCsv import can now handle the date being specified through three separate columns (year, month and day), and the time being specified through one to three separate columns (hour, minute and second). If no second or minute column is given, they are assumed to be 0. https://publicwiki.deltares.nl/display/FEWSDOC/General+Csv#GeneralCsv-Importingdatesandtimeswithseparateyear,month,day,hour,minuteandsecondcolumns(since2017.01)FOEN
FEWS-16111Plugin - Module - General AdapterFEWS-17266 importing multiple states in one GA run {code:xml} <importStateActivity> <stateImportDir>$TEST_DIR$</stateImportDir> <stateFileDateTimePattern>'state'yyyyMMddHHmm'.bin'</stateFileDateTimePattern> <relativeExportFile>start.bin</relativeExportFile> </importStateActivity> {code}https://publicwiki.deltares.nl/display/FEWSDOC/05+General+Adapter+ModuleTVA
FEWS-18559Plugin - Module - General AdapterFEWS-14299 NFFS: Improve the exportCustomFormatRunFileActivity with formatadded option to specify the width of output values in exportCustomFormatRunFileActivityThe exportCustomFormatRunFileActivity now takes two additional optional elements: <fixedWidth> and <numberOfDecimals>. The <fixedWidth> element can be used to specify the length of the output each location attribute or property tag ('@' or '$') is replaced with. The <numberOfDecimals> element can be used to specify the number of decimals the number attribute values must be rounded to.{code:xml} <generalAdapterRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/generalAdapterRun.xsd"> <general> ... <startDateTimeFormat>yyyy MM dd HH mm</startDateTimeFormat> <endDateTimeFormat>yyyy MM dd HH mm</endDateTimeFormat> </general> <activities> <exportActivities> <exportCustomFormatRunFileActivity> <templateFile>%ROOT_DIR%/templatefiles/event_tox2_template.inp</templateFile> <exportFile>event_tox2.inp</exportFile> <locationId>locationWithAttributes</locationId> <fixedWidth>10</fixedWidth> <numberOfDecimals>5</numberOfDecimals> </exportCustomFormatRunFileActivity> </exportActivities> </activities> </generalAdapterRun> {code}https://publicwiki.deltares.nl/display/FEWSDOC/05+General+Adapter+Module#id-05GeneralAdapterModule-exportCustomFormatRunFileActivityEA
FEWS-16265Plugin - Module - General AdapterFEWS-17266 TVA: Add ImportShapeFileActivity to GA moduleShape files can now be imported as time series via the importShapeFileActivity in the generalAdapterShape files can now be imported as time series via the importShapeFileActivity in the generalAdapter{code:xml} <?xml version="1.0" encoding="UTF-8"?> <!-- edited with XMLSPY v2004 rel. 3 U (http://www.xmlspy.com) by rooij_e (WL | Delft Hydraulics) --> <generalAdapterRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/generalAdapterRun.xsd"> <!-- General information for General Adapter run --> <general> <rootDir>$REGION_HOME$</rootDir> <workDir>%ROOT_DIR%</workDir> <exportDir>%ROOT_DIR%</exportDir> <importDir>%ROOT_DIR%/polygon</importDir> <dumpFileDir>%ROOT_DIR%/polygon/dumpfiledir</dumpFileDir> <dumpDir>%ROOT_DIR%/polygon/dumpdir</dumpDir> <diagnosticFile>%ROOT_DIR%</diagnosticFile> </general> <activities> <importActivities> <importShapeFileActivity> <shapeFileImportDir>import</shapeFileImportDir> <fileDateTimePattern>'ImportShapeFileActivity_'dd MMM yyyy HH mm ss'.shp'</fileDateTimePattern> <geoDatum>EPSG:102736</geoDatum> <timeSeriesSet> <moduleInstanceId>ImportShapeActivity</moduleInstanceId> <valueType>polygon</valueType> <parameterId>QPE</parameterId> <locationId>Polygon</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </importShapeFileActivity> </importActivities> </activities> </generalAdapterRun> {code}https://publicwiki.deltares.nl/display/FEWSDOC/05+General+Adapter+Module#id-05GeneralAdapterModule-importShapeFileActivityTVA
FEWS-17411Plugin - Module - General AdapterImport loop over directories while import ensemble results openda using GAAdded unit tests and a clear description with config examples (also on WIKI) for an OpenDA ensemble member importAdded unit tests and a clear description with config examples (also on WIKI) for an OpenDA ensemble member importIn the workflow file specify the ensemble and index range to loop over: {code:xml} <workflow version="1.1" xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/workflow.xsd"> <activity> <moduleInstanceId>ImportOpenDAEnsembles</moduleInstanceId> <ensemble> <ensembleId>EnKF</ensembleId> <ensembleMemberIndexRange start="0" end="64"/> <runInLoop>false</runInLoop> </ensemble> </activity> </workflow> {code} ModuleConfigFile.xml should contain the %ENSEMBLE_MEMBER_ID% tag in either the <importDir> or <importFile> (in <importNetcdfActivity>). Do not specify the ensemble member. This only works for the importNetcdfActivty. Other activities that do not contain the %ENSEMBLE_MEMBER_ID% tag will only be executed once. {code:xml} <?xml version="1.0" encoding="UTF-8"?> <generalAdapterRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/generalAdapterRun.xsd"> <general> <description>Test run for nautboom</description> <rootDir>../modules/fews/src/test/java/nl/wldelft/fews/system/plugin/generaladapter</rootDir> <workDir>%ROOT_DIR%</workDir> <exportDir>%ROOT_DIR%/importDir</exportDir> <importDir>%ROOT_DIR%/importDir/ensemblesmultipleidenticalfiles/work%ENSEMBLE_MEMBER_ID%</importDir> <importIdMap>ImportNetcdfScalarEnsembleMultipleIdenticalFiles</importIdMap> <dumpFileDir>%ROOT_DIR%/..</dumpFileDir> <dumpDir>%ROOT_DIR%</dumpDir> <diagnosticFile>%ROOT_DIR%</diagnosticFile> </general> <activities> <importActivities> <importNetcdfActivity> <importFile>netcdf_timeseries.nc</importFile> <timeSeriesSets> <timeSeriesSet> <moduleInstanceId>ImportNetcdfScalarEnsembleMultipleIdenticalFiles</moduleInstanceId> <valueType>scalar</valueType> <parameterId>WaterLevel</parameterId> <locationId>27</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant" /> <readWriteMode>read complete forecast</readWriteMode> </timeSeriesSet> </timeSeriesSets> </importNetcdfActivity> </importActivities> </activities> </generalAdapterRun> {code}https://publicwiki.deltares.nl/display/FEWSDOC/05+General+Adapter+Module#id-05GeneralAdapterModule-CombinedwithworkflowensembleloopGLOFFIS
FEWS-17297Plugin - Module - Modifiers (ModuleParameters)create location specific drop-down enumeration in location attribute modifier using fixed boolean attributesdefine location specific options in drop down list by using attributesAttributes can be modified by using location attribute modifiers. By default the attributes can be changed by using a text box. It is also possible to use a drop down list. The content of this drop downlist can be controlled by using an a multi value attribute.{code} <attribute id="NWP"> <selection> <optionsControllingLocationAttributeId>NWP_OPTIONS</optionsControllingLocationAttributeId> </selection> <comment>Default value: @NWP_DEFAULT@</comment> </attribute>{code} SAVA
FEWS-16912Plugin - Module - Modifiers (ModuleParameters)FEWS-16887 NWS: #25022 incorrect BASEFLOW and UNITHG modifier interactionCombine multiple module parameter modifiersThe unithg modifiers and baseflow modifier are both module parameter modifiers which both apply changes to the same module parameter file. It is now possible to apply multiple module parameter modifiers to the same module parameter file. This means that it is now possible to apply a unithg and baseflow mod to the same module parameter file at the same time. NWS
FEWS-17561Plugin - Module - Modifiers (ModuleParameters)FEWS-16887 NWS: #34172 (a) CHPS Calibration: add attributeModifier capability for snow17, sacsma, lagk parameter calibrationsCalibration modifiers can now be used in combination with csv filesIt is possible to use attributes in the general adapter parameter export. It was not possible yet to combine this feature with the calibration modifiers (multiple model modifiers). This is now possible. NWS
FEWS-16900Plugin - Module - Modifiers (TimeSeries)FEWS-16887 NWS: #24038 Add shift arrows for UNITHG modUNITHG modifier : shift arrows to shift the unit hydrograph ordinate valuesThe unit hydrograph ordinate values can be shift forward or backward using the forward or backward arrows. Times in fields “Start time”, “End time” and “Valid time” are shifted accordingly. To shift the values, also a context menus ‘Shift Values forward in Time (Ctrl Right)’ and ‘Shift Values backward in Time (Ctrl Left)’ can be used. An example is shown in the picture UnitHG_shiftButtons.png NWS
FEWS-10848Plugin - Module - Performance IndicatorsFEWS-10851 Performance Indicators: Store all individual indicator values in separate time seriesleadTimeAccuracyIndicator - new options to store intermediate indicator values and forecast and observed values, that have been used for the analysis, in the output time series arraysTo create the new output time series, use the following options: - intermediateValuesVariableId to create time series with intermediate indicator values - analysedCalculatedVariableId to create time series with exact those forecast values, that have been used for the analysis - analysedObservedVariableId to create time series with exact those observed values, that have been used for the analysis Config example is available in PerformanceIndicator.xml The new time series are created for each input forecast. For example , if 3 input forecast are used, then also 3 time series with intermediateValues are created. To be able to create multiple simulated forecasts using the same TimeSeriesSet, the ensembles are used. Values associated with a particular forecast are stored using an ensemble member Id and this member Id equals to the forecast time of that forecast. An example: Picture LeadTimePerformanceIndicatorResults.png shows the results of the computation that has been done with the configuration example PerformanceIndicator.xml This example uses observed series (Q.m) and 3 input forecasts (Q.sim). For each input forecast the following series are created : intermediate values (Q.rmse.interm), forecast values used in the analysis (Q.sim.analysed) and observed values used in the analysis (Q.m.analysed). Ensemble member Id’s are 19850101000000, 19850101060000, 1985010180000 and are equal to the forecast times of the used forecasts. The new output options are available only for leadTimeAccuracyIndicator that uses leadTimePeriods, RWS
FEWS-10847Plugin - Module - Performance IndicatorsFEWS-10851 Performance Indicator: Set the <ForecastSelectionPeriod> manually in the FEWS ClientPerformance Indicators: manually setting of the forecastSelectionPeriod and changing of the relativeViewPeriod*Manually setting of the forecastSelectionPeriod* With forecastSelectionPeriod the user defines how much of the forecasts or hindcast should be analysed. The configured forecastSelectionPeriod can be changed manually in the ManualForecastDialog or in the RunOptions of the IFD Forecasts, by selecting a certain cold state or warm state . The configured forecastSelectionPeriod should have the attributes startOverrulable and/or endOverrulable, to specify that the changing of the forecastSelectionPeriod is allowed. The user selects Cold state if only the start of the forecastSelectionPeriod should be amended. Then the cold state start time is used as start of the forecastSelectionPeriod. ForecastSelectionPeriod should have an overrulabel start: {code:xml} <forecastSelectionPeriod unit="day" start="-10" end="0" startOverrulable="true"/> {code} The user selects Warm state if the start and also the end of the forecastSelectionPeriod should be amended. The warm state start time is used as start of the forecastSelectionPeriod, the warm state end time is used as the end of the forecastSelectionPeriod. ForecastSelectionPeriod should have an overrulabel start and end: {code:xml} <forecastSelectionPeriod unit="day" start="-3" end="0" startOverrulable="true" endOverrulable="true"/> {code} *Manually setting of the relativeViewPeriod of the forecast and/or observed series* In PerformanceIndicators module the user can change the relativeViewPeriod of the time series in the same way as in other modules, for example in GeneralAdapter The configured relativeViewPeriod can be changed manually in the ManualForecastDialog or in the RunOptions of the IFD Forecasts. To change the start of the relativeViewPeriod, the user selects cold state or warm state. The start time of the state will be used as new start of the relativeViewPeriod. To change the end of the relativeViewPeriod, the user selects a particular forecast length in ManualForecastDialog. Then the new end of the relative view period will be set to T0+number of time units selected with forecast length option. The relativeViewPeriod can be also amended by Forecast Length estimator. For details, please see the Forecast Length estimator. To be able to change the relativeViewPeriod, the user should configure attributes startOverrulable and/or endOverrulable. RWS
FEWS-10846Plugin - Module - Performance IndicatorsFEWS-10851 Performance Indicator: store number of analysed samples in separate TimeSeriesPerformance Indicators module : leadTimeAccuracyIndicator optionally stores number of analyzed samples in separate time seriesleadTimeAccuracyIndicator optionally stores number of analyzed samples in separate time series. The number of samples can be stored in a single time series or in time series per lead time period. In single time series the number of samples is stored at T0 + end of the lead time periods . Otherwise the number of samples is stored at T0 in time series per lead time period. The number of samples is stored in single time series, referenced with sampleOutputVariableId "sampleOutput" {code:xml} <leadTimeAccuracyIndicator indicatorType="meansquareerror" calculatedVariableId="calculated" observedVariableId="observed" outputVariableId="output" sampleOutputVariableId="sampleOutput"> <leadTimePeriods unit="hour"> <leadTimePeriod start="0" end="1" outputVariableId="output1"/> <leadTimePeriod start="0" end="4" outputVariableId="output4"/> <leadTimePeriod start="0" end="6" outputVariableId="output6"/> </leadTimePeriods> </leadTimeAccuracyIndicator> {code} The number of samples is also stored in time series per lead time period: {code:xml} <leadTimeAccuracyIndicator indicatorType="meansquareerror" calculatedVariableId="calculated" observedVariableId="observed" outputVariableId="output" sampleOutputVariableId="sampleOutput"> <leadTimePeriods unit="hour"> <leadTimePeriod start="0" end="1" outputVariableId="output1" sampleOutputVariableId="sample1"/> <leadTimePeriod start="0" end="4" outputVariableId="output4" sampleOutputVariableId="sample4"/> <leadTimePeriod start="0" end="6" outputVariableId="output6" sampleOutputVariableId="sample6"/> </leadTimePeriods> </leadTimeAccuracyIndicator> {code} RWS
FEWS-17534Plugin - Module - ReportsUse scadaPanel defined in scadaDisplay for reports and other scadaDisplaysSchematicStatus display : scadaPanels , configured in one SchematicStatus display, can be included in other SchematicStatus displays or in reportsUse option scadaPanelId to include scadaPanels , configured in other SchematicStatus displays, in a particular SchematicStatus display or in a particular report. In SchematicStatus display both scadaPanel and scadaPanelId can be mixed. When we use scadaPanelId, then also the numberFormat(s), dateFormat(s) and variables that are configured in the refered SchematicStatus display are used. The formats and variables from the refered SchematicStatus display can be overruled by configuring the same Id’s but with a different content in the display with scadaPanelId When using scadaPanelId, then all scadaPanels should have an unique Id. If there are any duplicities, then the first scadaPanel found is used.scadaDisplay.xml : {code:xml} <scadaDisplay xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/scadaDisplay.xsd"> <displayName>SSD composed</displayName> <showTimeNavigatorToolbar> <timeNavigatorRelativePeriod unit="day" start="-1" end="0"/> <timeNavigatorTimeStep unit="hour"/> </showTimeNavigatorToolbar> <backgroundColor>gray</backgroundColor> <scadaPanelId>panelA</scadaPanelId> <scadaPanelId>panelB</scadaPanelId> </scadaDisplay> {code} Example from Reports.xml: {code:xml} <schematicStatusDisplayPanelSnapshotsPng> <variable> <variableId>Hmeasured</variableId> <timeSeriesSet> <moduleInstanceId>Import</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.m</parameterId> <locationSetId>ReportLocations</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour"/> <relativeViewPeriod unit="hour" start="-10" end="0"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </variable> <scadaPanelId>scadaPanel_01</scadaPanelId> <width>1200</width> <height>740</height> <snapshot id="Scada"> <relativeTime unit="day" value="0"/> <fileName>scada.png</fileName> </snapshot> </schematicStatusDisplayPanelSnapshotsPng> {code} IWP
FEWS-17207Plugin - Module - ReportsFEWS-17202 extend functionality rowperlocationHtmlTableReports/Scada template function improvements*VALUECOUNT(type; variable id)* This function counts the number of values in the time series. The argument 'type' specifies the value type that should be counted. Supported types are ALL, MISSINGS, COMPLETED, CORRECTED, RELIABLES, UNRELIABLES, DOUBTFULS Usage in Reports : VALUECOUNT(COMPLETED;Hmeasured) Usage in Scada : VALUECOUNT(COMPLETED) *THRESHOLDCROSSINGCOUNT*(<level threshold id;> variable id) This function counts the number of time steps in which the level thresholds have been crossed. If a specific level threshold id is configured, then only the crossings for this threshold are counted. Usage in Reports : THRESHOLDCROSSINGCOUNT(Hmeasured) , THRESHOLDCROSSINGCOUNT(Level_A;Hmeasured) Usage in Scada : THRESHOLDCROSSINGCOUNT() , THRESHOLDCROSSINGCOUNT(Hmeasured) Option *IgnoreMissings in STATISTICS* function Use IgnoreMissings if the missing values should be ignored while evaluating of the statistics function. By default the statistics are not computed if the time series has one or more missing values. Usage in Reports : STATISTICS(MEAN;IgnoreMissings;H.m;numberFormat1) Usage in Scada : STATISTICS(MEAN;IgnoreMissings;numberFormat1) Option *ClosestToT0 in MINTIME and MAXTIME* functions Use ClosestToT0 to find the date/time of the minimum c.q. maximum value in the time series that is closest to T0. By default , in case of forecast series the functions return the date/time of the first minimum/maximum value , and in case of external historical series the date/time of the last minimum/maximum is returned. Usage in Reports : MINTIME(ClosestToT0;H.m;dateFormat1), MAXTIME(ClosestToT0;H.m;dateFormat1) Usage in Scada : MINTIME(ClosestToT0;dateFormat1), MAXTIME(ClosestToT0;dateFormat1) APP
FEWS-17963Plugin - Module - ReportsFEWS-16663 Quebec: new report tag for userId who generated a certain workflowReport tag WORKFLOW(key; workflow Id; format Id)This function provides properties of the most recent run of the workflow configured with workflow Id. The key specifies the required run property. Format Id is optional and if specified it represents date format . The following keys are supported: USERID: user Id MCID: MasterController Id FSSID: Forecasting shell Id DESCRIPTION: description of the forecast TIMEZERO: time0 DISPATCH_TIME: dispatch time COMPLETION_TIME: completion time RUNTIME: duration of the forecast run OUTPUT_TIME_SPAN: time span of the forecast Examples: WORKFLOW(USERID; ImportExternalForecast) WORKFLOW(COMPLETION_TIME; ImportExternalForecast; dateFormat1) Where ImportExternalForecast is a workflow Id Quebec
FEWS-16978Plugin - Module - StatisticsFEWS-16132 FB89 TFS42046: Daily Aggregation Button does not appear to aggregate according to the parameter typeThe CalendarAggregationFunction has now the option to accumulate according to parameter type: SUM (accumulative), MEAN (mean) or LAST_VALUE (instantaneous)The CalendarAggregationFunction has now the option to accumulate according to parameter type: SUM (accumulative), MEAN (mean) or LAST_VALUE (instantaneous){code:xml} <quickViewStatisticalFunction function="calendarAggregation" ignoreMissings="true" aggregateByParameterType="true"> <timeStep id="daily00"/> <iconName>dailyv3.png</iconName> <label>Daily</label> <toolTip>Aggregate dailies</toolTip> <accelerator>ctrl alt D</accelerator> </quickViewStatisticalFunction> <quickViewStatisticalFunction function="calendarAggregation" ignoreMissings="true" aggregateByParameterType="true"> <timeStep id="weekly00"/> <iconName>weekly.png</iconName> <label>Weekly</label> <toolTip>Aggregate weeklies</toolTip> <accelerator>ctrl alt W</accelerator> </quickViewStatisticalFunction> {code} BPA
FEWS-16986Plugin - Module - ThresholdsFEWS-16315 HyFS-alerts: Improve logging of threshold crossingMore information in threshold crossing logs + improved logging of action events-Added threshold values and rate timespan to logs -Added the possibility to add location attributes to the threshold logs. Per ThresholdValueSet it is possible to configure which locationAttributeKeys to include in the messages. -Added option to be able to stand down each location separately by configuring the 'standDownIndividualLocations' option -Added option 'graceTime' to control how frequently (rainfall) rate thresholds are issued per location.{code} <thresholdValueSet id="GraceTime" name="ROC Observed water levels"> <description>rate of change threshold values should be specified ascending according to the element 'value'</description> <standDownIndividualLocations>true</standDownIndividualLocations> <locationAttributeKeys> <attributeKey>att1</attributeKey> <attributeKey>att2</attributeKey> </locationAttributeKeys> <graceTime unit="hour" multiplier="6" /> <rateThresholdValue> <rateThresholdId>EnhanceRate</rateThresholdId> <value>10</value> <upActionLogEventTypeId>Action.RateEnhanced</upActionLogEventTypeId> <downEventTypeId>Action.RateStandDown</downEventTypeId> <timeSpan unit="hour"/> </rateThresholdValue> <rateThresholdValue> <rateThresholdId>EnhanceRate1</rateThresholdId> <value>12</value> <upActionLogEventTypeId>Action.RateEnhanced1</upActionLogEventTypeId> <downEventTypeId>Action.RateStandDown1</downEventTypeId> <timeSpan unit="hour"/> </rateThresholdValue> <timeSeriesSet> <moduleInstanceId>RateThreshold</moduleInstanceId> <valueType>scalar</valueType> <parameterId>P.obs</parameterId> <locationSetId>LocationsWithAttributes</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="15"/> <relativeViewPeriod unit="hour" start="0" end="12"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </thresholdValueSet> {code} BoM (Aus)
FEWS-16987Plugin - Module - ThresholdsFEWS-16315 HyFS-Alerts: Simplify standdown activity in Threshold moduleAdded option to issue StandDown events individualyWit the option 'standDownIndividualLocations' in the ThresholdValueSets file it is now possible to issue standdown events for individual locations instead issuing a standdown only when entire catchment is stood down.{code} <thresholdValueSet id="HObserved2" name="Observed water levels"> <description> level threshold values should be specified ascending according to the element 'value'</description> <standDownIndividualLocations>true</standDownIndividualLocations> <levelThresholdValue> <levelThresholdId>EnhanceLevel</levelThresholdId> <value>10</value> <upActionLogEventTypeId>Action.Enhanced</upActionLogEventTypeId> <downActionLogEventTypeId>Action.StandDown</downActionLogEventTypeId> </levelThresholdValue> <timeSeriesSet> <moduleInstanceId>LevelThreshold</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.obs</parameterId> <locationId>A</locationId> <locationId>B</locationId> <locationId>C</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="15"/> <relativeViewPeriod unit="hour" start="0" end="12"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </thresholdValueSet> {code} BoM (Aus)
FEWS-17853Plugin - Module - TransformationFEWS-17145 Transformation Module - Merge simple optimizationnew merge transformation MergeInterpolationThis transformation can be used to merge multiple input grids to a single output grid. More detailed information can be found at: https://publicwiki.deltares.nl/display/FEWSDOC/Merge+Interpolation{code}<transformation id="merge interpolation example"> <merge> <interpolation> <inputVariable> <variableId>input</variableId> </inputVariable> <interpolationType>closestDistance</interpolationType> <outputVariable> <variableId>output</variableId> </outputVariable> </interpolation> </merge> </transformation>{code}
FEWS-17470Plugin - Module - TransformationConfigure keywords for transformation elementsadded possibility to provide a property ($) to several transformation config elementsAdded possibility to provide a property ($) to the following elements: * ImportNetcdfActivity -> maximumSnapDistance & maximumVerticalSnapDistance * TimeSeriesImportGeneral -> maximumSnapDistance & maximumVerticalSnapDistance * InterpolationSpatialClosestDistance -> searchRadius & distanceGeoDatum * InterpolationSpatialVerticalProfileClosestDistance -> searchRadius & distanceGeoDatum * InterpolationSpatialThiessenPolygon -> distanceGeoDatum * InterpolationSpatialInverseDistance -> searchRadius & distanceGeoDatum * InterpolationSpatialSnapTrackToLocations -> maximumSnapDistance * TimeShiftConstant -> numberOfTimeSteps Deltares
FEWS-18053Plugin - Module - TransformationFEWS-14299 FFFS: Allow use of multiple coordinates for locationsadded possibility to overrule location coordinates via attributes to closestDistance transformationThe spatial interpolation transformation <closestDistance> now has two additional optional elements <overrulingXAttribute> and <overrulingYAttribute>. If these are configured, the attribute value is used instead of the location coordinate if present, i.e., if the location has this attribute and has a value for the attribute. Otherwise, the regular coordinate is used. This is done for both input and output variables.{code:xml} <transformation id="ClosestDistanceWithOverrulingCoordinates"> <interpolationSpatial> <closestDistance> <inputVariable> <variableId>input</variableId> </inputVariable> <overrulingXAttribute>ALT_X</overrulingXAttribute> <overrulingYAttribute>ALT_Y</overrulingYAttribute> <outputVariable> <variableId>output</variableId> </outputVariable> </closestDistance> </interpolationSpatial> </transformation> {code}https://publicwiki.deltares.nl/display/FEWSDOC/InterpolationSpatialClosestDistanceEA
FEWS-18052Plugin - Module - TransformationFEWS-14299 FFFS: New Raingauge weighting functionadded option to use multi-value attributes to decide inputs for weighted average transformationThe existing interpolationSpatial - weighted transformation was expanded to allow specifying the input locations and their weights through two multi-value attributes of the output location. This means the module config file no longer needs to contain a transformation for each combination of inputs and output, but a single transformation using locationSets can be configured.{code:xml} <transformation id="interpolation spatial weighted"> <interpolationSpatial> <weighted> <inputVariable> <variableId>input</variableId> </inputVariable> <attributedOutputVariable> <outputVariable> <variableId>output</variableId> </outputVariable> <locationIdAttribute>LOCS</locationIdAttribute> <weightAttribute>WEIGHTS</weightAttribute> </attributedOutputVariable> </weighted> </interpolationSpatial> </transformation> {code}https://publicwiki.deltares.nl/display/FEWSDOC/InterpolationSpatialWeightedEA
FEWS-17112Plugin - Module - TransformationFEWS-17266 TVA: Edited data not overwritten in transformations, temporary flagPreserve manual edits in transformation and clear manual edits from dataviewerA new configuration has been added to the transformationModule to allow preserving manual edits. By default manual edits were overwritten. Its now also possible to clear manual edits from the TimeSeriesDialog dataviewer.{code} <transformationModule xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/transformationModule.xsd" version="1.0"> <preserveManualEdits>false</preserveManualEdits> {code}https://publicwiki.deltares.nl/display/FEWSDOC/20+Transformation+Module+-+Improved+schema#id-20TransformationModule-Improvedschema-ManualEditsTVA
FEWS-16869Plugin - Module - TransformationNew transformation: copy a (2D) data from an arbitrary time level in the past to a time series over a relative view periodNew sample transformation SampleSingleTimeStepA new sample transformation is available for copying the values of a time series with a single time step to all of the time steps in the view period of another time series. The transformation can be used for scalar and grids. A config example is available in the documentation: https://publicwiki.deltares.nl/display/FEWSDOC/sampleSingleTimeStephttps://publicwiki.deltares.nl/display/FEWSDOC/sampleSingleTimeStepRWS (NL)
FEWS-16034Plugin - Module - TransformationFEWS-17266 TVA. ability to use PI-tables (1D scalar map series) as lookup tables in transformations.It is now possible to use LookupTables.xml from RegionConfig in the simple and twoDimensional lookup transformations by referencing with locationId, inputParameterId and outputParameterId.It is now possible to use LookupTables.xml from RegionConfig in the simple and twoDimensional lookup transformations by referencing with locationId, inputParameterId and outputParameterId.Example lookup based on 1 input value https://publicwiki.deltares.nl/display/FEWSDOC/Simple#Simple-LookupusingLookupTables.xmlfromRegionConfigFiles {code} <?xml version="1.0" encoding="UTF-8"?> <transformationModule version="1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/transformationModule.xsd"> <variable> <variableId>scalar1</variableId> <timeSeriesSet> <moduleInstanceId>SimpleLookupFromPiTableTest</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.m</parameterId> <locationId>H-2002</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <relativeViewPeriod unit="day" start="-1" end="6"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </variable> <variable> <variableId>scalar2</variableId> <timeSeriesSet> <moduleInstanceId>SimpleLookupFromPiTableTest</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.obs</parameterId> <locationId>H-2002</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <relativeViewPeriod unit="day" start="-1" end="6"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </variable> <transformation id="simpleLookupFromPiTable"> <lookup> <simple> <input> <variableId>scalar1</variableId> </input> <coefficientSet> <interpolationType>linear</interpolationType> <extrapolationType>notAllowed</extrapolationType> <lookupTable> <piTable> <locationId>H-2002</locationId> <inputParameterId>H.m</inputParameterId> <outputParameterId>H.obs</outputParameterId> </piTable> </lookupTable> </coefficientSet> <output> <variableId>scalar2</variableId> </output> </simple> </lookup> </transformation> </transformationModule> {code} Example lookup based on 2 input values https://publicwiki.deltares.nl/display/FEWSDOC/twoDimensional#twoDimensional-LookupusingLookupTables.xmlfromRegionConfigFiles {code} <?xml version="1.0" encoding="UTF-8"?> <transformationModule version="1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/transformationModule.xsd"> <variable> <variableId>scalar1</variableId> <timeSeriesSet> <moduleInstanceId>TwoDimensionalLookupFromPiTableTest</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.m</parameterId> <locationId>H-2001</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <relativeViewPeriod unit="day" start="-1" end="6"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </variable> <variable> <variableId>scalar2</variableId> <timeSeriesSet> <moduleInstanceId>TwoDimensionalLookupFromPiTableTest</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.obs</parameterId> <locationId>H-2001</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <relativeViewPeriod unit="day" start="-1" end="6"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </variable> <variable> <variableId>scalar3</variableId> <timeSeriesSet> <moduleInstanceId>TwoDimensionalLookupFromPiTableTest</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.updated</parameterId> <locationId>H-2001</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <relativeViewPeriod unit="day" start="-1" end="6"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </variable> <transformation id="2dTableTest"> <lookup> <twoDimensionalLookup> <input1> <variableId>scalar1</variableId> </input1> <input2> <variableId>scalar2</variableId> </input2> <coefficientSet> <interpolationType>linear</interpolationType> <extrapolationType>extrapolate</extrapolationType> <lookupTable> <piTable> <locationId>H-2001</locationId> <inputParameterId1>H.m</inputParameterId1> <inputParameterId2>H.updated</inputParameterId2> <outputParameterId>H.obs</outputParameterId> </piTable> </lookupTable> </coefficientSet> <output> <variableId>scalar3</variableId> </output> </twoDimensionalLookup> </lookup> </transformation> </transformationModule> {code} Example [^LookupTables.xml] from RegionConfighttps://publicwiki.deltares.nl/display/FEWSDOC/twoDimensional#twoDimensional-LookupusingLookupTables.xmlfromRegionConfigFilesTVA
FEWS-18102Plugin - Module - TransformationCovadem: spatial interpolation van p-de percentiel bodemligging tracklayers in view period naar output polygonsA new interpolation transformation "trackToGrid" was added.The new transformation produces a grid time series from a track. The coordinates of the track are used to see which grid cell a track value corresponds to, the value is then linked to the closest time for this grid cell. To obtain the output values, either the minimum of the maximum of all track values corresponding to a grid cell and output time combination is used. Optionally, a minimum number of track values and a percentile range can be provided. https://publicwiki.deltares.nl/display/FEWSDOC/Transformation+-+InterpolationSerial+TrackToGridCovadem
FEWS-18101Plugin - Module - TransformationCovadem: interpolatie tijd en plaats van grid of profile tijdserie naar bestaand track layer tijdseriesA new interpolation transformation "LongitudinalProfileToTrack" was added.The new transformation produces values for a track using closest distance interpolation. It takes three time series as input: the longitudinal profile, track latitude and track longitude and produces a single scalar time series as output, which can be used as track values. See the wiki for more information. https://publicwiki.deltares.nl/display/FEWSDOC/Transformation+-+InterpolationSerial+LongitudinalProfileToTrackCovadem
FEWS-17153SystemFEWS-16767 Replace JMS messages between MC and MC Proxy with entry in ForecastingShells table Deltares - Roadmaps
FEWS-17152SystemFEWS-16767 Create overview of all places where and which JMS messages are sent Deltares - Roadmaps
FEWS-17356Database, SystemFEWS-16767 Create Delft_SQL.jar Deltares - Roadmaps
FEWS-17366SystemFEWS-16132 adjust Install/Update scripts to delete local caches/lds from all clients inc SR BPA
FEWS-17744SystemImprove fews.sh script on LINUX to interprete memory settings from *.inifews.sh script improvedDe Linux fews.sh script now by default has 1024Mbyte op max heap space. https://publicwiki.deltares.nl/display/FEWSDOC/02+Launching+FEWSDeltares
FEWS-18149SystemMerge configured truststore with JDK default truststoreclient.truststore will be merged with default JDK truststoreWhen a client truststore is configured, only the public certificates in that store were trusted. If no keystore is configured, all public certificates in the JDK are used to keep track of trused servers. This resulted for example in failure of https imports that used to work when no truststore was configured if the import used a secure connection for which the root certificate was in the trusted JDK store. With this change the root certificates of the JDK will be merged with the ones configured in the custom truststore. Deltares
FEWS-16618System - PI ServiceFEWS-15083 Simplify installation and system administration Simplification and allignment of FEWS Webservices has been completed: • Integrated all the different implementations of the pi-webservice into a single war-file, • Integrate the DAC.jar into this war-file, • Remove drequirement to change Tomcat configurations • Removed requirement to add libraries to Tomcat lib dir. • Made it possible to start and debug a pi-webservice from the Intelij (FEWS development environment) https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+Web+ServicesDeltares
FEWS-18371System - PI ServiceFEWS-15083 PI locations xsd should support location attributes for pi services.location attributes added to PI serviceLocation attributes are now available in the PI service.: https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI+REST+Web+Service Passing the showAttributes=true parameter to the locations resource, will generate the locations attributes. {code} curl "http://localhost:8080/FewsWebServices/rest/fewspiservice/v1/locations?showAttributes=true&documentVersion=1.24" {code}
FEWS-16975System - PI ServiceAdd status page to PI webserviceThe pi webservice (REST) has now a small status page to facilitate debuggingThe pi webservice (REST) has a small status page (status.jsp) which can be used to get some basic information about the webservice. The page provides info about the memory usages and several basic configuration options. Deltares - Roadmaps
FEWS-16619System - PI ServiceFEWS-15083 Improve testabilityTestability of Fews Web Services improved.FEWS test pages have been improved and made available for both PI-SOAP and PI-REST services. Unit testing of the FEWS Web Services has been improved. On the public Wiki examples are given on how to test the REST service using the curl command line. https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI-XML+REST+serviceDeltares - Roadmaps
FEWS-17639System - PI ServiceFEWS-15083 Align functionality of PI Webservice SOAP with PI Webservice RESTPI Webservice REST service has been aligened with SOAP serviceAll functionality available in the PI Webservice SOAP is now also available in the PI Webservice REST API. One exception is the support of POSTING binary timeseries to the REST service. https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI-XML+REST+serviceDeltares - Roadmaps
FEWS-17053System - PI ServiceFEWS-16132 Update the PI-Service so that it will Import ModifersImport modifiers added to the pi-webserviceThe pi-webservice is extended with a service which can be used to upload modifiers. https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI-XML+REST+serviceBPA
FEWS-16901System - PI ServiceFEWS-16887 NWS: #24580 Supply PI-service port numbers to FEWS plug-insAdditional consumer interface added to the Open APIIt is now possible for custom plugins to obtain the port number at which the pi webservice was started by implementing an interface. If a plugin implements the following interface: public interface EmbeddedPiServerPortConsumer { void setPortNumber(int portNumber); } The port number will be provided to the plugin by invoking the implementation of the method setPortNumber. NWS
FEWS-17070System - PI ServiceRetrieve manual edits from PIServiceAdded argument to getTimeSeries that allows client to retrieve only manual editsFor the method getTimeSeries it is now possible to pass the argument 'onlyManualEdits'. When used in combination with the arguments startCreationTime and endCreationTime it is possible to return all manual edited values from FEWS. Sava
FEWS-17801System - SessionFEWS-16767 Remove usage of Session classes from OCObsolete session classes removed. Session has been simplified to 1 row in the database with a unique id.Obsolete session classes removed. Session has been simplified to 1 row in the database with a unique id. Deltares - Roadmaps
FEWS-16446System - SynchronisationFEWS-16767 Dda clientConfig.xml jms configuration JMSServerInstallComplexType has no option to specify timeout. Not relevant anymore since JMS has been removedNot relevant anymore since JMS has been removed Deltares - Roadmaps
FEWS-17864System - Synchronisation, System - Synchronisation 2.0FEWS-16767 Remove old Synchronisation I and IIOld jars and code removed for synchronisation I and IIOld jars and code removed for synchronisation I and II Deltares - Roadmaps
FEWS-18144App - Data Conversion ModuleDCM Export: MeteoAlarm (CAP format)MeteoAlarm Cap exportMeteoAlarm Cap export generates cap files to folder and posts them to SOAP servicew. https://publicwiki.deltares.nl/display/FEWSDOC/MeteoAlarmCapRWS
FEWS-18774App - Master Controller ServerSynchronisation of ImportStatus table between two MC's Deltares
FEWS-17766App - Master Controller ServerFEWS-16767 GlobalRowIdRegeneratordatabase initialization tool generates global row idsGeneration of global row ids is part of the database initialization tool https://publicwiki.deltares.nl/display/FEWS2020/Database+InitializationToolDeltares
FEWS-18773App - Admin Web User Interface, App - Master Controller Server, System - PI ServiceFEWS-16767 Load ntlmauth_x64.dll in java.library.path Deltares
FEWS-18881App - Operator Client Gui (Explorer)Chinese language update for 2017.02 Deltares
FEWS-19121App - Operator Client Gui (Explorer)Correct reference Delft-FEWS Copyright & Credits page from About box Deltares
FEWS-18313App - Operator Client Gui (Explorer)FEWS-16767 Rolling Barrel Implementations SA / OC Deltares
FEWS-4834DatabaseFEWS-4832 DB Schema checkSchema validation https://publicwiki.deltares.nl/pages/viewpage.action?pageId=133857857
FEWS-18725DatabaseFEWS-16767 create clone script for migration of 2017.02Database clone scripts for duplicating a Delft-FEWS database in support of 2017.02 migration without offline time. https://publicwiki.deltares.nl/display/FEWSDOC/How+to+create+a+clone+of+the+databaseDeltares
FEWS-16943DatabaseMigrate MSSQL server script from using osql to sqlcmd. Osql will be removed from SQL Server. Deltares
FEWS-15954Databasedatabase replicator should be able to cope with default values / schema changes. Deltares
FEWS-17575DatabaseOptimize Snapshot / Replicate functionality {code:xml} <?xml version="1.0" encoding="UTF-8"?> <exportArchiveModule xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/exportArchiveModule.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews"> <exportSnapShot> <general> <archiveFolder>$ARCHIVE_DIR$</archiveFolder> </general> <activities> <exportSnapShot> <areaId>test</areaId> <filter id="only time series"> <xmlConfig enabled="false" name="Default xml config" synchLevel="11"/> <coldStates enabled="false" name="Default cold states" synchLevel="11"/> <moduleDataSets enabled="false" name="Default module data sets" synchLevel="11"/> <mapLayers enabled="false" name="Default map layers" synchLevel="11"/> <icons enabled="false" name="Default icons" synchLevel="11"/> <reportTemplates enabled="false" name="Default report templates" synchLevel="11"/> <reportImages enabled="false" name="Default report images" synchLevel="11"/> <continuousTimeSeries enabled="true" name="Simulated" synchLevel="0" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Telemetry" synchLevel="1" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Manual" synchLevel="5" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Astronomical and climatological" synchLevel="4" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Small external forecast grids" synchLevel="6" maxAge="1000" unit="week"/> <continuousTimeSeries enabled="true" name="Large external forecast grids" synchLevel="16" maxAge="10000" unit="week"/> <warmStates enabled="false" name="Warm states" maxAge="10" unit="week"/> <logEntries enabled="false" name="Log Entries" maxAge="1" unit="week"/> <thresholdEvents enabled="false" name="Threshold Events" maxAge="1" unit="week"/> </filter> </exportSnapShot> </activities> </exportSnapShot> </exportArchiveModule> {code} Deltares
FEWS-17901MCRecoveryToolFEWS-16767 Add "clear_database" task to mc recovery toolMcRecoveryTool optino to wipe all tables from the central database in order to replace no longer present functionality of populater tool. https://publicwiki.deltares.nl/display/FEWSDOC/MCRecoveryToolDeltares
FEWS-18831Plugin - Gui - Time Series, Plugin - Module - ReportsArrow in the display: plot and html reportadd support for rotated arrow markers to the report moduleFor FEWS-16981, support for rotated arrow markers, which could for example be used to plot a wind speed graph with arrow markers showing the wind direction, was added to the time series dialog (data display). The report module now also supports such arrow markers, allowing them to be used in the exported charts.In the <parameterDisplayOptions> of the TimeSeriesDisplayConfig.xml: {code:xml} <parameterDisplayOptions id="WS.15"> <preferredColor>purple</preferredColor> <lineStyle>solid</lineStyle> <markerRotationParameterId>WR.15</markerRotationParameterId> <markerIcon>arrow_icon_test.png</markerIcon> <markerRotationOffset>180</markerRotationOffset> </parameterDisplayOptions> {code} For the report module to include the arrows, the direction time series must be included in the chart of the module config file: {code:xml} <chart id="chartMain" formatId="chartFormat" width="1200" height="600"> <timeSeries label="speed" preferredColor="purple">Speed</timeSeries> <timeSeries label="direction" preferredColor="purple">Direction</timeSeries> <fileName>arrow_test</fileName> </chart> {code}https://publicwiki.deltares.nl/display/FEWSDOC/02+Time+Series+Display+Configuration#id-02TimeSeriesDisplayConfiguration-DirectionalarrowmarkersMozambique
FEWS-18883Plugin - Module - Data ImportCovadem: add header to existing Covadem import
FEWS-18996Plugin - Module - Data ImportNew import for SMN ETA based on previous UruguaySMNETAEtaSmn Import typeEtaSmn imports gridded time series from asci file format. File example : {code} lon lat p01 p02 p03 p04 p05 p06 -56.9874 -28.0166 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 -56.9250 -28.0166 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 -56.8625 -28.0166 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 {code} The forecast time is read from the file name. The file name should comply with the following file name pattern: ??????????yyyyMMddHH????, for example Datos_WRF_2018062000.txt. Event times are stored in the column headers p01, p02,... where the numbers correspond to the hours. The dates/times are always in GMT. This reader needs a geometry configured in the region config Yacyreta (Arg)
FEWS-18833Plugin - Module - Data ImportNew import for hydroestimator format fileNew import for hydroestimator format fileA new importType "UruguayHydroEstimator" was added for files following the hydroestimator format.ModuleConfigFile: {code:xml} <import> <general> <importType>UruguayHydroEstimator</importType> <folder>$IMPORT_FOLDER$/HYDRO_ESTIMATOR</folder> </general> <timeSeriesSet> <moduleInstanceId>Import_Hydro_Estimator</moduleInstanceId> <valueType>grid</valueType> <parameterId>P.pro</parameterId> <locationId>hydroEstimator</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour" multiplier="12"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </import> {code} With a grid configured for locationId "hydroEstimator" in grids.xml.https://publicwiki.deltares.nl/display/FEWSDOC/UruguayHydroEstimatorYacyreta
FEWS-17771Plugin - GUI - Sample Viewer, Plugin - Module - Data ImportFEWS-17944 Request to import same sample via different imports without overwritingAdd optional prefix to sampleIdColumn in generalCsv importIn the generalCsv import an optional "prefix" attribute was added to the <sampleIdColumn>. The prefix (if present) is added to the front of each sampleId imported from the file. This allows you to differentiate between samples from different imports, preventing the samples from another import from being overwritten.{code:xml} <table> <dateTimeColumn name="DATE_SMP" pattern="dd-MM-yy HH:mm"/> <locationColumn name="LOC_CODE"/> <unitColumn name="Eenheid"/> <parameterColumn name="PARAMETER_ID"/> <sampleIdColumn name="SMP_CODE" prefix="Prefix_"/> <propertyColumn name="COST_CODE" key="COST_CODE"/> <valueColumn name="Waarde"/> </table> {code}https://publicwiki.deltares.nl/display/FEWSDOC/General+Csv#GeneralCsv-SampleIdprefixWaternet
FEWS-17762Plugin - GUI - Sample Viewer, Plugin - Module - Data ImportFEWS-17944 GeneralCsv parser gives warning on incorrect date but just continues importing next line Waternet
FEWS-19124Plugin - Module - Data Import, Plugin - Module - General AdapterGA <importNetcdfActivity> doesn't recognize sea_surface_height as a CF conform standard name Water Technology (AUS)
FEWS-18032Plugin - Module - Data ImportVigicrues webservice importVigicrues webservice import addedTwo new import types were added, Vigicrues_web and Vigicrues_xml, which can be used to import data from the Vigicrues webservice. https://publicwiki.deltares.nl/display/FEWSDOC/Vigicrues+WebRijkswaterstaat
FEWS-18916Plugin - Module - Data ImportUpdate aqualarm importAqualarm REST service importAqualarmRest import has been implemented in favor of the deprecated Aqualarm import. Currently the import doesn't support ending a session. This means at most 3 sessions can be started in a period of 5 minutes. Another thing to notice is that the parameterId's have been changed. https://publicwiki.deltares.nl/display/FEWSDOC/AqualarmRestRWS
FEWS-18236Plugin - Module - Data ImportWIWB-API Time series importWIWB API importThe WIWB API import has been implemented and is available as import type: WIWB https://publicwiki.deltares.nl/display/FEWSDOC/WIWBGO-FEWS
FEWS-17529Plugin - Module - Data ImportHandling dynamic location coordinatesDynamic locations can be displayed using a tracklayer in the gridDisplayDynamic locations can be displayed using a tracklayer in the GridDisplay. Using the displayCurrentTrackOnly allows you to see the moving locations. {code} <gridPlot id="SkyGeo Demo" name="Sky Geo Track"> <trackLayer> <displayCurrentTrackOnly>true</displayCurrentTrackOnly> <lineColor>yellow</lineColor> <geoDatum>WGS 1984</geoDatum> <xTimeSeriesSet> <moduleInstanceId>ImportSkyGeo</moduleInstanceId> <valueType>scalar</valueType> <parameterId>X</parameterId> <locationSetId>sky_geo.locations</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read complete forecast</readWriteMode> </xTimeSeriesSet> <yTimeSeriesSet> <moduleInstanceId>ImportSkyGeo</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Y</parameterId> <locationSetId>sky_geo.locations</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read complete forecast</readWriteMode> </yTimeSeriesSet> <valueTimeSeriesSet> <moduleInstanceId>ImportSkyGeo</moduleInstanceId> <valueType>scalar</valueType> <parameterId>height</parameterId> <locationSetId>sky_geo.locations</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read complete forecast</readWriteMode> </valueTimeSeriesSet> </trackLayer> <classBreaks> <color color="070268" lowerValue="-0.01" opaquenessPercentage="70"/> <color color="0900AE" lowerValue="-0.008" opaquenessPercentage="70"/> <color color="4040FF" lowerValue="-0.006" opaquenessPercentage="70"/> <color color="0080C0" lowerValue="-0.004" opaquenessPercentage="70"/> <color color="129FFE" lowerValue="-0.002" opaquenessPercentage="70"/> <color color="00FF40" lowerValue="0" opaquenessPercentage="70"/> <color color="FFFF00" lowerValue="0.002" opaquenessPercentage="70"/> <color color="FF8000" lowerValue="0.004" opaquenessPercentage="70"/> <color color="FF0000" lowerValue="0.006" opaquenessPercentage="70"/> <color color="FF0080" lowerValue="0.008" opaquenessPercentage="70"/> <color color="FFFFFF" lowerValue="01.0" opaquenessPercentage="70"/> </classBreaks> </gridPlot> {code}https://publicwiki.deltares.nl/display/FEWSDOC/SkyGeoDamSAFE project
FEWS-18034SystemUpdate Indonesian language files APP
FEWS-18630System - PI ServiceFEWS-18470 No default filter configured error when no configuration is availablestandalone FEWS Web Services startup error improvementIn case the FEWS Web Services is started in standalone mode (by configuring the clientConfig.xml as a standalone client) without a Config folder this is now correctly reported. Deltares
FEWS-18695 FEWS-16767 Force/advise usage of Java 1.8.0_172 or later
FEWS-18186 FEWS-16767 Log Collector Servicelog collector can be installed as a separate processlog collector can be installed as a separate process.
FEWS-18817 FEWS-18245 Navigation panel's run options window larger than available screen Deltares

  • No labels