MarineDataExchange

This page lists the requirements for data exchange from RDMS systems to iMarine infrastructure. It collects requirements from similar yet distinct cases.

NEAFC

The North-East Atlantic Fisheries Commission (NEAFC) exchanges data with ICES scientists for further analysis. NEAFC acts as the data source, and does not bring many requirements wrt the data analysis.

NEAFC can not immediately say if it has a preference for a Web-service, JDBC, or other Data Exchange mechanism.

In this collaboration, NEAFC expects to enable ICES staff to run queries independently and obtain VMS data-sets in a secure environment. This will release NEAFC of the manual effort to generate and share the semestral reports. ICES will have to be involved to define exploitation scenario's.

The current data exchanges situation is as follows:

1. NEAFC uses queries to provides datasets to ICES scientists
   1. Vessel and position data in a csv are extracted from a vms system
   2. 3 csv files are generated; vessel data, authorization data (species they can catch), position data
   3. Data are anonymized, and the query execution will remain in NEAFC
   4. The only query parameters are related to semester; start and end-date within the semestral boundaries
   5. Further processing, filtering, and aggregation is all done by ICES
   6. IMPORTANT, the focus is on effort computation, and the RID is regenerated every semester to prevent backtracking
2. Data connections
   1. After a query generates the csv this is posted through Drupal in dedicated password ices user account.
   2. There is only one ICES user, connected to a role in Drupal ICES data. One person currently has been assigned this role
   3. Data extraction is done using SSL, storage is not encrypted or protected
3. Track users and usage
   1. NEAFC could currently track usage, but is currently not doing so
   2. Only if more users would require access is logging needed
   3. ICES asks to produce the semestral report and sometimes historical datasets.
   4. NEAFC does not maintain versions of reports, as the data are not changed

Examples of output

• Example position Record

RID DA TI LT LG SP CO
194706954 20130101 0039 42.399 -18.505 113 99
Random id / Date / time / Latitude / Longitude / Speed / Course

• Example Authorization Record

RID SPECIES
1506600978 WHB
Random identifier (for a vessel) Species. 
The license is NOT synchronized with the semester, and can not be used for monitoring, only for effort reports. 

• Example Vessel Record

RID LENGTH_CATEGORY POWER_CATEGORY VESSEL_TYPE FISHING_GEAR
-169485089 D B TOX OTB

NEAFC Data Descriptions

VMS data is provided by NEAFC to ICES according to Recommendation 10: 2013, and in the format described in the letter from NEAFC of July 16 2013, which for convenience is below.

VESSEL_DATA.CSV - Vessel profile with vessel length and engine power categorised below
AUTHORIZATION_DATA.CSV - Authorised species for vessels
POSITION_DATA.CSV - VMS positions of vessels for specified period

VESSEL DATA CATEGORIES

Vessel Length

A Category 1 Less than 24m OA or less than 20m PP
B Category 2 24-40m OA or 20-35m PP
C Category 3 41-60m OA or 36-55m PP
D Category 4 More than 60m OA or more than 55m PP
U Data is missing

Vessel Engine Power

A Category 1 Less than 1,500 hp or less than 1,150 kw
B Category 2 1,500-3,000 hp or 1,150-2,250 kw
C Category 3 3,001-4,500 hp or 2,251-3,350 kw
D Category 4 More than 4,500 hp or more than 3,350 kw
U Data is missing