-
Notifications
You must be signed in to change notification settings - Fork 87
model.GridType differences from 3.1.1 #43
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
Comments
Upon further inspection I see that the GridType returned is different. In Version 3.1.1 I get a dictionary: >>> from pydap.client import open_url
>>> ds = open_url('http://dods.mbari.org/opendap/data/auvctd/surveys/2010/netcdf/Dorado389_2010_300_00_300_00_decim.nc')
>>> ds['temperature']
{'temperature': <pydap.model.BaseType object at 0x7f18464a7650>, 'time': <pydap.model.BaseType object at 0x7f18464a7750>} With Version 3.2.0 I get something different: >>> from pydap.client import open_url
>>> ds = open_url('http://dods.mbari.org/opendap/data/auvctd/surveys/2010/netcdf/Dorado389_2010_300_00_300_00_decim.nc')
>>> ds['temperature']
<GridType with array 'temperature' and maps 'time'> Perhaps this is an improvement and I should change my code? |
This explains some of the compatibility issue I saw in pydata/xarray#1174 - namely, datatype returned by Does it make sense to implement these functions? From my understanding of the code, |
It wasn't too hard for me to make a work-around in my code, but it'd be nice to have the same behavior that we have 3.1.1. |
I'd love to have this compatibility as well! I'm new to Pydap - I've been using Xarray and now I'm trying to get it to work with |
I'm going to close this one following PR #48. If it turns out to be insufficient, I'll reopen. |
Uh oh!
There was an error while loading. Please reload this page.
GridType in Version 3.1.1 has len() method and other attributes:
Should they be added to maintain compatibility?
The text was updated successfully, but these errors were encountered: