Google Mars HiRISE base images for Opportunity Options

[elakdawalla]

Because it has become a forum FAQ, I've created this sticky thread containing information on where to obtain new base images for Opportunity's traverse for Google Mars, and for discussion on creating new ones. I will continue to add links to new base image layers to this first post as they become available.

New users: Download this 4-MB kml file and open it in Google Earth
Then go to the last post in the Opportunity Route Map thread for the latest traverse map
You need to download the new KML file each time in order to follow Opportunity's peregrinations.

Google Mars comes with a color base image mosaic created from HRSC imagery. In addition, there is an inset full-resolution HiRISE image covering the area from the landing site at Eagle crater, through Victoria, up to the point between sol 2040 and 2041 (just west of Mackinac) where Opportunity drove off the map.

Unfortunately, this Victoria crater HiRISE layer included within Google Mars is not perfectly registered to the HRSC base map. As far as is known, there is nothing to be done about that. Both John Cody's image layers and Eduardo Tesheiner's traverse maps are aligned with the inset HiRISE layer included with Google Mars, NOT to the HRSC base map.

In June 2009 SFJCody posted a reduced-resolution mosaic of HiRISE tiles that cover the entire future traverse area including Endeavour's rim. I have made some small modifications to that map and have hosted it in a single file here (17 MB). Download the file, run Google Earth, select the Mars view, and File>Open the KMZ to view it.

In September 2009 SFJCody posted another HiRISE base image, this one at full resolution, covering the Western Route and reaching not quite all the way to Santa Maria. Here is a link to the kml file (4 MB). Here is a link to a zipped version if you'd prefer to have it locally (256 MB) and I also wrote a blog entry about it.

During the discussion below, in late 2010, I created a small tile that covers just the immediate area around Santa Maria. Here is a link to the kml file covering that region.

In February 2011 Eduardo Tesheiner provided another set of base images covering the area from Santa Maria to Endeavour's rim. Here is a link to the kml file. If you would like to work from a local copy, you can download this 75 MB zip file and unzip it to a folder on your drive, then open the file PSP_010341_1775_RED.kml within it.

All three base images can be loaded at once using this kml file (the same one that is linked to at the very top of this post).

[KrisK]

Could you detail it a little bit?

Here you can see result: http://www.flickr.com/photos/55907406@N08/...320902/sizes/m/

Finally I decided not to use MapTiler. Instead I wrote my own bash script to create super_overlays. The following link was very helpful:
http://code.google.com/intl/pl/apis/kml/do...l#superoverlays
At this stage I can say that I almost there:

http://www.flickr.com/photos/55907406@N08/...795813/sizes/m/
As you can see there is a brightness difference between tiles. Have to think what is the origin of the problem...

Below is the area (size 2^n) that I want to overlay in GE:
width = 16384
height = 3x16384
so I have three squares 16384x16384. Currently I work with the first square.

That's due to small differences in the lat/long coordinates you are using (in relation to the map I made). I can provide you with some data that should solve it, if you want.

Yes please ...Previously I made the alignment mostly by hand now I have the following strategy:
1. take N,S,E,W out of LBL for full HiRISE product....DONE
2. recalculate N,S,E,W for my cropped area....DONE
3. add/subtract deltaLAT, deltaLON to perfectly match the existing overlay...TBD

So I suppose your data will allow me to finish step 3 right?

[Tesheiner]

