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.
Hi Jon, The FMRC code always determines the valid time of the data by opening the data file and looking at the time coordinates for the data. The run time, on the other hand, needs to be given either in the file name or elsewhere in the data, in a global attribute for instance. How is the run time encoded in these files? Can you send us some example datasets? Thanks, Ethan On 6/22/2010 3:02 PM, Jon Blower wrote: > Hi, > > We have a potential issue in MyOcean that filenames typically contain > two dates, representing the start and end validity times of data within > the file. When creating an FMRC aggregation the filename is usually > parsed to get the run time, but this parsing is hard when the file name > contains two dates/times, both of which vary between files, e.g. > "ice_drift_polstereo_wsm_envisat_north_20100601013759-20100602010520.nc" > . > > Is there a workaround for this? See > http://www.resc.reading.ac.uk/trac/myocean-tools/ticket/18. > > Cheers, Jon > > -- > Dr Jon Blower > Technical Director, Reading e-Science Centre > Environmental Systems Science Centre > University of Reading
thredds archives: