All Activity
This stream auto-updates
- Earlier
-
ODE - Mars Odyssey Release 63 Data Loaded into ODE
June Wang replied to June Wang's topic in Announcements
April 14th, 2018 --Loaded NS and HEND raw and derived data into ODE through October 17th, 2017 See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html. -
April 11th, 2018 - New MEX OMEGA and MARSIS data loaded into ODE - New OMEGA EDR data for the extended mission 5 and extended mission 6 have been loaded into ODE, with coverage through June 3rd, 2017 (Orbit 16996). - New MARSIS EDR and Subsurface RDR data for the extended mission 6 have been loaded into ODE, with coverage through June 20th, 2017 (Orbit 17053). See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
-
April 11th, 2018 - Mars Odyssey Release 63 THEMIS Data Updates Updated THEMIS standard data products (IREDR, IRRDR, IRBTR, VISEDR, VISRDR and VISABR data) from February 19th, 2002 to September 8th, 2017 Updated THEMIS geometry data products (IRGEO2, IRPBT2, VGEO2, and VISALB data) from September 28th, 2013 to September 8th, 2017 Release 63 of GRS data is delayed. The data would be available by April 15, 2018. See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html.
-
Hi Emran, There is no problem for the map context and CAT projected TRR3 image. The map context is coming from DDR which contains all lines including the key area and lines before it reaches key area. CAT map projection removes the lines before key area. If you run map projection in ENVI (on standard 5.4: Geometric Correction -> Georeference IGM), you can see all lines as following: But the lines CAT excludes is not useful and that's why CAT projection cuts these lines. Also please note: this is typical for the FRS and ATO data. Hope this answer your questions. Thanks, Feng
-
ODE - The April 2018 PDS release of MRO HiRISE data loaded into ODE
June Wang posted a topic in Announcements
April 9, 2018 – MRO HiRISE Updates - MRO HiRISE EDR, RDR, DTM and Anaglyph data products released through March 5, 2018 (Orbit 54,399) See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html -
Hi Feng, I use both ENVI 5.4 standard and classic version (whichever works well) and for this instance, I used classic one. I copied the three projections files and now it works, does not show any "Header Error'' message. However, the projected image does not match with map context. Hope to hear back from you soon. Thank you, Emran
-
Hi Emran, This is Feng. I am going to look into this. Have two questions: are you using ENVI 5.4 standard (not classic version)? Do you copy the three map projections files inside \CAT_ENVI\aux_files\crism_projection folder to your ENVi IDL folder (like C:\Program Files\Harris\ENVI54\IDL86\resource\pedata\user_defined folder)? Thanks, Feng
-
Dear all, I have been trying to use CRISM TRDR (trr3) image of ''FRS0002AEAB_01_IF167L_TRR3'' and ''FRS0003012C_01_IF167L_TRR3'' using CAT in ENVI. However, after standard corrections (ATP), I tried to project the image cube using ''Project Single Cube Data'' option. I got a projected image of bad shape which does NOT match with map context image and kml shape (attached the screenshots). I guess only a part of the image was projected. Also, CAT showed a message after performing the processes (attached also). Can anyone please let me know how can I fix the problem? Thank you, Emran
-
April 2nd, 2018 Updated Diviner RDR query tool database from July 5th, 2009 to December 15th, 2017.
-
Hi Subhabose, The ‘ellipse.txt’ file looks fine to me. In datum.txt, you had an extra ‘,’ in the last line. The correct string would be below. ‘D_Moon_2000, GCS_Moon_2000, 0,0,0’ In file ‘map_proj.txt’, I saw your definition for the Moon North Polar Stereographic projection. Since the maximum and minimum latitude for your data are 59.676 and -1.151 degrees, I would not suggest using the North Polar Stereographic projection.
-
Hi, I have attached the map_proj.txt, datum.txt and the ellipse.txt files with the updated strings. The image I am using is M3G20081229T022350_V01_RFL. datum.txt ellipse.txt map_proj.txt
-
March 27th, 2018 - 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 October 14th, 2016 (Orbit 10-16200). See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
-
Hi Subhabose, The product ID you gave was not a complete product ID. This value can be found in the product label file. From your ID I cannot tell what type of product you used. Is it the L0 raw data, or the L1B calibrated image, which has 3 versions, either Version1, V2 or V3? Or the L2 reflectance image? Please take a look of below help page. At the bottom of the right panel, you will see some additional M3 resource, including M3 ENVI User's Guide,working with M3 Data, Working with M3 L1B Data, M3 Data Tutorial and a few others. http://ode.rsl.wustl.edu/moon/pagehelp/quickstartguide/index.html?isros_chandrayaans_m3.htm Assuming you use the Version3 L1B calibrated image, e.g., ' M3G20081229T022350_V03_RDN', 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 as documented in the file 'M3 ENVI User's Guide'. And you can use GLT in ENVI to do the georeference. As for your question about map projection, from your screen copies, I can only tell the Datum you used are not correct. Because WGS-84 is used for Earth. If you can send me the strings that you have updated in three files datum.txt, ellipse.txt, map_proj.txt, I can dig more into your issues. Thanks, June
-
Data from Release 55 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 4771 through 4860 for the Opportunity rover.
-
Hi, The product ID is M3G20081229T022350. The projection used was Lunar Sinusoidal. I tried to follow the steps prescribed by you for assigning map information to PDS images in ENVI.
-
Hi Subhabose, Would you please give me more information about the M3 image you are working with? e.g., product ID and the projection name. I will take further look. Thanks, June
-
March 21st, 2018 - LRO Release 33 has been loaded into ODE. Updated LOLA EDR products from June 18th, 2009 to January 3rd, 2018 Updated LOLA RDR products from July 13th, 2009 to January 3rd, 2018 Updated LAMP EDR and RDR products from July 6th, 2009 to December 15th, 2017 Updated LEND EDR_SCI, EDR_HK, RDR_RSCI, and RDR_CHK products from June 18th, 2009 to December 14th, 2017 Updated LEND RDR_DLD and RDR_DLX products from June 27th, 2009 to September 4th, 2017 Updated Diviner EDR and RDR products from July 5th, 2009 to December 15th, 2017 Updated Mini-RF Bistatic data products (EDR, RDR, and DDR) from April 6th, 2011 to June 28th, 2017. Updated LROC EDR, CDR and RDR products from June 30th, 2009 to December 15th, 2017 Updated LOLA RDR query tool database from July 13th, 2009 to January 3rd, 2018 In Progress Diviner RDR query tool database from July 5th, 2009 to December 15th, 2017. Please see ODE Lunar Holdings - https://wufs.wustl.edu/ode/odeholdings/Moon_holdings.html
-
I want to georeference an M3 image (obtained via PDS) in ENVI. I was following "Assigning Map Information to PDS Images in ENVI", posted by Dr June Wang. I was able to perform most of the steps. Yet when the process is complete, it seems that the georeferencing is not correct. I have attached a couple of screenshots from the M3 image I was working with. To check the accuracy of georeferencing, I cross-checked the location from Google Moon and found that there are a lot of discrepancies between the 'georeferenced' M3 image and Google Moon. In the 'Edit Map Information' window, I entered X-pixel and Y-pixel sizes as 140. Please let me know if this is correct. When I cross-checked with Google Moon, the top of the image should have latitude as north and the bottom the image as south (also verified from LOC file of the M3 image). Please help.
-
Release 33 of Lunar Reconnaissance Orbiter data is now online at the Geosciences Node. This release includes new data acquired between September 15 and December 14, 2017, along with some revisions to previously released products, for CRaTER, Diviner, LAMP, LEND, LOLA, LROC, and Mini-RF. Data can be found on the Geosciences Node LRO page. The Lunar Orbital Data Explorer allows searching and downloading of LRO data.
-
March 2nd, 2018 - MRO Release 44 Loaded into ODE. - Updated MRO CRISM EDR and CDR products from September 27th, 2006 to November 9th, 2017 - Updated MRO CRISM DDR products from September 27th, 2006 to November 8th, 2017 - Updated MRO CRISM TRDR products from September 27th, 2006 to November 8th, 2017 - Updated MRO raw gravity data products released through August 8th, 2017 - Updated SHARAD Radargram data products released through August 14th, 2017 (orbits through 51797) - Updated MRO SHARAD EDR products from December 6th, 2006 to August 19th, 2017 - Updated MRO MCS EDR, RDR and DDR products from September 15th, 2006 to October 31st, 2017 - Updated MRO CTX EDR products from August 30th, 2006 to August 31st, 2017 - Updated MRO HiRISE EDR, RDR, anaglyph and DTM products released through February 2nd (Orbit 53999), 2018 Please see ODE Mars Holdings – https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
-
SHARAD EDR data from the ASI team members have been posted, covering previous MRO release 43 and current release 44. With this release, the team has recovered data from deliveries that were missed due to a hiatus in ground operations. The EDR data set is now up to date. See ERRATA.TXT for details. The data are available on the PDS Geosciences Node's SHARAD page.
-
Release 44 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.
-
Hi Emran, The image cube product after ATP correction (...._trr3_CAT_corr.img) has all original bands (438 which include 8 bad bands, you can see it through Data Manager in ENVI 5.4 ) When you project the image cube, these bad bands are removed, so there are 430 bands left. Can you do the spectral enhancement before map projection then projection the output afterwards? Thanks, Feng
-
Hello Feng, No, the file which is used for spectral enhancement in getting ratio spectra (part in spectral analysis and interpretation). I attached the manual and indicated it in a red box. Is ''same detector un-map-projected'' same to the image cube product after ATP correction (...._trr3_CAT_corr.img)? I tried collecting spectra as denominator from that file (un-projected one) and collected numerator spectra from the projected one. Then I tried to do spectral math (numerator/denominator) with these spectra(s). But ENVI shows an error message like spectral bands do not match for numerator and denominator (number of bands do not match). When we project the image cube, has there any changes in the number of bands from unprojected one to projected one? Thank you, Emran
-
Version 1.0.0
64 downloads
This zip file includes example Wget commands for downloading files from the PDS Geosciences Node. The first example demonstrates downloading a PDS data set from the PDS Geosciences Node archive. The second example demonstrates using Wget to download an Orbital Data Explorer (ODE) cart request.
