Data Model - Collected data¶

Base classes¶

data

Vessel¶

vessel

Scientific cruise¶

scientific-cruise

Trip¶

trip

Landing¶

landing

Sale¶

sale

Activity calendar¶

Fishing area¶

fishing-area

Vessel use features¶

vessel-use-features

Gear use and physical features¶

gear-use-features

Vessel owner¶

vessel-owner

Catch (batches)¶

catch-batch

Products and expected sales¶

product

Measurements¶

measurement

Image attachments¶

image-attachment

Details¶

Base classes¶

Each collected data has a root entity, linked to a program.

A root entity can be linked to one fishing vessel (see above: Trip, Landing, ...);
A root entity has some data quality attributes:
- A update date, to identify the exact version;
- A recorder department and person;
- A quality flag (e.g. Good, Bad, Out of stats, ...) used to exclude bad data on exports or map products;

Trip¶

Trip: a fishing trip, on a unique vessel.
- A trip start from a departure location (and date/time) and ends with a return location;
- A trip can define one or more physical gears: a gear (e.g. OTB) and its physical features;
- A trip can have many operations, as children;
Operation: A unique fishing operation, using a physical gear.
- A operation can define some features;

OperationVesselAssociation records other vessels associated to an operation (e.g. pair trawling).

Landing¶

Observed Location: an observation applied on a landing site (harbour, auction) on a date/time (or period);
- an observed location can have many landings (one or more by vessel), as children.
Landing: an observation on a vessel, observed at landing time.
- A landing can have a parent observed location, as parent;
- A landing can have many trips, as children;

A LandingOrigin records the origin (e.g. the trip) of a landing, with its landing location and date.

Sale¶

A Sale (sale) is the sale (total or partial) of a landing, with its measurements (SaleMeasurement) and its products sold.

Scientific cruise¶

A ScientificCruise is a survey campaign at sea: vessel, chief scientist, departure and return locations and dates. Observations (e.g. ObservedLocation) can be attached to it.

Vessel¶

VesselFeatures: the physical characteristics of a vessel (length, power, tonnage...), registered over time;
VesselUseFeatures: how a vessel is used during an operation (gear dimensions, engines...);
VesselOwner / VesselOwnerPeriod: the vessel owners and their ownership periods;
VesselRegistrationPeriod: the registration (mark, administration) periods of a vessel;
VesselPosition: a VMS position of a vessel;
the *Origin entities (GearUseFeaturesOrigin, GearPhysicalFeaturesOrigin, VesselUseFeaturesOrigin) link a feature to its source (e.g. a survey program).

Gear use and physical features¶

GearUseFeatures: how a gear is used during an operation (dates, surrounding features);
GearPhysicalFeatures / PhysicalGear: the physical gear aboard a vessel, with its measurements and origins;
Both are measured through PMFM measurements (GearUseMeasurement, GearPhysicalMeasurement, PhysicalGearMeasurement).

Catch (batches)¶

Batch: the catch hierarchy of an operation or a sale, sorted by species/size (parent/children tree);
- sorting and quantification are recorded through PMFM measurements;
DenormalizedBatch: a flat, pre-computed copy of the batch tree (weights, counts, sorting values) used for fast reporting.

Products and expected sales¶

Product: a commercial category (species/size/preservation) of a landing, sale, expected sale or batch, with its sorting and quantification measurements;
ExpectedSale: a sale planned at trip or landing time, with its own measurements (SaleMeasurement).

Measurements¶

All feature observations use the same PMFM measurement pattern, attached to their host entity: SurveyMeasurement (landing or activity calendar), LandingMeasurement, ObservedLocationMeasurement, GearUseMeasurement, VesselUseMeasurement, VesselPhysicalMeasurement.

Sorting and quantification of batches and products are also PMFM measurements: BatchSortingMeasurement, BatchQuantificationMeasurement, ProductSortingMeasurement, ProductQuantificationMeasurement, and the denormalized DenormalizedBatchSortingValue used for fast reporting.

Fishing area¶

A FishingArea is the geographic area of a fishing activity (operation, sale, landing...), optionally refined by a nearby specific area (NearbySpecificArea).

Image attachments¶

ImageAttachment stores a generic attachment (path, content type, quality) attached to any object by an object type and identifier.

Activity calendar¶

ActivityCalendar: the yearly fishing activity and effort of a vessel, per gear and month;
DailyActivityCalendar: the detailed daily activity of a calendar, with its fishing effort and effort zone.