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.
Greetings Ellyn, I think the shapes of the profile variables should be (profile, depth), while the coordinate attribute should be "time lon lat depth". Let me take a look at the raw file and see what I can come up with today, as it could be a little tricky. Thanks! Sean > Hi Sean- > > For the ADCP data, the raw file has variables of 2 kinds of dimensions: > (time, depth, lat, lon) and (time, lat, lon). The latter can be > represented as from the previous ticket, and the velocities fitting the > former shape should be timeSeriesProfiles (I think). Should the profile > dimension replace time? or is( time profile, depth) what's needed? > > Thanks! Ellyn > Ellyn T. Montgomery, Oceanographer and Data Manager > U.S. Geological Survey > Woods Hole Coastal and Marine Science Center > 384 Woods Hole Road, Woods Hole, MA 02543-1598 > (508)457-2356 > > > > From: > "Unidata netCDF Java Support" <address@hidden> > To: > address@hidden > Cc: > address@hidden > Date: > 09/25/2012 01:10 PM > Subject: > [netCDFJava #DCH-123831]: problems using ncML to represent as > timeSeriesProfile > > > > Greetings Ellyn, > > Are you following the CF 1.6 conventions for a Time series of profiles at > a single station? > > http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#idp8427872 > > > In this case, lat and lon will be scalars (i.e. shape = ""), you won't > need a station dimension, > but you will need a profile dimension. Your variables will have a shape = > "profile depth". > > Cheers, > > Sean > > > Hi- > > > > I am having trouble getting data morphed into a CF-1.6 > > timeSeriesProfile. Our single depth files only work in toolsUI, if > > there's a station dimension, even though it is size 1, so I tried to > > carry that over to adcp data with multiple depths, but have had no > > success. I think the two attached files are close to what they should > > be, but neither opens correctly in the toolsUI featureType > > > PointFeature tab. The prf file has a station dimension, and lat and lon > > are dimensioned as shape="station", the prf2 file has no station > > dimension and lat and lon are dimensioned as shape=" ". > > > > The the original file is viewable here: > > http://stellwagen.er.usgs.gov/opendap/HUDSON_SVALLEY/8181adc-a1h.nc.html > > > > If you're interested, the attached -ts file contains just the 1-depth > > variables from the same original file, with the station dimension that I > > think should be unnecessary. This opens fine in toolsUI featureType > > > PointFeature. > > > > Thanks for the help setting me straight on this- > > Best, Ellyn > > > > -- > > Ellyn T. Montgomery, Oceanographer and Data Manager > > U.S. Geological Survey > > Woods Hole Coastal and Marine Science Center > > 384 Woods Hole Road, Woods Hole, MA 02543-1598 > > (508)457-2356 > > > > > > > > Ticket Details > =================== > Ticket ID: DCH-123831 > Department: Support netCDF Java > Priority: Normal > Status: Open > > > > > Ticket Details =================== Ticket ID: DCH-123831 Department: Support netCDF Java Priority: Normal Status: Open