This data standard allows the recording of all stops from a vessels perspective- with the vessel being the only required field. It is intended for use of recorded stops in known locations, but other stops can be recorded within this structure.
A14.1 Vessel
LOOKUP / STRING A1: Vessel
The name or identifier of the vessel that made the port call (Internal ID from OMarine A1).
A14.2 Port or Destination Name
LOOKUP / STRING A3: Port
The name or identifier of the location (port) of the port call. This can be a lookup to the port dataset or a string value (Internal ID from OMarine A3).
A14.3 Arrival Time
DATETIME NA
The date and time at which the vessel arrived at the port.
A14.4 Departure Time
DATETIME NA
The date and time at which the vessel departed the port.
A14.5 Operations Performed
LIST (LOOKUP / STRING) B12: Vessel Operations
A list of operations that were performed during the Port Call. This should use terms from dictionary B12- Vessel Operations. If no dictionary value applies, then a string can be entered.
A14.6 Additional Particulars Attributes
TABLE Rows
A table recording data about the port call that does not allign with other fields in the schema. This data can be very generic and is recorded in a table with two fields as defined below.
-
A14.6.1 Key
STRING
Can be nullA description or name for the attribute that this piece of data describes.
-
A14.6.2 Value
STRING
Can be nullThe value of the particulars attribute. Note that while this is a string value, xml or other data forms can be stored as a string in this field.
A14.7 Internal ID
STRING NA
An ID for internal purposes used to identify this entity and link it to other entities.