18.06.2015 Views

Flood Risk and Vulnerability Analysis Project - Atlantic Climate ...

Flood Risk and Vulnerability Analysis Project - Atlantic Climate ...

Flood Risk and Vulnerability Analysis Project - Atlantic Climate ...

SHOW MORE
SHOW LESS

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

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

abrupt seasonal changes in images. Some seamlines were corrected manually by h<strong>and</strong> editing<br />

vector data, conversion to raster, <strong>and</strong> merged into new mosaics. For shadows, clouds, <strong>and</strong> ice,<br />

additional SPOT images were used where available <strong>and</strong> supervised classification steps were<br />

performed inside shadow, cloud <strong>and</strong> ice areas as masks. Results were verified against the<br />

original l<strong>and</strong> cover mosaics for any potential seamline issues (abrupt changes between input<br />

images) <strong>and</strong> then the data was merged into final mosaic l<strong>and</strong> cover data sets.<br />

3.3.3.5 L<strong>and</strong> Cover Tabulations by Watershed<br />

The final 9-class l<strong>and</strong> cover data sets were then intersected with the 39 community flood<br />

watersheds to tabulate total area (in square kilometers) <strong>and</strong> percent coverage of each class by<br />

watershed name (Table 3-7). For Quality Assurance / Quality Control purposes, r<strong>and</strong>om<br />

watersheds were selected <strong>and</strong> l<strong>and</strong> cover metrics were calculated by h<strong>and</strong> then checked<br />

against automated metrics. These tables were then used as direct inputs to the flood<br />

vulnerability assessment.<br />

3.3.4 Results<br />

Results are presented for the overall classification <strong>and</strong> for each community flood watershed<br />

delineation boundary inTable 3-7. Accuracy assessment results detail the effectiveness of the<br />

classification methods employed in this study. L<strong>and</strong> cover within 39 watersheds is presented<br />

covering the flood vulnerability areas for the 32 communities identified in the proposal. Table<br />

3-7is presented in alphabetical order by watershed name.<br />

3.3.4.1 Accuracy Assessment<br />

An accuracy assessment was completed to measure the effectiveness of classifying six classes<br />

of l<strong>and</strong> cover derived from the 10-meter SPOT imagery. Classification accuracy was assessed<br />

by comparing ground truth (from 2.5 meter resolution, natural color, pan-sharpened SPOT<br />

images) to the classified l<strong>and</strong> cover at each assessment point. When interpreting the<br />

contingency table (Figure 3-5) a number of important precautions should be considered:<br />

1. Ground truth data (2.5 m) used to assess the accuracy is of a higher spatial resolution than<br />

the data used in the classification (10 m). The difference in resolution <strong>and</strong> spatial shift can<br />

lead to exaggerated errors, since the larger pixels used in the classification can be a<br />

combination of a number of l<strong>and</strong> cover classes (See Figure 3-4 ).<br />

2. Ground truth data in some cases may be from a time period that differs from the time period<br />

of the classified imagery. While image dates are generally from the same period, not all 10-<br />

meter imagery used for classification had 2.5-meter imagery <strong>and</strong> vice versa. Spatial shifts<br />

<strong>and</strong> l<strong>and</strong> cover change may have occurred between the ground truth image <strong>and</strong><br />

classification image.<br />

3. Ground truth data are natural color 3-b<strong>and</strong> images, while the classification data use 4-<br />

b<strong>and</strong>s. In natural color, wetl<strong>and</strong>s <strong>and</strong> barren ground look very similar. Because of this,<br />

TA1112733<br />

42

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

Saved successfully!

Ooh no, something went wrong!