Check if mission swaps need to be handled more

[jacobbieker]

Describe the bug

Prior to 2016, all the coordinates are the same for those Zarrs, and all the coordinates for the 2017 to present zarrs are the same, for the non-HRV data. There were a few mission swaps in 2016, in March and October, so might be worth more investigating how much those coordinates are off from each other and how to handle it.

Expected behavior

Non-HRV is the same coordinates, as its the whole top 3rd of the disk, HRV does move around, so that would be more expected.

Additional context

Here is the output from the User Notification Service of all mission swaps.
Results.csv

[jacobbieker]

Possible solutions would be to split the 2016 zarr at the mission swap, or swaps, into smaller ones that each have consistent coordinates. Or add in a second coordinate system that has the updated coordinates, and then its more up to the end user on when to use the new coordinates vs the old.

[jacobbieker]

We also should see if the coordinate changes are large or not. If they are quite small (seems like potentially only a pixel size) then it might not matter that much