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
Context: Adding an image file to the bucket gs://street2sat-uploaded triggers the street2sat prediction pipeline which adds a new row to the Firestore database with the object detection predictions from that image.
Issue: If an image file is deleted from the bucket gs://street2sat-uploaded the associated row of predictions for that image file remains in the Firestore database. This becomes an issue when image files have been moved (copied then deleted) which results in new duplicate prediction rows in the database.
Potential solution: Create a python Google Cloud function triggered on image file removal that would also remove the associated prediction row from the Firestore database.
The text was updated successfully, but these errors were encountered:
@hannah-rae do you recall if the existing problems (gs://street2sat-uploaded/2021-07-08-T1, gs://street2sat-uploaded/USA/2021-08-20-croptour) are meant to be removed or just moved to a different folder?
Context: Adding an image file to the bucket gs://street2sat-uploaded triggers the street2sat prediction pipeline which adds a new row to the Firestore database with the object detection predictions from that image.
Issue: If an image file is deleted from the bucket gs://street2sat-uploaded the associated row of predictions for that image file remains in the Firestore database. This becomes an issue when image files have been moved (copied then deleted) which results in new duplicate prediction rows in the database.
Potential solution: Create a python Google Cloud function triggered on image file removal that would also remove the associated prediction row from the Firestore database.
The text was updated successfully, but these errors were encountered: