Skip to content

Handle new data model in pydap v3.5.5+ #10226

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

Closed
wants to merge 2 commits into from

Conversation

Zeitsperre
Copy link
Contributor

  • Tests added
  • User visible changes (including notable bug fixes) are documented in whats-new.rst
  • New functions/methods are listed in api.rst

The latest version of pydap (v3.5.5) slightly adjust their data model and is incompatible with the current backend handler here.

This proposes a backwards-compatible fix for the dims|dimensions field.

Changes were introduced in: pydap/pydap#481

@@ -131,7 +131,11 @@ def open(

def open_store_variable(self, var):
data = indexing.LazilyIndexedArray(PydapArrayWrapper(var))
return Variable(var.dimensions, data, _fix_attributes(var.attributes))
return Variable(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Mikejmnez does this look right to you?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @Zeitsperre ! Thanks for pointing me to this @dcherian .

Please see this #10182 , which is ready for review ;)

I have made some change on the pydap end of things (e.g. dims and dimensions). The documentation is not yet updated there.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @Mikejmnez, this change was working for my use-case, but it looks like the real fix is ever-so-slightly more complicated than my patch here ;). Closing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problems, and thanks a lot @Zeitsperre for the attempted fix :) . Indeed that would have gotten rid of the slashes on dim names +1

@Zeitsperre Zeitsperre closed this Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants