Wonderful work Olivier and Damia!
Before moving on the MastCam Left panorama, I wanted to finish a colorized version of a NavCam mosaic taken on sol 2979. Here it is:

The Navcam L panorama taken on Sol 2995.
Added 4 images taken by the R Navcam.

Jan van Driel

Jan's panorama in circular form. We are heading back to the planned route up the mountain.

Phil

[quote name='Ant103' date='Jan 9 2021, 03:54 PM' post='249184']
Nice to see you Olivier

Bravo Damia Nice to have good news from you also

Thanks a lot Thomas : it's as if we were here

Thanks for the 3 french interpreters!...and the others too
I agree Damia, this site is at least very aesthetic

The mission update that covered sols 2996-2998 refers to a drive back to the strategic route and onwards to the sulfate unit on sol 2998.

From the set of engineering images returned by the rover on sol 2998, it would appear the drive was either cancelled or failed to execute. I didn't find a 'fhaz00190' which is indicative of an aborted drive, so it may have been cancelled. The sol 2998 engineering images show the robotic arm is still extended with the turret horizontal, and the MAHLI camera pointing towards the rover. So I'm guessing that there may have been either an arm fault during stowage, or possibly a MAHLI lens cap issue that they want to check out before they continue. A new mission update should follow soon

EDIT: The flight software detected a small but unexpected movement when un-stowing the arm, so it stopped and called home... Link

I'm still mourning the loss of the 'traverse map' and their insets with the 1 meter contour lines. Doesn't look like it's coming back, so I'm looking for another way of visualising the amount of elevation change after each drive.

We have xyz data in the JSON files for the images. X and Z appear to be encoded pointing data, if my assumption is correct then Y may be elevation?

Does anyone know of a simple way of converting the encoded Y value into either an elevation, a change in elevation since landing? Or even a change in elevation compared to the current 'site'?

The new interactive map allows users to export a GeoJSON file for the current sol, it provides the coordinates... eg sol 2995 = 137.398459, -4.734068, and a whole bunch of other useful data, but it does not report elevation.

I did not post this on the maps thread to keep the signal to noise ratio of that thread at a respectful level

I guess you mean the rover_xyz field in the v2 json files? I would guess that those are the local level (LL) frame coordinates (in metres) relative to the current site origin. For the LL frame +x is north, +y is east, and +z is to nadir. So the third component should be the vertical coordinate you're looking for.

Many thanks Fredk: Yes, it's the rover xyz field. I'll see if I can find the elevation of the LL for "site_index": 84

Here is the roughly assembled R-NavCam for sol 3000. Looks like a good drive Hope it help narrow down the location until a better stitch is posted.

EDIT: Just realised I missed a couple of top tiers

Good enough for a rough location, Paul - we are here (final map will follow in the proper place)

Phil

The NAVcam R view on Sol 3000.

Jan van Driel

There's also the locations.xml file (currently over 15MB). That lists x,y,z coordinates and x,y appear to be relative to landing, but unfortunately z appears to be relative to the current site. That file also includes lat,long and coordinates called mapPixelH,mapPixelV, though it's not clear what map those relate to.

I guess you could accumulate the z increments since landing, but that would probably also accumulate large errors.

Here is Jan's panorama in circular format.

Phil

Rover position in any reference frame you want can be computed from the SPICE kernels at https://naif.jpl.nasa.gov/pub/naif/MSL/kernels/spk/