Call by Attributes Compute Groundwater recharge RUBINFLUX Create input_id (grid-based)...

The following input window appears:

 

Remark:

The right side of the dialogue window is used to import, characterise and define the input data (climate time series, e.g. from HYRAS or other weather/climate grid data).

The left side of the dialogue describes the output mechanisms for generating the input_idName.csv files required in SPRING.

Any numbers or names/terms in curly brackets must be manually edited by the user or they will be automatically populated by the programme.

 

Input data (right side)

Firstly, the procedure for the input data is described using HYRAS precipitation data:

 

 

• Input files

Use the "Preallocate" button to select any file in the directory with the time series data.

The following file formats are offered:

 

Since HYRAS data (netCDF file, *.nc) is stored by year, the year in the curly brackets is replaced by the generalisation YYYY (for the year). SPRING can then extrcat the desired years (see output area) from the file names when exporting the data. The column name for the target file is defined in the upper input field, with"P" used for precipitation (or precepitation). A separate spreadsheet is created for each imported data type.

The files for evapotranspiration usually have the following format:

 

 

The fields marked in red must be edited here.

• Target grid

The time series usually use different grids resolutions. For example, the precipitation data from HYRAS are typically available in a 1x1 km grid, while the evapotranspiration data is stored on a 5 km grid. In this case, it is advisable to use the coarser grid (5 km) as a "target grid" for HYRAS data.

The coarser raster data is then interpolated to match the finer resolution of the "target grid".

 

• Coordinate reference system (CRS)

The CRS of the imported data is extracted from the metadata and displayed. If this information is not available, the user can manually determine the correct coordinate reference system by clicking the button.

When the button is activated, the metadata of the file template is displayed for the user to review and adjust , if necessary:

 

 

The associated CRS is adopted, but it has no influence on the CRS of the underlying model

 

• Grid type

Here, the geometric data of the respective raster data is either extracted directly from the metadata or can be assigned manually by the user.

If the user wishes to assign their own NKID numbers, they can specify a custom file containing these individual numbers by activating the "ID:" checkbox. In this case, {ID} must be used instead of {row}{col:4} in the curly brackets within the output files name field.

 

• Values

The input data can be weighted in the "Values" line.

For example, if logger data for precipitation is available with hourly values, the user can choose whether the values should be summed (e.g. for precipitation) or averaged (e.g. for temperature).

It is important to note that the evapotranspiration data is provided in cm and must therefore be multiplied by a factor of 0.1 for proper processing with RUBINFLUX!

 

 

The NODATA value is retreived from the metadata.

The drop-down menu offers the option of converting global radiation data to sunshine duration and vice versa. Generally, no conversion is required.

 

Output data (left side)

 

• Output files

The file path for the generated files is defined. The number of the input_idNumber.csv is automatically assigned based on the rows and columns of the input data, or alternatively , from an ID file specified by the user.

The generated data can either be appended to existing time series data or an additional data column can be added to the existing files.

The "Correct non-Gregorean calendar" checkbox can be used when time series, e.g. from climate models, are available within a standard calendar (e.g., 365 days per year or 30 days per month). Activating this checkbox allows the system to either insert, the missing days (by averaging of the data) or remove any individual day (e.g. February, 29th).

• Options

The first step is to define the period to be exported.

The data to be exported can be limited to the model boundary.

The NKID data created can be saved directly as a structure within the opened model and/or additionally exported as a separate file (format: x, y, NKID number).

 

• Target grid/point cloud

The first step is to assign the x and y coordinates of the grid to the columns. This is performed automatically based on the entries on the right side of the dialogue. At this point, the coordinate reference system for the output data can be finally defined by the user

 

Generate input_ids (station-based)