methods | automatic update

Two of the data collection methods for the HydroDCS are through satellite telemetry (GOES and Iridium).  When collecting data via these data streams, it needs to be decoded before it can be read and stored on the HydroDCS.  To tell the HydroDCS how to do this, there are several methods.  

HydroDCS Decoding Methods

First, it's important to note that the HydroDCS relies on OpenDCS to do the decoding.  Knowing this, here are the methods for setting up the decoding information:

OpenDCS Client

The OpenDCS client can be used to set up decoding information for the sites that are installed on the HydroDCS.  This can be done manually, site by site, or it can be done by importing bulk information from another OpenDCS configuration.  For more information on this, take a look at the OpenDCS documentation here.

HydroDCS Bulk Import

The HydroDCS has the capability to import decodes information directly through one of the web pages.  To get there, you need to be logged in as a controller.  Using the profile drop-down, select "Import OpenDCS XML File".  Here you can import any file that has been exported by OpenDCS.  Decoding information is a large part of this, but this will also bring in platform and config information, that is, if they are in the XML file.

Automatically Update Decodes Specs

Must be logged in as controller to manually upload a rating table

Using the profile drop-down, navigate to "Operator > Auto Update Decodes Specs".  Here you can select the rating table file and upload it.


Here is a screen where users can automatically update decodes information from a remote file path.  If this feature is enabled, the HydroDCS will periodically access the remote URL to check for new decodes updates and, if there is new decodes information, it will update itself with that new information.  The remote URL must contain the following to properly update the HydroDCS:

  • The remote URL must output plain text in the following format:
    [CWMS ID].xml | Apr 18 10:37:46 2019
    [CWMS ID].xml | Apr 19 10:37:46 2019
    [CWMS ID].xml | Apr 12 10:37:46 2019
    For example, the total output of a valid specified URL would be:

    AGA.xml | Apr 18 10:37:46 2019
    MLBO.xml | Apr 19 10:37:46 2019
    DET.xml | Apr 12 10:37:46 2019

    In this case, this output is saying that there are 3 sites that require decodes information updates.  It's also saying that the following files (AGA.xml, MLBO.xml, and DET.xml) are in the same URL directory that the user has specified and that they are accessible by the HydroDCS.  The CWMS path must be the name of each file, with a file extension of .xml.  The HydroDCS will look for the installed sites it knows about, compare it with the list of sites at the remote decodes specs location, then compare the date, and if the date at the remote path is later than the date the HydroDCS last updated the decodes information for the corresponding site, it will grab that XML file and import it.
Options:
    • Update Decodes Specs Remotely - If the toggle switch is enabled, the HydroDCS will periodically check the specified URL for new decodes information.  A value URL must be specified.  See the information above for how to configure this properly.
    • Ignore SSL Certificate - In some cases, you may choose to update decodes information from a site with an untrusted SSL Certificate.  In many cases, this site is trusted, it just cannot be verified by the HydroDCS.  In these cases, the decodes information will never be downloaded.  The user can toggle this option on to allow downloads.
      NOTE - This should only be used if the server at the Update Location is trusted.  If you are not an expert in this area, you should not be toggling this on, as it can open the HydroDCS to vulnerabilities.
    • Check on DECODES Spec Difference - checks for differences in local file and remote file, and only updates the local file if there are differences. This ignores the 'lastmodifytimestamp', the file will only be updated if there are differences detected even if the remote file is marked as newer.
    • Force Deletion of Duplicate Platforms - Delete duplicate platform files. NOTE - the file with the most recent 'lastmodifytimestamp', of the duplicates, will be kept.
    • Force Update - This will run a manual update.  It is used in cases where the user does not want to wait for the periodic update to occur.
    • Submit Button - When you make a change to the values on this page, click submit to save those changes.