Printable Version of Topic

Click here to view this topic in its original format

Unmanned Spaceflight.com _ Mars _ Multiply overlapping Mars imagery

Posted by: elakdawalla Sep 24 2010, 09:34 PM

A reader (Bill Green, a retired JPL guy who helped develop MIPL) alerted me to a recent article in IEEE Computer, http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?isnumber=5481918&arnumber=5481931 (subscription only, I'm afraid) that describes a method that they refer to as the "high overlap paradigm" for developing extremely high-resolution digital elevation models by using many aerial photos from many look angles. I contacted the paper's first author, Franz Leberl, to see if he was interested in attempting to apply his method to images from Mars, and the answer was: Yes, he's very interested. So my question is, where on Mars do we have sets of highly overlapping images? Here's what Leberl said he needed:

QUOTE
For a fully automated process that associates a surface elevation with each pixel, we need 5 or so images of each terrain point. If it is more, that is even better. If you have a focal length and location of the principal point, that would be helpful also. We do not need any data about the camera positions; but if you had such data, we would want to compare our results to those you have. And if you also had previous results in the form of a digital surface model created by traditional two-image stereo, we could use this as well for an analysis and comparison.
Can the hivemind of UMSF help me connect Leberl with the data he would need to make some seriously detailed DTMs?

Posted by: nprev Sep 24 2010, 09:49 PM

I bet that the Spirit & Oppy landing sites probably are by now the most imaged places on the planet @ hi-res. Not the most interesting locales from orbit to be sure, but they could serve as test/validation cases for the method.

Posted by: djellison Sep 24 2010, 10:11 PM

That was going to be my response - Spirit's landing site has been images, I think, about 10 times.

Posted by: Bjorn Jonsson Sep 25 2010, 12:12 AM

One possible problem though:

QUOTE
developing extremely high-resolution digital elevation models by using many aerial photos from many look angles

If most/all of the images were obtained with the spacecraft directly (or close to directly) above the landing site the viewing geometry might not be different enough from image to image. For traditional stereo I have found that as an absolute minimum the angles must differ by ~5 degrees with ~30 degrees being optimal for the software I'm using (example: subspacecraft longitude 0 degrees in one image and 30 degrees in another one). The lighting probably needs to be similar as well.

Posted by: PDP8E Sep 25 2010, 10:26 PM

one of the best off-nadir shots from MRO has to Heimdall Crater. The Hirise site has 4 other images of Heimdall and I am sure MOC and CTX have coverage of Heimdall.

Posted by: nprev Sep 26 2010, 03:03 AM

Hmm. MRO got just the one image of Phoenix' descent, right? Too bad there wasn't another taken a couple of seconds later. Lots of relative motion/look angle change happening there. I wonder if this method could generate a really detailed look at the chute, which would presumably be useful for future chute engineering.

Posted by: djellison Sep 26 2010, 07:49 AM

Because the landing site HiRISE images are targeted, they're often off-nadir. End result - you get quite a range of viewing angles.

Posted by: algorimancer Sep 27 2010, 12:48 PM

I would think that rover-level imagery would be ideal, especially for places like the Columbia Hills and Victoria crater -- lots of images from lots of perspectives.

Posted by: centsworth_II Sep 27 2010, 02:14 PM

QUOTE (algorimancer @ Sep 27 2010, 08:48 AM) *
I would think that rover-level imagery would be ideal...
The the study linked in the opening post is about getting the information from aerial views. So the question here is how to use this method with orbital images of Mars rather than how to get the best elevation data for places the rovers have visited.

Posted by: tanjent Sep 27 2010, 03:11 PM

Without having access to the article, couldn't one or more views from a high point be combined with the satellite views? IIRC this was the basis for revised estimates on the height of McCool hill and other topographic features from Spirit's vicinity. I guess the ability to factor in information from the horizon lines might be considered cheating in the problem they set out to solve.

Posted by: centsworth_II Sep 27 2010, 03:19 PM

QUOTE (tanjent @ Sep 27 2010, 10:11 AM) *
...I guess the ability to factor in information from the horizon lines might be considered cheating in the problem they set out to solve.
I wouldn't call it cheating, but I think the objective of using the method is to get 3D images of as much of the martian surface as possible. The rover-visited locals are a drop in that bucket, area-wise. May be good for ground truth testing of the method though.

Posted by: djellison Sep 27 2010, 06:33 PM

It would make far more sense to use the orbital imagery to produce the best DEM possible, THEN use surface data to verify the accuracy of that DEM and thus hopefully the reliability of the technique.

Posted by: Pertinax Sep 27 2010, 11:41 PM

A bit more cost efficient as well! smile.gif

-- Pertinax

Posted by: tharrison Sep 28 2010, 04:02 PM

CTX images the Spirit and Opportunity landing sites about once a month, baring unforeseen complications like safe mode, so there are about 30 overlapping images of each of them in the PDS at the moment. We also have about 800 sites that we monitor at a frequency from weekly to every few months for things like changes in surface features (i.e. dust devil tracks), gullies, dust-raising events, etc., so if a site that is more diverse topographically than the MER landing sites would be better for Leberl's method, I can look for one.

EDIT: Completely forgot about MSL—there are a bunch of overlapping CTX images of the candidate MSL landing sites, particularly of Gale.

QUOTE (Bjorn Jonsson @ Sep 24 2010, 04:12 PM) *
If most/all of the images were obtained with the spacecraft directly (or close to directly) above the landing site the viewing geometry might not be different enough from image to image. For traditional stereo I have found that as an absolute minimum the angles must differ by ~5 degrees with ~30 degrees being optimal for the software I'm using (example: subspacecraft longitude 0 degrees in one image and 30 degrees in another one). The lighting probably needs to be similar as well.


For CTX, we've found that the minimum roll angle difference needs to be 9° for anaglyphs, but for DEMs, the larger the roll is, the better. HiRISE prefers angles >15°. When we acquire stereopairs, we try to get both images in the pair within ~4 months of each other (or at the same time the following Mars year) to make sure the illumination conditions are similar. Of course, both the illumination conditions and angle difference needed for optimal DEMs depends on the topography of that area.

QUOTE (nprev @ Sep 25 2010, 07:03 PM) *
Hmm. MRO got just the one image of Phoenix' descent, right? Too bad there wasn't another taken a couple of seconds later. Lots of relative motion/look angle change happening there. I wonder if this method could generate a really detailed look at the chute, which would presumably be useful for future chute engineering.


With CTX we can't command images less than 15 seconds apart (I'm not sure if this is the same for HiRISE, but I think they require more time between images due to the sheer file size). Taking an image of the same place on the same orbit would also require some special maneuvering of the spacecraft, because we typically only slew rather than pitch and yaw (although every so often MRO is pitched for some CRISM observations).

Posted by: Zack Moratto Oct 5 2010, 11:00 PM

I wish this paper had more content. Yet that doesn't take away the multiview stereo coolness.

Does Leberl know that on Mars we don't use frame cameras? He's response seems to be that he expecting a simple pinhole model.

Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)