-
Notifications
You must be signed in to change notification settings - Fork 0
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
DSCI-621 Implementing the functionality to publish to HDX #3
base: main
Are you sure you want to change the base?
Conversation
# Conflicts: # requirements.txt
Some issues i've noticed on the staged files so far:
with some finagling of tabular data set it can be opened as
|
These comments are related to an older version of the datasets. |
got it, thanks for pointing me to the updated data set in the jira ticket and explaining the caching/staging issues. So some new comments: Raster 90d zipped file: The zip file looks a bit strange. it appears to include the 90d prior to 2024-01-01 and just include 1 single band (SFED_BASELINE). This file is supposed to be the file that updates daily including the latest date. Each date/ cloud optimized geotif should include two bands 1. SFED, 2. SFED_BASELINE. tabular excel file:
|
…scan_300s_SFED_90d.zip file
@isatotun - i checked the issue leonardo noted on the call for the missing I can confirm that this bug is not introduced by the function i wrote to extract the baseline
Just to note the function above does return some some NaN values but that is only when the original admin units have no data in the postgres db because they are too small for the zonal stats methodology used here. I think these NaN values will all be removed when we filter to only HRP countries and they don't account for the more widespread issue seen in the data on stage |
Jira ticket -> https://humanitarian.atlassian.net/browse/DSCI-621