Jump to content
PDS Geosciences Node Community

All Activity

This stream auto-updates     

  1. Yesterday
  2. Last week
  3. Mars Exploration Rover Release 53

    Data from Release 53 of the Mars Exploration Rover mission is now online at the PDS Geosciences Node. This release includes APXS, Atmospheric Opacity, MI, Navcam, Pancam, and Rover Motion Counter data from sols 4591 through 4680 for the Opportunity rover.
  4. Repository for terrestrial geology applied to Mars

    Michael, Please reply to me at geosci@wunder.wustl.edu and tell me more about your project, including the science content and format of data products. Thanks, Susie Slavney
  5. I am the PI on a proposal to NASA PSTAR for a project that will collect digital data (predominantly still images and video) from Earth-based geological studies. I estimate about 3 Tb of data will be collected over 3 years. Our data will address operations of the Mars 2020 mission. I am wondering if the PDS Geosciences Node might be a suitable archive for our data.
  6. Hi Emily, You don't mention which of the three Mars Climate Sounder (MCS) data sets you are using. If you are looking for surface temperatures, you probably want to use the MCS DDR (Derived Data Record) data set. The primary documentation for this data set is here: https://atmos.nmsu.edu/PDS/data/MROM_2128/DOCUMENT/DP_SIS.PDF. To see if this is the right one, look at Table 2, which describes the columns in the data table. These data tables are ASCII text, so you can open them in any text editor or even in your browser. The columns are also described in a software-readable way in the "format files" in the LABEL directory of the archive, here: https://atmos.nmsu.edu/PDS/data/MROM_2128/LABEL/. The other two MCS data sets are the RDR (Reduced Data Record) and EDR (Experiment Data Record). EDRs are raw data from the instrument sensors. RDRs are calibrated versions of the EDRs. Finally, the DDRs contain data converted to geophysical units, derived from the RDRs. For each of the three data sets, you'll find an overview of its contents in the file CATALOG/DATASET.CAT, a detailed description in the file DOCUMENT/DP_SIS.PDF, and complete column descriptions in *.FMT files in the LABEL directory. All these files are on the MCS archive volumes, which are hosted at the PDS Atmospheres Node at http://pds-atmospheres.nmsu.edu/data_and_services/atmospheres_data/Mars/Mars.html (scroll down to the MRO section). I hope this is enough to get you started. Susie Slavney
  7. Hello, I am currently trying to find examples of the surface temperature on Mars, as taken by the Climate Sounder on the MRO, for the 3rd of August 2015. However, I'm very new at working with this data set and it is proving tricky. Firstly, there are a range of columns which mention "temp" in their title, however no amount of internet searching will tell me which one relates to actual ambient temperatures. Secondly, there should be some mention of Channels (aka Channel A. being measurements closest to the ground) but there isn't, so I'm not sure how to work out which data entries are from the surface. Thirdly, of all the temperature-related columns, none of them have data which varies by more than 1 degree throughout the 24 hour period, which suggests that they are actually referring to instrument temperatures rather than planetary temperatures. All in all, it is proving a tad difficult. The dataset was downloaded from Mars Orbita Datal Explorer. Any help at all would be greatly appreciated. A huge thank you in advance, Emily
  8. September 19th, 2017 - More MEX HRSC RDR Version 3 Data Loaded into ODE HRSC new radiometrically calibrated (RDR version 3) image data have been loaded into ODE, with coverage through August 17th, 2016 (Orbit 10-16000). See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
  9. M3

    First look in the Orbital Data Explorer's User Manual section on the M3 instrument, here: http://ode.rsl.wustl.edu/moon/pagehelp/quickstartguide/index.html?isros_chandrayaans_m3.htm. At the bottom of the page are some resources for finding and working with M3 data, including the M3 ENVI User's Guide. If you can't find the information you need, please contact the PDS Imaging Node, who archives the M3 data, at https://pds-imaging.jpl.nasa.gov/feedback.html.
  10. M3

    How to georefernce M3G20090608T000122_V01_RFL.IMG using envi GLT
  11. Earlier
  12. LRO Release 31

    Release 31 of Lunar Reconnaissance Orbiter data is now online at the Geosciences Node. This release includes new data acquired between March 15, 2017, and June 14, 2017, along with some revisions to previously released products, for CRaTER, Diviner, LAMP, LEND, LOLA, and LROC. Data can be found on the Geosciences Node LRO page. The Lunar Orbital Data Explorer allows searching and downloading of LRO data.
  13. September 14th, 2017 Release 7 of MRO CRISM MTRDR (Map-projected Targeted Reduced Data Record), TER (Targeted Empirical Record), and TRDR (Targeted Reduced Data Record) browse and extras data fills in data from 2006_273 through 2012_142 has been loaded into ODE. See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
  14. This is the seventh release of CRISM MTRDR and TER data products. In addition, the volumes MROCR_2101 through MROCR_2106 are updated with new TRDR browse and extras data products.
  15. ODE - MRO Release 42 Loaded into ODE

    September 8th, 2017 - - - Updated MRO SHARAD EDR products from December 6th, 2006 to February 21st 2015 Please see ODE Mars Holdings – https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
  16. MRO SHARAD EDR data released

    SHARAD EDR data from the ASI team members have been posted, covering previous MRO releases 23, 24, 33, and 34 (through Feb. 21, 2015). The team is recovering data from deliveries that were missed due to a hiatus in ground operations. See ERRATA.TXT for details. The data are available on the PDS Geosciences Node's SHARAD page.
  17. September 7th, 2017 - New OMEGA EDR data for extended mission 5 loaded into ODE Updated MEX OMEGA EDR data products released through June 19th, 2016 (Orbit 15799). See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
  18. ODE REST Python examples

    The ODE team has posted three simple Python examples of querying the ODE REST interface. These scripts are found in the forum's download section. https://geoweb.rsl.wustl.edu/community/index.php?/files/file/26-ode-rest-python-examples/
  19. ODE REST Python Examples

    Version 1.0.0

    4 downloads

    Attached are three simple Python examples of querying the ODE REST interface. odeProductCount_Python27.py - A Python 2.7 example of querying the ODE REST interface for the count of products of particular product type. The results are written to the command prompt interface. odeProductCount_Python36.py - A Python 3.6 example of querying the ODE REST interface for the count of products of particular product type. The results are written to the command prompt interface. odeREST_FileDownload.py - A Python 3.6 example of querying ODE for products of a particular mission/instrument/product type. The product files of the first 10 query results will be downloaded to the local machine.
  20. User Bobo Xi August 30, 2017 9:06 AM Dear Prof. I'm a postgraduate in xidian university,china. I'm research in the hyperspectral imge of mars at present and have downloaded the CRISM data on the PDS Geosciences Node. The datatype of the data is MTRDR and ID is “frt0000474a_07_if164j_mtr3”. Then,I have two problems with it : 1.First, I have read the "CRISM Data Product Specification", it said that the TER datas is "A spatially reconciled, full spectral range I/F targeted observation central scan image cube in the IR (L-detector) sensor space that has been corrected for geometric, photometric, atmospheric, and instrumental effects." and "MTRDRs are map-projected versions of TER data products." Then,I want to confim that does that mean that the MTRDR datas have calibrated for geometric, photometric, atmospheric, instrumental effects and map-projected ? 2. Second,the attachment of this email is the Browse Image of the MTRDR data I have dowmloaded . My question is that what is the meaning of the curve below ?In addition, I have open the MTRDR data by envi5.1 and why the spectral curve almost stay the same for each pixel in the image ? I'm feeling very confused and looking forward to your reply! Best regards! User Seelos, Frank P. August 30, 2017 1:38 PM > I want to confim that does that mean that the MTRDR datas have calibrated for geometric, photometric, atmospheric, instrumental effects and map-projected? This is correct. The only structural difference between the sensor space TER spectral image cube (the IF product) and the corresponding map-projected MTR spectral image cube is that radiometrically questionable bands have been removed from the MTR. The TER image cube has 545 bands and the MTR has 489. > Browse Image of the MTRDR ... My question is that what is the meaning of the curve below The plot shows the scene median and [5, 95] percentile envelope spectra. > the spectral curve almost stay the same for each pixel in the image The spectral variability in this scene is subdued by a relatively dusty atmosphere. The TER/MTRDR processing accounts for atmospheric gas absorptions and the relative geometric/photometric effects of aerosol scattering, but the data are top-of-atmosphere corrected I/F, not model ground reflectance. User Bobo Xi August 30, 2017 11:14 PM Hello, Thanks for your reply. but exuse me, I'm still not clearly understand my last question. In other words,if I want to make mineral classification in the image by using the material's spectral variability, does that mean that I have to use the TRDR datas and calibrate them myself by using some ground reflectance model rather than directly using the MTRDRs? User Seelos, Frank P 2017-09-01 03:40:48 If you’re interested in quantitative mineral abundance modeling then the retrieval of surface spectral reflectance through some type of surface/atmosphere separation or atmospheric correction will be required – either the TRDRs or the TERs/MTRDRs could be the starting point in this case. However, mineral identification, classification, and investigation of scene spectral variability are definitely possible with corrected I/F data – the majority of the CRISM-derived results in the literature used this type of workflow. Thanks, -Frank User Bobo Xi September 03, 2017 9:13 PM Sorry, I have been busy with something else and forgotten to write back. After seeing your reply I have totally understood, thank you very much!
  21. September 5th, 2017 - Re-releasing of the THEMIS VIS-ALB data from releases 0052-0059 (orbits 56800-65599) has been loaded into ODE. Please see ODE Mars Holdings – https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
  22. September 3rd, 2017 - MRO Release 42 Loaded into ODE. - Updated MRO CRISM EDR and CDR products from September 27th, 2006 to May 9th, 2017 - Updated MRO CRISM DDR products from September 27th, 2006 to May 8th, 2017 - Updated MRO CRISM LDR products from July 10th, 2009 to April 29th, 2017 - Updated MRO CRISM TRDR products from September 27th, 2006 to May 8th, 2017 - Updated MRO raw gravity data products released through October 21st, 2017 - Updated SHARAD Radargram data products released through 2017-02-16 (orbits 48202 through 49499). - Updated MRO MCS EDR, RDR and DDR products from September 15th, 2006 to April 30th, 2017 - Updated MRO CTX EDR products from August 30th, 2006 to March 1st, 2017 "There is no derived gravity data in this release. Previous releases of HiRISE data cover this period, and HiRISE's next three months of data are not all available yet." Please see ODE Mars Holdings – https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
  23. MRO Release 42

    Release 42 from the Mars Reconnaissance Orbiter mission includes new data for CRISM, SHARAD (U.S.), and Gravity / Radio Science. The data are online at pds-geosciences.wustl.edu/missions/mro.
  24. August 25, 2017 - ENVI header files have been loaded into ODE for MOLA topographic map products ENVI header files for the MEGDR image data products have been loaded into ODE. The ENVI headers can be downloaded from the data product search result page, along with the document MOLA_ENVI.PDF, which explains the use of the header files and other methods for providing correct map projection information to ENVI and ArcGIS. See http://pds-geosciences.wustl.edu/mgs/mgs-m-mola-5-megdr-l3-v1/mgsl_300x/extras/EXTRINFO.TXT for more information.
  25. August 25, 2017 ENVI header files for the MEGDR image data products have been provided in the EXTRAS directory of the MOLA MEGDR archive in http://pds-geosciences.wustl.edu/mgs/mgs-m-mola-5-megdr-l3-v1/mgsl_300x/extras/, along with the document MOLA_ENVI.PDF, which explains the use of the header files and other methods for providing correct map projection information to ENVI and ArcGIS. See EXTRINFO.TXT for more information. The ENVI header files and MOLA_ENVI.PDF can be downloaded from the data product search result page in ODE.
  26. In ENVI, you can assign map information to a PDS image based on values from the PDS label. 1. Download an image and corresponding PDS label file (.lbl extension) to the same directory. 2. Open the image in ENVI. It will not be map projected. 3. Select File > Edit ENVI Header and select the image. Click OK. 4. From Edit Attributes, choose Map Info... 5. Click Change Proj. 6. Unless you already have the correct lunar projection, create a new one (steps below assume projection does not exist). 7. Click New... on the Projection Selection dialog box. 8. Enter values based on label. For example, sphere radius 1738000 (notice in meters), projection type sinusoidal, 0 false easting and northing, 74 central meridian longitude. (False easting/northing not in the label.) 9. Save projection and map_proj file. Select newly created projection. 10. In the Edit Map Information dialog, enter values from the label. For example, image coordinate x,y of 1.5,1.5 (the upper left corner) might be 0,50 with pixel size of 400 m/pixel. Click OK to save map information and OK to save header. Due to a technical issue, the original comments on this blog post were lost. A transcription of the comments can be found below.
  27. Assigning Map Information to PDS Images in ENVI

    User Shashwat Shukla Apr 12 2017 05:07 AM Hi June, I am working on Chandrayaan-1 M3 Data. Product ID: m3g20090205t071411_v03_rdn I am trying to geo reference the data as the method you suggested in your earlier comments, but I am unable to find what should I enter in Central Longitude option in customized map projection settings. I changed the projection type to Sinusoidal, Sphere Radius: 1737400 Easting and Northing as 0 and still couldnt find what to enter for 'Longitude for Central Meridian'. For now, I entered 74 as you mentioned. Then in edit map information, Datum chosen was D_Moon_2000 as you suggested. What should I enter in X, Y Coordinates ? Pixel Size I am using is 140 m as Spatial Resolution of M3 in Global Mode of OP1B data is 140 m/pixel. Is this right? Kindly guide me in the above! PS: I am not able find any detail in label file. The label file I am using is : m3g20090205t071411_v03_l1b.lbl Thanks a lot for your time! User June Wang Apr 12 2017 02:23 PM Hi Shashwat Shukla, It looks other users may have similar confusion as you when working with Chandrayaan-1 M3 data in ENVI, so I put some tips here. A spectral radiance image cube label (*_L1B.LBL) is detached and points to the following L1B data products (Please see data product SIS file pages 20, 81 in https://pds-imaging.jpl.nasa.gov/data/m3/CH1M3_0003/DOCUMENT/DPSIS.PDF): "¢ the single multi-band image (*_RDN.IMG) and its respective detached header file (*_RDN.HDR), "¢ the pixel location data (*_LOC.IMG) and its respective detached header file (*_LOC.HDR), "¢ the observation geometry data (*_OBS.IMG) and its respective detached header file (*_OBS.HDR), "¢ the UTC timing data (*_TIM.TAB) Download all the *.loc, *.obs, *.rdn cubes together with the ENVI headers from ODE to your local drive. You can access the location and geometry information in the *.LOC and *.OBS files and relate it to the spectra of the *.RDN files using ENVI. Below link gives the instruction for basic viewing of an M3 *.img cube file using ENVI 4.3. Read those M3 cube file with high version of ENVI would have similar operations. https://pds-imaging.jpl.nasa.gov/documentation/Appendix_E_DPSIS_ENVI_Users_Guide.pdf note: In 'M3G20090205T071411_V03_LOC.HDR', it looks to me all the location data are in geographic lat and lons in degrees. There is no projection defined in the *.hdr. You can re-project the data to the Sinusoidal projection you defined. Central Meridian is the place where there is no distortion. Feel free to let me know if you need more help. Thanks, June User Shashwat Shukla Apr 13 2017 12:55 AM Hi June, I had linked all the display to access the location and geometry information in the *.LOC and *.OBS files and relate it to the spectra of the *.RDN file. I had come across another method of building GLT files and geo referencing through them. The process I followed in that is by choosing X as Longitude and Y as Latitude, and then keeping the input projection as Arbitrary with Unknown Datum and output projection as you suggested , i.e., Sinusoidal with Sphere Radius 1737400 m , False Easting and False Northing as 0 and Central Meridian as 74 (Unsure whether right or not). As you said that Central Meridian is the place where there is no distortion, how to know the exact value of that. Because I am using the value which you suggested but it might vary with datasets (Not sure). Kindly tell whether 74 which I am using is right or there is some file in which it is written ? And one more doubt, how to reproject the data when the input file is not geo referenced ? PS: Since the *_RDN.IMG file is not geo referenced, so reprojecting it to Moon Sinusoidal projection can come up with error. Thanks a ton for your timely assistance. Regards, Shashwat User June Wang Apr 13 2017 03:59 PM Hi Shashwat, It is not right to set 74 as the Central Meridian for the Sinusoidal projection. I didn't suggest this value before. I think it is just an example case that Jenn put together for users years ago. The Central Meridian of a Sinusoidal projection mainly depends on your own application. It is the place where you like it to have the least distortions. When you build the GLT in ENVI, you could choose Geographic Lat/Lon and D_moon_2000 for both the input and output as below figures. There are no data that could be free of errors. Uncertainties come from different sources such as instruments, measurements, processing methods and others. You could still reproject the data even it is not georeferenced, just with more uncertainties in the output. And the kind of projection depends on your own application and needs. Hope this will answer your questions. thanks, June User June Wang Apr 13 2017 04:02 PM Hi Shashwat, It seems I could not attach my screen shots in the above post. Feel free to let me know if you like me to send 'Geometry Projection Information' dialogue from ENVI to you by e-mail. Thanks, June User Shashwat Shukla Apr 15 2017 04:57 AM Hi June, I did by assigning Geographic Lat/Long and D_moon_2000, but still I m not getting the right output. It would be better if you share your 'Geometry Projection Information' dialogue with me. My email: sshashwat93@gmail.com And I could also share my results with you. Thanks a ton June! Regards, Shashwat User June Wang Apr 17 2017 06:51 AM Hi Shashwat, Please check your e-mail and let me know more details. Thanks, June
  28. Assigning Map Information to PDS Images in ENVI

    User Aeronstorm Dec 31 2016 05:00 AM Hi, I am trying to georeference, project and mosaic chandrayaan - 1, HYSI PDS 3 format files. It has a .qub and a label fle .lbl containing metadata. Do i need a separate grid file to georeference the raster ? What are the alternative softwares that can be used to finish the job ? It is an old post... But ,hey if anyone is hanging around .... help me. Thanks. User June Wang Jan 03 2017 03:05 PM Hi Aeronstorm, I haven't worked with Chandrayaan HYSI data before, but I would recommend ENVI for your work. ENVI works with multi-spectral and hyper spectral PDS data. It also includes geometric correction/registration, raster re-projection, and mosaicking tools. As for the grid, you can use it or not, depending on your own application. Feel free to let me know if I am wrong or if you have any difficulties with ENVI. Thanks, June User Aeronstorm Jan 03 2017 08:33 PM Thank you June. I did try the data with ENVI and it works fine. I need to know that if the polar stereo graphic projection technique mentioned above by you for LRO LOLA produts can be used with other Lunar satellite images. User June Wang Jan 04 2017 10:17 AM Hi Aeronstorm, Glad that ENVI works for you. The polar stereo graphic projection mentioned above should work with other Lunar data in ENVI. But please pay attention to below two points. 1) Three map projection files related to the definition of datum, ellipse and map projections were saved under the default system folder where ENVI was first installed. It varies on different machines and different versions of ENVI being installed. E.g., for ENVI 5.3 in my machine, it was at "C:\Program Files\Exelis\ENVI53\classic\map_proj" 2) you may need to change the parameters in the string in file map_proj.txt according to your own projection being used. "31, 1737400.0, 1737400.0, 90.000000, 0.000000, 0., 0., Moon North Polar Stereographic" is for Moon North Polar Stereographic projection "31, 1737400.0, 1737400.0, -90.000000, 0.000000, 0., 0., Moon South Polar Stereographic" is for Moon South Polar Stereographic projection In the string, 31 means Polar Stereographic projection in ENVI, 1737400.0 and 1737400.0 are the a and b value of an ellipse, (90.000000, 0.000000) degrees in (lat, lon) corresponds to (0, 0)m in a projected map. You may modified those numbers to apply for different projections you would like to use in ENVI. And it is not limited to Moon. Hope this will answer your questions. Thanks, June User Aeronstorm Jan 05 2017 02:16 AM Thanks June. Can i use the datum created as D_moon_2000 for other projections such as sinusoidal or should i create new datum file for other projections? User June Wang Jan 05 2017 09:42 PM In the string "D_Moon_2000, GCS_Moon_2000, 0, 0, 0", added to file datum.txt, 'GCS_Moon_2000' is the name of an ellipse defined in file ellipse.txt If you use the same ellipsoid for other lunar projections, you can use the same lunar datum, otherwise, change the datum accordingly. User Aeronstorm Jan 06 2017 02:42 AM Thanks June. I am trying to use sinusoidal projection for my satellite image. Should i change the sphere radius equal to one mentioned on the ellipse.txt? User June Wang Jan 06 2017 11:26 AM Would you please give me more information about the satellite image you are working on? e.g., instrument, product type, product ID etc. And if you can post your current projection string for your data, I can take a look. Thanks. User Aeronstorm Jan 07 2017 01:38 AM Thanks June. I am working on Chandrayaan M3 data. Product ID- M3G20090421T082045_V03_RDN. map_proj.txt - 16, 1734000.0, 276.331769, 0.0, 0.0, moonsinusoidal User June Wang Jan 09 2017 10:26 AM Hi Aeronstorm, Is '1734000.0' a typo? The radius should be 1737400.0. I am not sure ENVI works with longitude in the range of [0, 360] or [-180, 180]. If 276.331769 doesn't work for you, you can try to change it in the range of[-180, 180]. Otherwise, your map projection string looks fine for me. And you can use the same datum as above mentioned. thanks
  1. Load more activity
×