Jump to content
PDS Geosciences Node Community

Susie Slavney

Geo Staff
  • Content Count

    209
  • Joined

  • Last visited

About Susie Slavney

  • Rank
    Geo Staff

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Geosciences Node data for InSight Release 7 are online at https://pds-geosciences.wustl.edu/missions/insight/index.htm. This includes data for RISE, RAD, IDA, and SEIS.
  2. Geosciences Node data for InSight Release 6 are online at https://pds-geosciences.wustl.edu/missions/insight/index.htm. This includes data for RISE, RAD, IDA, and SEIS.
  3. Jee, 1. Yes. 2. To assign each pixel a latitude and longitude, you will need the information in the IMAGE_MAP_PROJECTION part of the label, and also the file DSMAP.CAT in the CATALOG directory of the archive (or DSMAP_POLAR.CAT if you are working with an image in polar stereographic projection). DSMAP.CAT is a text file that gives the details of the simple cylindrical map projection, including the equations to go between latitude-longitude and line-sample. The IMAGE_MAP_PROJECTION keywords in the label give you the values to plug in to those equations for that particular image.
  4. Geosciences Node data for InSight Release 5 are online at https://pds-geosciences.wustl.edu/missions/insight/index.htm. This includes data for RISE, RAD, IDA, and SEIS.
  5. Jee, The IMG files are just binary arrays, nothing complicated. The label file that accompanies each image file gives the information your software needs to read the file. For instance, in LDEM.LBL in the IMAGE object, you'll see these lines: LINES = 720 LINE_SAMPLES = 1440 MAXIMUM = 21008 MINIMUM = -17758 SAMPLE_TYPE = LSB_INTEGER SAMPLE_BITS = 16 UNIT = METER SCALING_FACTOR = 0.5 OFFSET = 1737400. This tells you the image array has 7
  6. As June says, the data values are int16, signed 16-bit integers. I think your fread statement looks correct, although I am not a Matlab user. The PDS3 label says SAMPLE_TYPE = LSB_INTEGER, which is defined as a signed integer in the PDS3 data dictionary, although it would have been helpful if the label explicitly declared the samples to be signed. You may assume that LSB_INTEGER and MSB_INTEGER in PDS3 labels always mean signed integers. LSB_UNSIGNED_INTEGER and MSB_UNSIGNED_INTEGER are used when the values are unsigned.
  7. MISSING_CONSTANT is the value used to indicate that no actual data value exists; that is, the data value is missing. It does not make sense to apply the SCALE and OFFSET to these pixels. Pixels with this value should be omitted from computations. The value that indicates "missing data" is chosen to be outside the expected range of actual data values. The PDS3 Data Dictionary defines MISSING_CONSTANT as follows: "The missing_constant element supplies the value used to indicate that no data were available." (https://pds.nasa.gov/datasearch/subscription-service/SS-20200212.shtml). Examples
  8. The SKYV* files are in the EXTRAS directory, which means they are not part of the official LOLA PDS archive, and therefore not peer reviewed. They are extra material that users may find interesting or helpful as an addition to the standard data products. For the product you mentioned, SKYV_65N_240M, there is an equivalent IMG product in http://imbrium.mit.edu/EXTRAS/ILLUMINATION/IMG/. According to its label, it is a binary array of 6420 by 6420 16-bit LSB signed integers (LSB = least-significant-byte-first = "little-endian"). To go from the DN value to solid angle in steradians, you appl
  9. Hi, I don't see any product in the LOLA archives with the name SKYV_65N_240M_JP2. Can you give me the URL where you found it? In general, the JP2 files are JPEG2000 images. You won't be able to read them easily in MATLAB. In the LOLA archives, JP2 images are included only for ease of displaying the data. For every JP2 file there is a corresponding IMG file containing the same data in plain raster format, which is readable in MATLAB. The OBJECT = IMAGE section of the label (*.LBL file) tells you the information MATLAB needs to know to read the file, such as number of lines, numb
  10. We were contacted by a user trying to read SHARAD EDR data with ReadPDS3 for IDL, but that tool does not read the bit fields and three-byte integers in the data product, and as it is a PDS3 tool it is not likely to be developed further. We suggested the following tools for working with SHARAD data. There was a SHARAD/MARSIS workshop at LPSC in 2014. Presentations are on the Geosciences Node’s web site at https://pds-geosciences.wustl.edu/workshops/sharadmarsis_Mar14.html. There's one by Than Putzig about the CO-SHARPS Processing Boutique, software that reads SHARAD products (not clea
  11. The InSight SEIS data for Release 4, which had been delayed, are now available at the PDS Geosciences Node at https://pds-geosciences.wustl.edu/missions/insight/seis.htm.
  12. Data for InSight Release 4 are online at https://pds-geosciences.wustl.edu/missions/insight/index.htm. This includes data for RISE, RAD, and IDA. SEIS data have been delayed, but will be released by April 3.
  13. Some users of LRO Diviner data have asked why there are some data products with negative temperature values. For example: "I'm exploring the temperature data of the Diviner, I have downloaded TB (Brightness Temperature) data for 6,7,8, and 9 channels and I found negative values (in K) in a few of the images after conversion (TB= (DN * scaling factor) + Offset). This negative value is not possible in K, I'm unable to understand this." Answers from Diviner team members: "The shorter wavelength channels are noisy at low temperatures. Each channel has a minimum temperature below which it
  14. Many publishers of scientific research, including AGU, are now requiring authors to make their data available in a public repository as a condition of publication. (See AGU's policy here.) The Geosciences Node has been contacted by a few such authors asking whether the PDS will receive their data so that their articles can be published. In some cases the data set in question is a suitable candidate for a PDS archive, but usually it is not. If you are the author of an article for a journal that requires you to archive your data in a public repository, you may not wish to undertake the ste
  15. Data for InSight Release 2 are now available at https://pds-geosciences.wustl.edu/missions/insight/index.htm. This release covers data acquired between April 1 and June 30, 2019.
×
×
  • Create New...