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

[THREDDS #PMC-685007]: Problem with radar subset service



Hi Joe,

I'll check with our web administrator.  I haven't pushed her in the last 
couple of weeks because she has been putting together metrics for our 
5-year funding proposal.

-Lansing

On 5/14/2013 1:28 PM, Joe Sirott wrote:
> New Client Reply: Problem with radar subset service
>
> Hi Lansing,
>
> Any update on compression for thredds.ucar.edu? It's been about six
> weeks since I reported this, so I'm concerned that this won't be fixed
> before motherlode is retired.
>
> Thanks, Joe
>
> On 4/24/13 8:04 AM, Unidata THREDDS Support wrote:
>> Joe,
>>
>> We're still working out a couple of server issues.  I'll let you know when 
>> compression is enabled.
>>
>> Thanks,
>>     Lansing
>>
>>> Hi,
>>>
>>> Any update on this? It looks like the radar server API is now working
>>> correctly, but compression is still not enabled on thredds.ucar.edu. I'd
>>> like to be able to convert over to the thredds.ucar.edu from motherlode
>>> soon, due to the upcoming shut down of motherlode, but I can't do it
>>> until compression is enabled.
>>>
>>> Thanks for your help, Joe
>>>
>>> On 4/12/13 1:54 PM, Unidata THREDDS Support wrote:
>>>> Joe,
>>>>
>>>> My apologies.  I've put in an inquiry on the http response compression, 
>>>> and I need to coordinate with one of our recently retired colleagues on 
>>>> the 00Z issue.  Thank you for reminding me.
>>>>
>>>> Regards,
>>>>      Lansing Madry
>>>>      Unidata
>>>>      Boulder, Colorado
>>>>
>>>>> Didn't get a response so I thought I'd try again... Also, the
>>>>> HTTP response is still not compressed as well...
>>>>>
>>>>> Thanks.
>>>>> -------- Original Message --------
>>>>> Subject:  Re: [THREDDS #PMC-685007]: Problem with radar subset service
>>>>> Date:     Mon, 08 Apr 2013 15:05:00 -0700
>>>>> From:     Joe Sirott <address@hidden>
>>>>> To:       address@hidden
>>>>>
>>>>>
>>>>>
>>>>> Hi Ethan,
>>>>>
>>>>> Looks like the problem with the THREDDS radar service is still there.
>>>>> Any idea when this might be fixed?
>>>>>
>>>>> Thanks, Joe
>>>>>
>>>>> On 3/26/13 3:11 PM, Unidata THREDDS Support wrote:
>>>>>> Hi Joe,
>>>>>>
>>>>>> Thanks for the report.
>>>>>>
>>>>>> The 00Z problem:
>>>>>> I think we're narrowing in on a solution. I'm afraid we won't have a fix 
>>>>>> in place till sometime next week.
>>>>>>
>>>>>> The HTTP response not compressed problem:
>>>>>> Definitely looks like a configuration problem for thredds.ucar.edu. I'm 
>>>>>> guessing we'll have a fix for this problem in the next day or so.
>>>>>>
>>>>>> Ethan
>>>>>>
>>>>>> Joe Sirott wrote:
>>>>>>> Hi Ethan,
>>>>>>>
>>>>>>> The thredds.ucar.edu service seems to also be broken. This yields 0
>>>>>>> datasets:
>>>>>>>
>>>>>>> curl
>>>>>>> 'http://thredds.ucar.edu/thredds/radarServer/nexrad/level3/IDD?stn=KFTG&time_start=2013-03-16T23:30:00&time_end=2013-03-16T23:53:00&var=NCR'
>>>>>>>
>>>>>>> while this works as expected:
>>>>>>>
>>>>>>> curl
>>>>>>> 'http://thredds.ucar.edu/thredds/radarServer/nexrad/level3/IDD?stn=KFTG&time_start=2013-03-16T22:30:00&time_end=2013-03-16T22:53:00&var=NCR'
>>>>>> Ticket Details
>>>>>> ===================
>>>>>> Ticket ID: PMC-685007
>>>>>> Department: Support THREDDS
>>>>>> Priority: Normal
>>>>>> Status: Open
>>>>>
>>>>>
>>>> Ticket Details
>>>> ===================
>>>> Ticket ID: PMC-685007
>>>> Department: Support THREDDS
>>>> Priority: Normal
>>>> Status: Open
>> Ticket Details
>> ===================
>> Ticket ID: PMC-685007
>> Department: Support THREDDS
>> Priority: Normal
>> Status: Open
>
>
> Ticket Details
> ===================
> Ticket ID: PMC-685007
> Department: Support THREDDS
> Priority: Critical
> Status: Open
> Link:  
> https://www.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=21808



Ticket Details
===================
Ticket ID: PMC-685007
Department: Support THREDDS
Priority: Critical
Status: Open


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.