Cassini image database & updates, And notifications of PDS data releases |
Cassini image database & updates, And notifications of PDS data releases |
Dec 25 2006, 08:52 PM
Post
#1
|
|
IMG to PNG GOD Group: Moderator Posts: 2254 Joined: 19-February 04 From: Near fire and ice Member No.: 38 |
I have noticed that the January 1, 2007 Cassini PDS release is already available, see http://pds-imaging.jpl.nasa.gov/data/cassi...assini_orbiter/
I haven't downloaded all of the imaging data and I'm just beginning to digest what I already have but there are some beautiful images of Enceladus' plumes and satellite mutual events, images of the G and D rings and interesting images of Saturn's nightside and fairly good Iapetus images. Radar and VIMS is also available. All in all a nice 'Christmas gift' . |
|
|
Jul 31 2007, 10:18 PM
Post
#2
|
|
Administrator Group: Admin Posts: 5172 Joined: 4-August 05 From: Pasadena, CA, USA, Earth Member No.: 454 |
I'm returning to this project after a hiatus. I am now trying to figure out what information will be valuable to include in the browse pages. There is a huge number of fields available in the database. Here is what I am thinking about including; let me know if there are any fields I've missed that you can't live without.
FILE_NAME (e.g. W1481738172_2.IMG) TARGET_NAME (e.g. DIONE) TARGET_LIST (listed only if it is not "N/A" or identical to TARGET_NAME -- picks up other bodies that may be in frame, useful for mutual events) OBSERVATION_ID (e.g. ISS_00BDI_GLOCOL001_PRIME) <-- note you get information on which rev you're on in this one IMAGE_MID_TIME and IMAGE_MID_TIME_SEC_FRAC (e.g. 12/14/2004 5:30:21.716) -- is this OK or is START_TIME better? PIXEL_SCALE (e.g. 9.3249958) <-- in km TARGET_DISTANCE (e.g. 156875.92) <-- in km. this is redundant with the pixel scale but I think it's useful to show both. PHASE_ANGLE (e.g. 34.258215) <-- in degrees SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE (e.g. 11.092879 and 207.90797) <-- I prefer this to the CENTER_LAT and CENTER_LON because I think it makes more sense for images where the entire body is contained somewhere within the FOV. EXPOSURE_DURATION (e.g. 5600) <--need to state units INSTRUMENT_MODE_ID (listed only if it's been 2x2 or 4x4 binned, "SUM2" or "SUM4") INST_CMPRS_TYPE (LOSSY or LOSSLESS) Some questions: Can I get away with skipping INSTRUMENT_ID? Whether it's WA or NA will be clear from the file name. Are EMISSION_ANGLE and INCIDENCE_ANGLE important, or is there enough information contained in PHASE_ANGLE? --Emily -------------------- My website - My Patreon - @elakdawalla on Twitter - Please support unmannedspaceflight.com by donating here.
|
|
|
Lo-Fi Version | Time is now: 27th September 2024 - 10:11 AM |
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. |