-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PRODUCT] APRFC data products #380
[PRODUCT] APRFC data products #380
Comments
ABRFC QPF, QPE deployed to stable. Thanks to @Enovotny for working on the migrations and processors. |
@msweier I'm still seeing large precip values. I cross checked a download from cumulus for a forecast starting at 09August2024-1200 against original grib files (which have "mm" units). It seems that Cumulus is not converting from "mm" to "inches" properly. Btw, the DSS download from Cumulus has units of "inches" for the DSS records, but I'm pretty sure the values have not truly been converted to inches. Suggest writing out the records with units of "mm" anyway, that way you wouldn't have to worry about unit conversions. @adamscarberry I'm curious if all the products in Cumulus are getting unit conversions? |
Here are the test Cumulus download and original APRFC files |
Also wanted to verify, once a fix is complete for this, will the entire archive for this product in Cumulus get corrected please? |
We do not convert units as it goes from raw product to geotif (done by async_geoprocessor). Original units should remain. The fix attempted by @msweier was to change the units for the product in the database which the async_packager uses to create the dss download. No files should need reprocessed. Once fixed the future downloads should e correct. I'm not able to look deeper into this issue right now. |
Thanks for the test data @FHanbali. I'll take a look. |
Product Source (URL Preferred)
https://cbt.crohms.org/akgrids/
Product Description
ABRFC QPF, QPE, QTE, QTF
Product Format
Format Description
APRFC Forcings for USACE (1).docx
The text was updated successfully, but these errors were encountered: