coordinate system object

[GoogleCodeExporter]

   in the old nj_toolbox, we had a coordinate system object, 
which had methods to return the lat,lon,time,z axes separately,
e.g.
    coordSys = getCoordSys(geogrid);
    % get coordinate axes
    lat=coordSys.getLatAxis();
    lon=coordSys.getLonAxis();

Could we do this also?  I would like to just return the lat and lon for a 
variable easily and clearly.

-Rich

Original issue reported on code.google.com by rsignell on 30 Nov 2011 at 3:16

[GoogleCodeExporter]

I guess having methods on the geovariable of getlonvar and getlatvar would be 
okay too.  (seeing as we already have gettimevar)

Original comment by rsignell on 30 Nov 2011 at 3:20

[GoogleCodeExporter]

Original comment by crosb...@gmail.com on 30 Nov 2011 at 3:59

• Changed state: Started

[GoogleCodeExporter]

I need this functionality so I can
- include my nj_lonlat function in the njcompatibility folder
- having nj_lonlat, will allow me to include my nj_tseries4d function, which 
allows for extraction of time series data from a CF-compliant URL.  This will 
an big improvement on the existing "interp2xy" that is in the utilities/interp 
directory, which requires downloading way too much data (if I'm understanding 
it right).  My nj_tseries4d function just downloads the timeseries from the 
nearest point, or downloads timeseries from the surrounding points, and then 
does linear interpolation.

-Rich

Original comment by rsignell on 5 Dec 2011 at 3:10

[GoogleCodeExporter]

interp2xy is not really intended for straight time series extraction, although 
it can be used as such and its not tied to data access at all. I'm going to 
make these changes to the ncgeovariable class, but I will recommend that you 
implement them directly in nj_tseries4d instead of adding another file in 
between.

Original comment by crosb...@gmail.com on 5 Dec 2011 at 5:28

[GoogleCodeExporter]

That sounds fine.  I don't need to use the nj_lonlat function (although I will 
put it in the njcompatibility directory for backwards compatibility).

Original comment by rsignell on 5 Dec 2011 at 8:15

[GoogleCodeExporter]

Original comment by crosb...@gmail.com on 5 Dec 2011 at 8:24

• Changed state: Fixed

[GoogleCodeExporter]

Sounds good, give it a try, they should show up with methods()

>> methods ncgeodataset

Methods for class ncgeodataset:

addlistener    data           findprop       getlonname     gt             
ncgeodataset   size           timeextent     
attribute      delete         ge             getlonvar      isvalid        ne   
          standard_name  variable       
attributes     eq             geovariable    gettimename    le             
notify         struct         
axes           extent         getlatname     gettimevar     lt             
numel          subsref        
close          findobj        getlatvar      grid           metadata       save 
          time           

>> methods ncgeovariable

Methods for class ncgeovariable:

addlistener    eq             geoij          getlonvar      gt             ne   
          timewindow     
attribute      extent         geosubset      gettimename    isvalid        
notify         timewindowij   
data           findobj        getlatname     gettimevar     le             size 

delete         findprop       getlatvar      grid           lt             
subsref        
end            ge             getlonname     grid_interop   ncgeovariable  
timeextent     

Original comment by crosb...@gmail.com on 5 Dec 2011 at 8:33

[GoogleCodeExporter]

Do you want to return the data as well?

Original comment by crosb...@gmail.com on 5 Dec 2011 at 9:05

[GoogleCodeExporter]

I'm not seeing this fixed in the code.  Did you commit and push?

Original comment by rsignell on 5 Dec 2011 at 9:15

[GoogleCodeExporter]

Does this not show up? Revision: 3f4e82fc9a34

Original comment by crosb...@gmail.com on 6 Dec 2011 at 1:37

[GoogleCodeExporter]

No, I got it.  My bad.

Original comment by rsignell on 6 Dec 2011 at 1:45