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/2437#issuecomment-866121675,https://api.github.com/repos/pydata/xarray/issues/2437,866121675,MDEyOklzc3VlQ29tbWVudDg2NjEyMTY3NQ==,7844578,2021-06-22T16:07:36Z,2021-06-22T17:01:35Z,NONE,"I believe the dates assocsiated with this particular dataset are days since ""1700-01-01""
> 86287 == 1936-04-01
```python
ds[""time""] = ds.time.assign_attrs(units=""days since 1700-01-01"")
ds = xr.decode_cf(ds)
```","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,363326726
https://github.com/pydata/xarray/issues/2437#issuecomment-787459912,https://api.github.com/repos/pydata/xarray/issues/2437,787459912,MDEyOklzc3VlQ29tbWVudDc4NzQ1OTkxMg==,14808389,2021-02-28T14:19:33Z,2021-02-28T14:20:25Z,MEMBER,"the issue is that without more information (units, reference date, calendar), `xarray` can't decode these integers correctly. For example, if the units are `days` your data would span more than 100 years, but if we assume milliseconds that would be about 2 hours. Same for reference date and calendar: if they are chosen incorrectly, the decoded data will be completely wrong.
You will have to check either the data provider's website or contact them and ask for help (it seems they started offering their data as netcdf files about two weeks ago so this might actually be a issue with their conversion code). Once you have that information we can help you with the code necessary to convert using `xarray`.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,363326726
https://github.com/pydata/xarray/issues/2437#issuecomment-787289605,https://api.github.com/repos/pydata/xarray/issues/2437,787289605,MDEyOklzc3VlQ29tbWVudDc4NzI4OTYwNQ==,20365917,2021-02-28T03:43:05Z,2021-02-28T03:43:05Z,NONE,"@spencerkclark
67935 67966 67994 ... 115355 115385 are actually time. But they are stored aa integer. I like to convert all integer to date. My attached data has exact same time.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,363326726
https://github.com/pydata/xarray/issues/2437#issuecomment-787069302,https://api.github.com/repos/pydata/xarray/issues/2437,787069302,MDEyOklzc3VlQ29tbWVudDc4NzA2OTMwMg==,6628425,2021-02-27T12:59:35Z,2021-02-27T12:59:35Z,MEMBER,"@hafez-ahmad yes, I'm trying to help, but in order to do that I need more information. What does 456852 represent?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,363326726
https://github.com/pydata/xarray/issues/2437#issuecomment-787065391,https://api.github.com/repos/pydata/xarray/issues/2437,787065391,MDEyOklzc3VlQ29tbWVudDc4NzA2NTM5MQ==,6628425,2021-02-27T12:27:41Z,2021-02-27T12:55:36Z,MEMBER,"Thanks @keewis.
@hafez-ahmad by [Julian date](https://en.wikipedia.org/wiki/Julian_day) do you mean that the time coordinate represents ""days since -4713-01-01T12:00:00"" in a Julian calendar?
Once we know the units (expressed as `""{time_unit} since {reference_date}""`) and the calendar of the time coordinate, we can convert it to datetime objects via something like the following:
```python
units = ""days since -4713-01-01T12:00:00""
calendar = ""julian""
ds[""time""] = ds.time.assign_attrs(units=units, calendar=calendar)
ds = xr.decode_cf(ds)
```
I'll admit though, with the values in your dataset, this assumption produces dates like `cftime.DatetimeJulian(-4527, 1, 30, 12, 0, 0, 0)`, which feel unlikely to be correct. Perhaps you are using a different reference date?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,363326726
https://github.com/pydata/xarray/issues/2437#issuecomment-787067778,https://api.github.com/repos/pydata/xarray/issues/2437,787067778,MDEyOklzc3VlQ29tbWVudDc4NzA2Nzc3OA==,20365917,2021-02-27T12:47:37Z,2021-02-27T12:47:37Z,NONE,"@spencerkclark
I like to convert datetime. My dataset time is not familiar. It looks like 456852,85993, is there anyvway to convert 456852 to dmy [01-01-2020]?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,363326726
https://github.com/pydata/xarray/issues/2437#issuecomment-787059836,https://api.github.com/repos/pydata/xarray/issues/2437,787059836,MDEyOklzc3VlQ29tbWVudDc4NzA1OTgzNg==,14808389,2021-02-27T11:40:09Z,2021-02-27T11:52:49Z,MEMBER,"@spencerkclark: if the dataset linked to above is a good example, that would be
ds.info()
```
xarray.Dataset {
dimensions:
id = 37 ;
time = 1380 ;
variables:
float32 runoff_mean(time, id) ;
runoff_mean:units = m3/s ;
runoff_mean:long_name = GRDC calculated from daily data ;
float32 flag(time, id) ;
flag:long_name = percentage of valid values used for calculation from daily data ;
float32 area(id) ;
area:units = km2 ;
area:long_name = catchment area ;
object country(id) ;
country:long_name = country name ;
country:iso2 = ISO 3166-1 alpha-2 - two-letter country code ;
float32 geo_x(id) ;
geo_x:units = degree_east ;
geo_x:long_name = station longitude (WGS84) ;
float32 geo_y(id) ;
geo_y:units = degree_north ;
geo_y:long_name = station latitude (WGS84) ;
float32 geo_z(id) ;
geo_z:units = m ;
geo_z:long_name = station altitude (m above sea level) ;
object owneroforiginaldata(id) ;
owneroforiginaldata:long_name = Owner of original data ;
object river_name(id) ;
river_name:long_name = river name ;
object station_name(id) ;
station_name:long_name = station name ;
float32 timezone(id) ;
timezone:units = 00:00 ;
timezone:long_name = utc offset, in relation to the national capital ;
int64 time(time) ;
time:long_name = time ;
int32 id(id) ;
id:long_name = grdc number ;
// global attributes:
:title = Mean daily discharge (Q) ;
:Conventions = CF-1.7 ;
:references = grdc.bafg.de ;
:institution = GRDC ;
:history = Download from GRDC Database, 26/02/2021 ;
:missing_value = -999.000 ;
}
```