| Literature DB >> 32336879 |
Aija S Kukkala1,2, Atte Moilanen1.
Abstract
CONTEXT: Spatial conservation prioritization (SCP) concerns, for example, identification of spatial priorities for biodiversity conservation or for impact avoidance in economic development. Software useable for SCP include Marxan, C-Plan and Zonation. SCP is often based on data about the distributions of biodiversity features (e.g., species, habitats), costs, threats, and/or ecosystem services (ES). OBJECTIVES AND METHODS: At simplest ES can be entered into a SCP analysis as independent supply maps, but this is not very satisfactory because connectivity requirements and consequent ideal spatial priority patterns may vary between ES. Therefore, we examine different ES and their connectivity requirements at the conceptual level.Entities:
Keywords: Accessibility; Biodiversity; Complementarity; Green infrastructure; Optimization; Spatial interactions; Systematic conservation planning; Trade-offs; Zonation software
Year: 2016 PMID: 32336879 PMCID: PMC7154789 DOI: 10.1007/s10980-016-0446-y
Source DB: PubMed Journal: Landsc Ecol ISSN: 0921-2973 Impact factor: 3.848
Technical solutions for inclusion of ES and their connectivity requirements into spatial conservation prioritization (SCP)
| Connectivity characteristics and examples | Possible solutions for integration in SCP |
|---|---|
| Low connectivity requirements | |
| The ES can be provided locally in small areas. Can be transported over distances when needed. Example: Carbon, or other ES with weak/uncertain spatial effects | Simply enter grid into SCP as a feature. Allow it to become protected with spatial pattern most governed by requirements of other features. (pre-processing) |
| Provision connectivity: aggregation and local minimum area requirements | |
| Service is not provided by too small areas, because of e.g. edge effects, minimum population sizes, space needs of dynamic processes. Also logistical/administrative requirements may imply minimum area size. This is a common requirement; examples include recreation, ground water, and biodiversity conservation | Many solutions for inducing aggregated priorities: (i) Connectivity techniques such as distribution smoothing (pre-processing), corridor connectivity (prioritization), boundary quality penalty (prioritization), or boundary length penalty (prioritization), with a suitably chosen spatial scales (see Lehtomäki and Moilanen (ii) Can also be implemented by using suitably large predefined spatial planning units in analysis (pre-processing) |
| Provision connectivity: regional connected networks desirable | |
| Maintenance of large-scale spatial dynamical processes. Example: area networks for the maintenance of biodiversity or pollinators | Comparatively difficult to implement due to technical complications and lack of data about connectivity effects: no standard SCP methodology exists for simultaneous design of networks for many partially conflicting factors. Local area requirements (above) contribute to regional connectivity. (i) Pre-computed connectivity layers can be entered into analysis to give priority to areas assumed important for network connectivity (pre-processing) (ii) Alternatively, regional connected networks can be detected from Zonation output maps in post-processing |
| ES flow: proximity between demand and supply needed | |
| This consideration is separate from, and can be combined with other connectivity components. Proximity between demand and supply can be regarded at local, regional, or global scales. Common requirement with ES. For example, recreation, or pollination | (i) Connectivity interaction (pre-processing) at given spatial scale (Rayfield et al. (ii) When spatial overlap is required, add product of demand and supply layer into analysis (pre-processing) (iii) Via multi-feature connectivity (matrix connectivity; Lehtomäki et al. (iv) Enter separate feature layer for each ES flow area (pre-processing) |
| Distributed ES provision | |
| Many countries, regions or other administrations wish to maintain their own ES, implying need for large-scale distributed priorities. Applies to most ES, such as recreation, ground water, cultural services. This consideration is separate from, and can be combined with other connectivity components. | (i) Use administrative units (ADMU) (Moilanen and Arponen (ii) Enter different feature layers for different areas (pre-processing) (iii) Combination of the above (iv) Use special dispersal kernel with lowest connectivity at middle distances (pre-processing) |
For each solution, we indicate where in the workflow of SCP the solution is implemented: data pre-processing, prioritization, or post-processing (Fig. 1)
Fig. 1Schematic illustration of the process of spatial prioritization, with entry points for connectivity considerations marked, linking to Table 1. Main options for dealing with connectivity considerations include in data preparation and preprocessing (either externally or by Zonation), or during the computational prioritization run itself. The strength and spatial scale of a connectivity response can typically be specific by parameters (see Lehtomäki and Moilanen 2013). Limited options for accounting for connectivity exist at the step where priority rank maps are interpreted and post-processed for decision making. Spatial prioritization methods can simultaneously balance the needs of many biodiversity features or ES, aiming at solutions that combine different spatial needs, illustrated by panels a–d
Illustrative examples of connectivity considerations for selected ES, following the most well-known classification into provisioning, regulating, and cultural ecosystem services (CICES 2016)
| ES category | Local area requirements | Regional network-type connectivity | Demand for ES flow | Need for distributed access |
|---|---|---|---|---|
| Provisioning services | Maintenance of ecosystem processes may imply minimum area size for successful ES provision; e.g. hunting, fishing Also logistical considerations may favor larger areas: e.g., cultivated crops e.g. ground water, whole ground water area requires maintenance | Maintenance of viable (ecological) networks needed for provisioning services that depend on biodiversity or ecosystem processes and function e.g. anything depending on biodiversity; river systems | Logistical requirements between ES provision and beneficiaries: low to high requirements e.g. cultivated crops (accessibility is important, although commonly transported long distances) e.g. wild food, often utilized in situ, flow only at short distances | Considerations of security or equitable provision imply distributed supply e.g. drinking water |
| Regulation and maintenance services | Large variation in local area requirements between different ES e.g. carbon sequestration, low local area requirements e.g. pollination, can be provided by smallish but high quality areas e.g. flood regulation, large enough areas required | e.g. biodiversity-dependent services including pollination: maintenance of (meta)populations needed via sufficiently dense networks of populations e.g. flood regulation, maintenance of landscape quality at catchment scale | Large variation. e.g. carbon sequestration, low local flow requirements e.g. air quality regulation, high local & regional-scale requirements e.g. pollination, high localized flow requirement | Largely same as above. e.g. air quality regulation: service desirable for all people e.g. flood regulation, service desirable for all people in flood-prone environments |
| Cultural services | Requirement highly variable e.g. sense of place, no specific area requirement e.g. green areas for recreation need to be large enough | Variable requirement e.g. sense of place: networks not needed necessarily e.g. outdoor recreation: connected network of green areas may be preferable | Requirement for flow is high: cultural services needed where there are people e.g. recreation; accessibility of local recreational areas | High requirement for distributed supply and access. Globally aggregated supply very unsatisfactory |
Note that multiple connectivity requirements (provision, flow & distributed access) can apply to an individual ES simultaneously