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

Re: 20051220: NcML Aggregation in THREDDS

Hi Bjorge:

Since you are explicitly writing the netcdf elements, we were expecting that 
you could write the correct values there without having to translate through a 
DateFormat. Is that not so? (see below also)

Unidata Support wrote:
------- Forwarded Message

To: address@hidden
From: =?ISO-8859-1?Q?Bj=F8rge_Solli?= <address@hidden>
Subject: NcML Aggregation in THREDDS
Organization: Nansen Environmental and Remote Sensing Center - Bergen
Keywords: 200512201217.jBKCH47s009594 THREDDS NcML aggregation


I am currently rewriting our xml-files to use the new aggregation functionality in Thredds 3.4. I have looked over all the documentation I could find on thredds and NcML but still have one unansvered Q. Hope you can help:

In the old version we used AggServer with an xml-statement like this:
<aggregation serviceName=".." aggType=".." varType=".." varUnit".." dateFormat="yyyy/M/d:hh:mm:ss z">
<fileAccess urlPath="long_name_b20030604_f200305289999.nc" coord="2003/05/28:00:00:00 GMT" />

My remaining Q is where I should write dateFormat now. I have something like this:
<variable name="time" type="int" shape="time">
<attribute name="units" value=".." />
<attribute name="_CoordinateAxisType" value="Time" />

Here you are defining a time coordinate of dataType "int"

<aggregation dimName="time" type="joinNew">
<variableAgg name="T" />
netcdf location="long_name_b20030604_f200305289999.nc" coord=""2003/05/28:00:00:00 GMT" />

But you are giving it String values.

Do you have the ability to write ISO 8601 date strings? If so, I would change the type of the time coordinate to String and do that.


Since I am not using the scan tag I cannot use the dateFormatMark either (which would not work on this example anyway since the filename is not the same in front of the #-mark, which would have to be after the '_f').

We will also add regular expression matcher for that case.

Hope you understand my question and find time to answer.


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.