Jump to content
PDS Geosciences Node Community

June Wang

Geo Staff
  • Content count

    214
  • Joined

  • Last visited

  • Days Won

    2

June Wang last won the day on February 10

June Wang had the most liked content!

Community Reputation

18 Good

About June Wang

  • Rank
    Geo Staff

Profile Information

  • Gender
    Not Telling
  1. Feb. 20, 2018. - Revised and new MARSIS EDR and Subsurface RDR data have been loaded into ODE, with coverage from May 2005 through December 2016. See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
  2. ODE - MRO SHARAD EDR Data Loaded into ODE

    February 15th, 2018 - MRO SHARAD EDRs from ASI for previous MRO releases 39-42 are now loaded into ODE. Data coverage: 2016-052 through 2017-049. Please see https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html and ERRATA.TXT(http://pds-geosciences.wustl.edu/mro/mro-m-sharad-3-edr-v1/mrosh_0004/errata.txt) for more details.
  3. February 13th, 2018 - MRO SHARAD EDRs from ASI (Italian Space Agency) for previous MRO releases 35-38 are now loaded into ODE. Data coverage: 2015-053 through 2016-051. Please see https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html and ERRATA.TXT(http://pds-geosciences.wustl.edu/mro/mro-m-sharad-3-edr-v1/mrosh_0004/errata.txt) for more details.
  4. Assigning Map Information to PDS Images in ENVI

    Hi Tarun, I just noticed that you are using the Mini-RF MAPCDR data product. And this product has an Oblique Cylindrical projection. I doubt if ENVI can handle the Oblique Cylindrical projection. USGS ISIS3 support the Oblique Cylindrical projection. You can use ISIS's cam2map or map2map functions to reproject the MAPCDR data to other projections, before you further process the data in other GIS software. More information about USGS ISIS tools could be found in the below link. thanks, https://isis.astrogeology.usgs.gov/ June
  5. Assigning Map Information to PDS Images in ENVI

    Hi Tarun, It looks to me you didn't edit the 'ellipse.txt'file as mentioned in the previous post. I have copied the steps below for your reference. Feel free to let me know if you still have problems. Thanks, June 1. Update the map projection files - ENVI includes three map projection files related to the definition of datum, ellipse and map projections. First check where ENVI points to the map projection files. - Select File > Preference, under User Defined Files Tab, find Map Projection File. - If the right blank is empty, ENVI will point to the map projection files saved under the default system folder where ENVI was first installed, e.g.,"C:\Program Files\Exelis\ENVI50\classic\map_proj\" for ENVI 5.0 classic. This path may vary machine by machine. Otherwise, ENVI will point to the map projection files saved in the path as defined in the right blank. - Go to the folder where ENVI points to the map projection files. Backup the three files: "datum.txt", "ellipse.txt", and "map_proj.txt" before you make any changes. - Update file datum.txt - Open datum.txt - Add string "D_Moon_2000, GCS_Moon_2000, 0, 0, 0" to the end of the file - Save (If you have permission problem to save the file, please copy the file out to another folder. After changing, copy the saved file back to the original folder. If the permission is still denied, please let your system administrator to update the files.) - Update file ellipse.txt - Open ellipse.txt - Add string "GCS_Moon_2000, 1737400.0, 1737400.0" to the end of the file - Save (take care of the permission problem as above) - Update file map_proj.txt - Open map_proj.txt - Add string "31, 1737400.0, 1737400.0, 90.000000, 0.000000, 0., 0., Moon North Polar Stereographic" to the end of the file [This string needs to be changed to the actual projection you needed for your data) - Save (take care of the permission problem as above) - Restarting ENVI will update the changes in the map projections.
  6. February 9, 2018 – MRO HiRISE Updates - MRO HiRISE EDR, RDR, DTM and Anaglyph data products released through January 1, 2018 (Orbit 53,599) See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
  7. February 6th, 2018 Release 8 of MRO CRISM MTRDR (Map-projected Targeted Reduced Data Record), TER (Targeted Empirical Record), and TRDR (Targeted Reduced Data Record) browse and extras data has been loaded into ODE. This release fills in data from 2007_299 through 2008_221. See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html for more information.
  8. Why is there a flip in LROC Images?

    Hi Shyam Mohan, Both the LROC *.img data and browse images in Lunar ODE are the original data provided by the LROC team. There is nothing wrong with the data products you downloaded from ODE. It is the way how to interpret the image and the index tables. Please refer to the index.tab and index.lbl in the below link. http://lroc.sese.asu.edu/data/LRO-L-LROC-3-CDR-V1.0/LROLRC_1013/INDEX/ In index.lbl, you will find below definitions for the columns 70 to 79 for the lat &lon coordinates of the center point and 4 corner points of the image. And you can find corresponding index records from index.tab for the data product M1106080949LC. If you fill those numbers for those 4 image corners, you will see the coordinates are correct and consistent with the LROC quickmap. OBJECT = COLUMN NAME = CENTER_LATITUDE COLUMN_NUMBER = 70 DATA_TYPE = ASCII_REAL START_BYTE = 798 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "The planetocentric latitude coordinate at the center of the observation." END_OBJECT = COLUMN OBJECT = COLUMN NAME = CENTER_LONGITUDE COLUMN_NUMBER = 71 DATA_TYPE = ASCII_REAL START_BYTE = 805 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "The planetocentric longitude coordinate at the center of the observation." END_OBJECT = COLUMN OBJECT = COLUMN NAME = UPPER_RIGHT_LATITUDE COLUMN_NUMBER = 72 DATA_TYPE = ASCII_REAL START_BYTE = 812 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "Upper right latitude." END_OBJECT = COLUMN OBJECT = COLUMN NAME = UPPER_RIGHT_LONGITUDE COLUMN_NUMBER = 73 DATA_TYPE = ASCII_REAL START_BYTE = 819 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "Upper right longitude." END_OBJECT = COLUMN OBJECT = COLUMN NAME = LOWER_RIGHT_LATITUDE COLUMN_NUMBER = 74 DATA_TYPE = ASCII_REAL START_BYTE = 826 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "Lower right latitude." END_OBJECT = COLUMN OBJECT = COLUMN NAME = LOWER_RIGHT_LONGITUDE COLUMN_NUMBER = 75 DATA_TYPE = ASCII_REAL START_BYTE = 833 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "lower right longitude." END_OBJECT = COLUMN OBJECT = COLUMN NAME = LOWER_LEFT_LATITUDE COLUMN_NUMBER = 76 DATA_TYPE = ASCII_REAL START_BYTE = 840 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "lower left latitude." END_OBJECT = COLUMN OBJECT = COLUMN NAME = LOWER_LEFT_LONGITUDE COLUMN_NUMBER = 77 DATA_TYPE = ASCII_REAL START_BYTE = 847 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "lower left longitude." END_OBJECT = COLUMN OBJECT = COLUMN NAME = UPPER_LEFT_LATITUDE COLUMN_NUMBER = 78 DATA_TYPE = ASCII_REAL START_BYTE = 854 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "Upper left latitude." END_OBJECT = COLUMN OBJECT = COLUMN NAME = UPPER_LEFT_LONGITUDE COLUMN_NUMBER = 79 DATA_TYPE = ASCII_REAL START_BYTE = 861 BYTES = 6 FORMAT = "F6.2" NOT_APPLICABLE_CONSTANT = 999.99 DESCRIPTION = "Upper left longitude." END_OBJECT = COLUMN The reality is the left and right of an image is not always the west and east of real direction as you noticed, and north of image will not always be the straight up direction. It totally depends on the flight direction of the satellite and the cameras onboard the satellite. That is why you will always need to look at the index table to find the corner coordinates of the LROC data to further interpret the images. Please let me know if you still have any questions about the LROC data set. Thanks, June
  9. DIVINER

    Each Diviner RDR data product consists of two files. They are a detached PDS label and an ASCII data table file. You can open the ASCII data table directly with UltraEdit, Excel or other tools. For more information about Diviner RDR products, please see the RDR and Derived Product Software Interface Specification file @ http://pds-geosciences.wustl.edu/lro/lro-l-dlre-4-rdr-v1/lrodlr_1001/document/dp_sis.pdf . Our lunar ODE provides the DIVINER RDR Query Tool (http://ode.rsl.wustl.edu/moon/indextools.aspx?displaypage=lrodiviner) to select RDR data from the products by area. The tool returns data in a variety of formats including an ASCII table, Shapefile, and Binned Images. In addition to the RDR products, DIVINER offers a set of gridded data products (GDRs). The GDR products are RDR products assembled into global grids, with various resolution and channel combinations. I am wondering the DIVINER GDR products might meet your needs. Please see below help page for more information and let me know if you have more questions. Thanks, http://ode.rsl.wustl.edu/moon/pagehelp/quickstartguide/index.html?diviner.htm
  10. DIVINER

    Hi, I am happy to help you with your Diviner data. Would you please give me more details of the data which you can not open in ENVI, e.g., product ID and screen copy of the error message? I will take a look. thanks, June
  11. ODE - Mars Odyssey Release 62 Data Loaded into ODE

    January 18th, 2018 --Loaded NS and HEND raw and derived data into ODE through June 30th, 2017 See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html.
  12. January 12th, 2018 –Interim Releases of MRO SHARAD EDR data loaded into ODE. Updated SHARAD EDR products from December 6th, 2006 to February 21st, 2015 (orbits through -40185) Interim Release. January 12, 2018. ---------------------------------- This release includes a redelivery of select EDR datasets due to errors in the selection of corresponding raw data files. The affected IDs are: edr2689301 edr2695502 edr2689501 edr2695801 edr2690401 edr2698501 edr2692001 edr2717901 edr2692401 edr2720601 edr2692402 edr3325001 edr2693301 edr3334301 edr2695201 edr3486101 edr2695501 Interim Release. January 4, 2018. --------------------------------- Two errors were discovered in the SHARAD Auxiliary Data Files for releases 23 through 34. The value of Orbit Number and the sign of Spacecraft Radial Velocity were incorrect. This release corrects all the errors in the affected observations. See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html See ERRATA.TXT (http://pds-geosciences.wustl.edu/mro/mro-m-sharad-3-edr-v1/mrosh_0003/errata.txt) for more details.
  13. January 12, 2018 – MRO HiRISE Updates - MRO HiRISE EDR, RDR, DTM and Anaglyph data products released through December 1, 2017 (Orbit 53,199) See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html
  14. January 11th, 2018 – The third release of Earth-based Venus radar data from Bruce Campbell loaded into ODE. This release contains data collected from August 10 - August 16, 2015 and March 21 - March 27, 2017. See below links for more details http://pds-geosciences.wustl.edu/missions/venus_radar/index.htm https://wufs.wustl.edu/ode/odeholdings/Venus_holdings.html
  15. January 5th, 2018 - Mar Odyssey Release 62 THEMIS Data Updates Updated THEMIS standard data products (IREDR, IRRDR, IRBTR, VISEDR, VISRDR and VISABR data) from February 19th, 2002 to June 9th, 2017 Updated THEMIS geometry data products (IRGEO2, IRPBT2, VGEO2, and VISALB data) from September 28th, 2013 to June 9th, 2017 Release 62 of NS and HEND data is delayed. The data would be available by January 15, 2018. See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html.
×