This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
Add a management command to set datasets property of every city #823
Comments
maurizi
added a commit
that referenced
this issue
Jun 29, 2018
The current dynamic check is not working very well. It checks for the presence of map cells and reports their dataset names, but doesn't check the values for those cells. In practice, this means that a location without LOCA data will be reported as supporting LOCA data, as the ingest will create LOCA cells, but fill them with NaN (not a number) values. Since checking the values in each cell would be computationally expensive, we've instead moved the list of supported datasets to be stored in the database. A future enhancement (#823) will ensure that this is properly set for every existing city. Closes #822
maurizi
changed the title
This was referenced Jun 29, 2018
ddohler
pushed a commit
that referenced
this issue
Aug 21, 2023
The current dynamic check is not working very well. It checks for the presence of map cells and reports their dataset names, but doesn't check the values for those cells. In practice, this means that a location without LOCA data will be reported as supporting LOCA data, as the ingest will create LOCA cells, but fill them with NaN (not a number) values. Since checking the values in each cell would be computationally expensive, we've instead moved the list of supported datasets to be stored in the database. A future enhancement (#823) will ensure that this is properly set for every existing city. Closes #822
ddohler
pushed a commit
that referenced
this issue
Aug 21, 2023
The current dynamic check is not working very well. It checks for the presence of map cells and reports their dataset names, but doesn't check the values for those cells. In practice, this means that a location without LOCA data will be reported as supporting LOCA data, as the ingest will create LOCA cells, but fill them with NaN (not a number) values. Since checking the values in each cell would be computationally expensive, we've instead moved the list of supported datasets to be stored in the database. A future enhancement (#823) will ensure that this is properly set for every existing city. Closes #822
ddohler
pushed a commit
that referenced
this issue
Aug 21, 2023
The current dynamic check is not working very well. It checks for the presence of map cells and reports their dataset names, but doesn't check the values for those cells. In practice, this means that a location without LOCA data will be reported as supporting LOCA data, as the ingest will create LOCA cells, but fill them with NaN (not a number) values. Since checking the values in each cell would be computationally expensive, we've instead moved the list of supported datasets to be stored in the database. A future enhancement (#823) will ensure that this is properly set for every existing city. Closes #822
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In #822 we plan to add a new field to the
Citymodel which notes which datasets (LOCA/NEX-GDDP) apply to each city.Once that is in place, we should add a command to backfill that information for every city already in the DB.
One idea for how to determine that is to check if the city is in the continental united states, and if not assume it does not have
LOCAdata.Depends on #822.
The text was updated successfully, but these errors were encountered: