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

[THREDDS #PSU-730086]: Error code 500: message= "NcSDArray InvalidRangeException=Number of ranges in section (2) must be = 3"

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #PSU-730086]: Error code 500: message= "NcSDArray InvalidRangeException=Number of ranges in section (2) must be = 3"
  • Date: Fri, 26 Feb 2010 14:21:11 -0700
You need new ncml. send me your config catalog and ill check on what changes 
are needed

> I have loaded that new version of THREDDS onto my EDAC server.
> The URL for the affected database is:
> http://edac-dap2.northerngulfinstitute.org/thredds/catalog/fmrc/rtofs/catalog.html
> 
> ----- Original Message -----
> From: Unidata THREDDS Support <address@hidden>
> Date: Friday, February 26, 2010 2:51 pm
> Subject: [THREDDS #PSU-730086]: Error code 500: message= "NcSDArray 
> InvalidRangeException=Number of  ranges in section (2) must be = 3"
> To: address@hidden
> Cc: address@hidden, address@hidden, address@hidden, address@hidden
> 
> 
> > snapshot release is at
> >
> > > Ah, excellent!  I missed the earlier message!
> > >
> > > -Rich
> > >
> > > On Thu, Feb 25, 2010 at 9:08 PM, Unidata THREDDS Support
> > > <address@hidden> wrote:
> > > > not sure if you saw my previous email, but we do have a fix for
> > these Curvilinear Orthogonal grids.
> > > >
> > > >> > John,
> > > >> >
> > > >> > I was just wondering, the fact that
> > > >> > [0:1:10][0:1:10]
> > > >> >
> > > >> > returns
> > > >> > Error {
> > > >> > code = 500;
> > > >> > message = "NcSDArray InvalidRangeException=Number of ranges in
> > > >> > section (2) must be = 3";
> > > >> > };
> > > >> >
> > > >> > when we access lon_rho, reminds me of some problem you
> > mentioned where
> > > >> > the FMRC tries to aggregate the lon,lat variables, and you said
> > we had
> > > >> > to explicitly exclude them from aggregation somehow.   Or something.
> > > >> > Do you remember this?  Would it be relevant here?
> > > >>
> > > >> yeah that sounds familiar, though i forget the details. do you
> > have any of the old emails?
> > > >>
> > > >>
> > > >
> > > >
> > > > Ticket Details
> > > > ===================
> > > > Ticket ID: PSU-730086
> > > > Department: Support THREDDS
> > > > Priority: Normal
> > > > Status: Open
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Dr. Richard P. Signell   (508) 457-2229
> > > USGS, 384 Woods Hole Rd.
> > > Woods Hole, MA 02543-1598
> > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: PSU-730086
> > Department: Support THREDDS
> > Priority: Normal
> > Status: Open
> >
> 
> 


Ticket Details
===================
Ticket ID: PSU-730086
Department: Support THREDDS
Priority: Normal
Status: Open