[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #DSQ-377902]: navigation issue with FY2C ADDE imagery

Hi Valentijn-

> I believe the new RC has an issue with reading HDF-EOS OPenDAP server
> url's, which properly work in the IDV 1.3
> 
> When i load in the URL data chooser an pointer to a DODS server:
> 
> http://g0dup05u.ecs.nasa.gov/opendap-bin/nph-dods/OPENDAP_DP/long_term/M
> OAT/MOD04_L2.004/2000.02.24/MOD04_L2.A2000055.0010.004.2002328163106.hdf
> .dods?Longitude[0:1:202][0:1:134],Latitude[0:1:202][0:1:134],Optical_Dep
> th_Land_And_Ocean[0:1:202][0:1:134
> <http://g0dup05u.ecs.nasa.gov/opendap-bin/nph-dods/OPENDAP_DP/long_term/
> MOAT/MOD04_L2.004/2000.02.24/MOD04_L2.A2000055.0010.004.2002328163106.hd
> f.dods?Longitude[0:1:202][0:1:134],Latitude[0:1:202][0:1:134],Optical_De
> pth_Land_And_Ocean[0:1:202][0:1:134> ]
> 
> I get this prompt:
> 
> 
> 
> And no matter what Data Source Type i choose, get something like this:
> 
> An error has occurred:
> There was an error loading the data:
> Cant open
> dods://g0dup05u.ecs.nasa.gov/opendap-bin/nph-dods/OPENDAP_DP/long_term/M
> OAT/MOD04_L2.004/2000.02.24/MOD04_L2.A2000055.0010.004.2002328163106.hdf
> .dods?Longitude[0:1:202][0:1:134],Latitude[0:1:202][0:1:134],Optical_Dep
> th_Land_And_Ocean[0:1:202][0:1:134] or as DODS
> dods://g0dup05u.ecs.nasa.gov/opendap-bin/nph-dods/OPENDAP_DP/long_term/M
> OAT/MOD04_L2.004/2000.02.24/MOD04_L2.A2000055.0010.004.2002328163106.hdf
> .dods?Longitude[0:1:202][0:1:134],Latitude[0:1:202][0:1:134],Optical_Dep
> th_Land_And_Ocean[0:1:202][0:1:134]
> "This DODS server does not know how to serve the dataset
> `/OPENDAP_DP/long_term/MOAT/MOD04_L2.004/2000.02.24/MOD04_L2.A2000055.00
> 10.004.2002328163106.hdf.dods.'
> It maybe that the server has not been configured for this type of
> dataset.
> Please double check the URL for errors and, if you think that the URL is
> correct, please contact the administrator of this site at:
> support\@unidata.ucar.edu"

In previous releases, the IDV would default to the VisAD data source.  However,
that resulted in numerous support requests with people getting an error
about loading their data.  In an effort to alleviate this, we decided
that if we couldn't figure out what kind of data it was, we'd put
up the prompt that you saw and let the user decide.  However, you've found 
a case where it can be confusing so we'll tweak this a bit for the final 
release.

It does still work in the RC, but does not default to the VisAD data source.
In this case, you can select the "Just try to load it in" Data Source Type
from the list (this is labeled "I'm Still Feeling Lucky" in the nightly
release).  We might change the label back to VisAD data source for
the final release, but I think we will continue to prompt the user
if we can't figure out the data type from the source's name.  We'll
also make the dialog smaller. ;-) If you have thoughts on this, let us know.
Thanks for finding this issue.

BTW, our current release plans are RC3 by the end of this week and a
full 2.0 release in late July, early August.

Don Murray

Ticket Details
===================
Ticket ID: DSQ-377902
Department: Support IDV
Priority: Normal
Status: Open