WSL/SLF GitLab Repository
Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
meteoio
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
snow-models
meteoio
Repository graph
Repository graph
You can move around the graph by using the arrow keys.
1f2f367175d2fbb356e8a2ffb31dc6543f007f87
Select Git revision
Selected
1f2f367175d2fbb356e8a2ffb31dc6543f007f87
Branches
4
master
default
protected
BUFR_changes
feature/web-service
limiting_trends
Tags
20
test
MeteoIO-2.11.0
webservice-2022
MeteoIO-2.10.0
MeteoIO-2.9.0
MeteoIO-2.8.0
MeteoIO-2.7.0
MeteoIO-2.6.1
MeteoIO-2.6.0
MeteoIO-2.5.1
MeteoIO-2.5.0
MeteoIO-2.4.2
MeteoIO-2.4.1
MeteoIO-2.4.0
MeteoIO-2.3.0
MeteoIO-2.2.0
MeteoIO-2.1.2
MeteoIO-2.1.1
MeteoIO-2.1.0
MeteoIO-2.0.0
25 results
Select display option
Display full history
Display full history
Display up to revision
Created with Raphaël 2.2.0
23
May
22
16
15
14
10
3
30
Apr
28
26
25
24
18
11
6
3
30
Mar
29
27
23
21
19
17
16
12
6
5
22
Feb
20
7
5
2
1
29
Jan
26
25
24
23
22
19
18
12
11
10
5
20
Dec
15
14
13
12
11
7
6
4
30
Nov
28
16
15
8
4
3
26
Oct
25
24
12
5
27
Sep
20
15
5
4
1
29
Aug
28
23
22
2
31
Jul
28
27
24
21
20
19
18
17
14
12
11
10
7
6
5
4
3
30
Jun
29
28
27
23
21
20
19
16
15
14
13
12
9
8
7
6
31
May
24
19
18
16
12
25
Apr
21
20
19
11
10
7
6
4
3
31
Mar
30
29
28
27
23
22
20
17
16
15
14
13
10
9
8
7
6
24
Feb
23
22
21
16
13
8
6
2
1
31
Jan
30
26
25
24
23
13
12
11
9
23
Dec
21
16
13
8
5
30
Nov
25
24
17
14
10
9
8
4
3
31
Oct
28
25
24
21
20
7
5
4
3
30
Sep
29
28
27
26
23
22
21
16
15
14
13
12
8
7
5
2
31
Aug
26
25
24
23
22
19
18
17
15
10
9
8
3
2
28
Jul
22
21
12
27
Jun
23
21
17
10
9
7
3
2
27
May
25
23
19
17
14
13
11
5
4
26
Apr
18
15
14
8
7
5
1
31
Mar
24
22
21
18
15
9
8
7
4
3
2
1
29
Feb
26
24
23
20
10
9
8
5
3
29
Jan
28
27
26
25
22
20
14
13
12
11
8
6
22
Dec
21
18
9
7
4
3
30
Nov
27
26
25
24
20
19
18
17
16
11
5
4
31
Oct
28
23
22
15
12
8
6
1
30
Sep
29
28
25
23
22
10
9
8
7
2
1
31
Aug
28
27
11
10
7
3
30
Jul
28
27
23
21
20
17
16
13
9
8
7
2
1
30
Jun
24
17
16
15
12
10
9
29
May
27
21
6
26
Apr
14
10
9
8
2
1
31
Mar
30
26
25
24
25
Feb
17
13
11
10
8
6
3
30
Jan
23
20
22
Dec
19
18
17
12
8
4
2
27
Nov
25
24
20
18
13
12
11
10
7
The support for one output file per station seems to work but is not (yet) exposed to the user. The Amundsen schema has been partially implemented and the CNRM schema renamed as Crocus.
Improved support for data type as part of the schema
Moving toward supporting different data types as part of the schema definition
More cleanup in NetCDFIO...
More code cleanup (ie moving more methods to libncpp)
Starting the work of more consistent DEM handling (for special cases, such as gridded data resampling).
The dem computation out of p, p_sea has been put back, but in GridsManager. There still needs some work to have a consistent DEM handling, though...
The DEM handling has to be improved. First, the whole "DEM_FROM_PRESSURE" is not active anymore in NetCDF and should be moved to the GridsManager
Oops, a debug cout should have been removed...
More code has been moved from NetCDFIO to libncpp
oops, the header file was wrong...
Preparing to deprecate CNRMIO and its associated libncpp: the "old" libncpp has been renamed as libncpp_old while the parts that are still required by NetCDFIO are now in the "new" libncpp (which is much smaller).
Lots of robustness improvements, better handling of "corner cases", specially when writing grids or timeseries of parameters not in the specified schema. More checks (invalid file name, non-existing file, etc)
Code cleanup, making the grids support more similar to timeseries support (so a few methods could be removed)
It was not possible to read gridded data in NetCDF anymore, this has been fixed
Now the station_ids are written into the netcdf. This was a nightmare, the handling of arrays of strings in netcdf<4 is a big hack: they must be provided as a 2d array of chars in Column-major order (of course, c/c++ is the other way around) in order to use nc_put_var_text(). So finally, we are using nc_put_vara_text() to write the strings one by one... Moreover, the string length MUST be defined as an extra dimension (since it is not a 1d array of strings but a 2d array of chars) and the vector of station_ids is represented as a 2d variable... It's just plain ugly
The NetCDF timeseries implementation is moving (slowly) toward a sane shape... The code is now much cleaner, some of these changes should also be used by the grids.
Finally, this is a first version that is able to write time series into a NetCDF. There is still a lot of clean up to do...
Fixing autoscale issue, see niviz issue 660
Some code cleanup and moving forward toward writing timeseries of meteodata...
Expanding the CF1 schema (and being horrified at the mess that NetCDf is: for CF1, the matching should be done on the standard_name while for ECMWF, it should be on the name...)
There was a bug when appending data to an "unknown" variable (ie variable that is not part of the schema)
Support for easting/northing grids has been added to NetCDF
some issues with the priorities of the sources of naming (ie user, schema or "try harder") have been fixed. Some unnecessary code has been removed, there is now an attempt to compute the integration period when reading integrated radiation data and the old documentation has been ported. Except for WRF, it seems to be working fine.
More checks, as well as a system to try to rescue some variables/dimensions out of the "unknown" map for added convenience
Writing 2d grids now seems to work in NetCDF and some elements of the WRF schema have been corrected. On the other hand, it is not yet possible to read/write in the WRF schema! Now some intensive testing has to take place...
The NetCDF plugin is slowly taking shape... It is now quite generic and should be soon usable!
The GridsManager now defaults to BUFFER_SIZE for the duration that defines the buffering of the list of 2d grids (since both would most probably be used together) with a default value of 370 days.
Moving closer to the data model underlying NetCDF... Some redundant structures and code have been removed, the code should get more generic.
First version that can write (some) grids... Again, don't use it for now!
This is an intermediate step into a major rewrite of the handling of NetCDF files. Please do not rely on this plugin yet, it can not write gridded data yet...
Finally, the support for time zones abbreviations has been implemented. The limitation is that the timezone MUST appear at the end of the date/time string (since when reading a string, it reads until the end of it).
Big cleanup, unifying the handling of metadata field types, improved and better structured documentation
There was a mistake when requesting the list of ARC grids, the wrong filename pattern was used. The grid2d_reading example did not use the configured timezone, this has been fixed.
The ability to extract metadata out of the filename itself has been added to CSVIO. A bug in the handling of the file indexer has been fixed (only one was used, for all files!). An automerge feature has been implemented, so it is possible to automatically merge all stations that have the same ID. The whole thing has been documented (including updated examples).
It was not possible to provide a numerical-only datetime for the Csv plugin. This now works.
minor cleanup
Some basic support for timezone information within the date/datetime field has been implemented. Currently, only numeric values are supported (so you have to replace fields such as "ECT" by "+01").
Added support for the (non-standard) time zones abbrevations (like CET, etc)
In CSV, if the timestamps are in descending order, they will be transparently converted back to ascending order
Loading