We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
copernicusmarine v2
Note that I just got an email from Copernicus Marine Service that they are about to update their copernicusmarine to v2.0.0, which has some breaking changes: https://help.marine.copernicus.eu/en/articles/9978784-what-s-new-in-the-pre-release-of-version-2-0-0-of-the-copernicus-marine-toolbox.
copernicusmarine
So it might be good to already implement the new API in virtualship fetch
virtualship fetch
Originally posted by @erikvansebille in #83 (comment)
Once copernicusmarine 2 is out on pypi (https://pypi.org/project/copernicusmarine/), we should update our code to use the latest version. Pinning <2 for now 3b5edc6
The text was updated successfully, but these errors were encountered:
Just received note that v2.0.0 of the copernicusmarine toolbox has been released: https://help.marine.copernicus.eu/en/articles/9978784-what-s-new-in-version-2-0-0-of-the-copernicus-marine-toolbox
Sorry, something went wrong.
Pin copernicusmarine >= 2
5669e41
Fixes OceanParcels#90
368f788
No branches or pull requests
Note that I just got an email from Copernicus Marine Service that they are about to update their
copernicusmarine
to v2.0.0, which has some breaking changes: https://help.marine.copernicus.eu/en/articles/9978784-what-s-new-in-the-pre-release-of-version-2-0-0-of-the-copernicus-marine-toolbox.So it might be good to already implement the new API in
virtualship fetch
Originally posted by @erikvansebille in #83 (comment)
Once copernicusmarine 2 is out on pypi (https://pypi.org/project/copernicusmarine/), we should update our code to use the latest version. Pinning <2 for now 3b5edc6
The text was updated successfully, but these errors were encountered: