[Thread Prev][Thread Next][Index]
[las_users] Illegal limits error on Western longitude using LAS Armstrong 1.1.1
- To: las_users@xxxxxxxx
- Subject: [las_users] Illegal limits error on Western longitude using LAS Armstrong 1.1.1
- From: "Oots, Penny C. (LARC-E301)[SCIENCE SYSTEMS & APPLICATIONS INC.]" <penny.c.oots@xxxxxxxx>
- Date: Wed, 30 Apr 2008 08:55:19 -0500
- Cc: Ansley Manke <Ansley.B.Manke@xxxxxxxx>
- Sender: owner-las_users@xxxxxxxx
- Thread-index: AciqydN5m8dijOMTQ4ayjzmKtMsGhw==
- Thread-topic: Illegal limits error on Western longitude using LAS Armstrong 1.1.1
I have included the following data in my LAS Armstrong 1.1.1 server
(Ferret 6.08) on a development server:
http://oceanwatch.pfeg.noaa.gov/thredds/dodsC/satellite/SW/chla/mday
A color plot is produced if the lon requested is 0 to 360. However, if
180W to 180E is used, I get the following error:
**ERROR: illegal limits: I on grid (G002) does not exist at X=180E(-180)
Axis extremes are X=0.3W(-0.3):0.1E(360.1)
DEFINE VARIABLE strd_lo = `i[gx=pvar,x=-180]`
Command file, command group, or REPEAT execution aborted
STOP -script mode, ERROR RUNNING SCRIPT statement executed
I included the following init script:
SET DATA ($data_url)
!<custom
set axis/modulo LON
!custom>
Got this error:
*** NOTE: Stride value not an integer factor of axis length: Axis loses
modulo property
**ERROR: illegal limits: I on grid (G002) does not exist at
X=180E(-180)
Axis extremes are X=0.3W(-0.3):0.1E(360.1)
DEFINE VARIABLE strd_lo = `i[gx=pvar,x=-180]`
Command file, command group, or REPEAT execution aborted
STOP -script mode, ERROR RUNNING SCRIPT statement executed
Note: This same dataset in a LAS 6.5.1 (Ferret 6.05) server will show a
plot starting at 0 degrees going to 160 degrees.
Can you suggest a way to make this dataset accessible using 180W to
180E?
Penny Oots
Science Systems & Applications Inc.
NASA Langley Research Center, MS 157D
Hampton, VA 23681-2199
(757) 864-9816
[Thread Prev][Thread Next][Index]
Contact Us
Dept of Commerce /
NOAA /
OAR /
PMEL /
TMAP
Privacy Policy | Disclaimer | Accessibility Statement