[las_users] FW: Re: [ferret_users] limit on storage

[Jerome King <jejeking@xxxxxxxxxxx>]

Thanks Ansley and Steve,

I don't mind having to twick a descriptor file if it can solve the issue.
I am not sure how ferret deals with an OPeNDAP data feed, but the result of 
the aggregation is served as an OPeNDAP url. Does it simplify the issue?

Also, it seems that the qualifier REGULART would work only if the data was 
close to being evenly spaced.  In this case, the data has big gaps in time. 
So I doubt it would work.

Thanks for any more help on this,
Jerome.








> From: Ansley Manke <Ansley.B.Manke@noaa.gov>
> To: Jerome King <jejeking@hotmail.com>
> Subject: Re: [ferret_users] limit on storage
> Date: Wed, 09 Aug 2006 10:38:50 -0700
>
> Hi - Could you ask this back to the LAS and Ferret list?  I know how to do 
> this with Ferret descriptor files, but I am not familiar with aggregation.
>
> Ansley
>
> Jerome King wrote:
> > Hi Ansley!
> >
> > Thanks for your response.
> > Yes. I believe the irregular spacing comes from the gaps in the time 
> > series.
> > Can you help me find a way to get around the problem?
> > Thanks a bunch!
> > Jerome.
> >
> >
> >
> >
> > > From: Ansley Manke <Ansley.B.Manke@noaa.gov>
> > > To: Jerome King <jejeking@hotmail.com>
> > > CC: oar.pmel.ferret_users@noaa.gov, oar.pmel.las_users@noaa.gov
> > > Subject: Re: [ferret_users] limit on storage
> > > Date: Wed, 09 Aug 2006 10:13:29 -0700
> > >
> > > Hi Jerome,
> > > Yes, we're aware that this is becoming a problem for some datasets. It's 
> > > not an easy one for us to resolve, however.
> > >
> > > If the data were regularly spaced this would not be an issue at all. Does 
> > > the data you're aggregating have truly irregular time steps? Sometimes 
> > > the times are in fact regularly spaced, but irregular spacing comes in 
> > > because of gaps in the time series.  If that's the case we can probably 
> > > work out a way to deal with the data.
> > >
> > > Ansley
> > >
> > > Jerome King wrote:
> > > > Hi Ferreters and LASers,
> > > >
> > > > I am not a Ferret expert as I have rarelly used it. I have been dealing 
> > > > indirectly with it because of the customization I do with the Live 
> > > > Access Server.
> > > >
> > > > With new technologies such as THREDDS that allows to aggregate several 
> > > > datasets together, one can end up with really big files with a lot of 
> > > > time steps.
> > > >
> > > > I have been reaching the infamous error message several times now:
> > > > **TMAP ERR: limit on storage for coordinates has been
> > > > reached MAX=750000
> > > >
> > > > I am aggregating unevenly spaced data over time which probably makes 
> > > > things worse.
> > > >
> > > > I was wondering if anyone found a way around this problem or if the 
> > > > Ferret developers plan on improving this. There is a message in the 
> > > > archive about using dynamic storage and this may solve the issue. Are 
> > > > there any updates about this?
> > > >
> > > > Thanks a lot!
> > > > Jerome King.