-
Notifications
You must be signed in to change notification settings - Fork 142
Upcoming Releases
Chahan Kropf edited this page Dec 15, 2021
·
113 revisions
updated features:
- new function
get_admin1_geometries
: return GeoDataFrame with geometries of admin 1 regions within given countries. - 'set_' method deprecated. New methods 'from_'.
- '+init CRS specs' deprecated.
- Update uncertainty quantification module - nicer plots, addition of helper methods.
- Rename uncertainty quantification module to ...
due date: 2021-10-01
description: This is the first release of the core package after CLIMADA sources have been devided into climada_python (core) and climada_petals (extensions).
changed environment:
- cartopy 0.20 and higher are not accepted yet, because of their changes in the CRS objects.
- rasterio 1.2.7 an higher are not accepted yet, also because of their changes in the CRS objects.
updated features:
- uncertainty_quantification: a complete rewriting of the module and its API. Now it can do uncertainty and sensitivity analysis for impact and cost benefit. All the data is stored in a data class with pandas dataframes attributes. Several plotting methods have been added. Saving and loading from hdf5 files has been added.
- impacts_funcs: added two easily modifiable generic impact functions (a step and a sigmoid function) which can be used for a broad range of hazards and resolutions.
-
api_client: added convenience methods for creating CLIMADA objects from files accessible through the api,
get_hazard
,get_exposures
andget_litpop
,
and for collecting dataset information into data frames:into_datasets_df
,into_files_df
.
minor changes:
- litpop: fix of faulty shape handling for admin1 shapes with a hole (e.g. Brandenburg)
-
litpop: remove parameter
reproject_first
(and functionality forreproject_first=False
in_get_litpop_single_polygon
) - litpop: minor improvements in readability and code efficiency, incl. better documentation
-
config: the
setup_logging
function was removed from the module, to change the logging level programmaticallyconfig.LOGGER.setLevel
can be used.