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
* Add function to test if lat and lon are in geographic coords
* Add test for geographic coords in dist_to_coast
* Add test for geographic coords in coord_on_land
* Switch branch feature/remove_implicite_use_crs to black format
* Extend allowed extent for geo coords
* Modify allowed extents in geo_coords check function to allow for bounds
* Include possible wrong lat lon extension in error message
* Add check for geo coords in get_country_code
* Add test for geocoords in convert_wgs_to_utm
* Update error message in coord_on_land
* Harmonize error messages
* Adapt test get_country_geometries_fail
* Check for geo coords in match_coordinates
* Add check for lat in get_gridcellarea
* Modify check geo coords function to please linter
* Add test for geo coords in calc of coriolis param
* Add tests for check_if_geo_coords function
* Incorporate suggestions from review 1
* Start adapating match_coordinates function to other crs
* Add handling of unit in match_centroids
* Rename deg to degrees
* Add function to infer unit of coordinates
* Use infer_unit_coords in match_centroids function
* Add tests for unit_infer and unit-adapted match_coordinates
* Make test_tack_land_params compliant with new requirement of geodetic coords
* Correct wrong is_geodetic crs attribute
* Add restriction for haversine with non-degree units
* Finish adding test for handling of different units
* Add test invalid unit for match coords and docstrings
* Update docstrings
* Try to fix new linter issues
* Correct error in logger warning
* Force check_antimeridian to False in distance euclidean if unit is not degree
* Remove outdated test for raise of ValueError when check_antimeridian is attempted in non-degree units
* Add function to get coordinates from axis of coordinates'crs
* Update unit names to be consistent with epsg notation and remove unit kw from match_centroids
* Clarify docstring check_if_geo_coords
* Make conversion between radians and degrees more consistent
* Remove deprecated infer_unit_coords function
* Update tests
* Force input coords and centroids to have crs attribute in match_centroids
* Re-harmonize unit names and raise error when crs of centroids or coords is None
* Add missing tests
* Fix linter issues
* Refix linter
* Wrap valuerror raising in check_if_geo_coords
* Update tests
* Remove useless info in get_crs_unit docstring
* Raise separate exceptions for missing crs in coord_gdf and centroids
Co-authored-by: Chahan M. Kropf <[email protected]>
* Fix error in _nearest_neighbor_approx docstring
* Make clearer error message for _nearest_neighbor with non-allowed units
* Simplify crs check in match_centroids
* Correct typo and update tests for new error messages in match_centroids
* Only warn for check_antimeridian when it is true and add tests
* Allow for units other than degree km and m by keeping distance threshold in the given unit
* Update thresholds in test to be consisten with handling of thresholds in non-degree units
* Remove mention to calling functions in error message in _nearest_neighbor_haversine
Co-authored-by: Chahan M. Kropf <[email protected]>
* Remove mention to calling functions in error message in _nearest_neighbor_approx
Co-authored-by: Chahan M. Kropf <[email protected]>
* Update docstrings match_centroids
* update docstrings for match_coordinates
* Update changelog
* Update docstring to removed grid centroids + black
* Add error to docstring and return value
* Replace default threshold by dynamic one and apply black
* Update tests to use dynamic threshold
* Simplify non degree crs handling
* Use crs instead of unit
* Update test to use crs as input
* Require explicit threshold for single centroid coordinates
* Add docstrings for km to degree and inverse
* Add docstrings for estimate threshold
* Update impact tests
* Add test for projected crs
* Add docstring in impact calc
* Update impact calc test to use correct distance threshold
* Add impact calc test with other crs
* Improve docstrings
* Separate check geo coordinates into two methods
* Improve docstrings
* Correct docstrings
* Add new coordinates methods to changelog
* Improve wording
* Fix resolution to be only positive
* Add coordinate checks for bounds
* Add test test resolution
* Add test assign other crs
* Update changelog
* Revert bounds and normalize degree check as test were broadly failing.
* Check that lon normalize values are actually proper longitudes
* Revert "Check that lon normalize values are actually proper longitudes"
This reverts commit 86bb4f5.
* Raise error if no res above min_threshold can be found in get_resolution_1d
* Add test exception exp.assign_centroids when crs not equal
* Add test get_unit_crs for undefined unit
* Add test unknown unit get_gridcell_area
* Add test estimate_matching_threshold
* check geocoords in lon_normalize and handle empty arrays in check geocoords
* Update tests lon_normalize
* Increase allowed lon extent in is_geo_coords to avoid failing tests with ibtracks
* Update offensive value for test_get_country_geometries_fail
* Add handling of nans in is_geo_coords
* Update changelog
* Update climada/engine/impact_calc.py
* Clarify meaning of highest resolution in docstrings
Co-authored-by: Chahan M. Kropf <[email protected]>
* Clarify meaning of highest resolution in docstrings
Co-authored-by: Chahan M. Kropf <[email protected]>
* Correct typo in docstring
Co-authored-by: Luca Severino <[email protected]>
* Fix typo in docstring
Co-authored-by: Luca Severino <[email protected]>
* Resolve linter issue
---------
Co-authored-by: luseverin <[email protected]>
Co-authored-by: luseverin <[email protected]>
Co-authored-by: Chahan Kropf <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,13 +28,17 @@ Removed:
28
28
- Added optional parameter to `geo_im_from_array`, `plot_from_gdf`, `plot_rp_imp`, `plot_rp_intensity`,
29
29
`plot_intensity`, `plot_fraction`, `_event_plot` to mask plotting when regions are too far from data points [#1047](https://github.com/CLIMADA-project/climada_python/pull/1047). To recreate previous plots (no masking), the parameter can be set to None.
30
30
- Added instructions to install Climada petals on Euler cluster in `doc.guide.Guide_Euler.ipynb`[#1029](https://github.com/CLIMADA-project/climada_python/pull/1029)
31
-
31
+
- Added util methods to handle crs coordinates consistently: `is_geo_coords`, `check_if_geo_coords`, `get_crs_unit`, `estimate_matching_threshold`, `degree_to_km`, and `km_to_degree`[#1080](https://github.com/CLIMADA-project/climada_python/pull/1080)
32
32
-`ImpactFunc` and `ImpactFuncSet` now support equality comparisons via `==`[#1027](https://github.com/CLIMADA-project/climada_python/pull/1027)
33
33
34
34
### Changed
35
-
35
+
- Changed default distance threshold for nearest neighbor matching in `util.coordinates.match_coordinates` from a fixed value of 100km to twice the highest resolution of the coords_to_assign [#1080](https://github.com/CLIMADA-project/climada_python/pull/1080).
36
36
- Changed the default mask_distance in `util.plot.geo_im_from_array` to 0.03 to avoid white gaps in gridded hazard data with comparably low resolution (>80 centroids per axis) [#1073](https://github.com/CLIMADA-project/climada_python/pull/1073)
37
37
- Increased speed of `util.plot.add_shapes` by avoiding for loops, substantially speeding up `Hazard.plot_intensity` and other functions. [#1073](https://github.com/CLIMADA-project/climada_python/pull/1073)
38
+
- Update `util.coordinates.match_centroids`, `util.coordinates.match_coordinates`, so that they also
39
+
accept coordinates that are not defined in degree. [#1080](https://github.com/CLIMADA-project/climada_python/pull/1080)
40
+
- Implement cheap test to check that input coordinates at least seem geographic for functions that require
41
+
geographic coordinates as input (e.g. `util.coordinates.dist_to_coast`, `util.coordinates.coord_on_land`, `util.coordinates.lon_normalize`, `util.coordinates.lon_bounds`). [#1080](https://github.com/CLIMADA-project/climada_python/pull/1080)
38
42
-`Hazard.local_exceedance_intensity`, `Hazard.local_return_period` and `Impact.local_exceedance_impact`, `Impact.local_return_period`, using the `climada.util.interpolation` module: New default (no binning), binning on decimals, and faster implementation [#1012](https://github.com/CLIMADA-project/climada_python/pull/1012)
39
43
- World Bank indicator data is now downloaded directly from their API via the function `download_world_bank_indicator`, instead of relying on the `pandas-datareader` package [#1033](https://github.com/CLIMADA-project/climada_python/pull/1033)
40
44
-`Exposures.write_hdf5` pickles geometry data in WKB format, which is faster and more sustainable. [#1051](https://github.com/CLIMADA-project/climada_python/pull/1051)
0 commit comments