isis2pds Improperly Handling ISIS Mapping Group Radius Units

[ascbot]

---

Author Name: Kris Becker (Kris Becker)

Original Date: 2013-10-16
Original Assignee: Kristin Berry

---

isis2pds assumes the radius units are kilometers when no specific unit specification exists. This is not consistent with other usage and produces erroneous output (off by a factor of 1000) in the PDS product labels.

It should assume all radius values in the EquitorialRadius and PolarRadius keywords are meters unless otherwise explicitly provided.

[ascbot]

---

Original Redmine Comment
Author Name: Tammy Becker (Tammy Becker)
Original Date: 2013-10-22T19:08:26Z

---

Moved following text from the 'Impact' field to Notes area.

PDS formatted file products are critical to final archival and exchange of data to collaborators. Improper conversions of ISIS labels compromises our data provisions to our collaborators.

[ascbot]

---

Original Redmine Comment
Author Name: Kristin Berry (Kristin Berry)
Original Date: 2014-06-06T22:52:32Z

---

isis2pds assumes that input values are in kilometers when they don't have any unit label. Instead, it should assume that input values without a label are in meters. Output should still be in km as specified in: http://pds.nasa.gov/tools/ddlookup/data_dictionary_lookup.cfm?type=element&letter=M&q=

[ascbot]

---

Original Redmine Comment
Author Name: Kristin Berry (Kristin Berry)
Original Date: 2014-06-09T23:47:00Z

---

Built on prog 6 for testing.

[ascbot]

---

Original Redmine Comment
Author Name: Kris Becker (Kris Becker)
Original Date: 2014-06-24T19:59:16Z

---

Tested and it worked fine. Thanks...