I saw this question and answer while researching how metadata works and wondered if I am reading it correctly: https://developer.milestonesys.com/s/question/0D50O00004UbM1nSAF/metadata-and-timestamps
This part of the answer in particular:
“So if you put in metadata fitting 11 am, you cannot put in metadata later fitting 10 am. You can only enter metadata fitting a later time. Metadata is perfect for a flow of analytics data but not for other events where chronological order is not possible.”
We have analytics service that processes live frames and forwards bounding box metadata along with text descriptions specific to that camera frame. For instance, the analytics metadata may specify the location of a bounding box over a car and in the Description text specify the car is a “Toyota”. If we later realize we are incorrect, and the car was actually a “Ford”, does the functionality exist in the system to look up that already stored metadata (perhaps by camera FQID and timestamp), and change that metadata to specify that the car is a “Ford”. If not, is there another approach we can take which will give us the speed of streaming metadata (so that we can draw overylays fast enough to be shown in the Live view), with the ability to later go back and correct that data if it is wrong?