Closed sfoks closed 1 month ago
@sfoks Looks like there must of been some library update that changed the offsets for kerchunk. I re-ran the kerchunk routine for nhm v1.0 and it looks like it's working correctly again. Give it a try and let me know if you see any problems. Thank you for catching this!
I also had to update the NHM v1.1 gridmet and c404-bc json files. They should all be working now.
@pnorton-usgs thank you!! Looks like NHM v1.0 works now (haven't tried the others yet).
Hi all, there seems to be some weirdness with the nhru and nsegment ids that are read in from the hytest catalog data file. I haven't explored all the NHM-PRMS datasets but it might be something consistent or a one-off issue.
When I access the
nhm-v1.0-daymet-catalog
,nhm-v1.0-daymet-byHW-musk-obs-onprem
dataset, I see that the minimum value for nhru is -2147483648 and nsegment is -1431085264. I know that the IDs start at 1 and end at 109,951 (nhru) and for nsegment ends at 56,460 so I think something must have happened in the json file? When I read in the netcdfs for a variable, I don't see this problem.I haven't checked NHM-PRMS v1.1 yet, or other calibrations for NHM-PRMS v1.0. Edit: all calibration configurations have this issue too for NHM-PRMS v1.0.