You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For users of pandas, the xray interface would be more obvious if we referred to what we currently call "coordinates" as "indices."
This would entail renaming the coordinates property to indices, xray.Coordinate to xray.Index and the xray.Coordinate.as_index property to as_pandas_index (all with deprecation warnings).
Possible downsides:
The xray data model would be less obvious to people familiar with the NetCDF.
There is some potential for confusion between xray.Index and pandas.Index:
The only real difference is that xray's Index is a xray.Variable object, and thus is dimension aware and has attributes.
In principle, xray.Index should have all the necessary properties to act like an index (or rather, it already has most of these properties and should get the rest).
Unfortunately, pandas doesn't accept non-pandas.Index objects as indices, nor will it properly convert an xray.Index into a pandas.Index.
The text was updated successfully, but these errors were encountered:
For users of pandas, the xray interface would be more obvious if we referred to what we currently call "coordinates" as "indices."
This would entail renaming the
coordinates
property toindices
,xray.Coordinate
toxray.Index
and thexray.Coordinate.as_index
property toas_pandas_index
(all with deprecation warnings).Possible downsides:
xray.Index
andpandas.Index
:xray.Variable
object, and thus is dimension aware and has attributes.pandas.Index
objects as indices, nor will it properly convert an xray.Index into a pandas.Index.The text was updated successfully, but these errors were encountered: