CSV fields & topic for seaMobile (SHIP) observations

[davidpodeur]

Hi,

We want to add more "SHIP" data to our WIS2BOX instance, but we but into a number of questions.

We saw the example file tests/data/metadata/station/wmo-test-ship.csv, but we need more information about it:

• we have many Vessels with the station_name (ship name) missing. Shall we put an empty string for "station_name" ? Or put "Unkwown"/"null" ?
• we do not always have "barometer height" in our metadata database, but it is then available in the BUFR files itself. How can we put a "missing" barometer height ? The examples put "0", which does not mean "missing".
• same for latitude / longitude
• what can we do when the WIGOS id is missing but the Traditional id is present ? Are there mandatory fields ?
• the Vessels go worldwide. We hence do not want to use "FRA,europe" for "territory_name,wmo_region" (e.g many Vessels commuting from Europe <=> Americas). Can we use "FRA,world"? Or "XXX,world"?

In addition, could you please provide the MQTT topic where this data shall be posted?

Greetings,
David

[maaikelimper]

@david-i-berry could you help answer David Podeur's questions on how to publish "SHIP" data using the wis2box and the bufr2bufr plugin ?

I believe most of the station metadata fields are irrelevant in this case, the barometer_height,territory_name,wmo_region from the station-metadata will not be encoded in the BUFR. David Berry may advice on what would be sensible placeholders for this case.

latitude,longitude will use the values encoded in the BUFR

WIGOS-ID is always required in the station metadata

[david-i-berry]

Hi @davidpodeur,

we have many Vessels with the station_name (ship name) missing. Shall we put an empty string for "station_name" ? Or put "Unkwown"/"null" ?

Use either an empty string or use the traditional ID. For some vessels the name is private due to security concerns and OceanOps have worked previously with the operators to address this.

we do not always have "barometer height" in our metadata database, but it is then available in the BUFR files itself. How can we put a "missing" barometer height ? The examples put "0", which does not mean "missing".
same for latitude / longitude

In the example we (incorrectly) use 0 as there is a bug in the wis2box that prevents null values being entered. The data are not intended to be used but the bufr2bufr plugin may use the values to infill if they are missing from the input BUFR file.

I've raised an issue here: #845

what can we do when the WIGOS id is missing but the Traditional id is present ? Are there mandatory fields ?

The wis2box enforces the use of the WSI, if this is missing I would check in the OceanOps database.

the Vessels go worldwide. We hence do not want to use "FRA,europe" for "territory_name,wmo_region" (e.g many Vessels commuting from Europe <=> Americas). Can we use "FRA,world"? Or "XXX,world"?

For marine data, these are used to indicate the WMO Member operating, or responsible for, the station and not where the station operates.

[jbcohuet]

Hi Dave @david-i-berry

Thanks for your reply

Fore some ship data we are receiving (Code41), the stations are not registered into OceanOps, but we do produce BUFR and would like to push them too on WIS2.
So of course we don't have the name, WIGOS-ID, etc...
What do you recommend in this case?
Thanks