Merge Perimeter and (Fireline/New Pixel) so that the t column in Fireline/New Pixel matches the t_ed of perimeter with matching mergeID

Right now, the different fire layers (perimeter, fireline, and newfirepix) all acquire their "t" attribute from different sources. Fireline, and newfirepix will show a "t" attribute to lines up with the most recent algorithm execution. The "perimeter" dataset as a "t" the lines up with the "t_ed" columns of fire perimeters.

It would be more intuitive for the "t" in Fireline, and newfirepix to match the "t_ed" of the perimeter with a matching mergeID, so that "t" represented the time of the most recent observation.

changed due date to May 02, 2023

By Tempest McCabe on 2023-04-04T19:32:34 (imported from GitLab)

changed milestone to %API Hardening for public facing Veda-dashboard

@greg -- This is IMO the highest priority issue that I wanted to draw your attention to. Is this sort of merge something that has to happen on the Algorithm side, or on the API automation side?

By Tempest McCabe on 2023-04-04T19:35:32 (imported from GitLab)

added InProgress label

added MergeRequest label and removed InProgress label

closed