WSL/SLF GitLab Repository

  1. 22 Dec, 2011 1 commit
    • Mathias Bavay's avatar
      This addresses the 2D part of issue 168: the ability to specify which meteo... · 8ad5d61f
      Mathias Bavay authored
      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.
      8ad5d61f
  2. 22 Aug, 2011 1 commit
  3. 17 May, 2011 1 commit
  4. 21 Mar, 2011 1 commit
  5. 04 Feb, 2011 1 commit
    • Mathias Bavay's avatar
      The full support for timezones has been brought back. This fixes issue 71. The... · 904aeaa8
      Mathias Bavay authored
      The full support for timezones has been brought back. This fixes issue 71. The SMET, SMET, IMIS, BORMA plugins have been validated. Geotop should be validtaed if an input data set is available. A new class will have to be implemented to represent time periods. This is currently only a typedef pointing to the Date class, but a specific class would be welcomed.
      
      GSN has been fixed for some changes on the web service, but does not retrieve the correct timestamps (is this a GSN issue?). The GSN compilation has been improved: the warnings related to GSOAP have been removed. 
      
      A new long wave radiaiton model using cloudiness as input has been added (Omstedt, 1990). 
      904aeaa8
  6. 07 Jan, 2011 1 commit
    • Mathias Bavay's avatar
      The documentation and examples have been updated to reflect the latest changes... · f7afddcf
      Mathias Bavay authored
      The documentation and examples have been updated to reflect the latest changes in MeteoIO (namely: the merging of MeteoData with StationData). A documentation bug has been fixed, that involved deleting the doxygen comments for the commented "clone()" method in IOInterface. Since this is not used anywhere and has been commented out for a while, this method has been fully deleted.
      
      Meteo2DInterpolator now has its own << operator for debugging purposes.
      f7afddcf
  7. 09 Dec, 2010 1 commit
    • Thomas Egger's avatar
      MeteoData now has an extra public member variable: StationData meta. It will... · 3f940ba5
      Thomas Egger authored
      MeteoData now has an extra public member variable: StationData meta. It will hold the meta information of the measurment instead of dragging along a second vector<StationData> alongside the vector<MeteoData> everywhere.
      
      This has huge implications: the IOInterface has been rewritten, subsequently changes need to be propagated into all plugins and all modules dealing with meta data.
      3f940ba5
  8. 10 Aug, 2010 1 commit
  9. 06 Aug, 2010 1 commit
    • Mathias Bavay's avatar
      The DEMObject was not properly buffered (the update flag was not honored),... · 8e574ceb
      Mathias Bavay authored
      The DEMObject was not properly buffered (the update flag was not honored), this has been fixed. The A3DIO plugin now implements readStationData. A few speed improvements have been brought to A3DIO and SMETIO by using the "reserve" method of the vectors (so that the vectors don't have to reallocate memory constantly).
      8e574ceb
  10. 26 Jul, 2010 1 commit
  11. 21 Jun, 2010 1 commit
    • Thomas Egger's avatar
      Directory structure change: src folder now called meteoio · 752c0068
      Thomas Egger authored
      Overall all include statements within in the library have been replaced by angle brackets, the default install path for the include file is $CMAKE_INSTALL_DIR/include/meteoio, the meteoio libraries (static and shared) will be installed in $CMAKE_INSTALL_DIR/lib per default.
      
      The plugins will be installed in the subdirectory $CMAKE_INSTALL_DIR/lib/meteoio/plugins
      752c0068
  12. 27 May, 2010 2 commits
  13. 26 May, 2010 1 commit
    • Mathias Bavay's avatar
      Two minor potential bugs have been fixed in SNIO. · f62e474c
      Mathias Bavay authored
      The A3DIO plugin now has a writeMeteo() method. It writes all timesteps, even if truncating the timestamp to the hour. It also assumes that all stations have synchronized timesteps (ie: reading the timesteps for the first station is enough). It can also not handle metadata that change over time and it does not split 2D files per years...
      f62e474c
  14. 21 Apr, 2010 1 commit
  15. 13 Apr, 2010 1 commit
    • Thomas Egger's avatar
      changed the way we deal with the projection parameters within the io.ini.... · 31474cb6
      Thomas Egger authored
      changed the way we deal with the projection parameters within the io.ini. COORDSYS must be declared in the [Input] section and is optional for the [Output] section (it becomes mandatory if a function is to be used, that creates output)
      
      The parsing of the ConfigReader object is done in IOUtils, this is not the final solution on that.
      31474cb6
  16. 31 Mar, 2010 1 commit
  17. 15 Mar, 2010 1 commit
    • Thomas Egger's avatar
      A new function is introduced into the IOInterface: writeMeteoData. It expects... · 4100a120
      Thomas Egger authored
      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 is:
      METEODEST = GEOTOP
      
      Only GeotopIO has this method fully implemented thus enabling to convert all meteo data captured from any other source to a GEOtop compliant meteo files. The relevant tags are:
      METEODESTPATH = /tmp
      METEODESTSEQ	= WindS WindDir RelHum AirT SWglobal Iprec
      
      METEODESTPATH determines where the files will be written to and METEODESTSEQ determines the order in which the meteo parameters will be written into the CSV file
      4100a120
  18. 23 Feb, 2010 2 commits
    • Mathias Bavay's avatar
      A problem was found during the intialization of the plugins (as well as... · 9bd7b27c
      Mathias Bavay authored
      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 the previous element. This lead to some copies not to be up to date when calling their constructor (see A3DIO.cc for a clearer view!!).
      9bd7b27c
    • Mathias Bavay's avatar
      The write2DGrid members of the plugins now use the features of the Coords... · 4e158737
      Mathias Bavay authored
      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 is fixing issue 3
      4e158737
  19. 22 Feb, 2010 1 commit
    • Mathias Bavay's avatar
      The plugin's interface (IOInterface) has been slightly modified:... · 2ee54369
      Mathias Bavay authored
      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 modified accordingly and POINTS and POINTSArray have been removed from Array.h
      2ee54369
  20. 16 Feb, 2010 1 commit
    • Mathias Bavay's avatar
      The MapProj class has been renamed in Coords. It now contains the coordinates... · d393958b
      Mathias Bavay authored
      The MapProj class has been renamed in Coords. It now contains the coordinates (lat,long) and (xcoord, ycoord) and should therefore be used as a storage and conversion class. The necessary changes have been made to the rest of the code so it uses this class, but it still does NOT use it as a storage of coordinates (which will have to be done in the future). This addressed partially issue 35.
      d393958b
  21. 10 Feb, 2010 1 commit
  22. 03 Feb, 2010 1 commit
    • Mathias Bavay's avatar
      The Special_PTS and CSpecialPointsArray structures have been renamed in... · 11d9c246
      Mathias Bavay authored
      The Special_PTS and CSpecialPointsArray structures have been renamed in "POINT" and "POINTSArray" (there was no reason to call them "special points"). 
      
      A few new methods have been added to DEMObject: getPointsBetween that returns a vector containing the indices of all points located on the line between two points (given by their real world (x,y) coordinates), horizontalDistance that returns the horizontal distance between two points and terrainDistance that returns the distance between two point accros the terrain as described by the DEM (ie: going up and down the terrain).
      11d9c246
  23. 09 Dec, 2009 1 commit
  24. 09 Nov, 2009 1 commit
  25. 05 Nov, 2009 1 commit
    • Thomas Egger's avatar
      Introducing the new filter system: MeteoFilter; documentation will follow; · 196cc4b6
      Thomas Egger authored
      MeteoFilter operates on static filter algorithms which are defined in FilterAlgorithms.*
      FilterProperties is a small helper class to declare properties of an Algorithm (e.g. how many data points it requires, ...)
      The new MeteoFilter system is utilized by class BufferedIOHandler.
      
      The old filter system is removed from Makefiles/CMake and the SVN directory.
      Legacy MeteoIO classes Meteo1DResampler and MeteoBuffer, which were solely required by the old filter system are also removed.
      196cc4b6
  26. 22 Oct, 2009 1 commit
    • Mathias Bavay's avatar
      A new define (DEBUG_ARITHM) has been added that activates the non-catching of... · 85135ebd
      Mathias Bavay authored
      A new define (DEBUG_ARITHM) has been added that activates the non-catching of arithmetic exceptions. This is specially required for parallel execution when the code from the library might execute in a process different from the caller (thus not having the required flag set on the cpu for its process). This is enabled/disabled in the Makefile.in (or the Makefile for the end user). 
      
      The std:: namespace declaration has been added to a lots of places, making the "use namespace std" usage irrelevant (and thus suppressed). Other namespaces that were called with a "use" have been found not to be used anymore and therefore also removed.
      
      Several bugs in the doxygen comments have been fixed: typo (misplaced space), comments not matching the declaration anymore, etc Doxygen now executes without warnings.
      
      85135ebd
  27. 05 Sep, 2009 1 commit
  28. 26 Aug, 2009 1 commit
    • Thomas Egger's avatar
      * plugin GrassIO fully functional · 2a9377ae
      Thomas Egger authored
      * MapProj is a new class that deals with all kinds of map projections (some can be implemented directly, like CH1903, others can be based on the Proj.4 library)
      * changes in map projections made it necessary to adapt the children of IOInterface that have an implementation of readMeteoData or read2DGrid
      2a9377ae
  29. 18 Aug, 2009 1 commit
  30. 17 Aug, 2009 1 commit
  31. 13 Aug, 2009 2 commits
  32. 07 Aug, 2009 1 commit
    • Thomas Egger's avatar
      * Complete rewrite of IOHandler: Now it is very easy to add new plugins... · b1b0497b
      Thomas Egger authored
      * Complete rewrite of IOHandler: Now it is very easy to add new plugins (adding one line), all the internals (allocation, loading, deleting, loading the right plugin for each IOInterface function) are transparently done.
      
      * changed one parameter in readMeteoData to const unsigned int& from unsigned int. Therefore all children of IOInterface needed to undergo that change
      b1b0497b
  33. 28 Jul, 2009 1 commit
  34. 27 Jul, 2009 1 commit
    • Thomas Egger's avatar
      New design for MeteoIO library: · e569ad90
      Thomas Egger authored
      * function readMeteoData is there to read an interval of data
      	readMeteoData(fromDate, toDate, vector< vector<MeteoData> >, vector< vector<MeteoData> >)
      * BufferedIOHandler is constructed with another child of IOInterface (e.g. IOHandler) as parameter and deals with all intrinsic issues of buffering, resampling, filtering: so if you have an IOHandler and you want to add buffering:
      	BufferedIOHandler(iohandler, configreader)
      and then you can access all IOInterface functions, plus a few convenient ones that only BufferedIOHandler exposes:
      	getNextMeteoData(date, vector<MeteoData>, vector<StationData>)
      	readMeteoData(date, vector<MeteoData>, vector<StationData>)
      you can enable and disable buffering:
      	bufferediohandler.enableResampling(true);
      
      * A3DIO and IOHandler had to be adapted to the changes in IOInterface 
      * added a getYear() function to Date_IO
      * MeteoData has a new member variable "resampled" to indicate whether data has been resampled or not
      e569ad90
  35. 23 Jul, 2009 2 commits
    • Mathias Bavay's avatar
      Ok, this is the correct implementation of what I tried to do in the previous... · d7efb8a5
      Mathias Bavay authored
      Ok, this is the correct implementation of what I tried to do in the previous commit... Now, the Meteo2DInterpolator can take either Array2D<double> or Grid2DObjects as tables to fill. The overloading of the Write2DGrid has therefore been suppressed: since Grid2DObjects are geography-friendly, they should be used in our applications instead of Array2D (that should be reserved for internal implementation of objects).
      
      So, this is mostly reverting to the code before the last commit, with a few extra lines of code to do the magic...
      d7efb8a5
    • Mathias Bavay's avatar
      In order to make using the spatial interpolations easier to use, there is a... · 7444d587
      Mathias Bavay authored
      In order to make using the spatial interpolations easier to use, there is a need to be able to write to files objects of type Array2D. This has been added to IOInterface and implemented in the different plugins.
      
      meteoio_demo has been modified accordingly and is now much simpler.
      
      More fundamentally, we need to think about the way to handle in a nice and elegant way the different type accross the plugins (typically as seen for Write2DGrid): where should we handle what in order to let the user seemlessly write objects to the available mediums?
      7444d587
  36. 28 May, 2009 1 commit