IMarine Species App

Product

The iMarine Species App is an Android / iPhone application that uses data from iMarine partners to display summary fact sheets for selected marine species.

The app is a mash-up of FAO - Fishbase - OBIS - WoRMS data, and uses the ICIS VREVirtual Research Environment. for data preparation, and reads from an iMarine geoserver to read AquaMaps.

Final product release

AppliFish was released as an android / iPhone app in January 2013.

Feed-back comments are collected here

Feed-back and requirements for an even better integrated AppliFish (working title FishFacts) are collected here. The expected product is described here.

The feedback will be incorporated in a release planned for late April 2013.

Final product design

The fact sheets have the following fields:

• Atlantic cod (the FAO species name in English. The app is english only, no need for a language)

• Gadus morhua Linnaeus 1758 (Gadidae) (Scientific name in italics, 2 spaces, Author, 3 spaces, Family on same line as species, between brackets)

• Species image

• Click for other pictures [FishBase/SeaLifeBase]

• IUCN status: Critically Endangered , Endangered , Vulnerable , Near Threatened , Least Concern , Data Deficient

• Common names Morue de l’Atlantique (Fr) | Bacalao del Atlántico (Es) | … [FAO]

• Click for more common names [FishBase/SeaLifeBase]

• Sizes Max size: 2 m (male); Max weight: 96 kg (female); Size at maturity: 31 cm. [FishBase/SeaLifeBase]

• Distribution and maps

• Thumbnail AquaMaps Native

• Other maps: FAO | Other AquaMaps

• Production

• Catch statistics Click for chart view. [FAO]

• Data aggregated by iMarine from the following providers ICIS | FAO | FishBase/SeaLifeBase | OBIS

A list of suggested improvements is available in the AppliFish2 page

Priority to CoPCommunity of Practice.

List proposed solution priority following the iMarine Board priority setting criteria:

• The app is intended as a demonstration o iMarine data and potential. It is a communication tool
• The planned users are contacts of iMarine partners that may be interested to learn more about the project in general, and marine species in particular;
• The app is funded through the project, but was quick to draw attention. It may be considered to attract co-funding;
• There has not been a Structural allocation of resources;
• The app is not Referred in DoW;
• The app was not devised with Business Cases in mind, but rather as a communication tool;
• The action attracts attention and increases visibility of the project. It thus indirectly supports sustainability aspects;
• How consistent it is with EC regulations/strategies (eg INSPIRE);
• Re-usability – benefits – compatibility;

Parentage

The app data are loaded with CoPCommunity of Practice. Software; using FAO web-services, WoRMS web services, Fishbase database extractions;

The ICIS VREVirtual Research Environment. is used to prepare data to load, and a D4S geoserver is used to store the maps.

Productivity

The production of the App was scheduled for 2 Months, with 3 PM in total effort. This was largely met, although minor adjustments were required after release.

Presentation

How must the component be delivered to users? (UI Design / on-line help / training material / support)

Policy

Are there any policies available that describe data access and sharing?

Have the Copyright / attribution / metadata / legal aspects been addressed from a user and technology perspective?

The [AppliFish] access and sharing page contains a detailed overview of the policies, including the publication aspects.