Rubén,
Yes, each update should happen every 6 hours, but this is not exact,
because the process of data dissemination depends of many factors. Some
delays could happen.
As general rule, the data for 06UTC analysis is available 5-6 hours after.
http://nomads.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gfs.2016121506/
but another delay could happen to update the dataset on the thredds server.
It may be someone else has the answer.
Regards
Antonio
On 14/12/16 14:40, Rubén Vázquez wrote:
One last question Antonio. At what time UTC could call the xml for
each update of the model. It's every 6 hours right? What I want is to
save the xml data in each update to serve it on the map. At what time
UTC do I have to program in CRON? Thank you very much.
> El 13 de diciembre de 2016 a las 20:00 "Antonio S. Cofiño"
<cofinoa@xxxxxxxxx> escribió:
>
>
> yes ... and is quite more easy and convenient
>
>
http://thredds.ucar.edu/thredds/ncss/grib/NCEP/GFS/Global_0p25deg/Best?var=Wind_speed_gust_surface&latitude=42.5&longitude=-8.5&time_start=present&time_duration=P5D&accept=xml
>
> the "Best" forecast from present to 5-day period
> (time_start=present&time_duration=P5D)
>
> Antonio
>
>
>
> On 13/12/16 17:09, Rubén Vázquez wrote:
> > Sorry Antonio. I am realizing that in nomands I do not have the last
> > outlets of the model. I appear only from day 12. To have access to
the
> > last exit I have to do it from www.thredds.ucar.edu? Can I also pull
> > out the maximum wind gusts in xml?
> >
> > > El 13 de diciembre de 2016 a las 16:12 "Antonio S. Cofiño"
> > <cofinoa@xxxxxxxxx> escribió:
> > >
> > >
> > > Rubén,
> > >
> > > The URL you are accessing only contains one time step... in this
case
> > > the 384hours forecast for the 2016-12-11T06:00UTC analysisreference
> > time.
> > >
> > > If you want al the steps for the forthcoming 5 days (120 hours)
from
> > the
> > > 2016-12-11T06:00UTC analysis you need to loop over all the
> > availabletime
> > > steps:
> > >
> > > In bash scripting, something like this.
> > >
> > > #!/bin/bash
> > >
> > > touch Wind_speed_gust.xml
> > >
> > > for STEP in $(seq -w 0 3 120); do
> > >
> >
URL="http://nomads.ncdc.noaa.gov/thredds/ncss/grid/gfs-004/201612/20161211/gfs_4_20161211_0600_${STEP}.grb2?var=Wind_speed_gust&latitude=42.5&longitude=-8.5&accept=xml&point=true";
> > > wget -O - "$URL" >> Wind_speed_gust.xml
> > > done
> > >
> > > the script it's just a proof of concept purpose ... you need to
improve
> > > the reliability and scalability.
> > >
> > > Regards
> > >
> > > Antonio
> > >
> > >
> > >
> > > On 13/12/16 14:08, Nathan Potter wrote:
> > > > Hi Rubén,
> > > >
> > > > The specific server to which you are sending this request is a
> > THREDDS Data Server (aka TDS). I am forwarding your question to the
> > TDS support group in the hopes that they will have more insight
than I
> > can provide.
> > > >
> > > > Thanks for you patience.
> > > >
> > > > Sincerely,
> > > >
> > > > Nathan Potter
> > > >
> > > >
> > > >> On Dec 13, 2016, at 2:36 AM, Rubén Vázquez
> > <meteovigo@xxxxxxxxxxxx> wrote:
> > > >>
> > > >> Hello good day. My name is Rubén Vazquez and I am administrator
> > of www.meteovigo.es. I am making a map to show the maximum gusts in
> > Europe and North Atlantic and I want to do it with the GFS since I
> > think it is the best model in the world. What I do not get is to call
> > an xml with maximum wind gusts for the next 5 days. Could you help
me?
> > I just got this:
> > > >>
> > > >>
> >
http://nomads.ncdc.noaa.gov/thredds/ncss/grid/gfs-004/201612/20161211/gfs_4_20161211_0600_384.grb2?var=Wind_speed_gust&latitude=42.5&longitude=-8.5&temporal=all&time_start=2016-12-27T06%3A00%3A00Z&time_end=2016-12-27T06%3A00%3A00Z&time=2016-12-27T06%3A00%3A00Z&vertCoord=&accept=xml&point=true
> > > >>
> > > >>
> > > >>
> > > >> Thank you very much
> > > >>
> > > >> <logo-firma.png>
> > > >>
> > > >> Meteovigo Información Meteorológica
> > > >> Canido Playa, 157, 36390
> > > >> Vigo - Pontevedra - Spain
> > > >> 986 49 26 34 - 622 36 22 82
> > > >>
> > > >> meteovigo@xxxxxxxxxxxx
> > > >> www.meteovigo.es
> > > >>
> > > >>
> > > > = = =
> > > > Nathan Potter ndp at opendap.org
> > > > OPeNDAP, Inc. +1.541.231.3317
> > > >
> > > > _______________________________________________
> > > > NOTE: All exchanges posted to Unidata maintained email lists are
> > > > recorded in the Unidata inquiry tracking system and made publicly
> > > > available through the web. Users who post to any of the lists we
> > > > maintain are reminded to remove any personal information that they
> > > > do not want to be made public.
> > > >
> > > >
> > > > thredds mailing list
> > > > thredds@xxxxxxxxxxxxxxxx
> > > > For list information or to unsubscribe, visit:
> > http://www.unidata.ucar.edu/mailing_lists/
> > >
>
