Jump to content
PDS Geosciences Node Community

June Wang

Geo Staff
 View Profile  See their activity

  • Posts

    660

  • Joined

  • Last visited

 Content Type 

Posts posted by June Wang

    ODE - MEX HRSC REFDR3 Loaded into ODE

    in Announcements

    Posted

    June 1st, 2018 - MEX HRSC new map projected data (REFDR3) data have been loaded into ODE
    - HRSC new Version 3 of map projected RDR data (REFDR3) have been loaded into ODE, with coverage through August 17, 2016 (Orbit 10-16000).
    See https://wufs.wustl.edu/ode/odeholdings/Mars_holdings.html for a full list of data holdings in ODE.

     

    ODE - New MEX Data Loaded into ODE

    in Announcements

    Posted

    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

     

    ODE - Mars Odyssey Release 63 Data Loaded into ODE

    in Announcements

    Posted

    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.

     

    Georeferencing PDS images in ENVI

    in For data users

    Posted

    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.

     

    Georeferencing PDS images in ENVI

    in For data users

    Posted

    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

    ODE - LRO Release 33 Loaded into ODE

    in Announcements

    Posted

    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

     

    ODE - MRO Release 44 Loaded into ODE

    in Announcements

    Posted

    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

     

    ODE - Release 8 of MRO CRISM MTRDR, TER data is loaded into ODE, along with new TRDR browse and extras data products

    in Announcements

    Posted

    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.

     

    Why is there a flip in LROC Images?

    in For data users

    Posted

    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 

    DIVINER

    in For data users

    Posted

    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
     

    DIVINER

    in For data users

    Posted

    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 

     

    ODE - Interim Releases of MRO SHARAD EDR Data Loaded into ODE

    in Announcements

    Posted

    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.

     

×
×
  • Create New...