dst_nodata must be in valid range for destination dtype

for the GPM IMERG dataset (example file: s3://gesdisc-cumulus-prod-protected/GPM_L3/GPM_3IMERGDF.07/2000/06/3B-DAY.MS.MRG.3IMERG.20000601-S000000-E235959.V07B.nc4) many variables throw this error when generating a tile

Start by reproducing tile generation with the GPM IMERG example file referenced in the issue and capture which variables trigger the error. Trace the destination dtype and nodata handling used during tile generation; done means the affected variables generate tiles without the “dst_nodata must be in valid range” error.

Written by the indexing model from the issue text.