You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE_NOTES.rst
+29-29Lines changed: 29 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Upcoming Release
20
20
Version 0.2.10
21
21
==============
22
22
23
-
* atlite now supports shapely >= v2.0.
23
+
* atlite now supports shapely >= v2.0.
24
24
* Bugfix: For certain time spans, the ERA5 influx data would be incorrectly shifted by 12 hours.
25
25
This is now fixed and influx data is **always** shifted by minus 30 minutes.
26
26
See `#256 <https://github.com/PyPSA/atlite/issues/256#issuecomment-1271446531>`_ for details.
@@ -52,13 +52,13 @@ Version 0.2.8
52
52
The returned object `masked` (numpy.array) is now dtype `bool` instead of `float64`. This can create broken workflows, if `masked` is not transformed ahead of certain operations (https://github.com/PyPSA/atlite/pull/243).
53
53
* Bugfix: Avoid NaN values into the hydro inflows
54
54
55
-
Version 0.2.7
55
+
Version 0.2.7
56
56
==============
57
57
58
-
* The function `SolarPosition` does not return the atmospheric insolation anymore. This data variable was not used by any of the currently supported modules.
58
+
* The function `SolarPosition` does not return the atmospheric insolation anymore. This data variable was not used by any of the currently supported modules.
59
59
60
60
61
-
Version 0.2.6
61
+
Version 0.2.6
62
62
==============
63
63
64
64
* Atlite now supports calculating dynamic line ratings based on the IEEE-738 standard (https://github.com/PyPSA/atlite/pull/189).
@@ -68,65 +68,65 @@ Version 0.2.6
68
68
* The solar position (azimuth and altitude) are now part of the cutout feature `influx`. Cutouts created with earlier versions will become incompatible with the next major.
69
69
* Automated upload of code coverage reports via Codecov.
70
70
* DataArrays returned by `.pv(...)` and `.wind(...)` now have a clearer name and 'units' attribute.
71
-
* If the `matrix` argument in conversion functions (`.pv(...)`, `.wind(...)` etc.) is a `DataArray`, the alignment of the coordinate axis with the cutout grid is double-checked.
72
-
* Due to ambiguity, conversion functions (`.pv(...)`, `.wind(...)` etc.) now raise an `ValueError` if shapes and matrix are given.
71
+
* If the `matrix` argument in conversion functions (`.pv(...)`, `.wind(...)` etc.) is a `DataArray`, the alignment of the coordinate axis with the cutout grid is double-checked.
72
+
* Due to ambiguity, conversion functions (`.pv(...)`, `.wind(...)` etc.) now raise an `ValueError` if shapes and matrix are given.
73
73
* Atlite now supports calculating of heat pump coefficients of performance (https://github.com/PyPSA/atlite/pull/145).
74
74
* Enabled the GitHub feature "Cite this repository" to generate a BibTeX file (Added a `CITATION.cff` file to the repository).
75
75
76
76
**Bug fixes**
77
77
* The solar position for ERA5 cutouts is now calculated for half a time step earlier (time-shift by `cutout.dt/2`) to account for the aggregated nature of
78
78
ERA5 variables (see https://github.com/PyPSA/atlite/issues/158). The fix is only applied to newly created cutouts. Previously created cutouts do not profit
79
79
from this fix and need to be recreated `cutout.prepare(overwrite=True)`.
80
-
* The functions `make_latitude` and `make_latitude_optimal` were not converting degrees to radian correctly. This resulted in a wrong calculation of the power output when using the orientation `latitude_optimal` or `latitude` in the `pv` conversion function. We are sorry for inconveniences.
80
+
* The functions `make_latitude` and `make_latitude_optimal` were not converting degrees to radian correctly. This resulted in a wrong calculation of the power output when using the orientation `latitude_optimal` or `latitude` in the `pv` conversion function. We are sorry for inconveniences.
81
81
82
82
83
-
Version 0.2.5
83
+
Version 0.2.5
84
84
==============
85
85
86
86
* Clarification for ``ExclusionContainer.add_raster(..)`` that ``codes=..`` does not accept ``lambda``-functions in combination with ``multiprocessing``.
87
87
* Internal change: We are moving to `black` for internal code formatting.
88
88
* Fix ignored keywords in convert_and_aggregate(...) for capacity_layout=True.
89
89
90
-
Version 0.2.4
90
+
Version 0.2.4
91
91
==============
92
92
93
93
* Fix cutout merge and update for xarray ``>=v0.18.0`` (https://github.com/PyPSA/atlite/issues/147)
94
-
* Set multiprocessing context to ``spawn`` for ensuring equal computation across all platforms.
94
+
* Set multiprocessing context to ``spawn`` for ensuring equal computation across all platforms.
95
95
96
-
Version 0.2.3
96
+
Version 0.2.3
97
97
==============
98
98
99
99
* The progressbar used in ``atlite.gis.availability_matrix`` is now a `tqdm` progressbar which displays better in parallel executions.
100
-
* The function ``layout_from_capacity_list`` was added to the cutout class. It is a convenience function that calculates the aggregated capacities per cutout grid cells (layout) based on a list of capacities with coordinates, e.g. list of wind turbines.
100
+
* The function ``layout_from_capacity_list`` was added to the cutout class. It is a convenience function that calculates the aggregated capacities per cutout grid cells (layout) based on a list of capacities with coordinates, e.g. list of wind turbines.
101
101
* The dask version was fixed to a xarray-compatible versions (see https://github.com/dask/dask/issues/7583)
102
102
103
-
Version 0.2.2
103
+
Version 0.2.2
104
104
==============
105
105
106
-
This update is mainly due to fixes in the data handling of the SARAH module. If you work with the SARAH data, we encourage you to update.
106
+
This update is mainly due to fixes in the data handling of the SARAH module. If you work with the SARAH data, we encourage you to update.
107
107
108
108
* Fixed compatibility with xarray v0.17.
109
-
* Fixed sarah data for ``dx = dy = 0.05``. Due to the float32 dtype of the sarah coordinates, the cutout coordinates were corrupted when merging. This was fixed in the sarah module by converting the coordinates to float64. This also speeds up the cutout creation for more coarse grained cutouts.
109
+
* Fixed sarah data for ``dx = dy = 0.05``. Due to the float32 dtype of the sarah coordinates, the cutout coordinates were corrupted when merging. This was fixed in the sarah module by converting the coordinates to float64. This also speeds up the cutout creation for more coarse grained cutouts.
110
110
* Fixed sarah data for a time frequency of 30 minutes. This was raising an assertion error as the (new) pandas frequency string for 30 minutes is '30T' not '30min'.
111
111
* Fix the ``regrid`` function in ``atlite.gis`` for target coords which are not having the same bounds as the original ``xarray.Dataset``. The previous implementation was leading to a small shift of coordinates in the preparation of SARAH data.
112
112
113
113
114
114
115
115
Version 0.2.1
116
116
==============
117
-
* The `regrid` function in `atlite.gis` was fixed. The previous implementation set an affine transform starting at the center of a cell at the origin. The corrected transform starts at the real origin (origin of the origin cell). Further a padding of the extent ensures that all values are taken into account in the target projection.
118
-
* Exclusion Calculation is now possible with `atlite` (find an usage example at Examples -> Calculate Landuse Availability), Therefore
117
+
* The `regrid` function in `atlite.gis` was fixed. The previous implementation set an affine transform starting at the center of a cell at the origin. The corrected transform starts at the real origin (origin of the origin cell). Further a padding of the extent ensures that all values are taken into account in the target projection.
118
+
* Exclusion Calculation is now possible with `atlite` (find an usage example at Examples -> Calculate Landuse Availability), Therefore
119
119
120
-
- a new class `atlite.gis.ExclusionContainer` was added. It serves as a container of rasters and geometries which should be excluded from the landuse availability.
121
-
- `Cutout` has a new `availabilitymatrix` function which calculates the overlap of weather cells with shapes while excluding areas based on an `ExclusionContainer`.
122
-
- `Cutout` has now a affine transform property (`rasterio.Affine`).
120
+
- a new class `atlite.gis.ExclusionContainer` was added. It serves as a container of rasters and geometries which should be excluded from the landuse availability.
121
+
- `Cutout` has a new `availabilitymatrix` function which calculates the overlap of weather cells with shapes while excluding areas based on an `ExclusionContainer`.
122
+
- `Cutout` has now a affine transform property (`rasterio.Affine`).
123
123
* Fix resolution for dx and dy unequal to 0.25: Due to floating point precision errors, loading data with ERA5 corrupted the cutout coordinates. This was fixed by converting the dtype of era5 coordinates to float64 and rounding. Corresponding tests were added.
124
-
* Round cutout.dx and cutout.dy in order to prevent precision errors.
125
-
* Allow passing keyword arguments to `dask.compute` in `convert_and_aggregate` functions.
124
+
* Round cutout.dx and cutout.dy in order to prevent precision errors.
125
+
* Allow passing keyword arguments to `dask.compute` in `convert_and_aggregate` functions.
126
126
* The Cutout class has a new property `bounds` (same as extent but in different order).
127
127
128
128
**Breaking Change**
129
-
* `Cutout.extent` was adjusted to cover the whole cutout area. The extent is now a numpy array. Before, it indicated the coordinates of the centers of the corner cells.
129
+
* `Cutout.extent` was adjusted to cover the whole cutout area. The extent is now a numpy array. Before, it indicated the coordinates of the centers of the corner cells.
130
130
131
131
Version 0.2
132
132
===============
@@ -140,20 +140,20 @@ Version 0.2
140
140
appropriate functions or (what we recommended) recreated.
141
141
* The backend change also includes some changes to the API.
142
142
Most notably:
143
-
143
+
144
144
- The `xarray` for cutouts is now exposed as `Cutout.data`
145
145
- The `Cutout.meta` attribute was deprecated in favour of
146
146
`Cutout.data.attrs`
147
147
- `xarray` and `dask` can now handle some data caching
148
148
automatically.
149
149
If you wish to preload some data before your calculation,
150
150
you can now use `Cutout.data.load()` to load all of the
151
-
cutouts data into memory.
151
+
cutouts data into memory.
152
152
*(Warning: Requires a large enough memory.)*
153
-
- The `Cutout` class has a new property `grid`, a GeoPandas DataFrame
153
+
- The `Cutout` class has a new property `grid`, a GeoPandas DataFrame
154
154
which combines and deprecates `grid_cells()` and `grid_coordinates()`
155
155
* The order of coordinates (indices) for `Cutouts` changed: `x` and `y` (e.g. longitude and latitude) are now both ascending (before: `x` ascending and `y` descending).
156
-
* Following the lead of geopandas, pyproj, cartopy and rasterio, atlite now uses Coordinate Reference System (`CRS`) instead of the old fashioned projection strings.
156
+
* Following the lead of geopandas, pyproj, cartopy and rasterio, atlite now uses Coordinate Reference System (`CRS`) instead of the old fashioned projection strings.
157
157
158
158
**New features**
159
159
@@ -170,7 +170,7 @@ Version 0.2
170
170
171
171
**Breaking changes**
172
172
173
-
* The argument `show_progress` of function `atlite.convert.convert_and_aggregate` does not take strings anymore.
173
+
* The argument `show_progress` of function `atlite.convert.convert_and_aggregate` does not take strings anymore.
174
174
* The argument `layout` of function `atlite.convert.convert_and_aggregate` must be a `xarray.DataArray`.
175
175
* Due to the change of the order of coordinates in cutouts the order of coordinates in `matrix` passed to `convert_*` functions
176
176
changed likewise: `x` and `y` are both ascending now.
@@ -183,7 +183,7 @@ Version 0.0.4
183
183
184
184
* support negative latitudes to PV panel orientation
0 commit comments