Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warp - needs to test serial number within input cnet against input files #1495

Closed
ascbot opened this issue Feb 12, 2019 · 1 comment
Closed
Labels
automatically_closed Issue closed by a bot due to inactivity bug Something isn't working

Comments

@ascbot
Copy link
Contributor

ascbot commented Feb 12, 2019


Author Name: Tammy Becker (Tammy Becker)


warp does not test against the serial numbers that exist in the input cnet file.

Details:
There is currently no testing for serial numbers. All assumptions are completely based on a 'coreg' output netfile. There is no cross-checking for a serial number in the input net and the input image. There is also no cross-check between a reference measure (coreg-match input file) and a non-reference measure, this would be bad if more than two measures (images) exist in a single point within the network.

(This is dangerous, especially now that the qview-match tool allows any number of files to be in a 'net' file).

By 'net' file, this is not the same a control-suite net file used with qnet/jigsaw. This type of net file is focused on pixel locations without lat/lon's associated. This type of netfile is most often the output of 'coreg' (where coreg used to be the only app to automatically generate a net file for warp, but now the qmatch match tool allows interactive creation of such a net file (or editing of the coreg output net).

The serial numbers might or might not use the instrument group. This type of net file and applications such as warp do not use a camera or sensor model at all.

@ascbot ascbot added the bug Something isn't working label Feb 12, 2019
@ascbot
Copy link
Contributor Author

ascbot commented Sep 1, 2020

I am a bot that cleans up old issues that do not have activity.

Happy Birthday to this issue! 🎂

Unfortunately, this issue has not received much attention in the last 12 months. Therefore, I am going to close it. Please feel free to reopen this issue or open a new issue sometime in the future. If this issue is a bug report, please check that the issue still exists in our newest version before reopening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automatically_closed Issue closed by a bot due to inactivity bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant