How to Build Your io.ini Configuration File

Table of Contents

• Introduction
• Sections walk through
  • [General]
  • [Input]
  • [InputEditing]
  • [Output]
  • [Filters]
  • [Interpolations1D]
  • [Interpolations2D]
  • [GridInterpolations1D]
• Final considerations

Introduction

MeteoIO is driven by a configuration file (io.ini). While it is possible to edit this file manually, it is highly recommended to use Inishell to reduce errors and access help text for each key. This section explains how to manually set up your io.ini file.

Note

Please read the "General Documentation" page before starting!

An ini file is made of several sections:

Section	Purpose
[General]	Buffering and general settings
[Input]	Input plugins and parameters
[InputEditing]	Edit input timeseries and resampling
[Output]	Output plugins and parameters
[Filters]	Pre-processing stack for meteorological data
[Interpolations1D]	Temporal resampling of meteorological data
[Interpolations2D]	Spatial interpolation of meteorological data
[GridInterpolations1D]	Temporal resampling between gridded data

Sections walk through

[General]

The documentation about this section is found in Config. It currently Contains buffering keys (see BufferedIOHandler).

[Input]

This section contains the list of all the plugins that you want to use as well as their arguments. There are plugins for:

• METEO (meteorological data)
• GRID2D (grids)
• POI (Points Of Interest)
• DA (data assimilation)
• LANDUSE (land use)
• DEM (Digital Elevation Model)

Each plugin has its own set of keys (see the Available plugins page).

Note

Specify the geographic coordinate system (see Available coordinate systems) and a fallback time zone (so if some time information comes without a time zone, it will use the one declared in this section).

[InputEditing]

Edit input meteorological timeseries (see Input Data Editing) and perform spatial resampling (see Spatial resampling and regridding handling).

[Output]

Similar to [Input], but for outputting data.

[Filters]

Define the pre-processing that has to be performed on the incoming meteorological data. This is done by building a stack of processing elements that will be applied one after the other one (ie in series), for each meteorological parameter (see Processing overview).

[Interpolations1D]

Temporal resampling of meteorological data (see Resampling overview). The goal is to be able to take in data at any sampling rate and to extract values at any user given time step according to the resampling specifications of the user. The maximum gap size can be given with the MAX_GAP_SIZE key that expresses (in seconds) how far a valid point can be searched for when re-interpolating a missing value (up to MAX_GAP_SIZE/2 before and after the requested point).

[Interpolations2D]

Spatial interpolation of meteorological data, based on a provided Digital Elevation Model (see Spatial interpolations). The goal is to populate two dimensional grids with meteorological parameters from point measurements, according to the specifications of the user.

[GridInterpolations1D]

Temporal resampling between gridded data.

Final considerations

It is recommended to always validate your configuration with Inishell to avoid runtime errors. And please keep in mind that the application that you are using might also need its own section(s)!