Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

horizontal_Stride: default setting is 1. Needs to be configured only if a different value is needed.
time_Stride : default setting is 1. Needs to be configured only if a different value is needed.
add_latitude_longitude : default is true.  Needs to be configured only if a different value is needed.
disable_Project_Subset: default is true.  Needs to be configured only if a different value is needed.
TIME_ZERO is the time the forcast was created. Can be replaced by actual time in the following format: FMRC_RUN_2019-02-23T12:00:00Z.

 

Code Block
languagexml
linenumberstrue
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2009 sp1 (http://www.altova.com) by ICT (Stichting Deltares) -->
<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">
   <!--Surface currents-->
   <import>
      <general>
         <importType>Hycom_netcdf</importType>
         <serverUrl>http://ncss.hycom.org/thredds/ncss/GLBv0.08/expt_93.0/data/forecasts/runs/FMRC_RUN_%TIME_ZERO(yyyy-MM-dd'T'HH:mm:ss'Z')%</serverUrl>
         <relativeViewPeriod unit="day" start="0" end="8" startOverrulable="true"/>
         <idMapId>IdImport_HYCOM</idMapId>
         <maximumVerticalSnapDistance>0.1</maximumVerticalSnapDistance>
         <missingValue>-999</missingValue>
         <importTimeZone>
            <timeZoneOffset>+00:00</timeZoneOffset>
         </importTimeZone>
         <dataFeedId>HYCOM</dataFeedId>
      </general>
      <properties>
        <bool key="import_all_layers" value="false"/>
		<bool key="add_latitude_longitude" value="true"/>
		<bool key="disable_Project_Subset" value="true"/>
		<int key="horizontal_Stride" value="1"/>
		<int key="time_Stride" value="1"/>
      </properties>
      <timeSeriesSet>
         <moduleInstanceId>Import_HYCOM_Currents</moduleInstanceId>
         <valueType>grid</valueType>
         <parameterId>C.simulated.u</parameterId>
         <locationSetId>HYCOM.ArabianSea_AllLayers</locationSetId>
         <timeSeriesType>external forecasting</timeSeriesType>
         <timeStep unit="hour" multiplier="3"/>
         <readWriteMode>add originals</readWriteMode>
         <synchLevel>6</synchLevel>
         <expiryTime unit="day" multiplier="30"/>
      </timeSeriesSet>
      <timeSeriesSet>
         <moduleInstanceId>Import_HYCOM_Currents</moduleInstanceId>
         <valueType>grid</valueType>
         <parameterId>C.simulated.v</parameterId>
         <locationSetId>HYCOM.ArabianSea_AllLayers</locationSetId>
         <timeSeriesType>external forecasting</timeSeriesType>
         <timeStep unit="hour" multiplier="3"/>
         <readWriteMode>add originals</readWriteMode>
         <synchLevel>6</synchLevel>
         <expiryTime unit="day" multiplier="30"/>
      </timeSeriesSet>
   </import>   
</timeSeriesImportRun>

 

The importer module should be registered in FEWS  Config/RegionConfigFiles/ModuleInstanceDescriptors.xml. Locations of the wanted time series should be registered in Config/RegionConfigFiles/Locations.xml.  Parameters should be registered in  Config/RegionConfigFiles/Parameter.xml. The workflow should be registered in Config\RegionConfigFiles\WorkflowDescriptors.xml. 

A grid needs to be configured in the  Config/RegionConfigFiles/Grids.xml file. Location id of the grid and the time series configured in import should be the same.  Most of the HYCOM grid is available with a cell resolution of 0.08 degrees. However, below -40 degrees, the vertical (y) resolution becomes 0.04 (horizontal x resolution stays the same). If you need data on both sides of this line you will have to import two different HYCOM grids using separate import modules.