X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 21 Dec 2012 01:42 PM by  anon
Georeferencing Sensor Zenith Angle dataset
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
21 Dec 2012 01:42 PM
    Hello all, I am experiencing difficulties with georeferencing MYD021KM SensorZenith files. I have approx. 703 files that I need to extract the viewing geometry (sensorzenith and sensorazimuth) angles from. I downloaded the MCTK in order to do so. The process works when I use associated MYD03 geolocation files in the toolkit in ENVI, but the process is very slow, so i tried to do it programmatically. However, I have tried all of the example procedures in the user's guide--none of them will work (from either the MYD03 or MYD021KM files). I am wondering if anyone knows of an efficient way to go about georeferencing the SensorZenith and SensorAzimuth datasets. Thanks! CK

    Deleted User



    New Member


    Posts:
    New Member


    --
    02 Jan 2013 11:26 AM
    Can you clarify what you mean by "none of them will work". Are there error messages or are the results incorrect etc. Are you calling the associated MYD03 file correctly? Please provide the steps you are following. Would the following help in any way: http://www.exelisvis.com/...974/scope/posts.aspx

    Deleted User



    New Member


    Posts:
    New Member


    --
    03 Jan 2013 02:34 PM
    None of the example procedures mentioned at the end of the MCTK user guide will georeference the MYD03 files. For example, when I try using the Level 1B or Level 1A examples, it simply states that the supplied MODIS product name is not recognized. If I attempt to georeference the MYD03 files by using the "level 2 swath example" and extract the corresponding sd_names that I need (SensorZenith and SensorAzimuth) it states that the process was "unable to attach to specified swath. Check name against HDF file contents." Here is the procedure for the Level 1b example ENVI> compile_opt idl2 ENVI> modis_l1b_file ='S:\Cole_Krehbiel\Undergrad_Research_Project\IDL\hdf\MYD03.A2010223.1920.005.2010229080808.hdf' ENVI> output_location ='S:\Cole_Krehbiel\Undergrad_Research_Project\IDL\hdf\' ENVI> output_rootname = 'level_1b' ENVI> calib_method = 1 ENVI> out_method = 1 ENVI> output_projection = envi_proj_create(/geographic) ENVI> convert_modis_data, in_file=modis_l1b_file, out_path=output_location, $ ENVI> out_root=output_rootname, /l1b, out_method=out_method, $ ENVI> out_proj=output_projection, calib_method=calib_method, /bowtie, $ > sd_pos=[1,3], /no_msg, background=0.0 And here is the procedure from the swath example ENVI> modis_swath_file ='S:\Cole_Krehbiel\Undergrad_Research_Project\IDL\hdf\MYD03.A2010223.1920.005.2010229080808.hdf' ENVI> output_location ='S:\Cole_Krehbiel\Undergrad_Research_Project\IDL\hdf\' ENVI> output_rootname ='SensorZenith' ENVI> swath_name='MYD03' ENVI> sd_names= ['SensorZenith','SensorAzimuth'] ENVI> out_method=1 ENVI> output_projection = envi_proj_create(/geographic) ENVI> interpolation_method = 6 ENVI> convert_modis_data, in_file=modis_swath_file, $ > out_path=output_location, out_root=output_rootname, $ > /higher_product, /swath, swt_name=swath_name, $ > sd_names=sd_names, out_method=out_method,out_proj=output_projection, num_x_pts=50, num_y_pts=50, interp_method=interpolation_method, /no_msg ENVI>

    Deleted User



    New Member


    Posts:
    New Member


    --
    04 Jan 2013 12:40 PM
    Hard to say where the problem is but given that you are able to process your data using the GUI you should be able to do it using one of the example codes. If I read the MCTK User's Guide correctly the code examples should do exactly what happens interactively. The only suggestion is to look at your interactive workflow and its settings/parameters and then find the code example that matches best. Check the User's Guide for any details that may help.
    You are not authorized to post a reply.