| Fill value problem in MODIS Processing... [message #54557] |
Tue, 26 June 2007 12:40  |
kim20026
Messages: 54
Registered: November 2006
|
Member |
|
|
Good day, Everyone!
Actually the main topic of my study was wetland modelling few years
ago. My co-workers at that time may not like this expression..., but I
need some help to "get out of this SWAMP!!!"... T.T
I am currently retrieving aerosole optical thickness from MODIS04
Aerosole product of 2003 (Level 2, collection 4, and bands of 470,
550, and 660 nm).
There are 702 *.hdf files in 2003 and I processed these in a batch
mode. After I ran IDL/ENVI with these data and opened the output
file, I found about 550 of 702 lines were processed into fill value
(-9999.99), 120 lines were N/I ("not included in the swath"). Only 30
lines were reasonable values.
Three weeks have passed since I faced this problem. I thought I could
solve this problem by myself at first. I checked the source codes ->
there was no problem. IDL/ENVI has been running perfectly...
Therefore, I thought this problems was just nothing, but I got stuck
for over 20 days... I believe it is time to listen to your
suggestions.
Is there anyone who experienced similar problem like this? Please give
me any comments or suggestions. Thanks.
Harry
|
|
|
|
| Re: Fill value problem in MODIS Processing... [message #54650 is a reply to message #54557] |
Sat, 30 June 2007 16:27  |
devin.white
Messages: 50
Registered: March 2007
|
Member |
|
|
You might want to try running one of your problematic granules through
the MODIS Conversion Toolkit, if you haven't done so already. It's
set up to automatically check each SD to see if a fill value is
specified and then convert any pixel it finds within the SD that has
the fill value to 'NaN' so it won't affect later processing. You
could then compare the locations of NaN values in the output file
generated by the toolkit to the locations of -9999 in the output file
generated by your code. If the locations match, then your code is
running correctly. You can download the toolkit here:
http://www.ittvis.com/codebank/search.asp?FID=485
On Jun 26, 3:40 pm, DirtyHarry <kim20...@gmail.com> wrote:
> Good day, Everyone!
>
> Actually the main topic of my study was wetland modelling few years
> ago. My co-workers at that time may not like this expression..., but I
> need some help to "get out of this SWAMP!!!"... T.T
>
> I am currently retrieving aerosole optical thickness from MODIS04
> Aerosole product of 2003 (Level 2, collection 4, and bands of 470,
> 550, and 660 nm).
>
> There are 702 *.hdf files in 2003 and I processed these in a batch
> mode. After I ran IDL/ENVI with these data and opened the output
> file, I found about 550 of 702 lines were processed into fill value
> (-9999.99), 120 lines were N/I ("not included in the swath"). Only 30
> lines were reasonable values.
>
> Three weeks have passed since I faced this problem. I thought I could
> solve this problem by myself at first. I checked the source codes ->
> there was no problem. IDL/ENVI has been running perfectly...
> Therefore, I thought this problems was just nothing, but I got stuck
> for over 20 days... I believe it is time to listen to your
> suggestions.
>
> Is there anyone who experienced similar problem like this? Please give
> me any comments or suggestions. Thanks.
>
> Harry
|
|
|
|
| RE: Fill value problem in MODIS Processing... [message #82633 is a reply to message #54557] |
Thu, 27 December 2012 12:47 |
sh_bah
Messages: 1
Registered: December 2012
|
Junior Member |
|
|
Hi harry
i get your question now :)
it s too late
the is scale factor in mod04 that u should read from file its .001 for your case
but there is question in your result why is AOT range -10 to 2 cause the correct range is 0 to 10
if your case is solve please answer
i read MOD04 and i get negative range
Shima
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
