Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Steve Emmerson wrote: > > Bill, > > >Date: Thu, 06 Apr 2000 12:45:03 -0500 > >From: Bill Hibbard <hibbard@xxxxxxxxxxxxxxxxx> > >To: Stuart Wier <wier@xxxxxxxxxxxxxxxx> > >Subject: Re: basic topology and the Data Model with geo-locations > > In the above message, you wrote: > > > 3. ((lat, lon, alt) -> (time, obs)) > > In this case, the domain Set would be a Gridded3DSet with > > manifold dimension = 1. This is probably the preferable > > way, since it preserves the notion that the spatial points > > are along a path rather than just a random scatter. > > How would one programatically know that "time" is the manifold variable > and not "obs"? > I'm partial to (time) -> ((lon, lat, alt) -> (obs)). This makes resampling by time or space rather convenient. VMET assumes such an arrangement. I don't want to start a religious war but I also prefer (lon,lat,alt) over (lat,lon,alt) because it relates directly to (x,y,z). Doug -- *----------------------------------------------------------------------* | Doug Lindholm, Software Engineer | E-mail: lind@xxxxxxxx | | Research Applications Program | Phone: 303-497-8374 | | National Center for Atmospheric Research | | | P.O. Box 3000 | There's no place | | Boulder, Colorado 80307-3000 | like $HOME | *----------------------------------------------------------------------*
visad archives: