07.05.2015 Views

o_19ko2dt161ng2j4e1tgnoqv1s45a.pdf

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

APPLICATION OF GIS TO CONSERVATION ASSESSMENTS AT THE ROYAL BOTANIC GARDENS, KEW<br />

fragmentation, decline or fluctuations). and D (very small population or very restricted<br />

distribution).<br />

IUCN recommends obtaining estimates by counting the number of occupied cells in a uniform<br />

grid that covers the entire range of a taxon, then tallying the total area of all occupied cells<br />

(Fig. 2b). This is a calculation that can be easily automated within a GIS.<br />

One problem which arises with area of occupancy calculations is that the results of this method<br />

are highly influenced by the placement of the grid. For example, if an organism is found at<br />

four localities that are less distant from each other than the distance across a grid cell, the<br />

calculated area of occupancy can vary by a factor of four (White 2004). This problem can be<br />

reduced by searching for a grid position which minimizes the area of occupancy. White (2004)<br />

describes a method for automating this procedure within ArcView and concludes that “the<br />

arbitrary nature of using fixed grid methods should be avoided”. Using an automated method<br />

has the advantage that it results in a consistent grid placement, ensuring consistent results if<br />

the procedure is replicated (Willis et al. 2003).<br />

However, another problem arises with calculating AOO because the “size of the area of<br />

occupancy will be a function of the scale at which is measured, and should be at a scale<br />

appropriate to relevant biological aspects of the taxon, the nature of the threats and the available<br />

data” (IUCN 2001). For example if a species has been rarely sampled, then the distance between<br />

observed locations might reflect a lack of observations rather than a lack of occupied habitat<br />

and a coarser grid may therefore be more appropriate. It is therefore not appropriate to use one<br />

set cell size for a wide range of taxa, but what is an appropriate grid size to use when automating<br />

AOO calculations?<br />

The guidelines for using the IUCN criteria (IUCN 2005) recommend a grid size of 2 km,<br />

recognising that for intensely sampled species, a finer grid of 1 km may be more appropriate,<br />

and for sparsely sampled species, a coarser grid. Grid sizes of more than 3.2 km are not<br />

recommended as they preclude the listing of species as Critically Endangered (CR) because<br />

the AOO threshold for CR is 10 km 2 . A method is described of standardising AOO estimates<br />

by scaling the AOO estimate up or down to the reference scale (a 2 km grid size).<br />

Willis et al. (2003) suggest that a suitable grid cell width/height is one tenth of the maximum<br />

distance between any two points on the extent of occurrence polygon. This effectively scales<br />

AOO to the EOO measurement and has given good results so far. Calculations of AOO using<br />

this ‘sliding scale’ grid width/height are currently adopted by the GIS unit at Kew, although<br />

the grid cell size can be manually set by the user within the application. AOO can also be<br />

calculated when there are only two unique localities; the ‘sliding scale’ technique can be used<br />

where grid cell width/height is one tenth of the distance between the two points.<br />

Number of Sub-populations<br />

IUCN defines sub-populations as “geographically or otherwise distinct groups in the population<br />

between which there is little demographic or genetic exchange” (IUCN 2001). Subpopulations<br />

are used in Criteria B (geographical range size, and fragmentation, decline or fluctuations)<br />

and C (small population size and fragmentation, decline or fluctuations). Two techniques for<br />

estimating the number of subpopulations of a species have been developed: the cell adjacency<br />

250

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!