For example, such software could display the actual coordinates on Mars of the pixels you are looking at, allow you to measure features directly in physical units, or stitch together images based on their absolute location on the planet. A number of GIS (Geographical Information Systems) applications use GeoTIFF; many on our science team have been waiting patiently for this feature to be rolled out.

We have already begun to produce RDRs with GeoTIFF, and they will start appearing in our weekly releases. At some point, a major reprocessing effort will be underway to bring this feature (and others) to all of our pre-existing products.

This brings up the topic of versioning: namely, how to tell which version of a HiRISE product you are working with.

Every HiRISE product has a line in the PDS label with the DATA_SET_ID. Every released HiRISE product to date shows that it has a DATA_SET_ID version of 1.0. The GeoTIFF RDR’s have a DATA_SET_ID showing version 1.1. This 1.1 version of our RDR processing also contains the updated color stretches described in a previous post. Later this year, that version number will likely be bumped up again when our improved calibration algorithms are put into production.

In addition, every HiRISE PDS product also has a line in the label with the PRODUCT_VERSION_ID. And every released HiRISE product to date has a PRODUCT_VERSION_ID of 1. When we make a new version of a released product, the version number will be incremented. If that new version is then released, it will replace the older version. We will only replace products with newer versions after a process of validation.

We’re halfway through a major update to our production pipelines that allows us to create, store, and reprocess these newer versions without effecting the released versions. This version number will only increase by integer amounts, and will never “skip”.