I've heard from a few 311 users that they take a bunch of photos as they ride and then upload from home/office. We know that the location is pulled from the picture metadata, but the timestamp is pinned to the actual time of submission. DataSF is unable or unwilling to make changes to the submission time, which is problematic if we're hoping to perform time-sensitive analyses.
Let's investigate this "batch upload" use case and see if we can implement an improved version in our app. It may make sense to pull a "incident time" from the photo metadata and save it to our own backend.
I've heard from a few 311 users that they take a bunch of photos as they ride and then upload from home/office. We know that the location is pulled from the picture metadata, but the timestamp is pinned to the actual time of submission. DataSF is unable or unwilling to make changes to the submission time, which is problematic if we're hoping to perform time-sensitive analyses.
Let's investigate this "batch upload" use case and see if we can implement an improved version in our app. It may make sense to pull a "incident time" from the photo metadata and save it to our own backend.