RE: Intelligent dealing with duplicate element by LAS.pm

["McCann, Mike" <mccann@xxxxxxxxx>]

Jon,

The problem is that I have different DEPTH_HR axes.  The met data is
at only one level and the Tstring and ADCP data are at mulitiple levels.
The TIME_HR axis is common for all the instruments.

This requires at least 2 different grids, since the lat, lon, & time
are all the same this produces duplicate tags.  I've renamed the lat
and lon for the different instruments, but the time axis needs to have
the same name as it is my unlimited dimension.

For now, I think I'm going to write a little script to remove the 
duplicate time axis tag.  

-Mike 

> -----Original Message-----
> From: Jonathan Callahan [mailto:callahan@pmel.noaa.gov]
> Sent: Tuesday, August 28, 2001 1:08 PM
> To: McCann, Mike
> Cc: 'sirott@pmel.noaa.gov'; las_users@ferret.wrc.noaa.gov
> Subject: Re: Intelligent dealing with duplicate element by LAS.pm
> 
> 
> Mike,
> 
> I presume the duplicated axes are longitude and latitude.  When I look
> at your data with Ferret I see three grids:
> 
> yes? show grid gmj1
>     GRID GMJ1
>  name       axis              # pts   start                end
>  LONGITUDE LONGITUDE            1 r   122.39W              122.39W
>  LATITUDE  LATITUDE             1 r   36.7N                36.7N
>  DEPTH_HR  DEPTH (m)          101 r-  0                    500
>  TIME_HR   TIME             24456 r   29-JUN-1998 00:00    12-APR-2001
> 23:00
> yes? show grid gmj2
>     GRID GMJ2
>  name       axis              # pts   start                end
>  LONGITUDE_HR LONGITUDE         1 r   122.39W              122.39W
>  LATITUDE_HR LATITUDE           1 r   36.7N                36.7N
>  DEPTH_HR  DEPTH (m)          101 r-  0                    500
>  TIME_HR   TIME             24456 r   29-JUN-1998 00:00    12-APR-2001
> 23:00
> yes? show grid gmj3
>     GRID GMJ3
>  name       axis              # pts   start                end
>  LONGITUDE_MET_HR LONGITUD      1 r   122.39W              122.39W
>  LATITUDE_MET_HR LATITUDE       1 r   36.7N                36.7N
>  DEPTH     DEPTH (m)            1 r-  3.5                  3.5
>  TIME_HR   TIME             24456 r   29-JUN-1998 00:00    12-APR-2001
> 23:00
> 
> 
> The longitude axes appear to be the same in all three grids but have
> three separate names.  The same is true for the latitude 
> axes.  The time
> axis is shared by all three grids.
> 
> I expect that if your netCDF files specified a single 
> longitude axis and
> a single latitude axis the multiple axes created by 
> genLas2.pl would go
> away.
> 
> Let us know if my hunch is incorrect.
> 
> 
> -- Jon
>  
> 
> "McCann, Mike" wrote:
> > 
> > Hi,
> > 
> > This message is probably just for Joe, but others may have 
> encountered this issue as well, so I am copying the list. I 
> have a data set that generates duplicate axes when processed 
> by genLas2.pl:
> > 
> http://dods.shore.mbari.org/cgi-bin/nph-nc/data/OASISdata/netc
df/hourlyM2.nc <http://dods.shore.mbari.org/cgi-bin/nph-nc/data/OASISdata/netcdf/hourlyM2.nc>
> 
> Would it be possible to have some code in LAS.pm (or somewhere) that would not create these duplicate axes, or remove it if a duplicate is encountered?  I'm trying to automate data set additions and removing these duplicate axes prevents this for me.
> 
> Thanks,
> Mike
> 
> --
> Mike McCann   (mccann@mbari.org)
> Monterey Bay Aquarium Research Institute
> 7700 Sandholdt Road
> Moss Landing, CA 95039-9644
> Voice: (831) 775-1769   Fax: (831) 775-1646 http://www.mbari.org/rd/iag.htm <http://www.mbari.org/rd/iag.htm>