| Re: Question on MODIS Conversion Toolkit [message #70621] |
Tue, 27 April 2010 17:52  |
Harry Kim
Messages: 16
Registered: April 2010
|
Junior Member |
|
|
On Apr 28, 5:41 am, "devin.wh...@gmail.com" <devin.wh...@gmail.com>
wrote:
> I think your problem is here:
>
>> out_ps_x = 0.008365, out_ps_y = 0.08365
>
> The output pixel size for Y is too large (by a factor of 10). That's
> probably leading to an output array size that is too small for the
> georeferencing routines to handle.
>
> On Apr 26, 7:45 am, Harry Kim <kim4ecohy...@gmail.com> wrote:
>
>
>
>> Hi, Everyone. I am back with MODIS Converision Toolkit (MCTK)
>> Question.
>
>> Are there anyone working on MODIS data?
>
>> I am working on various MODIS products for ecohydrological processes
>> in Korean penninsula. I tried to use MODIS Conversion Toolkit in
>> programming mode. This tool seems to be useful to process various
>> kinds of MODIS products.
>
>> AS some of you know this very well, we can do MCTK both in GUI mod and
>> in batch (programming) mod. I have to process thousands of file, and I
>> cannot do this in GUI mode.
>
>> Everytime I tried in programming mod, I got this error message.
>
>> "Map information contains an invaild pixel size. This file will not be
>> georeferenced."
>
>> Strangely, there was no problem in making images when I tried with the
>> same value in GUI mode.
>
>> This is what I have done so far. Please take a look, and let me know
>> what to do.
>
>> Hyun Woo
>
>> -------------------------------
>> PRO MCTK_MOD11
>> compile_opt idl2
>> modis_grid_file = 'D:\MODIS11\Data
>> \MYD11A1.005\MYD11A1.A2002189.h28v05.005.2007216150809.hdf'
>> output_location = 'D:\MODIS11\output'
>> output_rootname = 'MYD11_LST'
>> grid_name = 'MOD_Grid_Daily_1km_LST'
>> sd_names = ['LST_Day_1km']
>> out_method = 1
>> output_projection = envi_proj_create(/geographic)
>> ;out_ps_x = 0.008365
>> ;out_ps_y = 0.008365
>> interpolation_method = 6
>> convert_modis_data, in_file=modis_grid_file, $
>> out_path = output_location, out_root= output_rootname, $
>> /higher_product, /grid, gd_name=grid_name, sd_names=sd_names, $
>> out_method= out_method, out_proj=output_projection, $
>> out_ps_x = 0.008365, out_ps_y = 0.08365, num_x_pts=50,
>> num_y_pts=50, interp_method=interpolation_method ;, $
>> background = -999
>> end
>> ----------------------------------------
Thank you, Devine, then what is your suggested values?
In addition, it is interesting. This value is no problem in GUI Mod.
|
|
|
|
| Re: Question on MODIS Conversion Toolkit [message #70622 is a reply to message #70621] |
Tue, 27 April 2010 13:41  |
devin.white
Messages: 50
Registered: March 2007
|
Member |
|
|
I think your problem is here:
> out_ps_x = 0.008365, out_ps_y = 0.08365
The output pixel size for Y is too large (by a factor of 10). That's
probably leading to an output array size that is too small for the
georeferencing routines to handle.
On Apr 26, 7:45 am, Harry Kim <kim4ecohy...@gmail.com> wrote:
> Hi, Everyone. I am back with MODIS Converision Toolkit (MCTK)
> Question.
>
> Are there anyone working on MODIS data?
>
> I am working on various MODIS products for ecohydrological processes
> in Korean penninsula. I tried to use MODIS Conversion Toolkit in
> programming mode. This tool seems to be useful to process various
> kinds of MODIS products.
>
> AS some of you know this very well, we can do MCTK both in GUI mod and
> in batch (programming) mod. I have to process thousands of file, and I
> cannot do this in GUI mode.
>
> Everytime I tried in programming mod, I got this error message.
>
> "Map information contains an invaild pixel size. This file will not be
> georeferenced."
>
> Strangely, there was no problem in making images when I tried with the
> same value in GUI mode.
>
> This is what I have done so far. Please take a look, and let me know
> what to do.
>
> Hyun Woo
>
> -------------------------------
> PRO MCTK_MOD11
> compile_opt idl2
> modis_grid_file = 'D:\MODIS11\Data
> \MYD11A1.005\MYD11A1.A2002189.h28v05.005.2007216150809.hdf'
> output_location = 'D:\MODIS11\output'
> output_rootname = 'MYD11_LST'
> grid_name = 'MOD_Grid_Daily_1km_LST'
> sd_names = ['LST_Day_1km']
> out_method = 1
> output_projection = envi_proj_create(/geographic)
> ;out_ps_x = 0.008365
> ;out_ps_y = 0.008365
> interpolation_method = 6
> convert_modis_data, in_file=modis_grid_file, $
> out_path = output_location, out_root= output_rootname, $
> /higher_product, /grid, gd_name=grid_name, sd_names=sd_names, $
> out_method= out_method, out_proj=output_projection, $
> out_ps_x = 0.008365, out_ps_y = 0.08365, num_x_pts=50,
> num_y_pts=50, interp_method=interpolation_method ;, $
> background = -999
> end
> ----------------------------------------
|
|
|
|
| Re: Question on MODIS Conversion Toolkit [message #70715 is a reply to message #70621] |
Wed, 28 April 2010 02:43 |
devin.white
Messages: 50
Registered: March 2007
|
Member |
|
|
The value of 0.008365 should be fine (that's close to 1km in
degrees). I think you have a typo in your program that's creating a
problem (out_ps_y is set to 0.08365). Try setting *both* the out_ps_x
and out_ps_y variables to 0.008365. Or, if you prefer, change the
output projection to a locally appropriate UTM zone and use an output
pixel size of 1000.0 (meters).
On Apr 27, 8:52 pm, Harry Kim <kim4ecohy...@gmail.com> wrote:
> On Apr 28, 5:41 am, "devin.wh...@gmail.com" <devin.wh...@gmail.com>
> wrote:
>
>
>
>> I think your problem is here:
>
>>> out_ps_x = 0.008365, out_ps_y = 0.08365
>
>> The output pixel size for Y is too large (by a factor of 10). That's
>> probably leading to an output array size that is too small for the
>> georeferencing routines to handle.
>
>> On Apr 26, 7:45 am, Harry Kim <kim4ecohy...@gmail.com> wrote:
>
>>> Hi, Everyone. I am back with MODIS Converision Toolkit (MCTK)
>>> Question.
>
>>> Are there anyone working on MODIS data?
>
>>> I am working on various MODIS products for ecohydrological processes
>>> in Korean penninsula. I tried to use MODIS Conversion Toolkit in
>>> programming mode. This tool seems to be useful to process various
>>> kinds of MODIS products.
>
>>> AS some of you know this very well, we can do MCTK both in GUI mod and
>>> in batch (programming) mod. I have to process thousands of file, and I
>>> cannot do this in GUI mode.
>
>>> Everytime I tried in programming mod, I got this error message.
>
>>> "Map information contains an invaild pixel size. This file will not be
>>> georeferenced."
>
>>> Strangely, there was no problem in making images when I tried with the
>>> same value in GUI mode.
>
>>> This is what I have done so far. Please take a look, and let me know
>>> what to do.
>
>>> Hyun Woo
>
>>> -------------------------------
>>> PRO MCTK_MOD11
>>> compile_opt idl2
>>> modis_grid_file = 'D:\MODIS11\Data
>>> \MYD11A1.005\MYD11A1.A2002189.h28v05.005.2007216150809.hdf'
>>> output_location = 'D:\MODIS11\output'
>>> output_rootname = 'MYD11_LST'
>>> grid_name = 'MOD_Grid_Daily_1km_LST'
>>> sd_names = ['LST_Day_1km']
>>> out_method = 1
>>> output_projection = envi_proj_create(/geographic)
>>> ;out_ps_x = 0.008365
>>> ;out_ps_y = 0.008365
>>> interpolation_method = 6
>>> convert_modis_data, in_file=modis_grid_file, $
>>> out_path = output_location, out_root= output_rootname, $
>>> /higher_product, /grid, gd_name=grid_name, sd_names=sd_names, $
>>> out_method= out_method, out_proj=output_projection, $
>>> out_ps_x = 0.008365, out_ps_y = 0.08365, num_x_pts=50,
>>> num_y_pts=50, interp_method=interpolation_method ;, $
>>> background = -999
>>> end
>>> ----------------------------------------
>
> Thank you, Devine, then what is your suggested values?
>
> In addition, it is interesting. This value is no problem in GUI Mod.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
