Add functions to compute, plot, store the local hazard exceedence intensity and RP maps

[simonameiler]

Changes proposed in this PR:

• addition of new functions to store the hazard maps that are generated in the Hazard.plot_rp_intensity() function as netCDF write_netcdf_local_exceedance_inten or raster files write_raster_local_exceedance_inten.
• addition of new functions to compute local return period maps local_return_period and _loc_return_period for given hazard intensities, incl. plotting function plot_local_rp.
• addition of new functions to store these local return period maps for given hazard intensities as NetCDF write_netcdf_local_return_periods or raster files write_raster_local_return_periods.

This PR fixes #854

PR Author Checklist

• Read the Contribution Guide
• Correct target branch selected (if unsure, select develop)
• Descriptive pull request title added
• Source branch up-to-date with target branch
• Documentation updated
• Tests updated
• Tests passing
• No new linter issues
• Changelog updated

PR Reviewer Checklist

• Read the Contribution Guide
• CLIMADA Reviewer Checklist passed
• Tests passing
• No new linter issues

[chahank]

This is a confusing method signature to me. Why would a method of the class Hazard require the user to supply hazard intensities? These are already an attribute of the object.

[ValentinGebhart]

Here the variable hazard_intensities does not refer to the intensities of the Hazard object but to the threshold intensities for which the return period per grid point should be calculated. To avoid confusion we could rename this to "threshold_intensities"?

[emanuel-schmid]

👍 threshold_intensities would be much better. 😄

[chahank]

Be careful, this might lead to very large memory usage. Hazard intensities are on purpose sparse matrices.

[ValentinGebhart]

See comment above, hazard_intensities usually only includes a few values.

[emanuel-schmid]

@simonameiler looks like the branch is not yet up to date with the develop branch and, e.g., changes from have been reversed.
I'd suggest to merge from develop the sooner the better. Merging conflicts usually get worse the longer the merging is postponed. 😟

[simonameiler]

@simonameiler looks like the branch is not yet up to date with the develop branch and, e.g., changes from have been reversed. I'd suggest to merge from develop the sooner the better. Merging conflicts usually get worse the longer the merging is postponed. 😟

Thank you for the hint. I handed the pull request off to @ValentinGebhart

[ValentinGebhart]

I don't know how to resolve the issue that, even after merging develop back into this branch, many of the changes made to develop are not transferred here. One solution would be to create a new branch from develop (say "feature/write_haz_rp_maps2") and add the new functions again there. Do you think that this is fine or do you see a better solution? @emanuel-schmid @chahank

[chahank]

@ValentinGebhart : keeping it simple is good to me, so just making a new branch is fine for me. Just then delete the old one.

[ValentinGebhart]

PR completed in a different branch (PR #898). I saved a local copy of the functions here, if needed please contact me.