Hi -
I am sure that we had this in the past (and has disappeared in more recent times), but in this moment the forum does not let me search.
Running McV 1.01 under W7 64-bit I have hit again on "invalid file name convention" when trying to open any MOD021KM*.hdf regularly downloaded from the Rapid Response System. To tell the truth I was able to open one file once, but then the error occurred and persists.
HP
McV 1.01 - MOD02 files - invalid file name convention
Re: McV 1.01 - MOD02 files - invalid file name convention
HP,
What datasource are you using?
Tom
What datasource are you using?
Tom
Re: McV 1.01 - MOD02 files - invalid file name convention
Tom -
I get the files via
http://rapidfire.sci.gsfc.nasa.gov/realtime/
but if I understand correctly they are coming finally from
http://ladsweb.nascom.nasa.gov/data/search.html
Here is a sample name:
MOD021KM.A2011097.1155.005.2011098181353.hdf
I tried to shorten/change the file path that helped earlier on - no success now.
HP
I get the files via
http://rapidfire.sci.gsfc.nasa.gov/realtime/
but if I understand correctly they are coming finally from
http://ladsweb.nascom.nasa.gov/data/search.html
Here is a sample name:
MOD021KM.A2011097.1155.005.2011098181353.hdf
I tried to shorten/change the file path that helped earlier on - no success now.
HP
Re: McV 1.01 - MOD02 files - invalid file name convention
using the HYDRA datasource?
Re: McV 1.01 - MOD02 files - invalid file name convention
No, using the local ADDE server for MOD02 data.
Re: McV 1.01 - MOD02 files - invalid file name convention
Hi HP-
We are looking into this problem through the Image chooser. I downloaded a file from the LAADS Web site and we are getting the same invalid filename convention errors that you see. I'm seeing this error in 1.01 and 1.0. If you have any guess as to when this might have worked in the past, I can try to find an older version.
I have some other older MOD021KM files lying around and those work fine in -V at the moment. I tried messing with their filenames to directly match the LAADS web name and they still worked fine. (e.g. MOD021KM.A2004303.1605.001.2005063230546_29992.hdf) I used the LAADS Web file in McIDAS-X with success too. I will do some more testing on Monday and see if we can figure out why these files aren't working.
Thanks, Jay
We are looking into this problem through the Image chooser. I downloaded a file from the LAADS Web site and we are getting the same invalid filename convention errors that you see. I'm seeing this error in 1.01 and 1.0. If you have any guess as to when this might have worked in the past, I can try to find an older version.
I have some other older MOD021KM files lying around and those work fine in -V at the moment. I tried messing with their filenames to directly match the LAADS web name and they still worked fine. (e.g. MOD021KM.A2004303.1605.001.2005063230546_29992.hdf) I used the LAADS Web file in McIDAS-X with success too. I will do some more testing on Monday and see if we can figure out why these files aren't working.
Thanks, Jay
Re: McV 1.01 - MOD02 files - invalid file name convention
Good news. With 1.01 of 18 April I can access MODIS files again.
HP
HP
Re: McV 1.01 - MOD02 files - invalid file name convention
Hi HP -
Thanks for the update. Jay and I both tried our MODIS files with the newest nightly (4/20) and everything works fine for us as well. It must have just been something temporary that got fixed.
Thanks -
Bob
Thanks for the update. Jay and I both tried our MODIS files with the newest nightly (4/20) and everything works fine for us as well. It must have just been something temporary that got fixed.
Thanks -
Bob
Re: McV 1.01 - MOD02 files - invalid file name convention
Hi -
It happens again.
Recent nightlies of 1.02beta1 come up again with 'invalid file name convention' when accessing a AQUA MODIS file through the local ADDE server for M02 data. The file in question is retrieved from LAADS:
MYD021KM.A2007295.2055.005.2009299054715.hdf
HYDRA has no problem reading it.
I also have another file that still works:
MOD021KM.A2011157.1425.005.2011158040336.hdf
HP
It happens again.
Recent nightlies of 1.02beta1 come up again with 'invalid file name convention' when accessing a AQUA MODIS file through the local ADDE server for M02 data. The file in question is retrieved from LAADS:
MYD021KM.A2007295.2055.005.2009299054715.hdf
HYDRA has no problem reading it.
I also have another file that still works:
MOD021KM.A2011157.1425.005.2011158040336.hdf
HP