Google Mars HiRISE base images for Opportunity |
Google Mars HiRISE base images for Opportunity |
Sep 28 2010, 09:23 PM
Post
#1
|
|
Administrator Group: Admin Posts: 5172 Joined: 4-August 05 From: Pasadena, CA, USA, Earth Member No.: 454 |
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). -------------------- My website - My Patreon - @elakdawalla on Twitter - Please support unmannedspaceflight.com by donating here.
|
|
|
Sep 28 2010, 09:33 PM
Post
#2
|
|
Administrator Group: Admin Posts: 5172 Joined: 4-August 05 From: Pasadena, CA, USA, Earth Member No.: 454 |
OK, now that I've posted the existing maps, here is a call for help with future ones. At her current pace, Opportunity will run off of SFJCody's high-resolution base map in about two months. He can't do the next map, and I tried but couldn't figure out how to make any region file generators work within the amount of time I allotted myself to spend on the project, so someone else needs to try to figure out how to do this!
The first step is to get the images. I can provide those, thanks to James Canvin, who processed the small piece of PSP_005423_1780 that covers the area around Santa Maria plus the entirety of PSP_010341_1775 which covers the rest of the way to Endeavour plus the entire western rim into 8192x8192 JPEG format subimages, each of which overlaps by 10% with the next. They can be downloaded here: Santa Maria (PSP_005423_1780, 33 MB) Endeavour 1 of 3 (PSP_010341_1775, 183 MB) Endeavour 2 of 3 (PSP_010341_1775, 199 MB) Endeavour 3 of 3 (PSP_010341_1775, 148 MB) Then, SFJCody had the following advice to me on how to get these into Google Mars: QUOTE (SFJCody) It's not complicated, but it is fiddly, time-consuming and sometimes annoying. James Canvin split the map-projected JP2 into 10% overlapping 8192x8192 chunks which I could overlay in Google Mars manually. I did this the standard way; temporarily making the overlaid image partially transparent in order to see the existing features beneath. Once each section was done I adjusted the brightness & contrast in photoshop to match the existing neighbouring HIRISE frame. There are brightness/contrast variations even within the frames so indivdual adjustment of sections was necessary to avoid any visible seams. Pieces that are on the edge of the HIRISE frame are set to GIF or PNG so that the black border can be made a transparent colour. Others are JPEG. As I went through this process of 'laying down tiles' I would switch off the earliest tiles, away from the 'work area' leaving only those immediately adjacent to the section I was about to add. That way I would have a reference for the alignment of the next section without overloading Google Mars by keeping too many 8192X8192 images switched on simultaneously. Note that, for the base map to be useful to Eduardo and all of us who follow his maps of Opportunity's progress, the images should NOT be registered to the color HRSC base map included within Google Mars, but instead to the low resolution HiRISE base map linked to in the first post in this thread.
Once all the full sized tiles had been created and georeferenced the next step was to turn the tile data (images and location references) into region files. I tried several methods and I'm not sure which is best: here are some of the references I used: http://code.google.com/apis/kml/documentat...#workingregions http://superoverlay.geoblogspot.com/ http://www.ogleearth.com/2006/10/super_overlay_t.html http://www.maptiler.org/ Sometimes the region files created by software turned out to be buggy (they would switch on and off bits of the image so that at some elevation ranges it looked like a chessboard. These ones I tried to create manually using the method outlined in the first reference. -------------------- My website - My Patreon - @elakdawalla on Twitter - Please support unmannedspaceflight.com by donating here.
|
|
|
Sep 30 2010, 01:33 AM
Post
#3
|
|
Senior Member Group: Members Posts: 1887 Joined: 20-November 04 From: Iowa Member No.: 110 |
The first step is to get the images. I can provide those, thanks to James Canvin, who processed the small piece of PSP_005423_1780 that covers the area around Santa Maria plus the entirety of PSP_010341_1775 which covers the rest of the way to Endeavour plus the entire western rim into 8192x8192 JPEG format subimages, each of which overlaps by 10% with the next. Are subimages of the path between Oppy's current location and Santa Maria available? They work much better for me than using the overlays SFJCody provided for GoogleMars which slows to a crawl when the high-res overlays are enabled. |
|
|
Lo-Fi Version | Time is now: 31st October 2024 - 11:01 PM |
RULES AND GUIDELINES Please read the Forum Rules and Guidelines before posting. IMAGE COPYRIGHT |
OPINIONS AND MODERATION Opinions expressed on UnmannedSpaceflight.com are those of the individual posters and do not necessarily reflect the opinions of UnmannedSpaceflight.com or The Planetary Society. The all-volunteer UnmannedSpaceflight.com moderation team is wholly independent of The Planetary Society. The Planetary Society has no influence over decisions made by the UnmannedSpaceflight.com moderators. |
SUPPORT THE FORUM Unmannedspaceflight.com is funded by the Planetary Society. Please consider supporting our work and many other projects by donating to the Society or becoming a member. |