McIDAS-V Support Forums

Hi -
The other day I have downloaded several MOD021km*.hdf from the LAADS DAAC site. The Local Server won't read them, saying:
edu.wisc.ssec.mcidas.adde.AddeURLException: Invalid filename convention
at edu.wisc.ssec.mcidas.adde.AddeURLConnection.connect(AddeURLConnection.java:767)
at edu.wisc.ssec.mcidas.adde.AddeURLConnection.getInputStream(AddeURLConnection.java:817)
at edu.wisc.ssec.mcidas.AreaDirectoryList.<init>(AreaDirectoryList.java:119)
at edu.wisc.ssec.mcidasv.chooser.adde.AddeImageChooser.readTimesInner(AddeImageChooser.java:1376)
at edu.wisc.ssec.mcidasv.chooser.adde.AddeImageChooser$7.run(AddeImageChooser.java:1324)
at ucar.unidata.util.Misc$3.run(Misc.java:1243)
I get the same both on a windows and an Ubuntu machine.
I happen to have a MOD021km*.hdf downloaded in 2008 (nothing more recent). It works fine.
cheers, HP

Hi HP,

Our McV guru (Bob) said he downloaded a couple MOD02 1km files from LAADS today and they worked fine in McV using the "MODIS MOD 02" format when making the new local ADDE dataset. The files he downloaded were named:

MOD021KM.A2020359.1625.061.2020360011759.hdf
MOD021KM.A2021002.1620.061.2021003010941.hdf

He suggested that you check the directory with your downloaded files to make sure there are no other random files in it. Extra files in the directory can sometimes cause errors similar to what you reported. He specifically mentioned that sometimes when you order data it comes with a manifest.xml file (or some other text file containing a listing of file names) that can confuse the servers.

If that isn't the issue can you please provide a file listing of the directory?

Thanks!
Barry

Hi Barry -
Bob's hint Helped! I have MOD03 geolocation files going with the MOD021km files, because I need them for another application. Removing the geolocation files did the trick.
many thanks and wishes for a better year, HP