issue_comments: 760459257
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/4784#issuecomment-760459257 | https://api.github.com/repos/pydata/xarray/issues/4784 | 760459257 | MDEyOklzc3VlQ29tbWVudDc2MDQ1OTI1Nw== | 53100696 | 2021-01-14T20:32:48Z | 2021-01-14T20:32:48Z | NONE | I haven't found anywhere where geotiffs are meant to follow cf-conventions and the HDF from which the geotiff was generated doesn't seem to have the scale_factor/add_offset metadata. I think the change that should be made is that when loading a zarr or anything else that is expected to follow CF conventions a type check (and possible type cast) is made before trying to apply |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
782440858 |