Feature #92

Ability to view co-registered match points between random images

Added by Tammy Becker almost 8 years ago. Updated about 6 years ago.

Tracie Sucharski
Target version:
Software Version:
Test Reviewer:


We need the ability to view and modify match points that are measured between random images (i.e., no-camera model, mosaics, and/or level2 images). The ISIS3 coreg application will collect points between any two images of the same size, but unfortunately there is no way to view these points if the images are a pair of level2 images...or images that have no camera model.

Additional information:

This would be somewhat related to post 0000076 regarding registering color sets. In some cases the color sets need to be projected to level2 in order to correct camera distortion and timing offsets before co-registering.

One issue the Messenger team is having is with coreg and the inability to view the points to determine whey the sub-pixel registration is not working.

Related issues

Related to ISIS - Feature #76: Need an application to register stacked color sets Acknowledged
Related to ISIS - Feature #729: qmos won't display coreg output network Acknowledged
Related to ISIS 2 Ports - Feature #220: ISIS 2 applications to be ported to ISIS 3 Acknowledged


#1 Updated by Steven Lambright almost 8 years ago

"qmos" should be able to visualize these points. I think "qnet" and "qtie" are what needs updated. Is this correct?

  • Steven Lambright

#2 Updated by Tammy Becker almost 8 years ago

Some qnet/qtie functionality will be required to be able to modify the points and perform an interactive subpixel registration,etc. We used to have this functionality in Isis2-qview-"tvreg". Neither qnet or qtie will dispaly/accept points shared between 2-level2 images or 2-mosaics. This is not a cartographic or jigsaw network, it would be for the translate or warp applications...simply moving pixels (though, in the past we have wanted a translation of a co-reg pixel shifts to be translated to a ck-pointing shift in certain cases...a level1-to-level1/2 scenario). Also, This same type 'coordinate' collecting would (in ISIS2) be performed in measuring & storing the reseaus line/sample coordinates of a single image and fiducial intercept coordinates.

#3 Updated by Tracie Sucharski almost 8 years ago

Do you need this functionality in both qnet and qtie? If so, which would be the higher priority?

#4 Updated by Tammy Becker almost 8 years ago

I don't know that it matters which one, I suppose the app that is the most straight foward application for the developer 'point of view'. A coreg network might be between 2 images that are map projected, or no camera model at all. The current serial number for the output network of coreg is 'filename' whatever application can be change to handle this type of scenario...there is currently no work around with this..a single app would be the priority.


#5 Updated by Tracie Sucharski almost 7 years ago

This is being implemented as a new tool in qview.

#6 Updated by Tracie Sucharski almost 7 years ago

The impacted programs in Isis include qview.

Other applications that were changed:

coreg - Added control net keyword, NetworkId = Coreg

Other classes that were changed:

SerialNumberList - added a new Add method that takes a filename and an already created serial number.

ControlMeasure - Fixed bug in operator==

ViewportMdiSubWindow - emit new signal when user closes a cubeviewport

CubeViewport - emit new signal when user closes a cubeviewport

ChipViewport - added a new option which allows the two chips to be linked for zooming

ControlPointEdit - added 2 new methods, zoomFactor() and zoom(double zoomFactor)

#7 Updated by Tracie Sucharski almost 7 years ago

There is a version of isis in /work/projects/isis/latest/m00092 for testing. This was built on astrovm1.

#8 Updated by Tammy Becker almost 7 years ago

This tool is awesome! Thank you Tracie!!

Also available in: Atom PDF