22.03.2013 Views

Final Technical Report: - Southwest Fisheries Science Center - NOAA

Final Technical Report: - Southwest Fisheries Science Center - NOAA

Final Technical Report: - Southwest Fisheries Science Center - NOAA

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.

avoid these problems, we decided to use ArcGIS only as an optional method for viewing model<br />

outputs and extracting information from geospatial images. The primary software would be<br />

hosted on a website and would not require any specialized software on the user’s computer.<br />

Because of their long experience in developing web-based data servers for marine mammal<br />

research, the Duke Team agreed to take the lead in developing this web-based SDSS software.<br />

Furthermore, Duke University volunteered to initially host the SDSS software on their website.<br />

Subsequent to the March 2007 user’s workshop, the Duke Team developing the SDSS decided to<br />

use Google Earth as the primary visualization tool within the SDSS software.<br />

Most of the specifications for the SDSS were developed at the 2007 Users Workshop in<br />

La Jolla. The primary recommendations of the users were:<br />

• Nobody likes to read manuals. Therefore, we should try to minimize the need for a user<br />

manual by testing the SDSS software on naïve users to develop a user-friendly interface.<br />

• Absolute population density estimates are the highest priority model products. Relative<br />

population density and probability of occurrence are the second- and third-best options,<br />

respectively.<br />

• We should obtain peer-review of the bootstrap approach for estimating the CVs of density<br />

estimates within the scientific community.<br />

• We should allow survey effort and sightings from input datasets to be displayed on all<br />

maps of model output.<br />

• We should allow the user to set the categories and extents for figure legends.<br />

• We should provide spatial plots of user-specified upper and lower confidence limits for<br />

density or probability of occurrence estimates as an output option.<br />

• We should provide a session history tool to record user choices.<br />

• Software documentation should provide a stepwise explanation of everything from model<br />

development to the extraction of model results from the SDSS.<br />

• We should provide a complete list of model assumptions, caveats, and limitations.<br />

• The users prefer a single, peer-reviewed model per species/species group per region and<br />

time period rather than a collection of alternative models.<br />

• Contingent upon future funding, the SDSS development team should send the user<br />

community regular updates of relevant changes to the software.<br />

40

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

Saved successfully!

Ooh no, something went wrong!