Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6

2012-04-03 Thread Lowry, Roy K.
Hello again, It has been pointed out to me that in the current SeaDataNet format specification (written and updated by me!) that the initial position of insisting upon depth for the z co-ordinate was relaxed to allow either pressure or depth. So, I guess we need to be relaxed and leave z

Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6

2012-04-03 Thread Nan Galbraith
Hi Andrew - I am not sure if I should have TEMPERATURE and SALINITY arrays with 4 dimensions like TEMPERATURE(TIME,LATITUDE,LONGITUDE,PRESSURE) or just 1 dimension like I have above i.e. TEMPERATURE(PRESSURE). ? While we don't store profile data in OceanSITES, we are working on our

Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6

2012-04-03 Thread Jonathan Gregory
Dear Andrew and Nan If your pressure isn't monotonic, and so can't be a coordinate variable, I don't know whether it's preferable to demote ALL the coordinates to auxiliary coordinate variable status, TEMPERATURE: coordinates = TIME,PRESSURE,LATITUDE,LONGITUDE ; I don't think there's a

Re: [CF-metadata] CF-1.6 Conformance Requirements/Recommendations

2012-04-03 Thread Jonathan Gregory
Dear Karl I am not quite sure if I have understood you. I have changed ticket 85 to propose the following for sect 9.6: Wherever there are unused elements in data storage, the data variable and all its auxiliary coordinate variables (spatial and time) must contain missing values. This situation

Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6

2012-04-03 Thread Jim Biard
Hi. A colleague of mine has told me that if you use size-1 array for a variable, then data servers such as THREDDS can aggregate the variable over multiple files and deliver a single file in which the variables will be arrays of size 1. He said that if a variable is a scalar, THREDDS won't do

Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6

2012-04-03 Thread Upendra Dadi
Hi, I think Jim is talking about NCML (virtual) aggregation. THREDDS can aggregate even when the variable is a scalar using joinNew. But I think THREDDS can aggregate only over regular arrays. That is, all the dimensions other than over which a variable is aggregated should be of same size

Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6

2012-04-03 Thread John Caron
Hi all: Lets see, I havent followed the entire conversation, but: 1) Andrew if you can send me a sample file (not just the CDL) I can check if it works in the CDM with the new 1.6 conventions, and maybe give you some advice from my POV. 2) Aggregation in the CDM comes in 2 flavors. 1) The

Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6

2012-04-03 Thread andrew walsh
Hi Thierry, Thank you for this information. These netCDF examples and documentation are excellent. I was able to visualise (vertical cross section of Temperature ,Salinity) the Pheidippides glider netCDF data with the ncBrowse tool OK. Regards, Andrew - Original Message - From:

Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6

2012-04-03 Thread andrew walsh
Hi Jonathan, Thanks, for your reply and from others in the CF community. I certainly have had lots of responses on this topic, all useful information. I appreciate your deep knowledge of the CF standard which often clarifies the best way to do things. Actually I am not 100% clear about use of

Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6

2012-04-03 Thread andrew walsh
Hi Upendra and Jim, Thanks for answering my questions about capabilities of the viewing sofware e.g ncBrowse and also the ideas around aggregation. A NCML enhancement to allow aggregation of different sized depth/pressure arrays could be very useful for ocean profile data from e.g. CTD, ARGO,