Thanks Ken, that helps make sense of it.
On Mar 25, 2013, at 9:32 AM, Kenneth S. Casey - NOAA Federal wrote:
> Nathan - the underlying data files are on both our TDS and our OPeNDAP Hyrax
> server… the aggregation NCML currently points explicitly to the Hyrax service
> endpoints.
>
> Thanks to Bob Simmons, we see that at least one specific file in the
> aggregation is failing. We determined that it is because a version 2 of the
> file replaced the version 2 pointed to by the aggregation. The newer file
> has a "v02" in the file name instead of the "v01"… there may be more failures
> but suspect this is at the root of our problem… simply failing to ensure that
> our aggregation NCMLs are always pointing to the most up-to-date files and
> file names.
>
> This failure explains why the data requests fail sometimes and not others… if
> your requested time period doesn't include the updated files it works… if it
> does then the request fails.
>
>
> Ken
>
>
>
> On Mar 25, 2013, at 12:19 PM, Nathan Potter <ndp@xxxxxxxxxxx> wrote:
>
>>
>>
>> Li,
>>
>> It's odd this error you have. All of the source URL's are from an instance
>> of the TDS, and work, at least to a certain extent. For example the second
>> dataset's DDS can be seen with no problem here:
>>
>>
>> http://data.nodc.noaa.gov/thredds/dodsC/testdata/ghrsst_ncml/fullAgg/aggregate__ghrsst_L4_GLOB_NCDC_AVHRR_AMSR_OI.ncml.dds
>>
>> Adding the constraint expression produces the correct result:
>>
>> http://data.nodc.noaa.gov/thredds/dodsC/testdata/ghrsst_ncml/fullAgg/aggregate__ghrsst_L4_GLOB_NCDC_AVHRR_AMSR_OI.ncml.dds?analysed_sst%5B0:1:1439%5D%5B360%5D%5B720%5D
>>
>> But the ASCII data request fails:
>>
>> http://data.nodc.noaa.gov/thredds/dodsC/testdata/ghrsst_ncml/fullAgg/aggregate__ghrsst_L4_GLOB_NCDC_AVHRR_AMSR_OI.ncml.ascii?analysed_sst%5B0:1:1439%5D%5B360%5D%5B720%5D
>>
>> (My requests for this URL time out with no response.)
>>
>> However the error you submitted:
>>
>>> Error {
>>> code = 500;
>>> message = "
>>> http://data.nodc.noaa.gov/opendap/hyrax/ghrsst/L4/GLOB/NCDC/AVHRR_AMSR_OI/2003/348/20031214-NCDC-L4LRblend-GLOB-v01-fv01_0-AVHRR_AMSR_OI.nc.bz2
>>> is not a valid URL, return status=404";
>>> };
>>>
>>
>> is unrelated to the TDS in that the referenced dataset URL:
>> http://data.nodc.noaa.gov/opendap/hyrax/ghrsst/L4/GLOB/NCDC/AVHRR_AMSR_OI/2003/348/20031214-NCDC-L4LRblend-GLOB-v01-fv01_0-AVHRR_AMSR_OI.nc.bz2
>>
>> References a different dataset on an instance of a Hyrax server, not a TDS.
>>
>> I'm thinking there may be some copy/paste confusion happening that's mudding
>> the waters here...
>>
>>
>> Nathan
>>
>>
>>
>> On Mar 25, 2013, at 6:43 AM, Yuanjie Li - NOAA Affiliate wrote:
>>
>>> We are trying to pull out time series values in ASCII format through TDS.
>>>
>>> e.g.
>>> http://data.nodc.noaa.gov/thredds/dodsC/testdata/ghrsst_ncml/fullAgg/aggregate__ghrsst_L4_GLOB_NCDC_AVHRR_AMSR_OI.ncml.ascii?analysed_sst[0:1:365][360][720]
>>>
>>> Worked fine..
>>>
>>> But when we tried:
>>>
>>> http://data.nodc.noaa.gov/thredds/dodsC/testdata/ghrsst_ncml/fullAgg/aggregate__ghrsst_L4_GLOB_NCDC_AVHRR_AMSR_OI.ncml.ascii?analysed_sst[0:1:1439][360][720]
>>>
>>> we got:
>>>
>>> Error {
>>> code = 500;
>>> message = "
>>> http://data.nodc.noaa.gov/opendap/hyrax/ghrsst/L4/GLOB/NCDC/AVHRR_AMSR_OI/2003/348/20031214-NCDC-L4LRblend-GLOB-v01-fv01_0-AVHRR_AMSR_OI.nc.bz2
>>> is not a valid URL, return status=404";
>>> };
>>>
>>> Please advise us if this is a problem with our TDS server?
>>>
>>> The version of our server: TDS 4.2.9
>>>
>>> Thanks in advance,
>>> Li
>>> _______________________________________________
>>> thredds mailing list
>>> thredds@xxxxxxxxxxxxxxxx
>>> For list information or to unsubscribe, visit:
>>> http://www.unidata.ucar.edu/mailing_lists/
>>
>> = = =
>> Nathan Potter ndp at opendap.org
>> OPeNDAP, Inc. +1.541.231.3317
>>
>>
>>
>>
>> _______________________________________________
>> thredds mailing list
>> thredds@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> http://www.unidata.ucar.edu/mailing_lists/
>
= = =
Nathan Potter ndp at opendap.org
OPeNDAP, Inc. +1.541.231.3317
