Skip to content

What is mangrove, mangrove_1km, mangrove_offshore? #33

Description

@jules32

For global assessments, we use mangrove data from global raster data, and process it in a several different ways to use for three goal models: CS, CP, HAB (read more about data processing for extent, health, and trend here).

If you look at one of these layers, e.g. hab_mangrove_extent, you will notice three different habitat types:

  • mangrove_inland1km
  • mangrove_offshore
  • mangrove

What does this mean?

These distinctions stem from two things: the goal model philosophies and the quality of the available data.

Data-quality-wise:

  • mangrove_inland1km is calculated by clipping the global raster file 1-km inland (land-wards) from the high-tide line for each region.
  • mangrove_offshore is calculated by clipping the global raster file from the high-tide line (ocean-wards) to the EEZ boundary.
  • mangrove is calculated from all mangroves within the EEZ. This includes inland1km, offshore, and any other mangroves that were somehow not included in the previous categories.

Philosophically,

  • Coastal Protection should only include mangroves that can protect the coastline. So this means only the layers including data from land: "mangrove_inland1km" and "mangrove_offshore".
  • Carbon Storage and Habitats can include mangroves from anywhere in the EEZ, since it doesn't need to be limited to the shoreline to be relevant: "mangrove"

For OHI+ assessments, it might not be necessary or possible to distinguish inland1km from offshore – and that is OK. Depending on how data are collected and reported, you may use the same data for all three goal models, and tailor the goal models accordingly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions