Orbiter-Forum  

Go Back   Orbiter-Forum > Far Side of the Moon > Spaceflight News
Register Blogs Orbinauts List Social Groups FAQ Projects Mark Forums Read

Spaceflight News Share news, stories, or discussions about government and private spaceflight programs; including ESA, ISS, NASA, Russian Space Program, Virgin Galactic, & more!

Reply
 
Thread Tools
Old 03-16-2017, 03:13 PM   #1
martins
Orbiter Founder
Default Mars Express/HRSC

The other day I attended the i-Mars Final Dissemination Event here at UCL (it's nice to find that your Uni shares interest in your hobby )

i-Mars is (or was) a project to use high-resolution imagery (mainly the HRSC datasef generated by Mars Express, but also locally CTX and HiRISE) to create co-registered 3D datasets including elevation and orthoimages. They specialise mainly on finding change (new impacts, moving dunes, dust devil tracks, polar ice falls, etc.), but also showed a few cool 3D movies of terrain flyovers.

This got me to look into the HRSC data to use for Orbiter, to replace the current MOC/MOLA data. Unfortunately HRSC currently has got fairly patchy coverage, and they don't seem to provide high-level data products so far, so I'll need to stitch the mosaics together myself. But certain scenic areas like Valles Marineris and Olympus Mons seem to be well-covered, so I'll try a local high-res treatment of Valles Marineris to see if this is feasible.
martins is offline   Reply With Quote
Old 03-17-2017, 02:23 AM   #2
llarian
Orbinaut
 
llarian's Avatar
Default

I haven't checked recently myself either, but is there any chance that Pavonis Mons is included in the Valles Marineris and Olympus Mons datasets?
llarian is offline   Reply With Quote
Old 03-17-2017, 12:16 PM   #3
martins
Orbiter Founder
Default

Quote:
Originally Posted by llarian View Post
 I haven't checked recently myself either, but is there any chance that Pavonis Mons is included in the Valles Marineris and Olympus Mons datasets?
The front page of the i-Mars site contains the current level-4 DTM coverage (actually from 2015, according to the caption). According to that, Pavonis Mons is not covered. In fact I may have been wrong about Olympus Mons as well.

Level-3 coverage is more extensive (75% of the surface according to another quote), but I think level-3 doesn't contain the stereo DTM data. I don't know if only a subset of the level-3 data is suitable for level-4 generation, or if they are simply still in the processing pipeline.

I am currently generating a global DTM mosaic from all the level-4 data I can find (up to orbit 6500) to see what is available. Might take me a while to download and process.

Edit: Level-5 coverage is even sparser. Level-5 contains the co-registered mosaics. (hopefully including seam removal). Currently there appears to be only a single area ("MC11E", identified on the i-Mars image) available at level 5. This area was of interest since it contains a number of landing sites.
martins is offline   Reply With Quote
Thanked by:
Old 05-15-2017, 05:00 PM   #4
martins
Orbiter Founder
Default

Just a quick update on this. It's taking a bit longer than expected (and I am feeling bad for neglecting potentially more pressing issues for this, but hey, it's my hobby ):

I have pretty much completed the HRSC elevation layer (using the current MOLA data to fill the gaps). This is looking quite reasonable, but may need more work. I am currently averaging the data from overlapping HRSC fragments, but it would be better to establish a quality ranking of the fragments and add them to the mosaic in order of quality (worst to best). Mars Express has quite an elliptic orbit, so the camera distance varies considerably. And since the data are generated from stereo images rather than radar distance measurements, image quality (lighting conditions, local weather) also affect the elevation data quality. I am in contact with a researcher at FU Berlin who is working on the HRSC data, and I got a quality ranking list for some parts of the surface which I will try for this.

The surface texturing will take more work. For a start, the amount of data is huge (12.5 m resolution for the panchromatic nadir images - my 2TB drive dedicated to Mars data is slowly filling up with the HRSC data).

The first processing step is a brightness correction against a global albedo reference. I am using my MOC mosaic for that: The global MOC mosaic is mapped into a low-resolution bilinear basis expansion. Each of the HRSC fragments is mapped into the same basis, the basis coefficients are shifted to fit the reference, and then used to adjust the low spatial frequencies of the full resolution HRSC fragment. In other words, at frequencies of the basis expansion and lower, the surface will look like the MOC reference, while higher frequencies will make use of the HRSC high resolution data.

Next, the fragments are feathered and added on top of the MOC background.

Adding HRSC colour channels is yet more work. The colour channels are lower resolution (50m) than the panchromatic channel, so I will need to employ some pansharpening mechanism. I am trying different colourspace conversions (HSV, HSI, HSL, LAB) to see which extracts the closest match to the nadir channel.

The other problem is that there is no real global colour reference to match the fragments to. According to a paper, the FUB guys are simply matching against a constant "Mars" colour at low frequency, but maybe I can do a little better and use the MDIM/Viking composite as a reference. Problem is, I am not too happy with the albedo on this image, so I might try to do another colourspace conversion and swap the intensity channel against MOC. I might need to do the entire mosaicking in HSI space anyway, because some HRSC fragments have a nadir channel but no colour channels.

To top it all, the original MOC data was mapped into an areographic reference frame, while MOLA and HRSC are using areocentric coordinates. For the current Orbiter Mars data, I mapped MOLA to areographic, but now it makes more sense to map everything to areocentric (and it better matches Orbiter's rendering geometry anyway). Also, I am now using elevation data referenced against the reference sphere instead of the geoid, so the oblate ellipsoid shape of Mars will be correctly represented.

TL:DR: I'm still crunching away at making Orbiter better
martins is offline   Reply With Quote
Reply

  Orbiter-Forum > Far Side of the Moon > Spaceflight News


Thread Tools

Posting Rules
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
Forum Jump


All times are GMT. The time now is 05:00 PM.

Quick Links Need Help?


About Us | Rules & Guidelines | TOS Policy | Privacy Policy

Orbiter-Forum is hosted at Orbithangar.com
Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright 2007 - 2012, Orbiter-Forum.com. All rights reserved.