X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 15 Apr 2015 05:56 AM by  anon
failed to get the output with a certain resolution
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
15 Apr 2015 05:56 AM
    I retrieve AOD from MOD04 based on MCTK. But the resolution of output is random when use geographic coordinate system. I wonder if I could get geographical output with a certain resolution without resampling or resizing the output. I use 'out_ps = [0.03d,0.03d] ;' in my IDL pro, but it doesn't work for MOD04 is not the grid dataset. And I know I can get the output with 10km resolution when I choose the projected coordinate system. However, I prefer the output with geographic coordinate system and a certain spatial resolution. My part code is as following: ... output_projection = envi_proj_create(/geographic) out_ps = [0.03d,0.03d] ; convert_modis_data, in_file=modis_swath_file, $ out_path=output_location, out_root=output_rootname, $ swt_name=swath_name, sd_names=sd_names, $ out_method=out_method, out_proj=output_projection, $ interp_method=interpolation_method, /no_msg,$ background=-999,fill_replace_value=-999, $ r_fid_array=r_fid_array, r_fname_array=r_fname_array, $ bridges=bridges, msg=msg .... Anybody can help me? Thanks. Regrads, Qingqing

    MariM



    Veteran Member


    Posts:2396
    Veteran Member


    --
    15 Apr 2015 07:34 AM
    I don't see you setting the pixel size within the call to CONVERT_MODIS_DATA. It looks like the keywords to use are: OUT_PS_X, OUT_PS_Y according to the help document that comes with the toolkit: CONVERT_MODIS_DATA [,IN_FILE=string] [,OUT_PATH=string] [,OUT_ROOT=string] [,/L1A] [,/L1B] [,/MOD14] [,/HIGHER_PRODUCT] [,/SWATH] [,/GRID] [,SWT_NAME=string] [,GD_NAME=string] [,SD_NAMES=string array] [,OUT_METHOD={0 | 1 | 2}] [,GEOLOC_FILE=string] [,OUT_PROJ=envi projection structure] [,OUT_PS_X=double] [,OUT_PS_Y=double] [,NUM_X_PTS=integer] [,NUM_Y_PTS=integer] [,INTERP_METHOD={6 | 7 | 8}] [,/BOWTIE] [,CALIB_METHOD={0 | 1 | 2}] [,SD_POS=integer array] [,/NO_MSG] [,BACKGROUND=integer or float], FILL_REPLACE_VALUE=integer or float] [,R_FID_ARRAY=variable] [,R_FNAME_ARRAY=variable] Additionally, it states you must set the GRID keyword: OUT_PS_X (optional) Set this keyword to a double-precision value containing the X pixel size of the output image. You should specify the pixel size in the units contained in the projection structure passed to the OUT_PROJ keyword. This keyword is ignored unless the /GRID keyword is set. OUT_PS_Y (optional) Set this keyword to a double-precision value containing the Y pixel size of the output image. You should specify the pixel size in the units contained in the projection structure passed to the OUT_PROJ keyword. This keyword is ignored unless the /GRID keyword is set.

    Deleted User



    New Member


    Posts:
    New Member


    --
    15 Apr 2015 09:49 PM
    Thanks for your reply. But MOD04 dataset is not the grided product (it is swath product), so this keyword doesn't work in my pro. As noted that "This keyword is ignored unless the /GRID keyword is set." Is there any other idea? Thanks.

    MariM



    Veteran Member


    Posts:2396
    Veteran Member


    --
    16 Apr 2015 06:53 AM
    It sounds like the tool only allows you to specify the output pixel size for gridded datasets. In this case, use the pixel size default and resample to your desired pixel size after the dataset is extracted.
    You are not authorized to post a reply.