Re: [thredds] Wind Vectors with TDS 5.0.0 ?

  • To: Sean Arms <sarms@xxxxxxxx>
  • Subject: Re: [thredds] Wind Vectors with TDS 5.0.0 ?
  • From: Jason Greenlaw - NOAA Affiliate <jason.greenlaw@xxxxxxxx>
  • Date: Tue, 28 Feb 2017 22:24:34 -0500
Hi Sean,

Sure, I'll submit a bug report.  I didn't want to submit one without first
having asked around to make sure I'm not doing something stupid :).

Thanks for the response.
Jason



On Tue, Feb 28, 2017 at 7:54 PM, Sean Arms <sarms@xxxxxxxx> wrote:

> Greetings Jason,
>
> Thanks for the report! We are still in the process of getting ncWMS2
> working in the TDS, and it looks like you've found one of the many
> holes! Do you by any chance use github, and if so, would you mind
> submitting a bug report there? If not, would you mind if I used your
> message to put up a bug report for us to track?
>
> Thank you!
>
> Sean
>
>
> On Tue, Feb 28, 2017 at 9:15 AM, Jason Greenlaw - NOAA Affiliate
> <jason.greenlaw@xxxxxxxx> wrote:
> > A couple more pieces of information about this...
> >
> > 1) The GFS u/v wind component variables do appear to use the proper
> naming
> > conventions (per ncWMS2 documentation)
> >
> > 2) Using similar model output but in NetCDF format (instead of GRIB2) and
> > specifying featureType="FMRC", the wind vectors work fine.
> >
> >
> >
> >
> > On Mon, Feb 27, 2017 at 11:08 PM, Jason Greenlaw - NOAA Affiliate
> > <jason.greenlaw@xxxxxxxx> wrote:
> >>
> >> Hello all,
> >>
> >> I'm trying to replicate in TDS 5.0.0 some functionality I had working
> with
> >> TDS 4.6 -- producing a collection/aggregation of NCEP GFS model output
> >> (GRIB2 format) and exposing it via WMS.
> >>
> >> I've been able to successfully generate the "Full Collection Dataset"
> >> resource and it's working great (see config snippet below), but with one
> >> exception:  the u & v components of wind are not being combined into a
> >> unified "wind" variable, i.e., a single WMS layer that will allow the
> u/v
> >> wind field to be rendered with ncWMS using barb/vector styles.
> >>
> >> This functionality was working in TDS 4.6 without any additional
> >> configuration, but does not seem to be working the same with TDS 5.0.
> >>
> >> Are there specific settings I should be using in catalog.xml to tell TDS
> >> 5.0 that the "u/v component of wind" variables represent a vector field?
> >>
> >> FYI, I'm using the TDS 5.0.0 snapshot from 2017-02-21T21:22:48.
> >>
> >> Thanks,
> >> Jason
> >>
> >>
> >>
> >> from catalog.xml:
> >>
> >> ------------------------------------------------------------
> -------------------
> >>  <service name="all" base="" serviceType="compound">
> >>     <service name="odap" serviceType="OpenDAP" base="/thredds/dodsC/" />
> >>     <service name="dap4" serviceType="DAP4" base="/thredds/dap4/" />
> >>     <service name="http" serviceType="HTTPServer"
> >> base="/thredds/fileServer/" />
> >>     <service name="wcs" serviceType="WCS" base="/thredds/wcs/" />
> >>     <service name="wms" serviceType="WMS" base="/thredds/wms/" />
> >>     <service name="ncss" serviceType="NetcdfSubset"
> base="/thredds/ncss/"
> >> />
> >>   </service>
> >>
> >>  <featureCollection name="NCEP GFS 2.5 Degree" featureType="GRIB2"
> >> path="gfs2p5">
> >>     <metadata inherited="true">
> >>       <serviceName>all</serviceName>
> >>       <documentation type="summary">NCEP GFS 2.5 degree</documentation>
> >>     </metadata>
> >>     <collection spec="content/gfs/.*grib2$"
> >>                 name="GFS_2P5"
> >>                 timePartition="file"
> >>                 olderThan="5 min" />
> >>     <update startup="nocheck" />
> >>     <tdm rewrite="test" rescan="0 0/15 * * * ? *" />
> >>   </featureCollection>
> >>
> >> ------------------------------------------------------------
> -------------------
> >>
> >
> >
> > _______________________________________________
> > 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/
>
  • 2017 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: