IMarine Species App
- Product
- Describe the expected service in maximum 3 sentences
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 version: layout
iMarine / fish brief (A final name has not been selected)
The fact sheets have the following fields:
Atlantic cod (the FAO species name in English. The app is english only, so ne 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]
Common names | Sizes | Distribution and maps | Production | Catch statistics | Data sources
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 Cape Hatteras xxx xxx xxx … [FAO]
Thumbnail AquaMaps Native
Other maps: FAO | Other AquaMaps
Production The various xxx xxx xxx … [FAO]
Catch statistics Click for chart view. [FAO]
Data aggregated by iMarine from the following providers ICIS | FAO | FishBase/SeaLifeBase | OBIS Final version: fields in database
Field name or computation in highlighted in grey
iMarine fish brief account Atlantic cod [English_name] Gadus morhua Linnaeus 1758 (Gadidae) [Full name] if italics tags are correct or [Scientific name] in italics & “ ” & [Author] & “ (” & proper([Family]) & “ (” Picture [Thumb]
Click for other pictures [FishBase/SeaLifeBase] [Link: FSLB_Pictures_Link]
Common names | Sizes | Distribution and maps | Production | Catch statistics | Data sources
Common names Morue de l’Atlantique (Fr) | Bacalao del Atlántico (Es) | … [FAO] [Local_names] Click for more common names [FishBase/SeaLifeBase] [FSB_commonnames_link]
Sizes Max size: 2 m (male); Max weight: 96 kg (female); Size at maturity: 31 cm. [FishBase/SeaLifeBase] [FSLB_sizes]
Distribution and maps Cape Hatteras xxx xxx xxx … [FAO] [fact_distribution]
Thumbnail AquaMaps Native [AquaMaps]
Other maps: FAO | Other AquaMaps [Other_Maps]
Production The various xxx xxx xxx … [FAO] [fact_production]
Catch statistics Click for chart view. [FAO] [Stats]
Data aggregated by iMarine from the following providers ICIS | FAO | FishBase/SeaLifeBase | OBIS [fact_link]
- 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
- Are the proposed measures effective?
- Does it reduce a known workload?
- 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?