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
It would be nice to have a single source of truth for this file on the backend. Or at least a single source within sql_app/. But I'm also not sure why we want a default database value defined in this model. I updated the raster being used by the worker, but did not update this default value, and it seemed to have no impact on anything. Should the worker be responsible for populating this database field?
The text was updated successfully, but these errors were encountered:
I believe the reason there is a default here is because it's not an optional field and during the creation process we don't have this input quite yet. So an error gets thrown. So perhaps the thing to do is remove the default value and make this an optional field? In both cases I think it'll end up being updated / overwritten.
There's likely a better workflow for this too but wanted to provide some context from my memory!
There are three places that reference the LULC file, the frontend, the backend-worker, and the sql_app.
I'm not sure that it makes sense for these three different components to reference a single source of the truth for the LULC filename because it is conceivable that in production these 3 components of the system will run on separate systems. @dcdenu4 , if you have a good sense of how to easily resolve this issue, feel free. Otherwise I don't think it's necessarily worth figuring out a solution.
The SQL app hardcodes a default database value for the source LULC raster path:
It would be nice to have a single source of truth for this file on the backend. Or at least a single source within
sql_app/
. But I'm also not sure why we want a default database value defined in this model. I updated the raster being used by the worker, but did not update this default value, and it seemed to have no impact on anything. Should the worker be responsible for populating this database field?The text was updated successfully, but these errors were encountered: