You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently validate that all the right files are there, but we're not checking that the information in the upload actually corresponds to the neighborhood it's being uploaded for.
I think it should be feasible to check while importing the results geometries that they intersect with the geometry stored on the neighborhood (e.g. intersect import_layer_map.layer.extent and job.neighborhood.geom_simple after loading the layer.
It would make sense for the validation check to be optional, since we don't need it when importing geometries during normal analysis runs. We could also do it for only one of the imports (ways or census_blocks but not both) to slowing the import down for no additional benefit.
The text was updated successfully, but these errors were encountered:
We currently validate that all the right files are there, but we're not checking that the information in the upload actually corresponds to the neighborhood it's being uploaded for.
I think it should be feasible to check while importing the results geometries that they intersect with the geometry stored on the neighborhood (e.g. intersect
import_layer_map.layer.extent
andjob.neighborhood.geom_simple
after loading the layer.It would make sense for the validation check to be optional, since we don't need it when importing geometries during normal analysis runs. We could also do it for only one of the imports (ways or census_blocks but not both) to slowing the import down for no additional benefit.
The text was updated successfully, but these errors were encountered: