Page History

...

<serverUrl>http://nomads.ncep.noaa.gov:9090/dods/gfs/gfs%RELATIVE_TIME_IN_SECONDS(yyyyMMdd, -18000 )%/gfs_%RELATIVE_TIME_IN_SECONDS(HH,-18000)%z</serverUrl>

fileNameDateTimeFilter

One can filter the reading of files and subdirectories by explicity defining which files and (sub)folders are to be read. This can be done using date-strings in the names to be able to read data from a folder setup like "data\2022\01\10\*.*" which in this example lists the year, month and day. This is very useful to read data from large datasets where only the most recent data is to be read. Note that zip files are always internally handled as if it were a folder. The relativeViewperiod defines in which folders FEWS will actively and only look for available data files.
Note that the subFolderLevel of 0 can be used for defining a file filter. The counting of real folders starts from 1 onwards.

The below example reads only the latest files from a server where many files are stored. In this example these are zipfiles provided at a 6-hour timestep. 

<fileNameDateTimeFilter subFolderLevel="1">
	<timeStep unit="hour" multiplier="6"/>
	<dateTimePattern>'hr44_'yyyyMMddHH'.zip'</dateTimePattern>
	<preFixLength>5</preFixLength>
	<postFixLength>4</postFixLength>
</fileNameDateTimeFilter>
<relativeViewPeriod unit="hour" start="-5" end="0"/>

Another example is where data is to be read from a folder structure like "data\<year>\<month>\<day>\*.*"
In this example FEWS will read the data for the given relativeViewPeriod of the last 10 days only.

<folder>data</folder>
<fileNameDateTimeFilter subFolderLevel="1">
	<timeStep unit="year" multiplier="1"/>
	<dateTimePattern>yyyy</dateTimePattern>
	<preFixLength>0</preFixLength>
	<postFixLength>0</postFixLength>
</fileNameDateTimeFilter>
<fileNameDateTimeFilter subFolderLevel="2">
	<timeStep unit="month" multiplier="1"/>
	<dateTimePattern>MM</dateTimePattern>
	<preFixLength>0</preFixLength>
	<postFixLength>0</postFixLength>
</fileNameDateTimeFilter>
<fileNameDateTimeFilter subFolderLevel="3">
	<timeStep unit="day" multiplier="1"/>
	<dateTimePattern>dd</dateTimePattern>
	<preFixLength>0</preFixLength>
	<postFixLength>0</postFixLength>
</fileNameDateTimeFilter>
<relativeViewPeriod unit="day" start="-10" end="0"/>

ftpPassiveMode

When using "ftp://" import the option of passive mode is supported.  This is an optinal field, default value is false, and can be configured in the general section.

...

The filenames must contain the forecast date and time. The pattern to define a group is specified in fileNameDateTimePattern, with the expected number of files for one forecast in numberOfFiles. The files will be imported only when all expected files are in the import folder. A time span also has to be specified in waitingTime to define when to consider the forecast as failed and move it to the failed folder. If more than the waiting time has passed between the forecast time and T0, the forecast is considered failed and the files are moved to the failed foldermoved to the failed folder.

This option can be used in combination with the importTriggeringFile option.

For example, for the following configuration:

...

eg: <fileNamePatternFilter>%TIME_ZERO(yyyy)%??????.nc</fileNamePatternFilter>

Note that the filter does not apply to any zip file directly, but only to the files that are within the zip file.

fileNameObservationDateTimePattern

...

Currently supported only by import from OpenDAP and from local folders.

fileNameForecastCreationDateTimePattern

...

Use the filename, or part of it, as the parameterId for the TimeSeries that will be imported, using Regular Expressions. See description above for fileNameLocationIdPattern.

user

User name, required when importing from protected database connections or protected servers.

...

for fileNameLocationIdPattern.

user

User name, required when importing from protected database connections or protected servers. The username/password is not used for accessing ftp folders. There the credentials have to be defined in the ftp address like ftp://<user>:<password>@ftp.addres.com

password, encryptedPassword

Password, required when importing from protected database connections or protected servers. Please use the Hex value for special characters (e.g. a @ must be specified as %40)
It is strongly recommend to using encryptedPassword, although the encryption within FEWS is relatively limited. Encrypting your password can be done by the "F12 →  S - clipboard → encrypt password" debug menu option.

relativeViewPeriod

The relative period for which data should be imported. This period is relative to the time 0 of the run. When the start and end time are overrulable the user can specify the download length with the cold state time and forecast length in the manual forecast dialog. It is also possible to import data for an absolute period of time using the startDateTime and endDateTime elements.

...

For some data formats an external unit is not defined in the file to be imported. This elements The element <externUnit> allows the unit to be specified explicitly. This unit , which is then used in to find the corresponding unit conversions that are as configured in a UnitConversion UnitConversionsFiles (see see 02 Unit Conversions).

<externUnit parameterId="P.nwp.fcst" unit="mm" cumulativeSum="false"/>

Attributes ;of <externUnit>:

• parameterId: Id of the parameter for which a unit is specified. This is the internal parameter Id.
• unit: specification of unit. This unit must be available in the UnitConversions specified in the unitConversionsId element.
• cumulativeSum:  if this option is set to "true", then it is possible to receive the parameters as cumulative sums. Cumulative sums are partial sums of a given sequence of numbers. For example, if the sequence is:  {a, b, c, d, ...}, then the cumulative sums are: a, a+b, a+b+c, a+b+c+d, .... . The import module will then calculate the values for the individual time steps {a, b, c, d, ...} by subtracting the cumulative sum of the previous cumulative sum value.
• cumulativeMean: similar to cumulativeSum, if cumulativeMean is set to "true", then it is possible to receive the parameters as cumulative means. Cumulative means are partial means of a given sequence of numbers. Therefore, for a given sequence of numbers s = {x₁,x₂,...,x_n,x_n+1} cumulative means are calculated as follows: CM (x_n+1) = [x_n+1 + n * CM (x_n)] ⁄ n+1. The import module will then calculate the values for the individual time steps {a, b, c, d, ...} by multiplying the cumulative mean with the amount of time steps already processed and then subtracting of the previous value that has been also multiplied with the amount of timestep processed minus 1.

...