-
Notifications
You must be signed in to change notification settings - Fork 25
Description
When reading a netcdf file (ERA5 hourly) with ReadNetCDF from metR 0.18.3, the timestamp is decoded partially: only the date is decoded, the time part is missing.
Did not have this problem with metR 0.18.0.
Example with metR 0.18.3:
valid_time latitude longitude u10 number expver v10 d2m
1: 2025-01-01 45.5 -75.1 -2.90934563 0 0001 -1.45308495 272.5151
2: 2025-01-01 45.5 -75.1 -3.37289524 0 0001 -1.44571972 272.4641
3: 2025-01-01 45.5 -75.1 -3.87220287 0 0001 -1.30654049 272.5964
4: 2025-01-01 45.5 -75.1 -4.14375687 0 0001 -1.11105251 272.7625
5: 2025-01-01 45.5 -75.1 -4.07659912 0 0001 -1.11179924 272.7988
6: 2025-01-01 45.5 -75.1 -3.86723900 0 0001 -0.92424434 272.8032
Example with metR 0.18.0:
valid_time latitude longitude u10 number expver v10
1: 2025-01-01 00:00:00 45.5 -75.1 -2.90934563 0 0001 -1.45308495
2: 2025-01-01 01:00:00 45.5 -75.1 -3.37289524 0 0001 -1.44571972
3: 2025-01-01 02:00:00 45.5 -75.1 -3.87220287 0 0001 -1.30654049
4: 2025-01-01 03:00:00 45.5 -75.1 -4.14375687 0 0001 -1.11105251
5: 2025-01-01 04:00:00 45.5 -75.1 -4.07659912 0 0001 -1.11179924
6: 2025-01-01 05:00:00 45.5 -75.1 -3.86723900 0 0001 -0.92424434
7: 2025-01-01 06:00:00 45.5 -75.1 -3.77702236 0 0001 -1.02590084
8: 2025-01-01 07:00:00 45.5 -75.1 -3.73343086 0 0001 -1.26933479
9: 2025-01-01 08:00:00 45.5 -75.1 -3.72810078 0 0001 -1.40158176
10: 2025-01-01 09:00:00 45.5 -75.1 -3.59781647 0 0001 -1.61381149