mapme.biodiversity 0.4.0

New features

• added new resource called ucdp_ged providing a database of violent conflict
  from 1989 to today

• added a new indicator called fatalities aggregating number of deaths
  by type of conflict on a monthly time scale based on the ucdp_ged resource.

• Added a new resource called fritz_et_al providing a raster layer of deforestation

• added a new resource called fritz_et_al providing a raster layer of deforestation
  drivers in tropical forests based on Fritz et al. (2022)

• added a new indicator called deforestation_drivers using the fritz_et_al resource
  to obtain information on the absolute and relative area driving forest losses in
  assets for the period 2008-2019

• added two new exported functions register_resource() and register_indicator()
  which allow users to register custom functions for resources/indicators

• added a new vignette for the web-version of the package only informing
  about how to obtain wide-output from indicators

• added a new vignette for the web-version for a custom analysis of the NASA
  FIRMS resource in the example section

• added the data for years 2017-2020 to the Global Mangrove Watch resource

Breaking changes

• Changed the parallel backend to the future
  package. Parallel processing is now implemented by
  furrr::future_map()
  on the asset level within the calc_indicators() function. User code is now
  required to set up a plan()
  to enable parallel processing. The function call needs to be wrapped on the user
  side with progressr::with_progress()
  to show a progress bar.

• mapme.biodiversity no longer sets terra's temporal directory for you.
  Instead you have to call terra::terraOptions() manually

Bug Fixes

• esalandcover indicator now returns the value per each land cover class
  exactly once (#177)

Internal

• disabled running examples on CRAN

• disabled tests for get_* functions on CRAN

• terra engines now use get() to resolve the requested zonal
  statistic function

• applying tidyverse coding style to existing code (#156, @karpfen)

• extensive re-factoring of vector-raster zonal statistic engines (#150)

• extensive re-writing of testing infrastructure for indicator functions omitting
  the usage of snapshot tests as far as possible (#142)

• rundir and todisk arguments removed from indicator functions since they were
  of no practical use

• instead of a resource and indicator backlog, resources and indicators are now
  registered to .pkgenv and queried there during runtime. This also allows
  users to register custom resources/indicator functions

• removed deprecation warnings for old resource/indicator name

CRAN release v0.3.0

mapme.biodiversity 0.3.0

Breaking changes

• on MacOS s2-based calculations are now enabled so users can expect the package
  to return numerically equivalent results on any operating system (#131)

• the online source for the nasa_srtm resource shows an expired SSL certificate
  since November 2022. The get_resources()` function now includes an error and
  instructions how to disable SSL certification at a users own risk. The
  websites maintainers have been contacted and asked to renew the certification. (#131)

New features

• GFW resources are now updated to use the latest version allowing analysis for
  the additional year of 2021 (#123, @fBedecarrats)

• GFW indicators now accept numeric min_size argument allowing to specify
  fractional covers (#110)

• fire indicators now allow the simultaneous calculation of indicators based on
  MODIS and VIIRS. Before users had to chose between one of the instruments for
  each analysis (#126)

Bug fixes

• case when one or multiple assets return NA instead of a tibble is now properly
  tested and handled (#101)

• Rasters are no longer temporary written to disk to omit a bug caused by
  applying mask/classify to an already existing raster file (#108, @Jo-Schie)

• Bug with soilproperties set to NA caused by the function to return a data.frame
  instead of a tibble was fixed (#116)

• both, treecoverloss_emissions and treecover_area_and_emissions now return
  0 instead of NaN for observation years where now forest loss occurred (#120)

Internal

• .make_global_grid() now specifies the CRS when constructing the bounding box
  and returns the grid in the specified CRS instead of Lat/Lon (#113)

• .calc_active_fire_properties now uses st_coordinates to retrieve locations
  of fires (#119, @DavisVaughan)

• tests for MacOS have been re-enabled (#131)

• tests for downloading nasa_srtm resource are skipped because the SSL certificate
  of the online source has expired (#131)

CRAN release v0.2.1

Fixes serious bug for gridded resources when one or more polygons lie within the same tile

CRAN release v0.2.0

Breaking changes

• extensive renaming of resources and indicators. These are handled gracefully
  until the next release (i.e. a warning is issued and names are replaced):

• resources:

• treecover2000 -> gfw_treecover

• lossyear -> gfw_lossyear

• greenhouse -> gfw_emissions

• traveltime -> nelson_et_al

• nasagrace -> nasa_grace

• mintemperature -> worldclim_min_temperature

• maxtemperature -> worldclim_max_temperature

• precipitation -> worldclim_precipitation

• ecoregions -> teow

• mangrove -> gmw

• srtmdem -> nasa_srtm

• indicators:

• treecover -> treecover_area

• emissions -> treecoverloss_emissions

• treeloss -> treecover_area_and_emissions

• chirpsprec -> precipitation_chirps

• accessibility -> traveltime

• popcount -> population_count

• wctmin -> temperature_min_wc

• wctmax -> temperature_max_wc

• wcprec -> precipitation_wc

• gmw -> mangroves_area

• teow -> ecoregion

New features

• new resource(s):
  • nasa_firms
• new indicator(s):
  • active_fire_properties
  • active_fire_counts

Internal

• adapted download routine to GMW v3 (#80)
• removed data.table from imports

Bug fixes

• fixing issue #84 concerning intersection of tiled datasets (#86, @Jo-Schie)

CRAN release v0.1.2

Merge pull request #76 from mapme-initiative/75-fixing-cran-issues

cleaned urls and portfolio test

CRAN release v0.1.1

disabled some tests on cran

CRAN release v0.1.0

Merge pull request #22 from mapme-initiative/20-reconsider-using-dot-…

CRAN release v0.0.1

Merge pull request #61 from mapme-initiative/58-fix-cran-feedback

changes in readme for cran release