Hi Shane,
Since I use CatlogStarGenerator to make a synthetic reference frame for registration, would I even see this issue? Does that synthectic frame contain whatever information ImageIntegration needs?
This should not make any difference. The synthetic image will only be used as a reference image for registration; existing metadata in registered frames will always be preserved by the StarAlignment tool.
Another question: Since my subs are typically taken over several months from several different locations (up to 700 miles apart if there is a good star party happening), can ImageIntegration decide what to use for the values even when they are in the correct format?
Clever question. With the current implementation, ImageIntegration will compute the
average longitude and latitude of the observation location. In other words, it will compute the unweighted centroid of all geodetic locations found in the metadata of the entire data set.
While this may not be the optimal solution, from a strict point of view, it should work well for practical purposes. The most accurate solution should use some form of weighted average, taking into account the amount of signal contributed by each frame to the final integrated image as a first approximation, but this is probably overkill here.
The same solution is currently implemented for the approximate coordinates of the center of the image, i.e. the OBJCTRA and OBJCTDEC keywords generated in the final integrated image.
