Times are out of order on two of your datasets

43 views
Skip to first unread message

Roy Mendelssohn - NOAA Federal

unread,
Dec 4, 2023, 5:11:06 PM12/4/23
to fo...@hycom.org
Please look at the following dataset:

https://tds.hycom.org/thredds/dodsC/glb_analysis.html

for this I did:

https://tds.hycom.org/thredds/dodsC/glb_analysis?MT[1700:1:1800]

the results show at the end:

41128.0, 41129.0, 41130.0, 41131.0, 41132.0, 41133.0, 41134.0, 41135.0, 41136.0, 41137.0, 41138.0, 41139.0, 41140.0, 40180.0, 40181.0, 40182.0

You can see the times are not ordered.

Thanks,

-Roy

**********************
"The contents of this message do not reflect any position of the U.S. Government or NOAA."
**********************
Roy Mendelssohn
Supervisory Operations Research Analyst
NOAA/NMFS
Environmental Research Division
Southwest Fisheries Science Center
***Note new street address***
110 McAllister Way
Santa Cruz, CA 95060
Phone: (831)-420-3666
Fax: (831) 420-3980
e-mail: Roy.Men...@noaa.gov www: https://www.pfeg.noaa.gov/

"Old age and treachery will overcome youth and skill."
"From those who have been given much, much will be expected"
"the arc of the moral universe is long, but it bends toward justice" -MLK Jr.

Michael McDonald

unread,
Dec 4, 2023, 7:13:21 PM12/4/23
to Roy Mendelssohn - NOAA Federal, fo...@hycom.org
Roy,
This (hidden/legacy) THREDDS aggregation "glb_analysis" is dated and
not recommended for use anymore. It was an aggregation "of
convenience" joining (crudely) all/multiple GLBa0.08 experiments (90.6
to 91.2). Any time overlap from the experiment that comes next will
cause this time order issue to occur as its time array gets appended
to the existing time array.

The GOFS 3.1 data should be used instead.
https://www.hycom.org/dataserver/gofs-3pt1/analysis


<dataset name="1/12 degree HYCOM + NCODA Global Hindcast Analysis (Combined)"
ID="GLBa0.08-glb_analysis" urlPath="glb_analysis">
<serviceName>all</serviceName>
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2">
<aggregation dimName="MT" type="joinExisting">
<netcdf location="dods://<%= @tds_URI %>/thredds/dodsC/GLBa0.08/expt_90.6"/>
<netcdf location="dods://<%= @tds_URI %>/thredds/dodsC/GLBa0.08/expt_90.8"/>
<netcdf location="dods://<%= @tds_URI %>/thredds/dodsC/GLBa0.08/expt_90.9"/>
<netcdf location="dods://<%= @tds_URI %>/thredds/dodsC/GLBa0.08/expt_91.0"/>
<netcdf location="dods://<%= @tds_URI %>/thredds/dodsC/GLBa0.08/expt_91.1"/>
<netcdf location="dods://<%= @tds_URI %>/thredds/dodsC/GLBa0.08/expt_91.2"/>
</aggregation>
</netcdf>
</dataset>


If you explicitly want this GOFS 3.0 data, then I would recommend the
use of the individual experiment aggregations here,

https://www.hycom.org/dataserver/gofs-3pt0/analysis

e.g.,
https://tds.hycom.org/thredds/catalogs/GLBa0.08/expt_91.2.html
...
https://tds.hycom.org/thredds/catalogs/GLBa0.08/expt_90.6.html
> --
> --
> You received this message because you are a member of HYCOM.org
> To ask a question, send an email to fo...@hycom.org
>
>


--
Michael McDonald
HYCOM.org Administrator

Roy Mendelssohn - NOAA Federal

unread,
Dec 4, 2023, 9:30:03 PM12/4/23
to Michael McDonald, fo...@hycom.org
Thanks. We want to use the recommended option. I will change to that tomorrow.

-Roy
Reply all
Reply to author
Forward
0 new messages