Thank you, 11.5*2.54=29.21 cm, which is about what I've been measuring. Also, I've resolved the differences between the models.

For those interested, the AlgorimancerPG rangefinding and photogrammetry utility is available on my website at:

http://www.clarkandersen.com/RangeFinder.htm

Support for Phoenix is now working. For best results, use stereo pairs (look for L and R in the filename) from somewhere like:

http://www.nasa.gov/mission_pages/phoenix/..._archive_1.html


For example,

http://www.nasa.gov/images/content/229920m...8_10C96L1M1.jpg
http://www.nasa.gov/images/content/229924m...8_10C96R1M1.jpg

Note the L & R near the right of the file name. Strip-off everything prior to SS from the file title before attempting to open it with AlgorimancerPG, so that the files look like:

SS000EFF896228288_10C96L1M1.jpg
SS000EFF896228288_10C96R1M1.jpg

so that when loaded with AlgorimancerPG the left and right images will be automatically identified.

Be aware that there is no database support for Phoenix, so correct azimuth and elevation will not be available for the images. Also, I don't have the Sol/time conversion displayed correctly yet. Measuring distances to various objects works fine, as does finding the distances between objects (in an image pair).

One more thing... as of the latest version (4.0.5), the AlgorimancerPG utility displays the correct Sol and Local time when the Phoenix image was acquired. As near as I can tell everything is working great, and (unless someone finds a problem) I don't anticipate any changes unless/until an image tracking database becomes available. Range/coordinates are effectively referenced from the SSI (someone's going to ask). Hopefully we'll have some stereo images to play with sometime in the next couple of hours.