McV 1.01 - MOD02 files - invalid file name convention

[jayh]

Hi HP-

I downloaded the MYD021KM.A2007295.2055.005.2009299054715.hdf file from http://ladsweb.nascom.nasa.gov/data/search.html.

This file worked fine using the Sept 02 and Sept 06 nightlies on my XP machine as well as our Windows 7 64-bit testing machine. What recent nightlies were you using? If they were older than my examples, hopefully getting the latest nightly will correct the problem.

You may also want to post your version of MYD021KM.A2007295.2055.005.2009299054715.hdf to our ftp.ssec.wisc.edu in pub/incoming and I can try that here as well.

Thanks, Jay

[hproe]

Hi -

Thanks to a brief brainstorming with TomW we have finally found the reason for the seemingly erratic appearance of the "invalid file name convention" error when opening MODIS files through the Satellite>Imagery path. The error occurs when MODIS files are mixed with non-MODIS files in the same folder, i.e. MODIS files have always to be separated out into proper folders. The Satellite >HYDRA path must use a different, more robust identification procedure that skips over non-MODIS files in the same folder.

I do not know whether one would register this as a bug. In any case it is good to know.

HP

[jayh]

Hi HP-

Thanks for your report back... and I'm not sure if it is a "bug" either, but it's something we have talked about for an enhancement for the Local ADDE Data Manager. It would also be more in line with how file masking works in McIDAS-X as well.

We have written up this in inquiry 1144 for evaluation: http://mcidas.ssec.wisc.edu/inquiry-v/in ... quiry=1144

Thanks, Jay