Greetings Pierre,
If you do not specify vertCoord in the request, then the data on all
vertical levels are returned and the TDS does not need to look at the
vertical coordinate at all. As you've found, the vertCoord subsetting
only works when the variables requests have the same vertical
coordinate variable. This is a limitation of the TDS.
Ideally the server should treat vertCoord like lat/lon or time, in
that the "closest" match to the coordinate value requested in the
subset should be returned. It's a bit tricky, though, as different
vertical coordinates can have different units, and so choosing the
closest "value" alone (which is what is supplied to vertCoord) would
not work. The TDS handles lat/lon and time a bit differently because
it knows about the units of lat/lon and time supplied by the request,
as those are determined by the web API (fore example, times are
spcified as W3C dates, lat/lon as degrees north, degree east):
http://www.unidata.ucar.edu/software/thredds/current/tds/reference/NetcdfSubsetServiceReference.html
There is no implied unit in vertCoord, so the assumption is made that
all variables have the same vertical coordinate variable when
vertCoord is used.
Perhaps a useful enhancement would be to allow a user to supply
vertCoord and vertCoordUnit independent of what vertical coordinate
variables are in the file, but then things again get tricky. Say a
user asks for a subset for the 600 hPa level, but the data are stored
on geopotential height levels. Should we assume an ideal atmospheric
profile to compute an equivalent height? While ideal profile? What
about a request of, say 36,000 ft, but the vertical coordinates are on
sigma levels? I suspect these kinds of questions are why vertCoord is
as limited as it is at the moment.
As an end user, how would you like to see vertCoord become more
useful? I think enhancements are possible, but I am not sure what the
appropriate assumptions are to make things work.
Sean
On Tue, May 16, 2017 at 9:13 AM, Lacoste Pierre (DAVIDSON)
<PLacoste@xxxxxx> wrote:
> Hello,
>
>
>
> I’m a user of Thredds and I try to execute a request with the parameter
> “VertCoord”.
>
> When I did it, I got the following error:
>
> “The variables requested: […] have different vertical levels. Grid requests
> with vertCoord must have variables with same vertical levels.”
>
> The variable list contains variable with different dimensions
>
> When I execute the request without “VertCoord”, I didn’t get the error.
>
> Why thredds does the difference between a request which contains variables
> with different dimensions without VertCoord specified and a request which
> contains variables with different dimension with a VertCoord specified
>
>
>
> Thanks,
>
>
>
> Pierre
>
>
>
> ________________________________
>
> Ce message et toutes les pièces jointes (ci-après le "message") sont établis
> à l'intention exclusive de ses destinataires et sont confidentiels. Si vous
> recevez ce message par erreur ou s'il ne vous est pas destiné, merci de le
> détruire ainsi que toute copie de votre système et d'en avertir
> immédiatement l'expéditeur. Toute lecture non autorisée, toute utilisation
> de ce message qui n'est pas conforme à sa destination, toute diffusion ou
> toute publication, totale ou partielle, est interdite. L'Internet ne
> permettant pas d'assurer l'intégrité de ce message électronique susceptible
> d'altération, l’expéditeur (et ses filiales) décline(nt) toute
> responsabilité au titre de ce message dans l'hypothèse où il aurait été
> modifié ou falsifié.
>
> This message and any attachments (the "message") is intended solely for the
> intended recipient(s) and is confidential. If you receive this message in
> error, or are not the intended recipient(s), please delete it and any copies
> from your systems and immediately notify the sender. Any unauthorized view,
> use that does not comply with its purpose, dissemination or disclosure,
> either whole or partial, is prohibited. Since the internet cannot guarantee
> the integrity of this message which may not be reliable, the sender (and its
> subsidiaries) shall not be liable for the message if modified or falsified.
>
>
> _______________________________________________
> 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/
