[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDFJava #QEX-289573]: point file

Greetings Bill,

I think maybe the confusion comes in when I say something like

"I'm not able to get this to open as a POINT either. However, if I make
a few modifications using NcML, I can get it to open as STATION (see
attached NcML)."

Here, POINT and STATION refer to how netCDF-Java deals with point based data. 
This was done before
and along-sdie development of CFs Discrete Sampling Geometries. Roughly, POINT 
maps to CFs point 
DSG, and STATION maps to CFs timeSeries DSG.

Your file was pretty close - just missing a few pieces of metadata. The changes 
I made to your file will 
make it compliant with the time series (H.2.3) DSG and recognizable by 
netCDF-Java (and thus RAMADDA):

http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-conventions.html#_single_time_series_including_deviations_from_a_nominal_fixed_spatial_location

In order to do that, I had to do the following:

Add the global attribute Conventions = "CF-1.6"

Add the attribute positive = "up" to the variable altitude

Add the attribute cf_role = "timeseries_id" to the variable station_name

Add the attribute coordinates = "time latitude longitude altitude station_name" 
to all data variables

I also fixed a few units values for temperature related variables, as "deg C" 
isn't udunts compliant, but "degC" is.

Cheers!

Sean

> Hi Sean.
> 
> I was trying to be CF metadata standard compliant with time series.  To 
> clarify, should I abandon that and go to CF *point* data?
> 
> http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-conventions.html#example-h.1
> 
> https://www.nodc.noaa.gov/data/formats/netcdf/v2.0/point.cdl
> 
> Cheers and Thanks
> Bill
> 
> 
> From: Jeff McWhirter <address@hidden>
> Date: Monday, February 5, 2018 at 18:16 MST
> To: "address@hidden" <address@hidden>
> Cc: William Capehart <address@hidden>
> Subject: Re: [netCDFJava #QEX-289573]: point file
> 
> Thanks Sean
> Bill, it would be optimal to change the format of your netcdf files (if 
> possible) to conform to the standard point convention (Perhaps Sean can help 
> with that).  Then add the .nc files to Ramadda as a "Netcdf  Point File". 
> Once added you can chart the data and/or access/convert it via the "Subset 
> and Products" service.
> You can also keep the current format and use the attached ncml template file 
> to dynamically transform your current files to the standard. To do this do:
> First - install the latest version of ramadda as I had to fix a bug to make 
> this work.
> Then, go to the parent folder that contains your netcdf files and do 
> "Edit->Add Property..." Under the "Thumbnails, Page Style, Etc." collection 
> choose "Add File Attachment". Select station.ncml and make sure to check on 
> the inherited checkbox. Any netcdf file that gets opened by ramadda under 
> that folder will use the ncml file
> Now add the netcdf files as "Netcdf Point File" - go to the folder's menu and 
> choose "Pick a Type". Under the "Geoscience->Point Data" you'll see the 
> netcdf point file.
> 
> Here is the charting page for an example file:
> https://geodesystems.com/repository/entry/show/Home/Community/People/Jeff+McWhirter/Development/Test+netcdf/Ghcnd-usw00024090+Rapid+City+Regional+Airport+Sd?entryid=04b67b3f-4a1b-48cc-8510-04404c002079&output=points.chart
> 
> and the subset page for it:
> https://geodesystems.com/repository/entry/show/Home/Community/People/Jeff+McWhirter/Development/Test+netcdf/Ghcnd-usw00024090+Rapid+City+Regional+Airport+Sd?entryid=04b67b3f-4a1b-48cc-8510-04404c002079&output=points.form
> 
> 
> -Jeff
> 
> On Fri, Feb 2, 2018 at 11:53 AM, Unidata netCDF Java Support 
> <address@hidden<mailto:address@hidden>> wrote:
> Hi Jeff,
> 
> I'm not able to get this to open as a POINT either. However, if I make
> a few modifications using NcML, I can get it to open as STATION (see
> attached NcML).
> 
> Cheers,
> 
> Sean
> 
> > Hi,
> >
> > Bill Capehart has a point netcdf file on his ramadda server (attached). The
> > CDM code fails to open this as a FeatureDatasetPoint with the below code.
> >
> > Any ideas?
> >
> > Thanks
> > Jeff
> >
> >
> >
> >
> > FeatureDatasetPoint pods =
> > (FeatureDatasetPoint) FeatureDatasetFactoryManager.open(
> > ucar.nc2.constants.FeatureType.POINT, path, null, buf);
> > if (pods == null) {  // try as
> > ANY_POINT
> > pods = (FeatureDatasetPoint) FeatureDatasetFactoryManager.open(
> > ucar.nc2.constants.FeatureType.ANY_POINT, path, null, buf);
> >
> >
> 
> 
> Ticket Details
> ===================
> Ticket ID: QEX-289573
> Department: Support netCDF Java
> Priority: Normal
> Status: Open
> ===================
> NOTE: All email exchanges with Unidata User Support are recorded in the 
> Unidata inquiry tracking system and then made publicly available through the 
> web.  If you do not want to have your interactions made available in this 
> way, you must let us know in each email you send to us.
> 
> 

Ticket Details
===================
Ticket ID: QEX-289573
Department: Support netCDF Java
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.