We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Actual Behavior: Earliest issue for nssp signals is 30-06-2024 when we query from the api.
Expected behavior
Earliest issue at county level could be mid April instead, since we do have source data stashed in big chunk dev 2 for these 3 months.
Context TODO: write code that take these stashed csv files, run nssp indicator on each, and output them in batch issue upload csv orderings.
The text was updated successfully, but these errors were encountered:
minhkhul
Successfully merging a pull request may close this issue.
Actual Behavior:
Earliest issue for nssp signals is 30-06-2024 when we query from the api.
Expected behavior
Earliest issue at county level could be mid April instead, since we do have source data stashed in big chunk dev 2 for these 3 months.
Context
TODO: write code that take these stashed csv files, run nssp indicator on each, and output them in batch issue upload csv orderings.
The text was updated successfully, but these errors were encountered: