home / github / issues

Menu
  • Search all tables
  • GraphQL API

issues: 34352255

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
34352255 MDU6SXNzdWUzNDM1MjI1NQ== 142 Rename "coordinates" to "indices"? 1217238 closed 0   650893 2 2014-05-27T08:47:51Z 2014-07-10T09:38:26Z 2014-06-22T00:44:26Z MEMBER      

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: 1. The xray data model would be less obvious to people familiar with the NetCDF. 2. 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.

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/142/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed 13221727 issue

Links from other tables

  • 2 rows from issues_id in issues_labels
  • 2 rows from issue in issue_comments
Powered by Datasette · Queries took 0.819ms · About: xarray-datasette