The aim of this issu is to generete a daily warring to support@ocean-ops.org and vturpin@ocean-ops.org when new trajectory file is available at the OceanGliders Coriolis DAC.
The alerte must be daily.
Fields "WMO,file,deployment_start_date,time_coverage_end,gdac_date_creation" are usefull to create the warning. The rest can be ignored.
Contrary to Argo, we can not base this warning on the comparison of the WMO ID registered in our DB and WMO ID available in the index file. So the alerte should be for every new deployment available in this file. This is why a daily warning is suggested.
Message should be:
Objet :
[OceanOPS - OceanGliders New traj Coriolis DAC]:
Message:
The following OceanGliders platforms have been created at Coriolis DAC today :
WMO,file,deployment_start_date,time_coverage_end,gdac_date_creation
The aim of this issu is to generete a daily warring to support@ocean-ops.org and vturpin@ocean-ops.org when new trajectory file is available at the OceanGliders Coriolis DAC. The alerte must be daily.
The OceanGliders trajectory index file is available here: https://co.ifremer.fr/co//ego/ego/v2/glider_traj_index.txt
Fields "WMO,file,deployment_start_date,time_coverage_end,gdac_date_creation" are usefull to create the warning. The rest can be ignored.
Contrary to Argo, we can not base this warning on the comparison of the WMO ID registered in our DB and WMO ID available in the index file. So the alerte should be for every new deployment available in this file. This is why a daily warning is suggested.
Message should be: Objet : [OceanOPS - OceanGliders New traj Coriolis DAC]:
Message: The following OceanGliders platforms have been created at Coriolis DAC today : WMO,file,deployment_start_date,time_coverage_end,gdac_date_creation