Mmm, more or less.
I'm providing some of the data I used to create the 8k x 8k tiles you already see on Google Mars and are hosted by TPS. So, if you use them and extrapolate the coordinates to the 16k x 16k tiles you want to create, they should match 100% with the current map. Note that I'm not saying that they are accurate (they aren't); they are only good for creating new maps matching with the current ones.

Lat/Long coordinates of PSP_010341 upper left corner: -2.07473360826446, -5.44490800928163
dLat/dLong of a pixel on the original picture: 4.21926255562616E-06

[KrisK]

Lat/Long coordinates of PSP_010341 upper left corner: -2.07473360826446, -5.44490800928163
dLat/dLong of a pixel on the original picture: 4.21926255562616E-06

Thanks for the numbers. They were very helpful. It looks I have a perfect match:

http://www.flickr.com/photos/55907406@N08/...683084/sizes/m/

Btw, asking out of curiosity...in LBL we have: MAP_RESOLUTION = 237098.79009322 <PIX/DEG> which gives:
1/237098.79009322=4.21765121452889e-6 but we are using 4.21926255562616e-6
Why is there a difference?


Oh and the problem with the brightness among tiles was caused by Google Earth. Somehow GE had problems using png's which I was creating using Image Magick "convert" program. Switching to jpg's resolved that issue.

Anyway...FINISHED!!!

http://www.flickr.com/photos/55907406@N08/...292143/sizes/m/
http://www.flickr.com/photos/55907406@N08/...842018/sizes/m/

Zipped kml's download link:
https://rapidshare.com/files/2039227902/end...ur_west_rim.zip
Edit: added another link just in case...
http://hotfile.com/dl/118744535/aaffb88/en...st_rim.zip.html

The only missing thing is the black area which could be removed. I don't know but maybe I'll do it somewhere in the future.

[Zeke4ther]

Great work! Well done!

[Tesheiner]

Btw, asking out of curiosity...in LBL we have: MAP_RESOLUTION = 237098.79009322 <PIX/DEG> which gives:
1/237098.79009322=4.21765121452889e-6 but we are using 4.21926255562616e-6
Why is there a difference?

As I said before, the data may not be accurate but is the one you have to use to match with the previous maps.
IIRC, I first calculated that value when attempting to match my version of ESP_011765 (the one covering the western detour) using MapTiler to SFJCody's version of the same map, which in other hand was already registered to the background covering Victoria embedded in GE. Later on, that value was used on subsequent maps to keep them matching together.

[Ross Beyer]

As I had mentioned a long, long time ago, we (the Ames Planetary Content team) were working on constructing new HiRISE/CTX overlays in the Google Earth client for the Opportunity route. We're far enough along that I want to have you guys take them for a spin so that I can get your feedback.

The attached KML file has NetworkLinks that point to our servers at Ames.

As far as geo-position goes, we decided to leave Victoria Crater where it is, and adjust the surrounding images. At some point in the future (I've been told "after the mission is over" as a time frame), there will be a giant geolocation solution by members of the MER team, at which point we'd move everything to be consistent with that, but its far enough in the future that I'm not gonna worry about it right now.

Also, the HiRISE image that covers the Endeavor rim isn't just any HiRISE image, but an ortho-image made from a HiRISE terrain model, and if things work out the way that I want them to, by the time this basemap makes it into the client (end of summer? fall at the latest, I hope), the HiRISE terrain will be in there, too.

Attached File(s)

 Opportunity_Traverse_2011.kml ( 963bytes ) Number of downloads: 1161

 

[hendric]

Works very well from here.

[Tesheiner]

From here too. It runs smoothly through the different levels of detail.

On the topic about geo-positioning there are, obviously and expected, differences with the maps we are using right now but it wouldn't take too much time for me to adjust my record of the route to this new HiRISE background; I only need to reposition some 15 "control points" I currently use on the map and all route points and ground features would be automatically aligned to the new background.

[brellis]

It's always like Christmas morning surfing through the updated images on Google Mars. Thanks Ross, Tesh et al!

[CosmicRocker]

... if things work out the way that I want them to, ... the HiRISE terrain will be in there, too.

That would be truly awesome. I can hardly wait.
Many thanks to you and your team for the excellent work.

[Ant103]

That's amazing ! Excellent work !

[Robert S]

Fantastic job!!!!

[tim53]

As I had mentioned a long, long time ago, we (the Ames Planetary Content team) were working on constructing new HiRISE/CTX overlays in the Google Earth client for the Opportunity route. We're far enough along that I want to have you guys take them for a spin so that I can get your feedback.

The attached KML file has NetworkLinks that point to our servers at Ames.

As far as geo-position goes, we decided to leave Victoria Crater where it is, and adjust the surrounding images. At some point in the future (I've been told "after the mission is over" as a time frame), there will be a giant geolocation solution by members of the MER team, at which point we'd move everything to be consistent with that, but its far enough in the future that I'm not gonna worry about it right now.

Also, the HiRISE image that covers the Endeavor rim isn't just any HiRISE image, but an ortho-image made from a HiRISE terrain model, and if things work out the way that I want them to, by the time this basemap makes it into the client (end of summer? fall at the latest, I hope), the HiRISE terrain will be in there, too.

Hi Ross:

I just completed a new basemap of CTX, MOC and HiRISE images in Arcmap that I'll be using for my localization work on Opportunity (I call this "HiThere!"). This map covers all of our traverse from Eagle Crater through Cape York, as well as all of Endeavour and Iazu Craters (since we can see so much of the interior of Endeavour, and Iazu is on our horizon). I first georeferenced the CTX low emission angle images to the HRSC and MOLA DEMs, then tied the HiRISE images to them (and each other, where they overlap). For Endeavour, there is still an annoying gap in the HiRISE coverage just east of center, so I used a couple of MOC images (3m/pixel) to fill that gap. Next step will be to correct the shading from one image to the next so the seams don't detract from the morphology. I've done this for the CTX background mosaic already, and I'm in the process of adjusting the HiRISE images. Next step will be to tile up and get the basemap into our planning software. But once that's done and the route is on it, exporting the path to applications like Google Mars ought to be straightforward. Much sooner than "after the mission is over", I'm hoping.

-Tim.

[elakdawalla]

(I call this "HiThere!")

Apart from that, I applaud the rest of your post and hope to see the product before the mission is over!

[tim53]

Apart from that, I applaud the rest of your post and hope to see the product before the mission is over!

This map is now completed. Stay tuned, as Trent Hare will be posting links to it on the USGS website.

While I consider the map "completed", I reserve the right to continue to update it as better/more images are acquired and I can georeference them to the base MOLA and HRSC topography maps. But I need to get cranking on the Gale basemap for localization and planning during Ops!

-Tim.