Michael/Joe, I think I have some light to shine on your issues:
* TDS 5.0 is using a new version of ncWMS (version 1 to version 2) so WMS
comparison with TDS 4.6 is difficult.
* The `time` parameter in WMS requests does indeed work for a number of
aggregated datasets that I know of running on 4.6. If it is not working in
4.6 it is a bug or a dataset problem.
* The GeoServer documentation linked does not apply to the TDS WMS
implementation. They are different beasts. You should Google "ncWMS 2
Documentation".
Could you both link to a TDS dataset you are having issues with?
On Thu, Apr 26, 2018, 12:12 AM Michael McDonald <mcdonald@xxxxxxxxxxxxx>
wrote:
> Joe,
>
> https://groups.google.com/a/hycom.org/d/msg/forum/S-eMRyZ9180/8M23JBJTBgAJ
>
>
> We too had a similar issue with WMS that no one really "pointed out to me"
> for our "aggregated" datasets until I read this WMS "Limitations" clause at
> the bottom of this page,
>
> http://docs.geoserver.org/stable/en/user/data/cascaded/wms.html#limitations
>
> One of them being certain dimensions, like "time" cannot be used with
> "external WMS"...
>
> quote from "Limitations" at the bottom:
> * Extra request parameters (time, elevation, cql_filter, etc.) cannot be
> used.
>
>
> So unless your dataset aggregation with the WMS service enabled *worked*
> in the previous 4.x release of THREDDS (ours 4.x THREDDS at HYCOM.org does
> exactly as yours does - only returning the last time slice in the
> aggregation), and assuming there was no major update to WMS in v5 of
> THREDDS, then this remote/external WMS limitation should still persist.
> i.e., in summary, you should only expose/enable the WMS service for
> individual "single time" datasets and not for aggregations with multiple
> time slices.
>
> Someone, please correct me if I am wrong.
> _______________________________________________
> 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/
