New methods "moveByXY" and "moveByBearing" have been added to Coords, addressing issue 39. Code cleanup and extensive documenting have been performed on Graphics and PNGIO, that now supports creating world file (optionnally). A new option has also been added to ARCIO, "A3D_view", to generate file names compatible with the Alpine3D's grid viewer (false by default). A new function to remove the extension from a file name has been implemented in IOUtils.

Better handling of "autoscale": the min and max are almost always taken into account (this is usefull to set fixed points, like the snow line, the sea level, etc) and the autoscale bool is used to tweak a given gradient for better display in autoscale (ie: removing the snow line in autoscale). The client is then responsible for provided the relevant min and max that he wants to use (constant -> no autoscale or variable -> autoscale).

Now, the plots are fitted/optimized depending on the meteo parameter (if available). The proper metadata is written into the file (again, if available). More gradients have been implemented.

Now the color gradient can be chosen (given as an argument in the Gradient constructor). This is not yet really used by PNGIO, but this will come!

The legend class is now free of hard-coded values in the middle of the code (all depends on the static consts).

The NearestNeighbour 2D resampling algorithm has been reshaped in order to offer the same interface as BiLinear. A typo in its name has been fixed. But NearestNeighbour does not work properly (bug not found yet)

A better way of submitting metadata to libpng has been implemented (ie: two vectors of strings that are then converted to char* to be given to libpng). The plugin basic options have been implemented, including size specifications. 

Some fonts improvements.

The purely graphical parts of PNGIO have been isolated in a new file, Graphics, that contain the Legend class, a Color namespace and a Gradient class. The gradient code is not so clean yet, but the PNGIO plugin is now much cleaner. The color gradients will actially need some serious re-actoring and design in order to be both flexible and efficient (the odds are, it would be based on a object factory and several derived classes like for libFit1D).

The 2D_interpolations example has been updated to reflect recent changes (see previous commit). Improvements in the legend for PNGIO.

This addresses the 2D part of issue 168: the ability to specify which meteo parameter and time step to read/write from/to a 2D grid. This should be the prefered reading method in the future, since it leaves to the plugin the task of building the file name, extension, database table, etc This also provides added metadata and more control over the writing process.

The legend text has now its own color and the legend background can also have its own color (or remain transparent).

Much improved legends: the font size is twice as big, the verticals are bold, the exponent is half-height. And spacing is more pleasant.

The png plugin can now generate a legend. This is still very primitive, the code is not so nice, but it compiles cleanly and works. Looking forward for the next version!

First version of a PNG plugin. It only writes a grid for now, and nothing is user configurable. In the process, a small bug has been found in the RH spatial interpolation method (not handling nodata correctly)

A lot of writes were using std::endl for end of line, which forces a buffer flush. This lead to a visible performance cost (as shown by the profiling project made in collaboration with HES_SO). These have been replaced by "\n" that lets ostream manage its buffer as it wants.

More error checking: the offsets and multipliers must match the number of fields and the number of fields must match the true number of columns at each line

The imisio USE_IMIS_HNW option is getting simpler... winter condition detection is not applied anymore (leaving the application do it, or an extra filter be implemented for it later).

Very small changes (ie: excluding exception backtrace) so that MeteoIO compiles for Android (follow the "Getting-started" documentation page if you're want to witness it by yourself!). Basically, android-cmake adds a new plateform variable (named "ANDROID", how surprising) that we use to skip the backtrace and its include.

Added parameter check to the HNW_MELT filter and changed its handling of filtered points: since when we can diagnose that the non-zero measurements are coming from melt in the sensor, we now set the measured value to zero. It gets set to nodata only when the melt conditions could not be established (ie: missing measurements on RH, TA, etc). We will have to see if it really makes sense by using it for a while...

The "RateFilter" filter has been renammed "FilterRate" in order to be more consistent with other filters (this does not change anything user-side). A new filter has been created, HNW_MELT. This applies the Snowpack criteria on a precipitation measurement: if relative humidity is not high enough or TA and TSS too far apart, it is considered that any measured precipitation comes from snow melting in the (unheated) rain gauge, therefore the measurement is deleted.

The last occurences of NROFSTATIONS have been deleted in BormaIO, closing issue 163.

Some code cleanup took place in CosmoIO and FilterMax.

In IMISIO, a new option and behavior has been implemented to properly manage precipitation measurements: ANETZ stations keep their HNW (they are considered reliable). IMIS stations by default don't produce HNW anymore. A key (USE_IMIS_HNW) can force using them, but a detection of winter conditions (ie: TA>0 and TSS>0) removes measurements known to be invalid. If neither TA nor TSS are available, then HNW is deleted (in order to prevent injecting HNW=0 in the system during a freeze event if the station would happen to miss TA and TSS). USE_IMIS_HNW should always be followed by the HNW_MELT filter.

The Fit1D class constructor can now read a fit model name as a string. This was necessary for parsing a user input coming from io.ini. 

The ordinary kriging interpolation algorithm is now active. It is far from perfect (the variogram is computed in a very cheap way that contributes to make it very fragile), but it is time for the first users to start playing with it. The variogram model to use can be provided as an optional argument and in case of fit failure, an appropriate error message is given (but no fallback mechanism exists). The next step will be to compute the variogram on time series, which should produce more reliable data sets for fitting the variogram model on.

Some error messages have been improved in the matrix class.

Oups, types mismatch... and the version numbers have been pushed up in order to prepare for the upcoming release

Some improvements, to give more errors and warnings in case of bad or sloppy input, or inproperly formatted SMET-files.

The LIDW interpolation was not safe when less stations were available than the requested number of neighbors. Since this interpolation method is still quite experiemental (the bilinear lapse rate can lead to very wrong results), it has been removed from the example io.ini.

On Windows, static libraries MUST be built in order to get the lib files. Warnings have been turned off on the gsoap files for vc++.

A bug was fixed in SMETIO: when given OLWR, it should have computed TSS, but it was not... (using the wrong MeteoData object).

Documentation and error messages improvements. A new method was added to Atmosphere: virtualTemperatureFactor.

The "soft" argument was not properly handled by the Min and Max filters, this has been fixed. All filters now properly reserve the vector size that they need, which reduces the number of instruction fetch misses and should (slightly) improved performances. Please try to use vector.reserve() whenever possible!

SNIO throws an exception if the user specified a METAFILE that does not exists/is not valid. ARPSIO was wrongly reading grids (wrong layer for DEM and swapping x and y)

A new method, getExtension() has been added to IOUtils in order to return the extension of a given filename. This is used by the SMETIO and SNIO plugins to automatically add the proper extension to input file names if they don't already have one.

The Median Average Deviation filter has been ported (and validated) to the new filtering infrastructure.

Several error messages have been improved.

SNIO.cc:173-176 Allow to read meta data from either *.sno (smet-format) or *.snoold (snowpack-format) if METAFILE is either not provided or not found

Because POPC does not properly support std::cout and requires cout instead, this has been fixed in the code, with the necessary "using namespace" added. Only one std::cout remains (in IOUtils) and will be removed if absolutely necessary later.

SNIO: Change of Config keys, the following keys are relevant now for reading meteo data and meta data:
METEOPATH:  Path to the meteo files directory
STATION#: Specifies the meteo data file for station number #
METADATA: Specifies the file with meta data for all meteo data files

Note that NROFKEYS is no longer necessary and METEOFILE# has been replaced by STATION# to be more consistent with the other MeteoIO plugins.

ImisIO: The key NROFSTATIONS is not required anymore and not parsed by ImisIO - the plugin now simply looks for STATION1, STATION2 and so on in the config object until a certain key STATION# can not be found.