CRS name as an EPSG string.
Must match regular expression:^EPSG:(3276[0-7]$|327[0-5]\d$|32[0-6]\d\d$|3[0-1]\d\d\d$|[1-2][0-9]{4}$|102[4-9]|10[3-9][0-9]$|1[1-9][0-9][0-9]$|[2-9][0-9][0-9][0-9]$)
The Trusted Node’s name, in free-text format.
A free-text field for the Trusted Node’s email address, so that data users can contact the Trusted Node with questions about the data.
Must match regular expression:^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,6}$
Generated by the Trusted Node, this number identifies the Trusted Node and uniquely identifies the contributing vessel. The characters preceding the hyphen (-) identify the Trusted Node, followed by a hyphen (-), and then the vessel’s unique identifier. The UUID assigned by the Trusted Node is consistent for each contributing vessel, throughout the life of service of the vessel. However, if the vessel chooses to remain anonymous to data users, the Trusted Node does not need to publish the vessel name in association with the UUID.
Must match regular expression:^[a-zA-Z][a-zA-Z0-9]*-[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
This field describes the format and version for the data and metadata, such as GeoJSON, CSV, or XYZT. Reference the version of the CSB data convention (e.g., CSB 2.0, CSB 3.0) where possible.
The Creative Commons public domain
dedication under which the Trusted Node is
providing CSB data to the IHO DCDB.
The software program or hardware logger used to log the data.
The software or hardware logger version.
The vertical reference of the depth. The vertical reference will most likely be the transducer (ex: NMEA DBT string) or the waterline (ex: NMEA DPT string).
Position Reference Point (PRP) is the reference point where the navigation data is output. Most likely the reference point will be the location of the GNSS antenna.
The type of vessel collecting the data, such as a cargo ship, fishing vessel, private vessel,
research vessel, etc.
The name of the vessel, in open string format.
The length overall (LOA) of the vessel, expressed as a positive value, in metres, to the nearest metre.
Value must be greater or equal to 1
ID numbers used to uniquely identify vessels. Currently, only two types are available: Maritime Mobile Service Identity (MMSI) or International Maritime Organization (IMO) number. The MMSI number is used to uniquely identify a vessel through services such as AIS. The IMO number is linked to a vessel for its lifetime, regardless of change in flag or ownership. Contributors may select only one ID Type.
The value for the ID Type. MMSI numbers are often nine digits, while IMO numbers are the letters “IMO,” followed by a seven-digit number.
^\d{9}$
^IMO\d{7}$
Composite element containing all information about a given sensor in use on the collection platform. Minimum specification of fields as shown; some sensors may have additional fields (e.g., frequency for an echo sounder). Position is given from the PRP (Position Reference Point) in metres. The offsets are positive NED (North (Bow), East (Starboard), Down)
Must contain a minimum of 1 items
Sensor manufacturer
Sensor model
Position is given from the PRP (Position Reference Point) in metres. The offsets are positive NED (North (Bow), East (Starboard), Down)
Must contain a minimum of 3 items
Must contain a maximum of 3 items
Draft of vessel
Uncertainty in vessel draft
Frequency of echo sounder
Pulse length of echo sounder
Position is given from the PRP (Position Reference Point) in metres. The offsets are positive NED (North (Bow), East (Starboard), Down)
Same definition as positionPosition is given from the PRP (Position Reference Point) in metres. The offsets are positive NED (North (Bow), East (Starboard), Down)
Same definition as positionModel of GNSS antenna
Some systems may have the ability to provide sound speed data and correct the sounding. If details regarding such corrections are known (“True”), it is strongly recommended that the ‘Sound Speed Correction’ field in Table 4 be populated. If “False”, no information about how sound speed was applied has been recorded.
Describes whether the final vessel position (longitude and latitude) has been corrected for the lateral and longitudinal offsets between the GNSS receiver and the transducer (“True”), or if they were not (“False”). If “True”, the position element of the sensor description field in Table 3 should be populated.
Raw data, without tidal corrections or additional processing, are preferable as a contribution to the IHO DCDB. This field allows the data contributor to state whether the data has been processed or corrected (‘True’) or not (‘False’). If ‘True’, it is strongly recommended that detailed information be captured in optional metadata fields as outlined in section 3.3.4. If ‘False’, information in section 3.3.4 is not needed.
If the contributor believes there were any problems or events that may have degraded the quality of the position or depth measurements, they can enter that information in this free-text field.
Generated by the Trusted Node, this number identifies the Trusted Node and uniquely identifies the contributing vessel. The characters preceding the hyphen (-) identify the Trusted Node, followed by a hyphen (-), and then the vessel’s unique identifier. The UUID assigned by the Trusted Node is consistent for each contributing vessel, throughout the life of service of the vessel. However, if the vessel chooses to remain anonymous to data users, the Trusted Node does not need to publish the vessel name in association with the UUID.
Same definition as uniqueVesselIDList of processing steps recorded for the data
Must contain a minimum of 1 items
Method by which times are assigned to data being recorded.
RFC3339 UTC time stamp
Must match regular expression:^([0-9]+)-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])[Tt]([01][0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9]|60)([.][0-9]+)?[Zz]$
Name of timestamp interpolation method.
Algorithm used to interpolate timestamps.
Version of timestamp interpolation method used.
Processing that changed the reference system of the data. Must include the original and destination coordinate reference system, and the method used to change.
Original coordinate reference system of the data (e.g., EPSG:4326).
Coordinate reference system to which data were transformed (e.g., EPSG:8252).
Method used to change coordinates (e.g., GeoTrans).
Steps taken to reduce raw data to a vertical reference system (Chart Datum, MSL, ellipsoid, water level, etc.). Must include the vertical reference system, and method used.
Vertical reference system (e.g., Chart Datum, MSL, ellipsoid, water level, etc.)
Datum of vertical reference system.
Method used to reduce raw data to vertical reference system.
Model used for reduction of raw data to vertical reference system
Steps taken to post-process or improve horizontal and vertical positioning.
Algorithm used for GNSS post-processing
Version of GNSS post-processing algoritm method used.
Correction to soundings for sound speed in the water.
Source of correction to soundings.
Method of sounding correction.
Version of sounding correction method used.
General algorithm used to triage data
Examples: deduplicate, uncertainty estimation, manual editing
Source (e.g., project, library) of the algorithm applied
Parameters used in data processing.
Version of algorithm used to triage data.
Explanatory text related to algorithm or its outputs
The distance from the vertical reference point to the seafloor. Should be collected as a positive value, in metres, with decimetre precision.
The date and UTC time stamp for the depth measurement as well as can be determined, ideally to millisecond precision in RFC3339 format.
Same definition as timestampMust contain a minimum of 2 items
Must contain a minimum of 4 items