issues

Table actions

1 row where comments = 5, repo = 13221727 and user = 6645714 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date), closed_at (date)

type 1

state 1

repo 1

  • xarray · 1 ✖
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
100601294 MDU6SXNzdWUxMDA2MDEyOTQ= 526 64-bit values are coerced to 32-bit when writing as NETCDF4_CLASSIC petercable 6645714 closed 0     5 2015-08-12T18:06:42Z 2015-09-01T21:02:08Z 2015-09-01T21:02:08Z CONTRIBUTOR      

``` import xray import numpy

ds = xray.Dataset() time_data = numpy.arange(10.0, 100.0, .5) raw_data = time_data.copy() times = xray.Variable('time', time_data) data = xray.DataArray(raw_data, dims=['time'], coords={'time': times}) ds['data'] = data ```

If you examine ds now, you’ll see:

<xray.Dataset> Dimensions: (time: 180) Coordinates: * time (time) float64 10.0 10.5 11.0 11.5 12.0 12.5 13.0 13.5 14.0 ... Data variables: data (time) float64 10.0 10.5 11.0 11.5 12.0 12.5 13.0 13.5 14.0 ...

Now, if we dump to netcdf and reload:

ds.to_netcdf('test1.nc', format='NETCDF4_CLASSIC') ds1 = xray.open_dataset('test1.nc')

The formerly 64-bit values are now 32-bit:

<xray.Dataset> Dimensions: (time: 180) Coordinates: * time (time) float32 10.0 10.5 11.0 11.5 12.0 12.5 13.0 13.5 14.0 ... Data variables: data (time) float32 10.0 10.5 11.0 11.5 12.0 12.5 13.0 13.5 14.0 ...

It looks to me like coerce_nc3_dtype is being called for all formats that aren't straight NETCDF4.

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

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);