home / github

Menu
  • Search all tables
  • GraphQL API

issues_labels

Table actions
  • GraphQL API for issues_labels

61 rows where labels_id = 1962650320

✎ View and edit SQL

This data as json, CSV (advanced)

Link labels_id issues_id
28376794,1962650320 topic-metadata 1962650320 Consistent rules for handling merges between variables with different attributes 28376794
90658514,1962650320 topic-metadata 1962650320 NetCDF attributes like `long_name` and `units` lost on `.mean()` 90658514
148902850,1962650320 topic-metadata 1962650320 Attributes are currently kept when arrays are resampled, and not when datasets are resampled 148902850
173612265,1962650320 topic-metadata 1962650320 Hooks for custom attribute handling in xarray operations 173612265
177903376,1962650320 topic-metadata 1962650320 Shouldn't .where() pass the attributes of DataArrays and DataSets?  177903376
207962322,1962650320 topic-metadata 1962650320 Attrs are lost in mathematical computation 207962322
212177054,1962650320 topic-metadata 1962650320 Encoding lost upon concatenation 212177054
264049503,1962650320 topic-metadata 1962650320 Rules for propagating attrs and encoding 264049503
335015296,1962650320 topic-metadata 1962650320 Indexing preserves outdated attrs which cause trouble downstream 335015296
363299007,1962650320 topic-metadata 1962650320 save "encoding" when using open_mfdataset 363299007
369673042,1962650320 topic-metadata 1962650320 Global option to always keep/discard attrs on operations 369673042
492966281,1962650320 topic-metadata 1962650320 DataArray.quantile does not honor `keep_attrs` 492966281
499196320,1962650320 topic-metadata 1962650320 Changing dtype on v0.13.0 causes Dataset attributes to be lost 499196320
510892578,1962650320 topic-metadata 1962650320 Attributes are dropped after `clip` even if `keep_attrs` is True 510892578
518966560,1962650320 topic-metadata 1962650320 Dataset global attributes dropped when performing operations against numpy data type 518966560
520110180,1962650320 topic-metadata 1962650320 Add option to choose mfdataset attributes source. 520110180
585868107,1962650320 topic-metadata 1962650320 Control attrs of result in `merge()`, `concat()`, `combine_by_coords()` and `combine_nested()` 585868107
587895591,1962650320 topic-metadata 1962650320 Keep attrs by default? (keep_attrs) 587895591
599074389,1962650320 topic-metadata 1962650320 interpolate_na drops DataArray attributes 599074389
618985094,1962650320 topic-metadata 1962650320 keep_attrs not respected for unary operators 618985094
626063031,1962650320 topic-metadata 1962650320 reset_index does not keep attributes 626063031
630062936,1962650320 topic-metadata 1962650320 coarsen deletes attrs on original object 630062936
636480145,1962650320 topic-metadata 1962650320 xarray.where() drops attributes 636480145
650236784,1962650320 topic-metadata 1962650320 Propagate attrs with unary, binary functions 650236784
656982083,1962650320 topic-metadata 1962650320 wrong time encoding after padding 656982083
661076732,1962650320 topic-metadata 1962650320 Xarray dimension interpolation strips coordinate attributes 661076732
683115879,1962650320 topic-metadata 1962650320 Preserve attrs with coarsen 683115879
706568536,1962650320 topic-metadata 1962650320 GroupBy.map with keep_attrs=True gives error 706568536
718395235,1962650320 topic-metadata 1962650320 ds.rolling() drops attributes and name  718395235
721853828,1962650320 topic-metadata 1962650320 rolling keep_attrs & default True 721853828
722168932,1962650320 topic-metadata 1962650320 where should keep_attrs be set in groupby, resample, weighted etc.? 722168932
746021108,1962650320 topic-metadata 1962650320 rolling_exp: keep_attrs and typing 746021108
762385879,1962650320 topic-metadata 1962650320 xr.where not preserving attributes 762385879
777327298,1962650320 topic-metadata 1962650320 Option for combine_attrs with conflicting values silently dropped 777327298
782440858,1962650320 topic-metadata 1962650320 Opening a tiff with scale_factor/add_offset attrs then saving as zarr and opening causes a UFuncTypeError 782440858
784484810,1962650320 topic-metadata 1962650320 attributes that are lists of strings with a single member don't survive a round-trip 784484810
792639470,1962650320 topic-metadata 1962650320 Coordinate attributes are dropped when interpolating datasets 792639470
809332917,1962650320 topic-metadata 1962650320 Record processing steps into history attribute with context manager 809332917
816016031,1962650320 topic-metadata 1962650320 set_index does not respect keep_attrs 816016031
911513701,1962650320 topic-metadata 1962650320 bug or unclear definition of combine_attrs with xr.merge() 911513701
957201551,1962650320 topic-metadata 1962650320 Allow .attrs to use dict-likes 957201551
1069449519,1962650320 topic-metadata 1962650320 DataArray.to_dataset(dim=...) does not preserve attributes 1069449519
1174386963,1962650320 topic-metadata 1962650320 `reindex` drops attrs 1174386963
1193704369,1962650320 topic-metadata 1962650320 xr.where with scalar as second argument fails with keep_attrs=True 1193704369
1299911907,1962650320 topic-metadata 1962650320 Suggestion for merge/concat(combine_attrs='override') 1299911907
1323521079,1962650320 topic-metadata 1962650320 Testing DataArray equality using built-in '==' operator leads to mutilated DataArray.attrs dictionary 1323521079
1325016510,1962650320 topic-metadata 1962650320 Align with join='override' may update index coordinate metadata 1325016510
1388326248,1962650320 topic-metadata 1962650320 xarray allows several types for netcdf attributes. Is it expected ? 1388326248
1423114234,1962650320 topic-metadata 1962650320 `xr.where(..., keep_attrs=True)` overwrites coordinate attributes 1423114234
1440354343,1962650320 topic-metadata 1962650320 `keep_attrs` for pad 1440354343
1486990254,1962650320 topic-metadata 1962650320 getting confused by xarray not reporting the netCDF ```_FillValue``` attribute in jupyter notebooks: add ```_FillValue``` to the "report"? 1486990254
1503542001,1962650320 topic-metadata 1962650320 `Dataset` binary ops ignore `keep_attrs` option 1503542001
1593602847,1962650320 topic-metadata 1962650320 DatasetGroupBy.mean discards attributes on coordinate 1593602847
1617939324,1962650320 topic-metadata 1962650320 Inconsistent coordinate attributes handling in apply_ufunc 1617939324
1696097756,1962650320 topic-metadata 1962650320 nanosecond precision lost when reading time data 1696097756
1722417436,1962650320 topic-metadata 1962650320 `open_dataset` with `chunks="auto"` fails when a netCDF4 variables/coordinates is encoded as `NC_STRING` 1722417436
1776441955,1962650320 topic-metadata 1962650320 improved docstring of to_netcdf (issue #7127) 1776441955
1849417292,1962650320 topic-metadata 1962650320 Dataset.chunk() and DataArray.chunk() now set encoding attribute 1849417292
1863676757,1962650320 topic-metadata 1962650320 Keep attributes across operations - "drop_conflicts" option? 1863676757
2035725001,1962650320 topic-metadata 1962650320 xr.to_netcdf() alters time dimension 2035725001
2098882374,1962650320 topic-metadata 1962650320 dtype encoding ignored during IO? 2098882374

Advanced export

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

CSV options:

CREATE TABLE [issues_labels] (
   [labels_id] INTEGER REFERENCES [labels]([id]),
   [issues_id] INTEGER REFERENCES [issues]([id]),
   PRIMARY KEY ([issues_id], [labels_id])
);
CREATE INDEX [idx_issues_labels_issues_id]
    ON [issues_labels] ([issues_id]);
CREATE INDEX [idx_issues_labels_labels_id]
    ON [issues_labels] ([labels_id]);
Powered by Datasette · Queries took 720.324ms · About: xarray-datasette