Skip to content
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

GSLA - input NetCDF not consistent dimensions #89

Open
lbesnard opened this issue Oct 23, 2024 · 0 comments
Open

GSLA - input NetCDF not consistent dimensions #89

lbesnard opened this issue Oct 23, 2024 · 0 comments

Comments

@lbesnard
Copy link
Collaborator

for example, when processing GSLA for 2012 Oct-> Dec

ValueError: variable 'GSLA' already exists with different dimension sizes: {'TIME': 7, 'LATITUDE': 351, 'LONGITUDE': 641} != {'TIME': 7, 'LATITUDE': 352, 'LONGITUDE': 641}. to_zarr() only supports changing dimensio
n sizes when explicitly appending, but append_dim=None. If you are attempting to write to a subset of the existing store without changing dimension sizes, consider using the region argument in to_zarr().

Some input files indeed don't have the same dimension of longitude in that case
https://thredds.aodn.org.au/thredds/dodsC/IMOS/OceanCurrent/GSLA/NRT/2012/IMOS_OceanCurrent_HV_20121225T000000Z_GSLA_FV02_NRT.nc.html
https://thredds.aodn.org.au/thredds/dodsC/IMOS/OceanCurrent/GSLA/NRT/2012/IMOS_OceanCurrent_HV_20120101T000000Z_GSLA_FV02_NRT.nc.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant