Release Notes

Upcoming Release

Version 0.2.3

  • The progressbar used in atlite.gis.availability_matrix is now a tqdm progressbar which displays better in parallel executions.

  • 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.

  • The dask version was fixed to a xarray-compatible versions (see

Version 0.2.2

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.

  • Fixed compatibility with xarray v0.17.

  • 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.

  • 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’.

  • 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.

Version 0.2.1

  • 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.

  • Exclusion Calculation is now possible with atlite (find an usage example at Examples -> Calculate Landuse Availability), Therefore

    • 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.

    • Cutout has a new availabilitymatrix function which calculates the overlap of weather cells with shapes while excluding areas based on an ExclusionContainer.

    • Cutout has now a affine transform property (rasterio.Affine).

  • 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.

  • Round cutout.dx and cutout.dy in order to prevent precision errors.

  • Allow passing keyword arguments to dask.compute in convert_and_aggregate functions.

  • The Cutout class has a new property bounds (same as extent but in different order).

Breaking Change * 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.

Version 0.2

Major changes

  • Atlite now requires Python 3.6 or higher.

  • We changed the Atlite backend for storing cutout data. Existing cutouts either need to be migrated with the appropriate functions or (what we recommended) recreated.

  • The backend change also includes some changes to the API. Most notably:

    • The xarray for cutouts is now exposed as

    • The Cutout.meta attribute was deprecated in favour of

    • xarray and dask can now handle some data caching automatically. If you wish to preload some data before your calculation, you can now use to load all of the cutouts data into memory. (Warning: Requires a large enough memory.)

    • The Cutout class has a new property grid, a GeoPandas DataFrame which combines and deprecates grid_cells() and grid_coordinates()

  • 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).

  • Following the lead of geopandas, pyproj, cartopy and rasterio, atlite now uses Coordinate Reference System (CRS) instead of the old fashioned projection strings.

New features

  • You can now use wind turbine configurations as stored in the Open Energy Database using the string prefix “oedb:” when specifying a turbine, e.g. “oedb:Enercon_E-141/4200”.

  • Atlite now has and uses a new configuration system. See the new section on configuration for details.

  • It is possible to merge two cutouts together, using Cutout.merge

Breaking changes

  • The argument show_progress of function atlite.convert.convert_and_aggregate does not take strings anymore.

  • The argument layout of function atlite.convert.convert_and_aggregate must be a xarray.DataArray.

  • Due to the change of the order of coordinates in cutouts the order of coordinates in matrix passed to convert_* functions

    changed likewise: x and y are both ascending now.

  • Due to the change of the order of coordinates in cutouts the order of elements returned by grid_coordinates() has changed.

  • Due to the change of the order of coordinates in cutouts the order of elements in the attribute grid_cells has changed.

Version 0.0.4

  • support negative latitudes to PV panel orientation

  • add support for ERA5 back extension to 1950

  • add PROJ>=7 valid ‘aea’ projection string

Version 0.0.3

Brings a minor bug fix and prepares for the next version jump to version 0.2.

  • Fix heat demand hourshift for xarray 0.15.1

  • Add Travis CI and simplified release management