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

Delft-FEWS 2019.02 Solved Features
Component/sKeyCustomer nameSummaryRelease Note TextRelease Note Text DescriptionLink to DocumentationConfig Example
App - Admin Web User InterfaceFEWS-15860RWS (NL)Admin Interface: Upload Multiple New Action ConfigurationAdmin Interface: It is now possible to upload multiple new action configuration at the same timeYou can upload any number of action configurations in one file if you click on "Upload multiple configurations" button. This feature is available since 2019.02. If you click the checkbox "Default", all uploaded configurations will be set as default. If there are no configurations in the database that share an action ID with the new uploaded configuration, it will be set to default automatically. If the set default checkbox is not checked, the new configurations will appear in the lists of versions under the same action id. The upload has a strict XML schema. https://publicwiki.deltares.nl/display/FEWSDOC/04+Setting+Up+Event-Action+Configuration#id-04SettingUpEvent-ActionConfiguration-Uploadingmultipleactionconfigurations<?xml version="1.0" encoding="UTF-8"?> <eventActions xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="file:///C:/Developement/trunk/master-controller/src/main/resources/schemas/eventactions.xsd"> <eventAction actionConfigurationId="New Zeland" description="Description"> <enhance> <tag name="AIRE_FORECAST"/> <resume/> </enhance> </eventAction> <eventAction actionConfigurationId="newId" description="Description2"> <enhance> <tag name="Denver"/> <suspend/> </enhance> </eventAction> <eventAction actionConfigurationId="EDEN_ID" description="Description3"> <enhance> <tag name="EDEN_FORECAST"/> <repeatinterval interval="3600"/> </enhance> </eventAction> <eventAction actionConfigurationId="EXPORT_ID" description="Description4"> <oneoff> <cardinaltime interval="900" reference="2004-01-01T00:00:00.000+00:00"/> <tag name="EXPORT_CURRENT"/> </oneoff> </eventAction> </eventActions>
App - Admin Web User InterfaceFEWS-20513EAFEWS-18050 FFFS-AI: Add audit functionality in the Admin Interfaceaudit trail event logsBoth the Admin Interface and the OC now generate audit trail event logs.https://publicwiki.deltares.nl/display/FEWSDOC/31.+Audit+Trail+Event+Log
App - Admin Web User InterfaceFEWS-20507EAFEWS-18050 FFFS-AI: Show additional information in Task Details pageThe task runs page allows showing all log files of one taskrun or of (max 50) recent task runs.The task runs page allows showing all log files of one taskrun or of (max 50) recent task runs.https://publicwiki.deltares.nl/display/FEWSDOC/Scheduled+Tasks+-+Task+Runs
App - Admin Web User InterfaceFEWS-20506EAFEWS-18050 FFFS-AI: Show runtime of last task in Scheduled Forecast pageLatest Run Time visible in scheduled tasks listLatest Run Time visible in scheduled tasks listhttps://publicwiki.deltares.nl/display/FEWSDOC/Scheduled+Tasks
App - Admin Web User InterfaceFEWS-20485EAFEWS-18050 FFFS-AI: Option to delete Importstatus records from database and use correct coloursimport status colors visible in admin interfaceConfigured Import Status Colors in the SystemMonitor configuration file are now also used by the Admin Interfacehttps://publicwiki.deltares.nl/display/FEWSDOC/Admin+Interface+Files+-+Import+Status
App - Admin Web User InterfaceFEWS-14310EAFEWS-18050 Add more info to database and Admin InterfaceImprovements on running tasks page of Admin InterfaceImprovements on running tasks page of Admin Interfacehttps://publicwiki.deltares.nl/display/FEWSDOC/Running+Tasks
App - Admin Web User InterfaceFEWS-21384DeltaresAdd filter option to workflow mapping matrix to show unmapped workflowsUnmapped workflows are marked with red background colorUnmapped workflows are marked with red background colorhttps://publicwiki.deltares.nl/display/FEWSDOC/Workflow+FSS+Groups+Mapping
App - Admin Web User InterfaceFEWS-21369DeltaresAI FSS Groups werkt niet lekker, erg foutgevoeligFSS Groups and workflow mapping improvementsFss Groups page show per FSS group if allow unmapped is enabled. When mapping all workflows to a group, a confirmation is required now. Workflow will have a red background colorhttps://publicwiki.deltares.nl/display/FEWSDOC/Workflow+FSS+Groups+Mapping
App - Admin Web User InterfaceFEWS-20486DeltaresAI: Improve wording/explanation for Scheduled Task - Run OptionsImproved tooltip text of runOptionsImproved tooltip text of runOptionshttps://publicwiki.deltares.nl/display/FEWSDOC/Scheduled+Tasks+-+New+Task
App - Admin Web User InterfaceFEWS-20818DeltaresCase insensitive login AIUsername is now case insensitve when logging in with the admin interfaceUsername is now case insensitve when logging in with the admin interfacehttps://publicwiki.deltares.nl/display/FEWSDOC/Delft-FEWS+Admin+Interface+-+Introduction#Delft-FEWSAdminInterface-Introduction-Introduction-Logonscreen
App - Admin Web User InterfaceFEWS-20683DeltaresAdmin Interface Editing FailOver tasks will change the ownerMcId of the Taskedit button is disabled for remote mc tasksedit button is disabled for remote mc taskshttps://publicwiki.deltares.nl/display/FEWSDOC/Scheduled+Tasks
App - Admin Web User InterfaceFEWS-20679DeltaresFEWS-19650 NGINX proroxy and 413 Request Entity Too Large for uploading basebuild to admin interfaceOIDC authentication requires large http headersOIDC authentication requires large http headers. {code} AD authentication can use large http headers that sometimes are larger that the maximum allowed 8K that is set by default for Apache 2. The /etc/apache2/apache2.conf configurations should be updated with the following settings: LimitRequestFieldSize 80000 LimitRequestBody 0 https://publicwiki.deltares.nl/display/FEWSDOC/Authentication+and+Authorization+using+the+Apache2+OpenID+Connect+module+-+mod_auth_openidc
App - ArchiveFEWS-21765 FEWS-21449 Not possible to use 2 archive servers on the same machine
App - ArchiveFEWS-21204TVA / BPA / NWS / BC HydroRetrieve states (Datastore related work)
App - ArchiveFEWS-20979DeltaresFEWS-18050 FFFS-Archive: get rid of config.zip file and use original files
App - ArchiveFEWS-17999DeltaresFEWS-18468 Open Archive Integration: Seamless Integration for grids
App - Configuration Manager GuiFEWS-21366EAFEWS-18050 Config manager. Checksum instead of download for config file equals check.A calculated hash is used to determine if imported config files are different from the current active one.A database column "hash" has been added for each config file type. This stores a calculated string for each inserted config file based on its contents. Whenever new config files are imported the hash of new file is compared with that of the current active file. Only if the hash is different the current active version is read from the database in order to show the differences. This saves a lot data that has to be transferred over the network. If the hash is not filled yet (file is imported in older version), it will be done after the file is read once.https://publicwiki.deltares.nl/display/FEWSDOC/20.2+Configuration+Manager+-+from+2017.02
App - Configuration Manager Gui, App - Operator Client Gui (Explorer)FEWS-20336DeltaresFEWS-18245 Opening an OC when you have the CM open (or vice versa) gives an unnecessary warning/pop-upDifference between OC and CM session is taken into account for duplicate session warningDifference between OC and CM session is taken into account for duplicate session warninghttps://publicwiki.deltares.nl/display/FEWSDOC/01+FEWS+Explorer#id-01FEWSExplorer
App - Configuration Manager GuiFEWS-21584DeltaresAllow Configuration manager over Database proxy
App - Configuration Manager Gui, App - Master Controller ServerFEWS-20347DeltaresAdd partition sequence mapping in config revisionset: parallel runs can not run as one-off
App - Delft-FEWSFEWS-20951DeltaresVERSION file in bin directory_build_manifest.txt in bin dirThe Delft FEWS version and build number of a bin dir is now readable as plain text in bin/_build_manifest.txt
App - Forecasting Shell ServerFEWS-19956EAFEWS-18050 FFFS: Improve deployment of FEWS in AzureAdmin Interface improvements for cloud integrationAdmin Interface improvements for cloud integrationhttps://publicwiki.deltares.nl/display/FEWSDOC/Dashboard
App - Forecasting Shell ServerFEWS-20345DeltaresFEWS-19650 Number of FSSs in ready state don't match the number in the FSS groupFix readyState for FSS GroupFix readyState for FSS Grouphttps://publicwiki.deltares.nl/display/FEWSDOC/FSS+Groups
App - Master Controller Server, System - SynchronisationFEWS-20559TVAFEWS-17996 Allow status MC-MC synchronization while in false failoverConfig option for Mc-Mc synchronization status onlyNew config option for Mc-Mc synchronization only on status tables, e.g. SystemActivities, ComponentLogFileSnapshots, MasterControllers, FSSGroups, ForecastingShells, FssStatus, LiveMcAvailabilities https://publicwiki.deltares.nl/display/FEWSDOC/Delft-FEWS+Installation+-+Configure+MasterController+application+-+2017.02+and+later{code} <remotemc mcid="..."> <database driverclass="oracle.jdbc.OracleDriver"> <connection string="..." password="..."/> </database> <mcSynchronisation statusOnly="true"/> </remotemc> {code}
App - Master Controller ServerFEWS-17386TVAFEWS-17996 TVA: Request to not automatically run tasks on primary system when a failover is triggeredNew task option to not run failover tasks on ownerMc when the ownerMc is in failoverWhere before a task was either a failover task or not, a task now has three different options 1. Run Duty - Run this Task only on the Master Controller that owns it (default). 2. Run Duty and Failover - When the Duty Master Controller is in Failover mode, run this task on the top priority Failover Master Controller, but also run this task on the Duty Master Controller that owns it. 3. Suspend Duty in Failover - When the Duty Master Controller is in Failover mode, run this task on the top priority Failover Master Controller and do not run this task on the Duty Master Controller that owns it. https://publicwiki.deltares.nl/display/FEWSDOC/Scheduled+Tasks+-+New+Task
App - Master Controller ServerFEWS-20834EAFEWS-18050 FFFS: Add function to send event codes to Azure Service BusAzure Service Bus AlerterThe Azure Service Bus Alerter can be used to configure MC_SystemAlerter tasks that can send messages to the Azure Service Bus.https://publicwiki.deltares.nl/display/FEWSDOC/Azure+Service+Bus+Alerts
App - Master Controller ServerFEWS-20976DeltaresImprove Caching of ActionConfiguration. Now it takes up to 5 minutes.
App - Operator Client Gui (Explorer)FEWS-19950EAFEWS-18050 FFFS: Improve KFlows functionalityFFFS KFlows improvementsFFFS KFlows improvementshttps://publicwiki.deltares.nl/display/FEWSDOC/16+KFlows+Display
App - Operator Client Gui (Explorer)FEWS-20849EAFEWS-18050 FFFS: Implement UK BST – British Summer Time TimezoneUK British time zone GMT/BSTShows GMT in the winter and BST in the summerhttps://publicwiki.deltares.nl/display/FEWSDOC/B+Enumerationsexplorer.xml {code:xml} <dateTime> <timeZoneName>GMT</timeZoneName> <timeZoneName>GMT/BST</timeZoneName> <dateTimeFormat>E dd-MM-yyyy HH:mm:ss</dateTimeFormat> <cardinalTimeStep unit="minute" multiplier="15"/> </dateTime> {code}
App - Operator Client Gui (Explorer), ConfigurationFEWS-21101EAFEWS-18050 Recognize "none" as qualifier id in time series filter (modifiers, products, etc)
App - Operator Client Gui (Explorer)FEWS-19961EAFEWS-18050 FFFS: Improvements to PermissionsIn the log browser users willno longer see log messages from workflows they have no permission to see.In the log browser users willno longer see log messages from workflows they have no permission to see.https://publicwiki.deltares.nl/display/FEWSDOC/07+Permissions
App - Operator Client Gui (Explorer)FEWS-20515EAFEWS-18050 FFFS-OC: Add audit functionality to the OCAudit trail for Operator Client. Generate event codes that are stored as log messagesAudit trail for Operator Client. Generate event codes that are stored as log messageshttps://publicwiki.deltares.nl/display/FEWSDOC/31.+Audit+Trail+Event+Log#id-31.AuditTrailEventLog-OperatorClientaudittraileventlogmessagesAudit trail for Operator Client. Generate event codes that are stored as log messages
App - Operator Client Gui (Explorer), SystemFEWS-21017DeltaresFEWS-18245 Use the same look and feel across all platforms and settingsUse the same GUI look and feel across all platforms and color schemesFEWS now uses the exact same GUI look and feel across all platforms and regardless of whether a color scheme is active or not (although color schemes of course do still change the colors of the GUI elements).https://publicwiki.deltares.nl/display/FEWSDOC/08+Color+schemes+and+custom+colors#id-08Colorschemesandcustomcolors-Changessince2019.02
App - Operator Client Gui (Explorer)FEWS-20124DeltaresFEWS-19650 FFFS: When uploading a new Patch.jar the OC has an incomplete messageClearly show who updated the root config and with which commentClearly show who updated the root config and with which commenthttps://publicwiki.deltares.nl/display/FEWSDOC/01+FEWS+Explorer#id-01FEWSExplorer
ConfigurationFEWS-20440WaternetRemove ConfigUpdateScriptConfig Editor has been removedConfig Editor has been removedhttps://publicwiki.deltares.nl/display/FEWSDOC/30+Config+Update+Module
ConfigurationFEWS-20901EAFEWS-18050 FFFS: Add one to many relations in locationSetOne to many location relations for building location setsbuilding dynamic locations sets. E.g. all locations in a catchment {code:xml} <locationSet id="Stations"> <esriShapeFile> <file>Stations</file> <geoDatum>WGS 1984</geoDatum> <id>%ID%</id> <name>%ID%</name> <x>%X%</x> <y>%Y%</y> <z>0</z> <attributeFile> <csvFile>upstream</csvFile> <id>%ID%</id> <oneToManyRelation id="UPSTREAM"> <relatedLocationId>%RELATION%</relatedLocationId> </oneToManyRelation> </attributeFile> </esriShapeFile> {code}
ConfigurationFEWS-21120EAFEWS-18050 Allow shapeIdFunction besides shapeId in the polygons.xml {code:xml} <?xml version="1.0" encoding="UTF-8"?> <polygons xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://chps1/schemas/polygons.xsd"> <esriShapeFile> <file>MARFC_SubBasins_WGS84</file> <geoDatum>WGS 1984</geoDatum> <shapeIdAttributeName>basin_id</shapeIdAttributeName> <shapeIdFunction>@SHAPE_ID@</shapeIdFunction> </esriShapeFile> </polygons> {code}
ConfigurationFEWS-20637EAFEWS-18050 Attribute exits constraint. Recognize multi value attributes with only null values as unavailable
DatabaseFEWS-20978EAFEWS-18050 make create scripts available to the EA branchAdded table UserSettings and ProductInfo
DatabaseFEWS-19974EAFEWS-18050 FFFS: Automatically generate locationSets with template and attributesAutomatically group a location set into sub location sets that share the same attributesubLocationSetIdFunction is used to generate the location set idhttps://publicwiki.deltares.nl/display/FEWSDOC/02+LocationSets{code:xml} <locationSet id="Meteo Stations"> <subLocationSetIdFunction>Meteo Stations @region@</subLocationSetIdFunction> <esriShapeFile> <file>Meteo_Stations</file> <geoDatum>WGS 1984</geoDatum> <id>%ID%</id> <name>%ID%</name> <x>%X%</x> <y>%Y%</y> <z>0</z> <relation id="UPSTREAM"> <relatedLocationId>%RELATION%</relatedLocationId> </relation> <attribute id="a"> <description>constant a</description> <text>a</text> </attribute> <attribute id="region"> <description>Catchment</description> <text>%REGION%</text> </attribute> {code}
DatabaseFEWS-20655EAFEWS-18050 changes in latest database update script need to be applied to FFFS Azure Databasedatabase changes for FFFS applied to 201902database changes for FFFS applied to 201902https://publicwiki.deltares.nl/display/FEWSDOC/Delft-FEWS+Installation+-+Central+Database
DatabaseFEWS-21562DeltaresFEWS-21449 Create 2019.02 database scripts
Debug Tool - Workflow NavigatorFEWS-20621MDBAFEWS-14730 Show description of transformation modules and transformation elements in OC GUI (R_323)Show description of transformation modules and transformation elements in OC GUI as mouse label textAdded <description> to individual transformations, they will appear as labels. However, the name of the transformation module is built not from the configuration file of the module, but from the workflow file. Therefore I added a new field workflow activity to add a <description> This description should work as a label also for import, export, sub-workflow, performace too.https://publicwiki.deltares.nl/display/FEWSDOC/20+Transformation+Module+-+Improved+schema#id-20TransformationModule-Improvedschema-Description {code:xml} <transformation id="merge"> <merge> <simple> <inputVariable> <variableId>Wiski</variableId> </inputVariable> <inputVariable> <variableId>Server</variableId> </inputVariable> <fillGapConstant>0</fillGapConstant> <outputVariable> <variableId>merge1</variableId> </outputVariable> </simple> </merge> <description>transformation description</description> </transformation> <?xml version="1.0" encoding="UTF-8"?> <workflow 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" version="1.1"> <activity> <runIndependent>true</runIndependent> <moduleInstanceId>CanadaMeteo</moduleInstanceId> <description>Description</description> </activity> </workflow> {code}
Plugin - Gui - Archive DisplayFEWS-21206TVA / BPA / NWS / BC HydroRetrieve + import States in database - GUI WorkArchiveDisplay - importing statesStates are archived in the forecast archiving process, together with time series, reports and modifiers. Up to now the states were only ingested while importing a simulated data set From now on, it is also possible to ingest the states only. For this purpose an (optional) element “statesWorkflowId” has been added to the ArchiveModuleDisplay config file. An example from _ArchiveModuleDisplay.xml_ : {code:xml} <archiveImportWorkflowId>ImportArchivedData</archiveImportWorkflowId> <dataTypeImportWorkflows> <statesWorkflowId>ImportArchivedStates</statesWorkflowId> </dataTypeImportWorkflows> {code} The import states workflow (ImportArchivedStates in this example) should have “moduleStatesImportActivity” , to ensure that only states are ingested from simulated folder, and not the whole forecast An example from _ importArchiveModule.xml _: {code:xml} <importSimulated> <activities> <moduleStatesImportActivity/> </activities> <importFolder>$ARCHIVE_DOWNLOAD_FOLDER$/simulated</importFolder> </importSimulated> {code} When “statesWorkflowId” is configured, and states data set is selected, the “download and import data” button becomes enabled and it is possible to ingest the selected states. See attached screen dump https://publicwiki.deltares.nl/display/FEWSDOC/21+Archive+display
Plugin - Gui - Archive DisplayFEWS-20746TVAFEWS-20739 TVA: Auto filter sources in the archive catalogue tool based on data set typeArchive Catalog Display shows per data set type only the relevant sourcesEvery time the harvester is scanning and updating the archive database, it creates also DataTypeInfo.xml. DataTypeInfo.xml contains per data type the source Id’s that are available in the archive database for that data type. Information from DataTypeInfo.xml is used by Archive Catalog Display to show the relevant source per data type. If the DataTypeInfo.xml is not available, or not created for some reason, the Archive Catalog Display shows all known sources , for each data type. https://publicwiki.deltares.nl/display/FEWSDOC/21+Archive+display
Plugin - Gui - DashboardFEWS-21311EAFEWS-18050 Add options to automatically arrange dashboard framesAdd options to new dashboard panel to neatly arrange framesThe dashboard panel has three menu options to arrange the frames currently in the panel: arrange horizontally, arrange vertically and arrange automatically. The arrange horizontally and vertically options perform as would be expected. The arrange automatically options attempts to determine the desired arrangement based on the current positions, removing as much overlap in frames and empty space as possible, preferring to assign extra space to the top frame if possible.https://publicwiki.deltares.nl/display/FEWSDOC/33+Dashboard+Display
Plugin - Gui - DashboardFEWS-14870EAFEWS-18050 New Dashboard display for Hyrad functionality https://publicwiki.deltares.nl/display/FEWSDOC/33+Dashboard+Display
Plugin - Gui - Grid DisplayFEWS-17182UAE NavyFEWS-17145 Spatial Display - show plot (cross section-z) based on user defined cross section (x,y) Create a 2D longitudinal profile on the fly for 3D data a in the spatial display. Start drawing a longitudinal profile with a CTRL-click in the spatial display and click to add points as required. Finish the profile with a double-click for the last point. Open up the longitudinal profile in the timeseriesdisplay with CTRL-F11, or via the context menu. Note, this feature only works for * data within 1 grid partition. In some cases 3D data model runs are run on multiple domain partitions. This data can be shown as a 2D longitudinal profile, but only if the profile remains within a single domain. * scalar data (e.g. Water temperature or salinity), and not yet for vector data like currents. (2 screenshots are attached to the issue)
Plugin - Gui - Grid DisplayFEWS-17736TVAFEWS-17689 TVA Hydrothermal: Extend vertical slider bar for Delft3D-FLOW or D-Flow FM grids from Sigma layers to Z layersVertical slider in spatial display for Z layersBesides sigma layers it is now also possible to configure a vertical slider for z layers
Plugin - Gui - Grid DisplayFEWS-19339TVAFEWS-20739 TVA: Increase number of grid cells allowed for Spatial Display to avoid Illegal argument for 1st check passed
Plugin - Gui - Grid DisplayFEWS-20908NWSFEWS-20886 NWS: #62738 Show updated (latest import) time in Spatial Display for external historical gridded/scalar time seriesShow last import time for external historical data in grid displayThis feature allowes to show last import time for external historical data in grid display. This option is supporten with online version only. The option dataFeedId needs to be configured per gridPlot. The value of the dataFeedId must be the same value that can be seen in System Monitor table, tab Import Status. The id should be the one that corresponds with the module instance id of the time series.https://publicwiki.deltares.nl/display/FEWSDOC/01+Grid+Display#id-01GridDisplay-Showlastimporttimeforexternalhistoricaldata{code:xml} <gridPlotGroup id="Radar KNMI"> <gridPlot id="TF0005_R" name="Uncorrected 5 min"> <dataFeedId>ATIS</dataFeedId> <timeSeriesSet> <moduleInstanceId>ImportWIWB</moduleInstanceId> <valueType>grid</valueType> <parameterId>P.radar</parameterId> <qualifierId>realtime</qualifierId> <locationId>KNMI-RADAR1km</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="5"/> <relativeViewPeriod unit="day" start="-10" end="5"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> <accumulationTimeSpan multiplier="1" unit="hour"/> <accumulationTimeSpan multiplier="6" unit="hour"/> <accumulationTimeSpan multiplier="12" unit="hour"/> <classBreaks> <break lowerValue="0" color="white" label="0 mm/hr" opaquenessPercentage="25"/> <break lowerValue="0.008" color="light blue" label="0.1" opaquenessPercentage="75"/> <break lowerValue="0.083" color="8CAAFF" label="1" opaquenessPercentage="80"/> <break lowerValue="0.167" color="636DFF" label="2" opaquenessPercentage="85"/> </classBreaks> <contourLinesColor>gray</contourLinesColor> </gridPlot> </gridPlotGroup> {code}
Plugin - Gui - Grid DisplayFEWS-20868FOENFEWS-9563 FOEN: Option in Spatial display to show less decimals in values on mapAdd option in spatial display to decrease number of decimals in labelsAdds two menu items to the label drop down menu in the spatial display. One to increase and one to decrease the number of decimals shown in the labels and tooltips. If a user has used these buttons to decrease the number of decimals, this will be stored in the user settings. This setting is stored separately for each parameter group. The number of decimals can never be increased to more than the resolution with which the values are stored (the configured value resolution of the parameter group).https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display#id-05SpatialDisplay-ControlToolbar
Plugin - Gui - Grid DisplayFEWS-20859FOENFEWS-9563 FOEN: Add aggregation timestep in time label of spatial displayFrom now on grid display aggregation slider shows start and end of aggregation period instead of one timestamp.When you use the aggregation slider in the grid displayt he time label used to only show a timestep. From now on it will show the aggregation period. For example if the aggregation period is 6 hours and the time is 15-05-2019 00:00, then the label should say "Time 14-05-2019 18:00:00 to 15-05-2019 00:00".https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display
Plugin - Gui - Grid DisplayFEWS-21210EAFEWS-18050 Store selected aggregation in user settingsStore selected aggregation in user settingsThe aggregation selected in the grid display is now stored in the user settings. When starting FEWS the same aggregation will be selected as was selected when closing.https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display#id-05SpatialDisplay-MovingAverageorAccumulationSlider
Plugin - Gui - Grid DisplayFEWS-20709EAFEWS-18050 Add forecast selection button to Grid DisplayAdd a forecast selection button to the Grid DisplayA forecast selection button was added to the grid display to allow the user to select a different (previous) forecast without opening the spatial thumbnails. The button can be pressed to cycle through the available forecasts or a specific forecast time can be selected from its drop-down menu. This also allows selecting a previous forecast when viewing an ensemble time series (where the regular spatial thumbnails are disabled and only the newly developed ensemble thumbnails are available).https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display#id-05SpatialDisplay-Selectingdifferentforecasttimes
Plugin - Gui - Grid Display, Plugin - Module - Spatial ModifiersFEWS-20546EAFEWS-18050 FFFS: compose best estimate NWPAdd spatial modifiers to modify grid time seriesTwo new modifiers have been added which allow modifying grid time series. These modifiers need to be created through the spatial display (instead of the modifiers panel). The spatial copy modifier allows copying values from a different grid time series for a certain area and time period. The spatial profile modifier allows replacing all grid values within a certain area with the values of a scalar time series entered by the user.https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display#id-05SpatialDisplay-CreatingSpatialModifiers
Plugin - Gui - Grid DisplayFEWS-20893EAFEWS-18050 Add sketch buttons section to GridDisplay toolbarMove sketch functionality in spatial display to new sketch button sectionThere was already a lot of functionality present in the spatial display to draw points, profiles and areas and use these to extract time series data and show it in a graph (time series dialog). This functionality was all "hidden" in the right-click menu. The functionality has been moved to two new buttons (with drop-down menus) in the spatial display toolbar to make it more accessible: one button for all "drawing" options and one for all options to then extract chart data.https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display
Plugin - Gui - Grid Display, Plugin - Module - Spatial ModifiersFEWS-21131EAFEWS-18050 Add a tooltip to the time slider and map where a spatial modifier has been appliedAdd a tooltip to the time slider and map where a spatial modifier has been appliedA tooltip with information about the applied spatial modifiers was added to the time slider and the applied modifier polygons (dashed polygons). The tooltip shows the name of the modifier as well as any user defined descriptions added to it.https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display#id-05SpatialDisplay-ViewingExistingSpatialModifiers
Plugin - Gui - Grid Display, Plugin - Module - Spatial ModifiersFEWS-21129EAFEWS-18050 Add option to set the application order of time series modifiersAdd option to set the application order of spatial modifiersFor the new spatial modifiers, the application order is important if the areas to which two modifiers apply overlap. To allow the user to control the application order, a priority was added. The priority of spatial modifiers can be edited (and viewed) in the modfiiers panel. Modifiers are applied from the one with the highest value for priority to the one with the lowest value (so a modifier with priority 1 will be applied after a modifier with priority 2). This causes the modifier with the lowest value to be "on top".https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display#id-05SpatialDisplay-Priority
Plugin - Gui - Grid DisplayFEWS-19690EAFEWS-18050 FFFS: Simplify configuration of ensemble member filterNow whole ensembles can be used in a gridplot and shown/picke by SpatialEnsembleThumbnailsPanelNow whole ensembles can be used in a gridplot and shown/picke by SpatialEnsembleThumbnailsPanelhttps://publicwiki.deltares.nl/display/FEWSDOC/01+Grid+Display#id-01GridDisplay
Plugin - Gui - Grid DisplayFEWS-21376EAFEWS-18050 Improve coloring grid display time slider
Plugin - Gui - Grid DisplayFEWS-21352EAFEWS-18050 FFFS: Spatial Display link to displaygroups through PlotId {code:xml} <gridPlotGroup id="Stations" name="Station Observations"> <viewPermission>All_Users</viewPermission> <gridPlot id="Stations_P_processed15m" name="Rain Gauges (15 min)"> <displayGroupPlotId>AUS_QC</displayGroupPlotId> {code}
Plugin - Gui - Grid DisplayFEWS-21466EAFEWS-18050 FFFS: Not load all forecasts when numberOfRecentForecasts is used
Plugin - Gui - Grid DisplayFEWS-20687EAFEWS-18050 Spatial display. Allow setting the speed of the animation when pressing the play buttonSpeed of animation can be set in grid displayAn configuration option in the grid display has been added to set the speed of the animationhttps://publicwiki.deltares.nl/display/FEWSDOC/01+Grid+Display#id-01GridDisplay-movieFrameDurationMillis{code:xml} <movieFrameDurationMillis>100</movieFrameDurationMillis> {code}
Plugin - Gui - Grid DisplayFEWS-20108EAFEWS-18050 FFFS: Import Shape file on the fly and compute catchment average https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display#id-05SpatialDisplay-Extractingminmaxandmeantimeseriesforanarea
Plugin - Gui - Grid DisplayFEWS-20106EAFEWS-18050 FFFS: Search functionality in Spatial Display
Plugin - Gui - Grid DisplayFEWS-21075EAFEWS-18050 FFFS-OC: Button in the Spatial Display time slider to move to last available time
Plugin - Gui - Grid DisplayFEWS-17861EAFEWS-18050 FFFS: Extend the Spatial Display thumbnails with sub-plots per ensemble memberSpatial display of an ensemble with multiple members contains a button to open the spatial ensemble thumbnails, to show all members at once. A selection for the grid display can be made by selecting the desired thumbnail.When an ensemble with multiple members is configured in a grid plot a button for opening the spatial ensemble thumbnails becomes enabled so all members can be shown at once and a selection for the grid display can be made by selecting the desired thumbnail.https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display#id-05SpatialDisplay-Selectingdifferentensemblemembers
Plugin - Gui - Grid DisplayFEWS-17962DeltaresFEWS-19648 Streaming grid data and gzip blob compressionStreaming Grid data Separation of the actual grid data and the time series meta data. Grid data is now stored in multiple separate columns at the same database row as the metadata. Reduction of 90% of the number of database rows required for storing grids. One TB of grid data now only requires 300.000 rows . Grid data is now read from the database on demand in chunks of 128 kB. One chunk holds at least the data for one grid but is filled up to 128kB with grids for other time steps and time series. The chunk required for the next grid time step is preloaded in the background. Improved concurrency. Reading grid data is no longer blocking other threads. Grid data that becomes invisible due an overwrite is no longer read Data hierarchy transformation only reads the selected grids.Streaming grid data (continued) Amalgamate is much faster in case of overlapping grid data. Instant database lister. Only the metadata is read from the database. Instant grid display. Grid appears instantly including the colored slider when switching nodes. Less database peak loads. The load on the database is spread over the duration of the grid processing workflow Better use of memory and disk caches for both scalar and grid data. Invisible and pre-loaded grid data is no longer exhausting the caches. GZIP compression. Up to 50% smaller time series rows for both scalars and grids. This GZIP compression is applied on top of the existing FEWS compression methods. Conversion Conversion of existing rows is optional and is done in the background. OC/FS/SA are working normally while conversion is in process. Conversion can be stopped and continued at any moment.
Plugin - GUI - IFD - DataviewerFEWS-21035EAFEWS-18050 FFFS: Threshold Icons on Forecast Tree
Plugin - GUI - IFD - ForecastsFEWS-20890NWSFEWS-20886 NWS: #45894 Color coding segments on the Forecasts (Navigation) PanelCustomising the text- and background colours of topology tree nodesCustom colors You can configure the text and background color(selected and non-selected). These are optional fields, you can configure all, none, or some. These properties can be configured on individual nodes and group nodes.https://publicwiki.deltares.nl/display/FEWSDOC/24+Topology#id-24Topology-Customcolors{code:xml} <?xml version="1.0" encoding="UTF-8"?> <!-- edited with XMLSpy v2009 sp1 (http://www.altova.com) by ICT (Stichting Deltares) --> <topology 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/topology.xsd"> <enableAutoRun>false</enableAutoRun> <nodes id="Tasks"> <node id="Import" name="Import"> <workflowId>Import</workflowId> <backgroundSelectionColor>forest green</backgroundSelectionColor> <backgroundNonSelectionColor>pale green4</backgroundNonSelectionColor> </node> <node id="Transformation" name="Transformation"> <workflowId>Transformation</workflowId> <textSelectionColor>gray18</textSelectionColor> <textNonSelectionColor>dark salmon</textNonSelectionColor> </node> <node id="CanadaMeteo" name="CanadaMeteo"> <workflowId>CanadaMeteo</workflowId> <backgroundSelectionColor>light yellow3</backgroundSelectionColor> <backgroundNonSelectionColor>turquoise3</backgroundNonSelectionColor> <textSelectionColor>yellow</textSelectionColor> <textNonSelectionColor>red</textNonSelectionColor> </node> <node id="NoosImport" name="NoosImport"> <workflowId>NoosImport</workflowId> <textSelectionColor>yellow</textSelectionColor> <backgroundNonSelectionColor>light pink2</backgroundNonSelectionColor> </node> <node id="RotterdamPort" name="RotterdamPort"> <workflowId>RotterdamPort</workflowId> <textNonSelectionColor>peach puff</textNonSelectionColor> </node> <node id="KiwisImport" name="KiwisImport"> <workflowId>KiwisImport</workflowId> </node> <node id="TaoGrid" name="TaoGrid"> <workflowId>TaoGrid</workflowId> <backgroundNonSelectionColor>cornsilk</backgroundNonSelectionColor> </node> <node id="MunisenseImport" name="MunisenseImport"> <workflowId>MunisenseImport</workflowId> </node> <backgroundSelectionColor>light yellow3</backgroundSelectionColor> <backgroundNonSelectionColor>turquoise3</backgroundNonSelectionColor> <textSelectionColor>yellow</textSelectionColor> <textNonSelectionColor>red</textNonSelectionColor> </nodes> </topology> {code}
Plugin - GUI - IFD - Forecasts, Plugin - Gui - Tabular Config Files DisplayFEWS-20891NWSFEWS-20886 NWS: #27156 Extend the Tabular Config Files Display to update depending on selected node in TopologyTabular Config File Display connected to Forecast TreeThe Tabular Config File Display is now connected to Forecast Tree. Using locationId's in the topology.xml will show the related tabular config files.https://publicwiki.deltares.nl/display/FEWSDOC/20+Tabular+Config+Files+Display
Plugin - GUI - IFD - ForecastsFEWS-21373EaFEWS-18050 FFFS-OC: Filter log messages for taskrunID in forecast tree nodeForecast Tree (topology tree) - ability to show the log messages for a segment selected in the forecast treeTo show the log-messages , check first if the System Monitor is open. Then select a segment and enter "ctrl L", or choose "Show in Log Browser" from popup menu (right mouse click) Log Brouwser becomes visible and shows log-messages associated with the task run of the selected segment. The menu item "Show in Log Browser" is disabled if the segment is not run yet. https://publicwiki.deltares.nl/display/FEWSDOC/23+Interactive+Forecasting+Displays
Plugin - GUI - IFD - ForecastsFEWS-19958EAFEWS-18050 FFFS: Link Display ID to Topology Node
Plugin - GUI - IFD - ForecastsFEWS-21144EAFEWS-18050 FFFS: Run forecasts non-approved from the Forecast Tree It now possible to select in the IFD if a forecast should be approved automatically or not. The details are described at the wiki https://publicwiki.deltares.nl/display/FEWSDOC/24+Topology#id-24Topology-Approveforecastautomatically
Plugin - GUI - IFD - ForecastsFEWS-20267EAFEWS-18050 FFFS: Add topology panel to mainPanel
Plugin - GUI - IFD - Forecasts, Plugin - Module - ThresholdsFEWS-20361EAFEWS-18050 FFFS: Link threshold display to Explorer/IFD selectionSystem wide Threshold Events display will automatically filter on all locations from the selected IFD node. When there are no explicit locations linked to a node, there will be no filtering.System wide Threshold Events display will automatically filter on all locations from the selected IFD node. When there are no explicit locations linked to a node, there will be no filtering.https://publicwiki.deltares.nl/display/FEWSDOC/29+System+Wide+Threshold+Events+Display#id-29SystemWideThresholdEventsDisplay-IFD
Plugin - GUI - IFD - ForecastsFEWS-20201DeltaresFEWS-18050 FFFS: Forecast Tree Status is not correct when task is killedWhenever a task is killed it will show as failed in the IFDWhenever a task is killed it will show as failed in the IFDhttps://publicwiki.deltares.nl/display/FEWSDOC/10+Interactive+forecast+display
Plugin - Gui - Manual ForecastFEWS-20202EAFEWS-18050 FFFS: Manual Forecast workflow list as TreeManual Forecast - workflows are displayed in a tree instead of in a combo boxThe workflow descriptors can be optionally grouped in WorkflowDescrtiptors.xml , using the optional configuration element ‘workflowNode’ . See an example in WorkflowDescriptors1.xml and WorkflowDescriptors2.xml (both files belong to single Fews config) Manual Forecast dialog shows then the workflows in a tree on the left side of Manual Forecast window If the workflow nodes are not configured, the tree displays the workflows in a simple list. Once configured in one or more WorkflowDescriptors.xml files, only the workflows referenced in workflowNode’s are displayed in ManualForecast dialog. To show all workflows, use F12-> Show all workflows The workflow info can be vieuwed in the workflow tool tip (previously it was a info button) https://publicwiki.deltares.nl/display/FEWSDOC/06+Manual+Forecast+Display
Plugin - Gui - MapFEWS-20540EAFEWS-18050 Disable map zoom and pan animation when using remote desktop or citrixQuicker response when zooming or panning maps when using remote desktop. https://publicwiki.deltares.nl/display/FEWSDOC/02+FEWS+Explorer#id-02FEWSExplorer-MapDisplay
Plugin - Gui - MapFEWS-20807EAFEWS-18050 FFFS. Show threshold icon based on last instead of max value for filter in data viewer {code:xml} <filter id="Worthing_Fluvial_FMP" name="FMP Forecasts"> <thresholdIconsBasedOnLastNonMissingValue>true</thresholdIconsBasedOnLastNonMissingValue> {code}
Plugin - Gui - Product InformationFEWS-19951EAFEWS-18050 FFFS: New Forecast Information Display https://publicwiki.deltares.nl/display/FEWSDOC/32+Forecast+Product+Information+Panel
Plugin - Gui - System MonitorFEWS-20123DeltaresFEWS-19650 FFFS: User ID should have Operator Client or Configuration Manager Info attachedLive system status monitor table shows the user id of logged in users + session type (OC, CM, FS etc.)Live system status monitor table shows the user id of logged in users + session type (OC, CM, FS etc.)https://publicwiki.deltares.nl/display/FEWSDOC/08+System+Monitor
Plugin - Gui - Tabular Config Files DisplayFEWS-21117NWSFEWS-20886 Add lock button to Tabular Config File DisplayAllow locking the Tabular Config File DisplayA lock button has been added to the tabular config file display the will allow locking the selection.https://publicwiki.deltares.nl/display/FEWSDOC/20+Tabular+Config+Files+Display
Plugin - Gui - Threshold DisplayFEWS-20358EAFEWS-18050 FFFS: Link Threshold crossings to Target Area CodesThresholds levels from thresholdValueSets can be linked to warning areas by <targetLocationIdFunction>Thresholds levels from thresholdValueSets can be linked to warning areas by <targetLocationIdFunction>https://publicwiki.deltares.nl/display/FEWSDOC/10+ThresholdValueSets#id-10ThresholdValueSets-targetLocationIdFunction{code:xml} <thresholdValueSet id="QT Thresholds" name="QT Thresholds"> <levelThresholdValue> <levelThresholdId>G2G_QMED</levelThresholdId> <valueFunction>@G2G_QMED@</valueFunction> <targetLocationIdFunction>@TARGET_LOCATION_ID@</targetLocationIdFunction> </levelThresholdValue> {code}
Plugin - Gui - Time SeriesFEWS-18543SEQWaterFEWS-10487 Seqwater: Scatter Plot with two different parameters for 2 locations in Display GroupPossibility to plot 2 time series with different location and parameter against eachother, and only show a marker for the last time stepPossibility to plot 2 time series with different location and parameter against eachother, and only show a marker for the last time stephttps://publicwiki.deltares.nl/display/FEWSDOC/03+Display+Groups#id-03DisplayGroups-ShowasScatterPlot
Plugin - Gui - Time SeriesFEWS-21045RWSDisplayGroups: add visibleInLegend, visibleInTable to all subplot elementsOptions visibleInLegend, visibleInTable, visibleInPlot are now available in clustered bar display groups tooOptions visibleInLegend, visibleInTable, visibleInPlot are now available in clustered bar display groups too.https://publicwiki.deltares.nl/display/FEWSDOC/03+Display+Groups#id-03DisplayGroups-line{code:xml} <displayGroup name="bars"> <display name="clusteredBars"> <subplot> <clusteredBars axis="left"> <bar> <color>blue</color> <visibleInLegend>false</visibleInLegend> <visibleInPlot>false</visibleInPlot> <timeSeriesSet> <moduleInstanceId>Import</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.m</parameterId> <locationId>LocA</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour"/> <relativeViewPeriod unit="hour" start="-12" end="12"/> <readWriteMode>editing visible to all future task runs</readWriteMode> </timeSeriesSet> </bar> <bar> <color>red</color> <visibleInTable>false</visibleInTable> <label>Rated Discharge</label> <timeSeriesSet> <moduleInstanceId>Import</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Q.m</parameterId> <locationId>LocA</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour"/> <relativeViewPeriod unit="hour" start="-12" end="12"/> <readWriteMode>editing visible to all future task runs</readWriteMode> </timeSeriesSet> </bar> </clusteredBars> </subplot> </display> {code}
Plugin - Gui - Time SeriesFEWS-20749RWSExtra option for displaying label in graph legendExtra option for customising the label in graph legendlegendTextFunction With the use of legendTextFunction you can customise what information you wish to see on the legend of a graph plot. Use the following tags in the legendformat, they will be automatically replaced with the correct values: %LOCATION_ID%  - %LOCATION_NAME% - %LOCATION_SHORTNAME% - %PARAMETER_ID% - %PARAMETER_NAME% - %FORECAST_INDEX% - %MODULE_INSTANCE% - %ENSEMBLE_ID% - %ENSEMBLE_MEMBER_ID% - %QUALIFIER_NAME% - %ADDITIONAL_PREFIX% - %HISTORICAL_EVENT_NAME% - %MODIFIED% - %CUSTOM_LABEL_EXTENSION% - %FUNCTION_LABEL% - %POSTPROCESSING% Tags are case sensitive. If a tag configured that does not exist in the given time series, it will be replaced by an empty string. Example: <legendTextFunction>%PARAMETER_NAME% %ENSEMBLEMEMBERID% measured at %LOCATION_NAME%</legendTextFunction> → Water level measured at Lobith H105 Legendformat does not work with timeseries header label function. showValueInLegend works the same with or without legendFormat.https://publicwiki.deltares.nl/display/FEWSDOC/02+Time+Series+Display+Configuration#id-02TimeSeriesDisplayConfiguration-legendTextFunction{code:xml} <legendTextFunctiont>%PARAMETER_NAME% measured at %LOCATION_NAME%</legendTextFunction> <legendTextFunction>%LOCATION_SHORTNAME% : %PARAMETER_ID%<legendTextFunction> <legendTextFunction> %LOCATION_SHORTNAME% (%PARAMETER_NAME%)</legendTextFunction> {code}
Plugin - Gui - Time SeriesFEWS-19649QuebecFEWS-16663 Québec: ability to have thresholds displayed on both left/right axesTimeSeriesDisplay – ability to have thresholds displayed on both left and right axesThresholds can be displayed on the left axis, or on the right axis, or on both. By default the thresholds are displayed on the left axis. To change it, an option ‘ thresholdAxis’ can be used in DisplayGroups.xml . Configure <thresholdAxis>right</thresholdAxis> if only the right axis should have thresholds, and <thresholdAxis>both</thresholdAxis> if both left and right axes should have thresholds Picture plot1.png shows a plot created with the config example below. Option <thresholdAxis>both</thresholdAxis> creates plot as shown in picture plot2.png https://publicwiki.deltares.nl/display/FEWSDOC/03+Display+Groups#id-03DisplayGroups-thresholdAxis{code:xml} <plot id="StageOnLeftAxis_DischargeOnRightAxis"> <subplot> <thresholdAxis>right</thresholdAxis> <line> <timeSeriesSet> <moduleInstanceId>Import</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.m</parameterId> <locationSetId>AllLocations</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour"/> <relativeViewPeriod unit="hour" start="-12" end="0"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </line> <line> <axis>right</axis> <timeSeriesSet> <moduleInstanceId>Import</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Q.m</parameterId> <locationSetId>AllLocations</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour"/> <relativeViewPeriod unit="hour" start="-12" end="0"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </line> </subplot> </plot> {code}
Plugin - Gui - Time SeriesFEWS-20889NWSFEWS-20886 NWS: #60808 Config option to size (enlarge) Plot Thumbnail displaysThumbnail graph are now cached and only recreated when visible and size or contents changedThumbnail graph are now cached and only recreated when visible and size or contents changedhttps://publicwiki.deltares.nl/display/FEWSDOC/01+FEWS+Explorer
Plugin - Gui - Time SeriesFEWS-20678MDBAshowing rating curves together with observations of Q-H relation (R_302)Rating Curve Display – displaying observations along with the rating curveTo show the observations in rating curve display, follow these steps: - open TimeSeriesDialog with the time series you want to see along with the rating curve - open rating curve display for required location - select option “Show selected stage and discharge as scatter plot” from the drop down menu of the button “ Rating Curves” (on the TSD toolbar) - select one stage series and one discharge series from the time series table or from the chart legend. The selected series will be shown as scatter plot along the rating curve. All values in the zoom period will be displayed. The number of values shown can be changed by changing of the zoom period. - Note: the selected series must be stage and discharge, it means the series parameter must be from the same parameter group as the rating curve parameters configured in Parameters.xml. Other series selection will be ignored. https://publicwiki.deltares.nl/display/FEWSDOC/04+Data+Display+and+Data+Editor#id-04DataDisplayandDataEditor-Displayingobservationsalongwiththeratingcurves
Plugin - Gui - Time SeriesFEWS-17892GO-FEWSFEWS-17812 Create on-the-fly expression series based on other on-the-fly expression seriesExpression series can now be created based on other expression series as sourceExpression series can now be created based on other expression series as sourcehttps://publicwiki.deltares.nl/display/FEWSDOC/30+Visibility+Dialog+and+On+The+Fly+Expression+Series#id-30VisibilityDialogandOnTheFlyExpressionSeries-Creatingexpressionseriesbasedonotherexpressionseries(since2019.02)
Plugin - Gui - Time SeriesFEWS-19656EA (UK)FEWS-18050 FFFS: Make plots in displaygroups depend on permissions
Plugin - Gui - Time SeriesFEWS-20373EAFEWS-18050 FFFS: Rating curve table and graph must show multiple ratings when these existRating curve display and multiple rating curves for one locationLocation might have multiple rating curves with different qualifiers. In this case the rating display shows a list where the specific rating curve can be selected https://publicwiki.deltares.nl/display/FEWSDOC/04+Data+Display+and+Data+Editor#id-04DataDisplayandDataEditor-Ratingcurve
Plugin - Gui - Time SeriesFEWS-20593EAFEWS-18050 FFFS-SA: Scaling of rating must only include reliable values.Rating curve display – option to show all rating curve values or only reliable and doubtful valuesUse menu item ”Scale to show unreliable data” to switch between showing all rating curve values or reliable and doubtful values only. This menu item is can be found under the rating curve button, see the attached picture. By default all rating curve values are shown. If the rating curve has only unreliable values, then all values are shown as wel. https://publicwiki.deltares.nl/display/FEWSDOC/04+Data+Display+and+Data+Editor#id-04DataDisplayandDataEditor-ScaletoshowunreliableData
Plugin - Gui - Time SeriesFEWS-21445EAFEWS-18050 FFFS: Time series display default datum (mAOD) configurable by location {code:xml} <?xml version="1.0" encoding="UTF-8"?> <timeSeriesDisplay xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/timeSeriesDisplay.xsd"> <defaultViewPeriod unit="day" start="-2" end="2"/> <globalDatumLocationSetId>Rivermouth_stations</globalDatumLocationSetId> {code}
Plugin - Gui - Time SeriesFEWS-21341EAFEWS-18050 FFFS: ModuleinstanceID Mapping with a pattern {code:xml} <moduleInstanceIdMappings> <moduleInstanceIdPatternMapping idPattern="Forecast_*"> <description>Forecast</description> </moduleInstanceIdPatternMapping> </moduleInstanceIdMappings> {code}
Plugin - Gui - Time SeriesFEWS-20480EAFEWS-18050 FFFS: Add visibilityGroups to plot in displayGroups
Plugin - Gui - Time SeriesFEWS-19431BC HydroFEWS-11235 Making a plot with two Y axes does not work with time series that are similarTSD plot allows the same parameters on the left and right axisAttached picture SameParameterOnLeftAndRightAxis.png shows the plot created with the config examplehttps://publicwiki.deltares.nl/display/FEWSDOC/03+Display+Groups#id-03DisplayGroups-subplot{code:xml} <plot id="SameParameterOnLeftAndRightAxis"> <subplot> <line> <label>H.m (small values)</label> <timeSeriesSet> <moduleInstanceId>Import</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.m</parameterId> <locationSetId>AllLocations</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour"/> <relativeViewPeriod unit="hour" start="-12" end="0"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </line> <line> <axis>right</axis> <label>H.m (large values)</label> <timeSeriesSet> <moduleInstanceId>Import2</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.m</parameterId> <locationSetId>AllLocations</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour"/> <relativeViewPeriod unit="hour" start="-12" end="0"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </line> </subplot> </plot> {code}
Plugin - Gui - Time Series ModifierFEWS-20907NWSFEWS-20886 NWS: #62737 Provide plot and table for reverseOrderModifiersMergeSimpleModifiers-reverseOrderModifiers show the time series to switchMergeSimpleModifiers-reverseOrderModifiers show the time series , that should be switched, in the table and plot . These time series match the input variables configured in the transformation <merge><simple>. First time series in the table matches the first input variable, second time series matches the second input variable. When the modifier applies only to one location, the display shows two time series, see an example picture SwitchTs_singleLocation.png When the modifier applies to multiple locations, the display shows the time series for multiple locations, see an example picture SwitchTs_multipleLocation.png https://publicwiki.deltares.nl/display/FEWSDOC/25+ModifierTypes#id-25ModifierTypes-Reverseordermodifiers
Plugin - Gui - Time Series Modifier, Plugin - Module - Modifiers (ModuleParameters), Plugin - Module - Modifiers (TimeSeries)FEWS-20887NWSFEWS-20886 NWS: #62489 Request to have extra column for modifier creator (original user name)ModifiersDisplay – new column ‘Creator’ in the modifiers tableColumn ‘Creator’ shows the name of the user that has created the modifier. When an another user copies or edits this modifier, the original creator will be retained and the user will be updated . Attached ModifiersDisplay.png shows some examples When you open an existing Fews application in 2019.01, new columns added in 2019.01 (Creator, Priority) are not visible . Use modifiers table popup menus “Restore default layout “ or “Select columns” to show the new columns. https://publicwiki.deltares.nl/display/FEWSDOC/08+Time+Series+Modifiers
Plugin - Gui - Time Series ModifierFEWS-21138EAFEWS-18050 Add option to show modifiers of current grid plot in modifier panelAdd option to show modifiers of current grid plot in the modifier panelIn previous versions, the modifiers shown in the modifiers panel were always based on the selected node in the forecast tree. Since there are now spatial modifiers which can be created through the spatial display (instead of the modifiers panel), the modifiers panel is able to display all modifiers for the current grid plot. When spatial modifier mode is active, the panel will show all modifiers of the grid plot on which the modifier mode was activated. When spatial modifier mode is not active the modifier panel behaves the same as before, showing all modifiers for the currently selected node in the forecast tree. A title was added to the modifiers table on the modifiers panel, to indicate for which plot / node the modifiers are shown.
Plugin - Gui - Time Series ModifierFEWS-20977DeltaresFEWS-18050 FFFS-SA: Comboboxen in modifiers moeten geen drop-down label hebben.The original values in the attribute modifiers panel dont have a combobox anymore. Because it cannot be edited.The original value of an attribute should never have a combobox in the display because it cannot be edited.
Plugin - Gui - Time Series VisibilityFEWS-21177DeltaresInvestigate what would be necessary to make expressions work with comma decimal separator ','Use ; in if statements of expression series when , is decimal separatorUse ; in if statements of expression series when , is decimal separatorhttps://publicwiki.deltares.nl/display/FEWSDOC/30+Visibility+Dialog+and+On+The+Fly+Expression+Series
Plugin - Gui - Web Browser DisplayFEWS-20362DeltaresFEWS-19373 Chromium embedded framework (JCEF) update warningThe Chromium embedded web browser package has been updated to Chromium version 73.0.3683The Chromium embedded web browser display uses the JCEF package (Java Chromium Embedded Framework) which allows Java developers to embed the Chromium web browser in their applications. The JCEF package is not automatically updated so a new build of this package has been made for both Windows and Linux platforms. The current JCEF package (dated 21 -3-2019) uses Chromium version Chromium version 73.0.3683. (see also: https://bitbucket.org/chromiumembedded/java-cef)https://publicwiki.deltares.nl/x/xQtHBw
Plugin - Gui - Web Browser DisplayFEWS-20392DeltaresFEWS-19373 Implement a whitelist of domains/urls that can be visited using web browserThe Web browser display can now be configured with a "white list" to control which internet domains a user can visit using the embedded Chromiun browser.For the embedded web browser display, a domain whitelist has been implemented to restrict the domains from which content can be displayed in the internal web browser. When the user follows hyperlinks to sites that are not whitelisted the system default browser will be opened instead.https://publicwiki.deltares.nl/x/xQtHBw
Plugin - Module - ArchiveFEWS-21205TVA / BPA / NWS / BC HydroImprove Import Achive Module (wrt states)ImportArchiveModule – importing of the (most recently archived) statesStates are archived in the forecast archiving process, together with time series, reports and modifiers. Up to now the states were only ingested as a part of archived forecast. From now on, it is possible to ingest the states only. For this purpose an (optional) import activity “moduleStatesImportActivity” has been added to the ImportArchiveModule. An example from importArchiveModule.xml : {code:xml} <importSimulated> <activities> <moduleStatesImportActivity/> </activities> <importFolder>$ARCHIVE_DOWNLOAD_FOLDER$/simulated</importFolder> </importSimulated> {code} When “moduleStatesImportActivity” is configured, only states are imported from the importFolder. These states are then simply added to the WarmStates table. The states to ingest, for example the most recent states , should be selected in the ArchiveDisplay
Plugin - Module - ArchiveFEWS-21202TVA / BPA / NWS / BC HydroImprove archive export moduleExportArchiveModule improvements – simulation metadata xml is extended with moduleInstanceId and state timeWhen archiving states, moduleInstanceId and state time are stored in simulation metadata xml, in separate elements. An example from simulationMetaData.xml: {code:xml} <states> <state> <moduleInstanceId>ModelA</moduleInstanceId> <stateTime date="2018-01-18" time="03:00:00"/> <relativeFilePath>modulestates\ModelA20180118030000.zip</relativeFilePath> </state> </states> {code} When the states are imported from archive, the importer is still able to read the old format, when the moduleInstanceId and state time are available in the zip file name only, for example {code:xml} <states> <relativeFilePath>modulestates\ModelA20180118020000.zip</relativeFilePath> </states> {code} https://publicwiki.deltares.nl/display/FEWSDOC/22-1+Datasets+of+the+Deltares+Open+Archive#id-22-1DatasetsoftheDeltaresOpenArchive-_Toc386122317SimulationsMetadata
Plugin - Module - ArchiveFEWS-20743TVAFEWS-20739 TVA: Ability to map multiple source ids to a single source nameMultiple source ids can now be combined into a single source idIt is now possible to combine several source ids to single source id. This parent souce id can be used to download the data sets of the children source ids in one go.
Plugin - Module - ArchiveFEWS-20741TVAFEWS-20739 TVA: Fix archive harvester speed (either through caching or a tool to fix metadata)The performance of the archive harvester is improvedAn initial harvest run can take a long time for large archives. The openening of the netcdf-files of the archives to collect metadata takes a long time. For each dataset a cachefile is now introduced which contains the metadata of each netcdf-file. The overall performance of a harvest run is now improved by 50%. No config is needed
Plugin - Module - ArchiveFEWS-20609RWSFEWS-20605 Archief harvester t.b.v. standaard NetCDF filesA new harvester is developed for harvesting CF-compliant netcdf-files without metadata.xml fileDeltares is now developing an extension to the open archive. It is now also possible to store plain cf-complaint netcdf files in the archive. To harvest these netcdf-files a new type of harvester is developed.
Plugin - Module - ArchiveFEWS-20516EAFEWS-18050 FFFS: Archive log messages
Plugin - Module - ArchiveFEWS-20497EAFEWS-18050 FFFS: Import External documents and move to Archive folderPossibility to remove source files after sending it to the archiveIt now possible to remove the source files for a products after sending it to the archive. https://publicwiki.deltares.nl/display/FEWSDOC/22-2+Export+to+Deltares+Open+Archive
Plugin - Module - ArchiveFEWS-20566EAFEWS-18050 FFFS: Add option in old Archive import to skip grid dataOld Archive import: new option includeGrids to include or exclude gridded time series while importingWhen includeGrids is false, the gridded time series are not imported. When includeGrids is omitted , all gridded time series are importedhttps://publicwiki.deltares.nl/display/FEWSDOC/12+Archive+ModuleExamples from archiveRun.xml: Example 1: {code:xml} <importArchiveRun> <archiveType>ForecastArchive</archiveType> <includeGrids>false</includeGrids> </importArchiveRun> {code} Example 2: {code:xml} <importArchiveRun> <archiveType>TimeSeriesArchive</archiveType> <includeGrids>false</includeGrids> </importArchiveRun> {code}
Plugin - Module - ArchiveFEWS-21473DeltaresIncrease number of logfiles in Archive ServerArchive Server Log now has a maximum of 20 log files of 1MByte eachArchive Server Log now has a maximum of 20 log files of 1MByte eachhttps://publicwiki.deltares.nl/display/FEWSDOC/The+Deltares+OpenArchive+%282017.01+and+newer%29+-+installation
Plugin - Module - Data Export, System - PI ServiceFEWS-20062SingaporeAdd a new data export type (NetCDF) to the pi-webserviceA new data type (netcdf) is added to the pi-webserviceA new datatype is added to the pi-webservice. This new datatype is netcdf. When data is requested from the pi-webservice the data is first exported to a set a netcdf-files. The files are zipped to a single zip-file. This zip-file is then exported to the client.
Plugin - Module - Data ImportFEWS-20352eThekwini Municipality (SA)Improve CMEMS import with propertiesImprove CMEMS import with propertiesCMEMS import was made easier by adding more property fields. The type of import should be configured using the DATA_TYPE property. DATA_TYPE should be set to "HOURLY" for hourly data. DATA_TYPE should be set to "DAILY" for daily data. DATA_TYPE should be set to "MONTHLY" for monthly data. Properties "product" and "service" are compulsory fields. Please fill them in exactly the same as it should be in the request url. (See the examples below) The product (i.e. ''Product Identifier" and service (found in "Services tab" on CMEMS website) can be found in the product explorer on the Copernicus website: http://marine.copernicus.eu/services-portfolio/access-to-products/. https://publicwiki.deltares.nl/display/FEWSDOC/CMEMS{code:xml} <?xml version="1.0" encoding="UTF-8"?> <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>Cmems</importType> <serverUrl>http://nrt.cmems-du.eu/motu-web/Motu?action=productdownload</serverUrl> <user>USERNAME</user> <password>PASSWORD</password> <relativeViewPeriod unit="hour" start="-24" end="0" startOverrulable="true"/> <idMapId>IdImportCmems</idMapId> <unitConversionsId>ImportUnitConversions</unitConversionsId> <expiryTime unit="week" multiplier="500"/> </general> <properties> <string key="DATA_TYPE" value="HOURLY"></string> <string key="TICKET_URL" value="https://cmems-cas.cls.fr/cas/v1/tickets"/> <string key="product" value="global-analysis-forecast-phy-001-024-hourly-t-u-v-ssh"/> <string key="service" value="GLOBAL_ANALYSIS_FORECAST_PHY_001_024-TDS"/> </properties> <timeSeriesSet> <moduleInstanceId>Import_E2O_Server</moduleInstanceId> <valueType>grid</valueType> <parameterId>Wind.u</parameterId> <locationId>CMEMS.L1</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </import> </timeSeriesImportRun></timeSer {code}
Plugin - Module - Data ImportFEWS-21479WRACapAlertTimeSeriesParser should not fail on files valid to CAP-v1.2.xsd
Plugin - Module - Data ImportFEWS-20266RWsOS WaterbeheerWaterbeheer: import munisense grondwaterdataNew import: munisense grondwaterdataData is imported from https://opendata.munisense.net. Example query: https://opendata.munisense.net/api/v2/wareco-water2/groundwaterwells/1082172/water_level_filtered/query/presets/last_month Example data set: {code} {"results":[{"timestamp":"2019-03-21T10:15:23.000+00:00","first_timestamp":1553164216716,"last_timestamp":1553164995278,"avg_manual_validation_state":1,"min_manual_validation_state":1,"max_manual_validation_state":1,"count":16,"avg_value":8.677,"min_value":8.389,"max_value":8.698},{"timestamp":"2019-03-21T11:15:23.000+00:00","first_timestamp":1553168033620,"last_timestamp":1553168033620,"avg_manual_validation_state":1,"min_manual_validation_state":1,"max_manual_validation_state":1,"count":1,"avg_value":8.7,"min_value":8.7,"max_value":8.7},{"timestamp":"2019-03-21T12:15:23.000+00:00","first_timestamp":1553171633620,"last_timestamp":1553171633620,"avg_manual_validation_state":1,"min_manual_validation_state":1,"max_manual_validation_state":1,"count":1,"avg_value":8.698,"min_value":8.698,"max_value":8.698},{"timestamp":"2019-03-21T13:15:23.000+00:00","first_timestamp":1553175233620,"last_timestamp":1553175233620,"avg_manual_validation_state":1,"min_manual_validation_state":1,"max_manual_validation_state":1,"count":1,"avg_value":8.7,"min_value":8.7,"max_value":8.7}, ,"meta":{}}{code} From the data set "avg_value" is imported. Important notice: The timestamp is used for parsing the time in the time series. However, the returned Json contains time steps that are not exactly round hour, such as: "11:15:23.000+00:00". How much it differs from the exact hour changes regularly. Time series sets should be configured either as non-equidistant (which will import data at the exact time the timestep shows) or the need tolerance configured, which will round the time to the closest exact time step. If the difference between the timestamp and the closest time step is bigger than the tolerance, the data will not be imported. Data can be imported from different time periods. The longer the time period, the larger the data aggregation period. Available choices are: last_day=sampled by minute last_week=sampled by 10 minutes last_month=sampled by hour last_year=sampled by 8 hour last_three_years= sampled by 24 hour The name of the period needed should be configured as external qualifierId of the time series. It should be configured either in the import module configuration or an id mapping, but not both.https://publicwiki.deltares.nl/display/FEWSDOC/Munisense+import{code:xml} <?xml version="1.0" encoding="UTF-8"?> <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>MunisenseImport</importType> <serverUrl>https://opendata.munisense.net/api/v2/wareco-water2/groundwaterwells</serverUrl> <user>XXX</user> <password>YYYY</password> <relativeViewPeriod unit="day" start="-10" end="8" startOverrulable="true" endOverrulable="true"/> <idMapId>MunisenseImportIdMapper</idMapId> <importTimeZone> <timeZoneOffset>+00:00</timeZoneOffset> </importTimeZone> </general> <tolerance parameterId="Tide" timeUnit="minute" unitCount="29"/> <timeSeriesSet> <moduleInstanceId>MunisenseImport</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Tide</parameterId> <!-- Do not configure a qualifierId here if you are using id-mapping --> <!-- <qualifierId>last_year</qualifierId> --> <locationId>LocA</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour" multiplier="1"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </import> </timeSeriesImportRun> {code}
Plugin - Module - Data ImportFEWS-20339RWSMatroos import: add an import type for get_netcdf.phpNew import type MATROOS_NETCDF-CF_GRID and MATROOS_NETCDF-CF_TIMESERIESMATROOS_NETCDF-CF_GRID and MATROOS_NETCDF-CF_TIMESERIES first download the nc file from Matroos and then read the downloaded files. To read the downloaded file, MATROOS_NETCDF-CF_GRID uses imported type NETCDF-CF_GRID and MATROOS_NETCDF-CF_TIMESERIES uses import type NETCDF-CF_TIMESERIES Both import types support the following Matroos query: [http://matroos.rws.nl/direct/get_netcdf.php?database=&source=&analysis=&timezone=&hindcast=] The query fields ‘database’ and ‘source’ are mandatory, ‘analysis’, ‘timezone’ and 'hindcast' are optional. The values for the query fields should be configured in the <properties> section of the import module. The downloaded nc file is automatically deleted after import. If you want to keep it, add key ’keep_downloaded_file’ to the <properties> sectionhttps://publicwiki.deltares.nl/pages/resumedraft.action?draftId=141623416&draftShareId=67184de8-b42a-43ad-8b0b-a0ea21275027This example uses mandatory fields only: {code:xml} <general> <importType>MATROOS_NETCDF-CF_GRID</importType> <serverUrl>http://matroos.deltares.nl</serverUrl> <idMapId>IdMapGrid</idMapId> </general> <properties> <string key="database" value="maps2d"/> <string key="source" value="nhi30_maps_ecmwf_det"/> </properties> {code} This example uses mandatory and optional fields: {code:xml} <general> <importType>MATROOS_NETCDF-CF_TIMESERIES</importType> <serverUrl>http://matroos.deltares.nl</serverUrl> <idMapId>IdMapScalarNc</idMapId> </general> <properties> <string key="database" value="maps1d"/> <string key="source" value="fews_meren_eps_ijsselmeer"/> <bool key="add_current_time" value="true"/> <string key="timezone" value="GMT+1"/> <string key="hindcast" value="1"/> <bool key="keep_downloaded_file" value="true"/> </properties> {code}
Plugin - Module - Data ImportFEWS-21621MoravaExtend the HDF importer for Serbian radar datasetKNMI-Hdf5 import type reads also Serbian HDF5 fileThe reading applies to the hdf5 file like pacproba.h5 To read the grid from this file, the external parameter Id "dataset1/data1/data" should be configured. The event date/time is read from attributes ‘enddate’ and ‘endtime’’ of the variable "/dataset1/what/"
Plugin - Module - Data ImportFEWS-21429Entidad Binacional YacyretáNew import for webservice data from CIH - Centro Internacional de HidroinformáticaNew parser to import data from https://hidroinformatica.itaipu.gov.py/services/hidrometricaestacion/2019-07-01/2019-09-01/5/?format=json.The parser imports data from https://hidroinformatica.itaipu.gov.py/services/hidrometricaestacion/2019-07-01/2019-09-01/5/?format=json. The two dates in the url come from the view period. The external location ID should be the same as in the url ( 5 in the case). Response example: {code} [ { "fecha":"2019-09-01 10:00:00 PYST", "nivel":9.6, "conductividad":null, "ph":null, "turbidez":null, "od":null, "tempagua":null } ] {code} Time is parsed from the field "fecha", data is parsed from the field "nivel". All other fields are ignored.https://publicwiki.deltares.nl/display/FEWSDOC/HidroInformatica+import{code:xml} <?xml version="1.0" encoding="UTF-8"?> <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>HidroInformatica</importType> <serverUrl>https://hidroinformatica.itaipu.gov.py/services/hidrometricaestacion</serverUrl> <user>user</user> <password>password</password> <startDateTime date="2019-07-01"/> <endDateTime date="2019-09-01"/> <idMapId>HidroInformatica</idMapId> <importTimeZone> <timeZoneOffset>+00:00</timeZoneOffset> </importTimeZone> </general> <timeSeriesSet> <moduleInstanceId>HidroInformatica</moduleInstanceId> <valueType>scalar</valueType> <parameterId>parameter</parameterId> <locationId>LocB</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant" /> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </import> </timeSeriesImportRun> {code}
Plugin - Module - Data ImportFEWS-19823EAFEWS-18050 FFFS: Import comments from EA XML filesThe importer for EA XML has been extended to import comments.The UK Environmental Agency (EA) uses a custom XML format for transfer of data. This format can include comments that apply to a specific period. The functionality of the EA XML parser has been extended to import these comments to Delft FEWS.https://publicwiki.deltares.nl/x/YYT4BQ
Plugin - Module - Data ImportFEWS-14312EAFEWS-18050 Develop Import from CAP Webservice for communication with WARNING systemImport types CapAlerts and CapAlertThese import types import alerts from CAP Webservice of EA Warning system and store the alerts in the time series. *CapAlerts* reads first all links to real CAP files, and then imports the alerts from these CAP files. {code:xml} <general> <importType>CapAlerts</importType> <serverUrl>https://environment.data.gov.uk/cap/flood-alerts.atom</serverUrl> <idMapId>IdMapAlert</idMapId> </general> {code} Configured serverUrl should be a link to the list of url’s *CapAlert* reads the alerts from the single CAP file. {code} <general> <importType>CapAlert</importType> <serverUrl>https://cap-xml.prd.defra.cloud/message/0768e13b0ab7aa4526c35a06b6533b37E</serverUrl> <idMapId>IdMapAlert</idMapId> </general> {code} Configured serverUrl should be a link to the CAP file. CapAlert is useful when there are no alerts (anymore) on the site with links, and we need to import some old alerts, for example as a test. The following elements are read from the CAP file : <value> of the <geocode> with valueName ‘TargetAreaCode’ is used as location Id <sent> is used as event time <severity> is used as event value (needs parameter enumeration, see below) <status> is used as event properties <msgType> is used as event properties <urgency> is used as event properties <certainty> is used as event properties <expires> is used as event properties *Importing <severity>:* The severity is a string, for example “Moderate”, “Minor”, … To be able to store the severity in the time series, use parameter enumeration. An example from Parameters.xml: {code:xml} <enumerations> <enumeration id="AlertEnum"> <value code="1" label="Minor"/> <value code="2" label="Moderate"/> <value code="3" label="Major"/> </enumeration> </enumerations> …….. <parameterGroup id="Alerts"> <enumerationId>AlertEnum</enumerationId> <parameter id="Alert" name="Alert"> <shortName>Alert</shortName> </parameter> </parameterGroup> {code}https://publicwiki.deltares.nl/display/FEWSDOC/CAP+Alerts
Plugin - Module - Data ImportFEWS-21165EAFEWS-18050 FFFS: Skip Missing values on importing {code:xml} <import> <general> <importType>PI</importType> <folder>..</folder> <flagConversionsId>PiImportFlagConversions</flagConversionsId> <importTimeZone> <timeZoneOffset>+01:00</timeZoneOffset> </importTimeZone> <skipMissingValues>true</skipMissingValues> <expiryTime multiplier="1" unit="hour"/> </general> {code}
Plugin - Module - Data ImportFEWS-20169DeltaresFEWS-18050 FFFS: Improve performance Import (compressed) NetCDF gridsPerformance of netcdf cf grid import improved for large datasets by reading more data at oncePerformance of netcdf cf grid import improved for large datasets by reading more data at oncehttps://publicwiki.deltares.nl/display/FEWSDOC/NETCDF-CF_GRID
Plugin - Module - Data ImportFEWS-21640DeltaresFEWS-21449 CSV reader does not correctly handle linebreak within a field
Plugin - Module - Data ImportFEWS-19420Aa en MaasTemporary import without Config
Plugin - Module - General AdapterFEWS-21893 FEWS-18050 FFFS-SA: Filter ID mapping with additional location attribute {code:xml} <?xml version="1.0" encoding="UTF-8"?> <idMap 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" version="1.1"> <locationIdFunction internalLocationSet="Meteo Stations" externalLocationFunction="@region@" externalLocationFunctionLookupAttributeId="lookup" externalLocationFunctionLookupText="model-a"/> </idMap> {code} {code:xml} <?xml version="1.0" encoding="UTF-8"?> <idMap 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" version="1.1"> <function internalLocationSet="Meteo Stations" internalParameter="Q.m" externalLocationFunction="@region@" externalLocationFunctionLookupAttributeId="lookup" externalLocationFunctionLookupText="model-a" externalParameterFunction="PAR@region@"/> </idMap> {code}
Plugin - Module - General AdapterFEWS-20149RWSPossibility to store intermediate restarts from a single run with various T0 and distinguish between forecast states and hindcast statesAdded <backupWarmStateModuleInstanceId> Different module instance id used for finding warm state, when original warm state can't be foundAdded <backupWarmStateModuleInstanceId> Different module instance id used for finding warm state, when original warm state can't be foundhttps://publicwiki.deltares.nl/display/FEWSDOC/05+General+Adapter+Module#id-05GeneralAdapterModule-backupWarmStateModuleInstanceId{code:xml} <stateSelection> <warmState> <stateSearchPeriod unit="hour" start="-96" end="-6"/> <insertColdState>true</insertColdState> </warmState> <backupWarmStateModuleInstanceId>BackupWarmState</backupWarmStateModuleInstanceId> </stateSelection> {code}
Plugin - Module - General AdapterFEWS-20517EAFEWS-18050 FFFS: Ignore missing locationSets in General Adapter burninprofile {code:xml} <burnInProfile> <length multiplier="4" unit="hour"/> <ignoreNonExistingLocationSets>true</ignoreNonExistingLocationSets> <timeSeries> .... </timeSeries> </burnInProfile> {code}
Plugin - Module - General AdapterFEWS-20848EAFFFS: Ignore missing locationSets in General Adapter when importing series {code:xml} <importTimeSeriesActivity> <importFile>EVAP.xml</importFile> <timeSeriesSets> <timeSeriesSet> <moduleInstanceId>ExportActivityTimeSeries</moduleInstanceId> <valueType>scalar</valueType> <parameterId>E.metoffice</parameterId> <locationId>SX.E7842</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="second" multiplier="900"/> <relativeViewPeriod unit="hour" start="0" end="2"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </timeSeriesSets> <ignoreNonExistingLocationSets>true</ignoreNonExistingLocationSets> </importTimeSeriesActivity> {code}
Plugin - Module - General AdapterFEWS-20444EAFEWS-18050 Allow GeneralAdapter to constrain array-type burn-in initial values Lookup initial value for specific model in case the initial value attribute contains a different value for each model {code:xml} <timeSeries> <parameterId>H.obs</parameterId> <locationSetId>locationInitialValueAttSet</locationSetId> <initialValueAttributeId>initialValues</initialValueAttributeId> <lookupAttributeId>modelName</lookupAttributeId> <lookupText>myModel</lookupText> </timeSeries> {code}
Plugin - Module - Modifiers (ModuleParameters)FEWS-17004NWSFEWS-20886 NWS: #34173 Multiple catchment modifiers with templatesA single module parameter template can now be used for multiple catchment modifiersThe usage templates for multiple catchment modifiers is improved. A single template can now be used if a modifier can be applied to multiple catchment in a catchment.
Plugin - Module - Modifiers (TimeSeries)FEWS-20888NWSFEWS-20886 NWS: #53507 SACCO compoundModifier - initial slider position should match the valueThe initial slider position now matches the the numerical value after initial startup of the display.The initial slider position now matches the the numerical value after initial startup of the display.
Plugin - Module - ReportsFEWS-19817SEQWaterFEWS-10487 Add <timeseries> in ReportModuleGeneralCsv export: ability to export ensemble and ensemble memberBy default the ensemble member index is exported. To export member Id’s , use an option <ensembleMemberFormat>name</ensembleMemberFormat> in the general section of the time series export module. An example : {code:xml} <general> <exportType>generalCsv</exportType> <folder>$EXPORT_FOLDER$</folder> <exportFileName> <name>ExportGeneralCsv.csv</name> </exportFileName> <table> <dateTimeColumn name="DateTime" pattern="yyyy-MM-dd HH:mm"/> <locationColumn name="Location"/> <parameterColumn name="Parameter"/> <ensembleMember name="Ensemble"/> <ensembleMemberColumn name="Ensemble Member"/> <valueColumn name="Value"/> </table> <ensembleMemberFormat>name</ensembleMemberFormat> </general> {code} Please note that ensembleColumn and ensembleMemberColumn are supported only for time series export, and not for time series import (so far)https://publicwiki.deltares.nl/display/FEWSDOC/General+CSV+Export
Plugin - Module - Spatial ModifiersFEWS-21541EAFEWS-18050 Add statistics to spatial profile modifier panelAdd time length and moving accumulation max statistics, add statistics to spatial profile editorTwo new descriptive statistical functions have been added:  "timeLength" and "movingAccumulationMax". The "timeLength" statistic states the length of the time series, for example "1 day 3 hours". The "movingAccumulationMax" statistic can be given several time spans for which the maximum of the moving accumulation is reported. A statistics panel has been added to the spatial profile modifier editor. The descriptive statistics included in this statistics panel can be configured through the ModifierTypes.xml (and differ from the descriptive functions configured in the TimeSeriesDisplayConfig.xml). https://publicwiki.deltares.nl/display/FEWSDOC/25+ModifierTypes#id-25ModifierTypes-SpatialProfileModifier  {code:xml} <spatialProfileModifier id="SpatialProfileBE" name="Spatial Profile"> <expiryTime unit="day" multiplier="2"/> <userDefinedDescriptionField id="Comment" descriptionField="Comment"/> <timeSeries> <moduleInstanceId>Import_NWP_Mediumrange</moduleInstanceId> <qualifierId>BE</qualifierId> </timeSeries> <descriptiveFunctionGroups> <descriptiveFunctionGroup name="Basic statistics"> <descriptiveFunction function="startTime" ignoreMissings="true"/> <descriptiveFunction function="endTime" ignoreMissings="true"/> <descriptiveFunction function="timeLength" ignoreMissings="true"/> </descriptiveFunctionGroup> <descriptiveFunctionGroup name="Accumulation"> <descriptiveFunction function="movingAccumulationMax" ignoreMissings="true"> <timeSpan unit="hour" multiplier="1"/> <timeSpan unit="hour" multiplier="2"/> <timeSpan unit="hour" multiplier="3"/> <timeSpan unit="hour" multiplier="4"/> <timeSpan unit="hour" multiplier="6"/> <timeSpan unit="hour" multiplier="12"/> <timeSpan unit="hour" multiplier="24"/> <timeSpan unit="hour" multiplier="48"/> <timeSpan unit="hour" multiplier="72"/> <timeSpan unit="hour" multiplier="96"/> <timeSpan unit="hour" multiplier="120"/> </descriptiveFunction> <descriptiveFunction function="sum" ignoreMissings="true"/> </descriptiveFunctionGroup> </descriptiveFunctionGroups> </spatialProfileModifier>  {code}
Plugin - Module - Spatial ModifiersFEWS-21286EAFEWS-18050 Allow setting all modifier properties in spatial modifier creation dialogUse modifier properties panel in spatial modifier creation dialogThe spatial modifier creation dialog contains the same modifier properties panel as is shown when a new modifier is created or a modifier is edited in the modifiers panel. This allows setting all modifier properties (like user defined description fields) for spatial modifiers through the spatial display when creating them, instead of having to navigate to the modifiers panel and edit them in later.https://publicwiki.deltares.nl/display/FEWSDOC/05+Spatial+Display#id-05SpatialDisplay-ModifierProperties
Plugin - Module - ThresholdsFEWS-20356EAFEWS-18050 FFFS: Allow usage of multivalued attributes for ThresholdsMultivariate threshold transformation added that can group inputs by locationSetMultivariate threshold transformation added that can group inputs by locationSet. For each locationSet can be specified which location attribute should be used to determine the threshold value and how many time series should cross their thresholdhttps://publicwiki.deltares.nl/display/FEWSDOC/Multivariate+Alerting+HyFS
Plugin - Module - TransformationFEWS-19890EAFEWS-18050 FFFS: New transformation for Multiple Linear Regression A new transformation Multiple linear regression is available. This transformation can be used to calculate a value by using a linear regression equation. The input values (time series, factor and constant value) will be defined by using location attributes. More details can be found here: https://publicwiki.deltares.nl/display/FEWSDOC/Multiple+linear+regression
Plugin - Module - TransformationFEWS-20833EAFEWS-18050 FFFS: multipleVariateThresholds: additional requirements / some modifications
Plugin - Module - TransformationFEWS-18490EAFEWS-18050 FFFS: Use qualifiers in rating curve and seasonal rating curves
Plugin - Module - TransformationFEWS-21277EAFEWS-18050 Allow specifying property for default value in serial interpolationAllow use of property-tags ($) in defaultValue element in default interpolationSerialThe <defaultValue> element in the <default> element of <interpolationSerial> now allows the use of property-tags ($).https://publicwiki.deltares.nl/display/FEWSDOC/06+Configuring+Workflows#id-06ConfiguringWorkflows-properties {code:java} <transformation id="FILL"> <interpolationSerial> <default> <inputVariable> <variableId>Merged</variableId> </inputVariable> <defaultValue>$MINIMUM$</defaultValue> <outputVariable> <variableId>Merged</variableId> </outputVariable> </default> </interpolationSerial> </transformation>{code}
Plugin - Module - TransformationFEWS-20324EAFEWS-18050 FFFS: new transformation for time to (or after) peakA new transformation for time to (or after) selection has been implementedIn the category Selection transformations, a new "time to selection" transformation has been implemented. This transformation can be used in combination with any of the existing Selection type transformation. For example, the output of the "Selection of peaks" can be used to calculate the nearest high tide.https://publicwiki.deltares.nl/display/FEWSDOC/Time+to+selection+transformation
Plugin - Module - TransformationFEWS-21339EAFEWS-18050 FFFS: Transformation to select correct ensemble member dataAdded selection ensemble member by index transformation which takes the value of the ensemble member that matches its index with the value of a provided time series. Added selection ensemble member by index transformation which takes the value of the ensemble member that matches its index with the value of a provided time series. https://publicwiki.deltares.nl/display/FEWSDOC/Selection+Ensemble+Member+by+Index
Plugin - Module - TransformationFEWS-20311EAFEWS-18050 FFFS: Add persistencetrend function to new transformation moduleMigrating persistencetrend function to new transformation moduleh4. Description and Usage This transformation "predicts" how the timeseries would continue based on the trend of the existing data. It can be configured how long of a window should be taken into consideration for the trend. Input/Output time series This function takes one input time series and produces one or two output time series. <inputTimeSeries>: An equidistant scalar time series <outputTimeSeries>:An equidistant scalar time series (longer than the original series) Has to have at least one overlapping existing time stap with inputTimeSeries. This will contain the forecast values only, observation values are not copied. <outputHistoricTimeSeries>::An equidistant scalar time series. Optional. It has to have the same time steps as the input time series. It uses the same window to create the trend as outputTimeSeries., and creates one forecast point (same time window into the future. Than it shifts the time window for the data trend one time step back in time, and creates another forecast (which it exactly one time step sooner than the previous one.) It loops though all the imput values like this, creating a seies of forecasts. h4. Configuration Define 2 time series as variables to be used as input and output. _<availableObservedValues>_ Required element defining how many non-missing values need to be present in the time window (from which the trend is calculated.) _<consecutiveObservedValues>_ Required element defining the non-missing values in the time window (from which the trend is calculated) need to be consecutive. If set to false the series of values present are allowed to be broken up by missing values. _<window>_ Required element defining the time period in the input time series from which the trend will be calculated. The window is calculated from the last observed value time and not from T0 .https://publicwiki.deltares.nl/display/FEWSDOC/PresistenceTrend{code:xml} <?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"> <!--2 variables (with any name) need to be configured to be used as inputs and output.--> <variable> <variableId>input</variableId> <timeSeriesSet> <moduleInstanceId>Import_Telemetry</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.obs</parameterId> <locationId>712170</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="15"/> <relativeViewPeriod unit="hour" start="-2" end="6" startOverrulable="false" endOverrulable="true"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </variable> <variable> <variableId>output</variableId> <timeSeriesSet> <moduleInstanceId>NewRateOfRise</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.forecast</parameterId> <qualifierId>RoR</qualifierId> <locationId>712170</locationId> <timeSeriesType>simulated forecasting</timeSeriesType> <timeStep unit="minute" multiplier="15"/> <relativeViewPeriod unit="hour" start="-2" end="6" startOverrulable="false" endOverrulable="true"/> <readWriteMode>add originals</readWriteMode> <expiryTime unit="hour" multiplier="6"/> </timeSeriesSet> </variable> <variable> <variableId>historicOutput</variableId> <timeSeriesSet> <moduleInstanceId>NewRateOfRiseHystory</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.forecast</parameterId> <qualifierId>RoR</qualifierId> <locationId>712170</locationId> <timeSeriesType>simulated forecasting</timeSeriesType> <timeStep unit="minute" multiplier="15"/> <relativeViewPeriod unit="hour" start="-2" end="6" startOverrulable="false" endOverrulable="true"/> <readWriteMode>add originals</readWriteMode> <expiryTime unit="hour" multiplier="6"/> </timeSeriesSet> </variable> <transformation id="PresistenceTrendFunction"> <interpolationSerial > <persistenceTrend> <inputTimeSeries> <variableId>input</variableId> </inputTimeSeries> <outputTimeSeries> <variableId>output</variableId> </outputTimeSeries> <outputHistoricTimeSeries> <variableIdhistoricOutput</variableId> </outputHistoricTimeSeries> <availableObservedValues>2</availableObservedValues> <consecutiveObservedValues>false</consecutiveObservedValues> <window unit="minute" multiplier="60"/> </persistenceTrend> </interpolationSerial> </transformation> {code}
Plugin - Module - TransformationFEWS-20760DeltaresTS: accumulation-max transformationNew transformation: accumulation maxThis transformation takes a time series, and replaces the values to the highest value, that has been observed up to that point. It ignores unreliable values. Example: input: 0 1 5 2 3 7 3 3 output: 0 1 5 5 5 7 7 7 The transformation supports scalar and grid time series. The input and the output types have to be the same. In case of an grid type time series set, the grid geometry must be the same for each time step.https://publicwiki.deltares.nl/display/FEWSDOC/Accumulation+max{code:xml} <!-- scalar --> <?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"> <!-- input variables --> <variable> <variableId>input</variableId> <timeSeriesSet> <moduleInstanceId>AccumulationMaxTest</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.m</parameterId> <locationId>H-2001</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour" multiplier="1"/> <relativeViewPeriod unit="day" start="0" end="3"/> <readWriteMode>editing visible to all future task runs</readWriteMode> </timeSeriesSet> </variable> <!-- output variables --> <variable> <variableId>output</variableId> <timeSeriesSet> <moduleInstanceId>AccumulationMaxTest</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Q.m</parameterId> <locationId>H-2001</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="hour" multiplier="1"/> <relativeViewPeriod unit="day" start="0" end="3"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </variable> <!-- transformations --> <transformation id="accumulation max test"> <accumulation> <max> <inputVariable> <variableId>input</variableId> </inputVariable> <outputVariable> <variableId>output</variableId> </outputVariable> </max> </accumulation> </transformation> </transformationModule> <!-- grid --> <?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"> <!-- input variables --> <variable> <variableId>input</variableId> <timeSeriesSet> <moduleInstanceId>AccumulationMaxTestGrid</moduleInstanceId> <valueType>grid</valueType> <parameterId>H.m</parameterId> <locationId>H-2001</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="day"/> <relativeViewPeriod unit="day" start="0" end="5"/> <readWriteMode>editing visible to all future task runs</readWriteMode> </timeSeriesSet> </variable> <variable> <variableId>output</variableId> <timeSeriesSet> <moduleInstanceId>AccumulationMaxTestGrid</moduleInstanceId> <valueType>grid</valueType> <parameterId>H.m</parameterId> <locationId>H-2001</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="day"/> <relativeViewPeriod unit="day" start="0" end="5"/> <readWriteMode>editing visible to all future task runs</readWriteMode> </timeSeriesSet> </variable> <!-- transformations --> <transformation id="accumulation max test"> <accumulation> <max> <inputVariable> <variableId>input</variableId> </inputVariable> <outputVariable> <variableId>output</variableId> </outputVariable> </max> </accumulation> </transformation> </transformationModule> {code}
System - LoggingFEWS-18005RWSRWsOS: Request to include taskRunId in each line of log.txt {code:xml} <?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"> <clientType>Stand alone</clientType> <logging> <logFileEntryIncludesTaskRunId>true</logFileEntryIncludesTaskRunId> </logging> </clientConfiguration> {code}
System - PI ServiceFEWS-21454WaternetFEWS-19536 Get Qualifiers support in PI Serviceget qualifiers endpoint added to FewsWebServices REST serviceThe get qualifiers endpoint has been added to FewsWebServices REST service. This will get a list of all configured qualifiers.https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI+REST+Web+Service#FEWSPIRESTWebService-GETqualifiers(2019.02)
System - PI ServiceFEWS-19945UAE NavyFEWS-19924 WMS Service: Support vendor parameter to get specific forecastWMS service supports requesting older forecastsWMS service supports requesting older forecasts. With the GetCapabilities method the available external forecast times and times available can be requested. The GetMap method supports passing a forecast time as request parameter for a layer.https://publicwiki.deltares.nl/pages/viewpage.action?pageId=134482048
System - PI ServiceFEWS-20766HDSRAdd locationRelations to getLocations call of PIWebserviceNew optional parameter added to getLocations call of PIWebservice: includeLocationRelationsNew optional parameter added to getLocations call of PIWebservice: includeLocationRelations Default value is false. If it is set to true, location relations will be included in the response. For XML format response this option is available from v.1.26 or greater. Url example: "http://localhost:8080/FewsWebServices/rest/fewspiservice/v1/locations?showAttributes=true&includeLocationRelations=true&documentVersion=1.26"https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI+REST+Web+Service#FEWSPIRESTWebService-GETlocations
System - PI ServiceFEWS-20765HDSRAdd info on time dependency to getLocations call of PIwebserviceAdded new optinal request parameter to PI web service getLocations call: includeTimeDependencyAdded new optinal request parameter to PI web service getLocations call: includeTimeDependency. Default value is true. For XML format response this option is available from version 1.26 or greater. If the option is set to true, the response will include: - start end end time of the location, if location is time dependent. - if showAttributes is true, and if an attribute is time dependent, for each value it can take it will be listed along with the start and end time and value. - if include RelationLocations is true, and the location relation is time dependent, the end and start time of the relation will be listed. Example response: {code} { "locationId" : "locB", "shortName" : "B", "lat" : "7.0", "lon" : "7.0", "x" : "7.0", "y" : "7.0", "z" : "7.0", "attributes" : [ { "name" : "TEST_ATTRIBUTE", "type" : "text", "id" : "TEST_ATTRIBUTE", "startDateTime" : "1930-01-01T00:00:00+0000", "endDateTime" : "2000-01-01T00:00:00+0000", "value" : "B" } ], "relations" : [ { "id" : "UPSTREAM", "relatedLocationId" : "locC", "startDateTime" : "1930-01-01T00:00:00+0000", "endDateTime" : "1980-01-01T00:00:00+0000" }, { "id" : "UPSTREAM", "relatedLocationId" : "locF", "endDateTime" : "1980-01-01T00:00:00+0000" }, { "id" : "UPSTREAM", "relatedLocationId" : "locE", "startDateTime" : "1930-01-01T00:00:00+0000" } ] } {code} {code:xml} <location locationId="locB"> <shortName>B</shortName> <lat>7.0</lat> <lon>7.0</lon> <x>7.0</x> <y>7.0</y> <z>7.0</z> <relation id="UPSTREAM"> <relatedLocationId>locC</relatedLocationId> <startDateTime>1930-01-01T00:00:00+0000</startDateTime> <endDateTime>1980-01-01T00:00:00+0000</endDateTime> </relation> <relation id="UPSTREAM"> <relatedLocationId>locF</relatedLocationId> <endDateTime>1980-01-01T00:00:00+0000</endDateTime> </relation> <relation id="UPSTREAM"> <relatedLocationId>locE</relatedLocationId> <startDateTime>1930-01-01T00:00:00+0000</startDateTime> </relation> <attribute id="TEST_ATTRIBUTE" name="TEST_ATTRIBUTE"> <startDateTime>1930-01-01T00:00:00+0000</startDateTime> <endDateTime>2000-01-01T00:00:00+0000</endDateTime> <text>B</text> </attribute> </location> {code}https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI+REST+Web+Service#FEWSPIRESTWebService-GETlocations
System - PI ServiceFEWS-20498EAFEWS-18050 FFFS: Make Archived products available through the FEWS-PI Webservicearchived products can now be downloaded from the archiveThe products can now be downloaded from the archive. Documentation can be found here https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI+REST+Web+Service#FEWSPIRESTWebService-GETProducts(2019.02)
System - PI ServiceFEWS-20835EAFFFS-PI: New Request to retrieve all time series of selected plotId of displaygroupsget timeseries using displayGroups plotIdThe get timeseries/displaygroups endpoint can retrieve all timeSeries configured using a displayGroups plotIdhttps://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI+REST+Web+Service#FEWSPIRESTWebService-GETtimeseries/displaygroups(2019.02)
System - PI ServiceFEWS-19855DeltaresRead-only support for FEWS webservicesREADONLY_MODE for FEWS Web ServicesSince 2017.02 it is possible to run the FEWS Web Services in readOnly mode. The FewsPiService.properties can be configured with the property READONLY_MODE=true to only allow read access. In 2017.02 this property has to be configured. Since 2018.02 read only mode is enabled by default.https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+Web+Services
System - PI ServiceFEWS-21074DeltaresFEWS-19650 FFFS-PI: WMS kijkt maar 2 folders diep in de spatial display configGetCapabilites was only using 2 levels of layersThe GetCapabilites was only using 2 levels of layers from the GridDisplay.xml. Now all levels are retrieved.https://publicwiki.deltares.nl/pages/viewpage.action?pageId=134482048
System - PI ServiceFEWS-20470DeltaresFEWS-19650 FEWS Web Services should be readonly by defaultREADONLY_MODE for FEWS Web Services enabled by defaultREADONLY_MODE for FEWS Web Services enabled by default since 2018.02.https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+Web+Services
System - PI ServiceFEWS-18927DeltaresFEWS-19646 Thinning support in REST serviceThinning support for timeseries in pi serviceThinning is used to retrieve the visually interesting time steps of timeSeries. It tries to keep the peaks and gaps and minimizes the number of time steps that have to be retrieved. It is typically used for visualizations. The value to be specified should be equal to the view period in milliseconds of the timeSeries that is visualized divided by the number of pixels that are available for display. For example: visualizing a view period of 5 years (157784760000 milliseconds) on a display of 1024 pixels, the thinning parameter should be set to 157784760000/1024 = 15408668. (Since 2019.02)https://publicwiki.deltares.nl/display/FEWSDOC/FEWS+PI+REST+Web+Service#FEWSPIRESTWebService-GETtimeseries
System - SynchronisationFEWS-18585DeltaresFEWS-17521 Database download is onduidelijkDialog for replicating database improvedDialog for replicating database improvedhttps://publicwiki.deltares.nl/display/FEWSDOC/The+F12+menu
System - WorkflowFEWS-18625eThekwini MunicipalityTemplate functionality for Workflows {code:xml} <workflowDescriptor id="Import_A"> <workflowFileName>Import_Template</workflowFileName> <properties> <string key="dir" value="%REGION_HOME%/A"/> </properties> </workflowDescriptor> {code}
Water CoachFEWS-21055RWSFEWS-21093 WaterCoach: Export (and import?) results with the right timestepsWaterCoach – exporting and importing time series with the times that correspond with the time delay configured in the WaterCoach scriptPresently the time series with delayed times are exported resp. imported  in : - Reports, - TimeSeriesDialog using table popup menu “Save As… - Interactive exporter using menu File -> Export timeseries. Only available if <interactiveExportFormats> are configured in Explorere.xml. - Time series export module - Time series Import module Time delay can be positive or negative {color:#000000}Please note:{color} {color:#000000}GeneralAdapter does not support timeDelay . {color}

  • No labels