|Mar 19, 2010|
|10 years 7 months ||Small bugfix in Date_IO: no double column at the end of the ISO
IOExceptions: added functionality for LINUX that enables a
stacktrace when an exception is printed (that is e.what() is called)
|Mar 16, 2010|
|10 years 7 months ||Thanks to valgrind, found a little bug in GeotopIO, where I
initialized a vector to having 4 fields, but later I used 5 fields.
|10 years 7 months ||Altered the function that returns a window of data to filters
(getWindowData) to optionally also provide the dates for the
elements in the window.
|10 years 7 months ||The buffering system shows itself improved - a fine tuning of the
performance is possible through the following tags:
BUFFERSTRATEGY = [always | newinterval] # default: always
BUFFERPERIOD = 1 2
The BUFFERPERIOD tag configures the amount of days be
|10 years 7 months ||A new function is introduced into the IOInterface: writeMeteoData.
It expects one vector<vector<MeteoData>> and one
vector<vector<StationData>> as well as an optional
string (for database info, file name, etc). The relevant io.ini tag
|10 years 7 months ||Added Filter to average wind speeds and directions called
WindAvgFilter, accessible through the io.ini tags: wind_avg;
VW::filter1 = wind_avg
VW::arg1 = soft center 1 60
The averaging is done vector based by computing the east-west and
|Mar 10, 2010|
|10 years 7 months ||Updated the gsnclient app to return the stations available before
any other output. Fixed spelling issue in GEOtopIO.
|Mar 9, 2010|
|10 years 7 months ||The java bindings now use the latest 2D interpolations interface.
This means that all data is immediately put into a vector of
MeteoData and then routed as usual through the Meteo2DInterpolator.
The includes have also been cleaned up (only using Mete
|10 years 7 months ||Add try/catch block surrounding the call to interpolation
|Mar 4, 2010|
|10 years 7 months ||updated the IOUtils functions to use const references where sensible.
|10 years 7 months ||Renamed test.cc to gsnclient.cc and updated the CMakeLists file
|Mar 1, 2010|
|10 years 7 months ||A better example of DEM usage has been prepared: it uses a 1000m
resolution DEM of the whole of Switzerland (that is, with holes in
the dem) and valid coordinates are now much easier to guess...
|10 years 7 months ||A new slope algorithm has been added (HORN), even if it computes the
same slopes as CORRIPIO (except for border cells). This is the
algorithm that is used in ArcGIS. Some cleanup has been done in the
references (it seems some algorithms have been pub
|Feb 25, 2010|
|10 years 7 months ||This is an updated version of the java interface to take into
account the recent changes in MeteoIO's API. The Makefile has been
improved, it now compiles on Linux.
|Feb 23, 2010|
|10 years 7 months ||A problem was found during the intialization of the plugins (as well
as A3DIO): the parameters that were passed to initialize the local
copies were not always initialized with the raw parameters passed to
the constructor but usually with the copy of
|10 years 7 months ||The write2DGrid members of the plugins now use the features of the
Coords object to output the grid in the input coordinate system (as
specified in the io.ini file). A copy of the Coords object is made,
so that it does not change the given grid. This
|Feb 22, 2010|
|10 years 7 months ||The plugin's interface (IOInterface) has been slightly modified:
readSpecialPoints now returns a vector of Coords. This means that a
plugin can provide coordinates as (lat,long) or (easting, northing)
or (grid_i, grid_j). All the plugins have been mo
|10 years 7 months ||A few issues have been fixed in Coords: the copyProj method had a
bug, the distance method now uses cartesian calculation if both
projections are equal, a new getProj() method is now available (but
it should be rarely needed). The GridxDObject::gridi
|Feb 19, 2010|
|10 years 8 months ||Finally, the implementation of issue 35 is here... A few bugs left
with the Coords class have been fixed (namely, the methods take 1
optional parameter and not more, because for this usage scenario it
was way too dangerous and the user (myself in thi
|Feb 18, 2010|
|10 years 8 months ||The constructor Coords(ConfigReader) was a bad idea... Convenient,
but way too specific. It has been removed. The documentation in the
Coords class has been updated.
A saner handling of nodata values by the plugins has been
implemented. Now, each pl