-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navy glider data flow update #322
Labels
Comments
Just adding Ben and John for this. The meeting is at 0900 on 29 Feb. |
Bill Lingsch's meeting notes: IOOS_Navy GDAC Meeting Feb 29 2024.docx Action Items:
|
Need Provider assistance on this. |
This is paused during hurricane season, and will be pushed again in ~Dec 2024. |
Moving to backlog as per @kbailey-noaa takeaways from discussion meeting |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pls work with the Navy reps (POC: Danny Illich) to update the Navy glider data flow.
The Navy data flow upgrade involved a costly 'workaround' solution of pushing all Navy gliders' files to 1 single folder. We requested they separate the deployment files into respective deployment folders, as the GDAC system was designed to handle.
The individual glider directories are already created when Tony Gilless registers/creates the deployment so we're just asking that they push the files to those deployment directories.
Bill Lingsch is taking the lead and coordinated a meeting with Navy reps and the GDAC team to review this process.
The text was updated successfully, but these errors were encountered: