Open Marine Data Standards
A4: Terminal Version History

1.0.0

28 September 2022

Data Standards
A1: Vessel A2: Organisation A3: Port A4: Terminal A5: Berth A6: Classification Society A7: Ship Builder A8: Certification A9: Restriction A10: Inspection A11: Incident A12: Vetting Data A13: Contract A14: Port Call

A4: Terminal

This data standard should be used to record all data about terminals (a location where the loading and unloading of people or goods takes place).

Download Version History

Fields within this standard can be compulsory (must be completed to meet the standard) or optional. Fields are optional if they ‘can be null’. Data can be recorded against a terminal for fields not defined in this standard- the standard only defines common fields.

A4.1 Terminal name

STRING NA

Cannot be null

The name of the terminal as used by the terminal’s operator. This is the name (or identifier) most commonly used to identify the terminal.

A4.2 Terminal type

LOOKUP / STRING B5: Terminal Types

Can be null

The value in the dictionary that best describes the type of the terminal. This will relate to the function, operations, structure and location of the terminal. If no value is available in the dictionary, a string value can be entered.

A4.3 Terminal latitude

FLOAT Degrees

Can be null

The latitude value corresponding to the terminal’s current physical location.

1: Must be a value between -90 and 90.

A4.4 Terminal longitude

FLOAT Degrees

Can be null

The longitude value corresponding to the terminal’s current physical location.

1: Must be a value between -180 and 180.

A4.5 Port containing terminal

LOOKUP / STRING A3: Port

Can be null

An identifier for the port associated with the terminal (the port within which the terminal is located). This must be the most unique identifier available for the port. If there exists a port dataset corresponding to data standard “A3 Port”, this value should refer to an element within that dataset (Internal ID).

1: If the terminal is active (currently available for use) and is not a vessel, this value cannot be null.

A4.6 Terminal operator

LOOKUP / STRING A2: Organisation

Can be null

An identifier of the organisation responsible for the operation of the terminal. If there exists an organisation dataset corresponding to data standard “A2 Organisation”, this should refer to an element in that dataset.

A4.7 Is the terminal currently active?

BOOLEAN NA

Can be null

A logical stating whether the terminal is currently in use- the terminal is currently available for use.

A4.8 Terminal Contact Details

TABLE Rows

Can be null

Contact information by which the terminal operator can be reached. The fields required for this table are defined below.

  • A4.8.1 Key

    STRING

    Can be null

    A description of the type of contact details being provided.

  • A4.8.2 Value

    STRING

    Can be null

    The corresponding contact details for the terminal.

A4.9 Additional Particulars Attributes

TABLE Rows

Can be null

A table recording data about the terminal 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.

  • A4.9.1 Key

    STRING

    Can be null

    A description or name for the attribute that this piece of data describes.

  • A4.9.2 Value

    STRING

    Can be null

    The 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.

A4.10 Internal ID

STRING NA

Can be null

An ID for internal purposes used to identify this entity and link it to other entities.