MeteoIODoc  MeteoIODoc-2.9.0
Plugins developement guide

The data access is handled by a system of plugins. They all offer the same interface, meaning that a plugin can transparently be replaced by another one. This means that plugins should follow some common rules, which are described in this guide. Templates header and code files are available to get you started, look into the "plugins" subdirectory of the source directory (files "template.cc" and "template.h").

# Plugins implementation

Each plugin must inherit the class IOInterface and implement all or part of its interface (at least for public methods). The plugins are then free to implement the private methods that they see fit. Because the interface described in IOInterface is quite generic, some methods might not be relevant for a given plugin. In such a case, the plugin should throw an exception as illustrated in the example below:

{
//Nothing so far
throw IOException("Nothing implemented here", AT);
}

It is the responsibility of the plugin to properly convert the units toward the SI as used in MeteoIO (see the MeteoData class for a list of parameters and their units). This includes converting the nodata value used internally in the plugin (as could be defined in the data itself) into the unified IOUtils::nodata nodata value. Moreover, it is required by the BufferedIOHandler that each plugin that implements readMeteoData also implements the readStationData method. This is required so that the metadata is available even if no data exists for the requested time period.

Finally, plugins must properly handle time zones. The Date class provides everything that is necessary, but the plugin developer must still properly set the time zone to each Date object (using the "TZ" key in the io.ini configuration file at least as a default value and afterwards overwriting with a plugin specified time zone specification if available). The time zone should be set before setting the date (so that the date that is given is understood as a date within the specified time zone).

The meteorological data must be returned in a vector of vectors of MeteoData (and similarly, of StationData in order to provide the metadata). This consists of building a vector of MeteoData objects, each containing a set of measurements for a given timestamp, at a given location. This vector that contains the time series at one specific location is then added to a vector (pushed) that will then contain all locations.

vector of vector structure

Various classes from MeteoIO can prove convenient for use by plugins: for example the Coords class should be used for geographic coordinates conversions, while the Config class should be used for getting configuration information from the user's configuration file. Please do NOT implement your own version of this kind of feature in your plugin but exclusively rely on the matching classes of MeteoIO, extending them if necessary. A template for writing a plugin class is available in the plugin directory under the name template.cc and template.h. Simply copy these two files under a new name and fill the methods that you want to implement. Some easy example implementation can be found in ARCIO or A3DIO.

# Plugins registration

Once a plugin has been written, it must be "registered" so that it is known by the rest of the library. This is done in IOHandler.cmake.cc by a) adding a compilation flag similar to the other plugins (cmakedefine PLUGIN_...), b) including its header file (optionally compiling it only if it is being installed), c) giving it a plugin key in IOHandler::getPlugin (that will be used by the user in the configuration file when they want to use said plugin), and d) adding it to the doc in the HTML table.

Finally, the build system has to be updated so that it offers the plugin to be built: a local file (meteoio/plugins/CMakeLists.txt) has to be edited so that the plugin is really built, then the toplevel file has to be modified so the user can choose to build the plugin if he wishes (CMakeLists.txt). Please keep in mind that all plugins should be optional (ie: they should not prevent the build of MeteoIO without them) and please call your plugin compilation flag similarly as the other plugins (ie: PLUGIN_MYNAME).

# Plugins documentation

It is the responsibility of the plugin developer to properly document his plugin. The documentation should be placed as doxygen comments in the implementation file, following the example of A3DIO.cc: a subpage named after the plugin should be created (and referenced in MainPage.h) with at least the following sections:

• format, for describing the data format
• units, expressing what the input units should be
• keywords, listing (with a brief description) the keywords that are recognized by the plugin for its configuration

The internal documentation of the plugin can remain as normal C++ comments (since they are addressed to the maintainer of the plugin).

# Plugins testing and validation

In order to check that a plugin operates properly, developers are invited to test the following (among others), for a plugin that reads meteorological data (these tests can be performed using the example code doc/examples/meteo_reading.cc):

• request one time stamp part of the original data set
• request one time stamp within the period of the original data set, but not matching an existing time stamp
• request a data point before the original data set
• request a data point after the original data set
• request a data point at the end of a very large data set (tens of Mb) and check that memory consumption remains the same as when requesting a data point at the beginning of the data set (ie: that the memory for one buffer is used, but that the temporary memory usage of the plugin does not increase with the amount of data it has to parse before returning it to the BufferedIOHandler)