Hi,
My changes to the capabilities_xml.jsp document based on the receipt
from MyOcean included, among other things, the following changes:
Original document:
<c:choose>
<c:when test="${verboseTimes}">
<%-- Use the verbose version of the time string --%>
<c:forEach var="tval" items="${tvalues}" varStatus="status"><c:if
test="${status.index >
0}">,</c:if>${utils:dateTimeToISO8601(tval)}</c:forEach>
</c:when>
<c:otherwise>
<c:choose>
<c:when test="${layer.intervalTime}">
<%-- Use the most concise version of the time string --%>
<c:out
value="${utils:getTimeStringForCapabilities(tvalues)}"/>
</c:when>
<c:otherwise>
<%-- Use the verbose version of the time string --%>
<c:forEach var="tval" items="${tvalues}"
varStatus="status"><c:if test="${status.index >
0}">,</c:if>${utils:dateTimeToISO8601(tval)}</c:forEach>
</c:otherwise>
</c:choose>
</c:otherwise>
</c:choose>
which I changed to:
<c:choose>
<c:when test="${verboseTimes}">
<%-- Use the verbose version of the time string --%>
<c:forEach var="tval" items="${tvalues}"
varStatus="status"><c:if test="${status.index >
0}">,</c:if>${utils:dateTimeToISO8601(tval)} </c:forEach>
</c:when>
<c:otherwise>
<%-- Use the most concise version of the time string --%>
<c:out value="${utils:getTimeStringForCapabilities(tvalues)}"/>
</c:otherwise>
</c:choose>
which shows that the test on intervalTime in the original document was
dropped in the edited version.
If the consice version of the time string is not essential for MyOcean,
I would prefer to add this test again in the edited version. This would
be a better solution to our problem with the WMS client we are using.
Best wishes,
Egil
On 08/14/2014 10:51 AM, Jon Blower wrote:
Hi Marcos,
Great! But I’m curious to know how the MyOcean-specific changes to the
capabilities doc template caused Egil’s problem. Does the current THREDDS
version of this template have code in that interact with the <intervalTime>
setting in wmsConfig? If so, we should make sure to migrate this code to the
MyOcean version of the template.
Cheers,
Jon
--
Dr Jon Blower,
Technical Director, Reading e-Science Centre,
MELODIES project coordinator,
School of Mathematical and Physical Sciences,
University of Reading
Tel: +44 118 378 5213
Email: j.d.blower@xxxxxxxxxxxxx <mailto:j.d.blower@xxxxxxxxxxxxx>
On 12 Aug 2014, at 19:29, Marcos Hermida <marcos.hermida@xxxxxxxxx
<mailto:marcos.hermida@xxxxxxxxx>> wrote:
> Hi Jon!
>
> yes, that is, actually, a feature originally introduced in the ASA Science
> version of the ncWMS which also ended up in the THREDDS.
>
> Egil just confirmed he found the source of the issue and was related to some
> changes he had done on the capabilities_xml.jsp file so no bug to look for.
>
> Cheers!
> Marcos.
>
>
> On 12 August 2014 17:04, Jon Blower <j.d.blower@xxxxxxxxxxxxx
> <mailto:j.d.blower@xxxxxxxxxxxxx>> wrote:
>
> Hi Marcos,
>
> I wasn’t aware of the <intervalTime> flag in the wmsConfig.xml file. I
> guess this facility (very useful!) was introduced by Unidata - I don’t
> think it was in our (Reading’s) code originally. If this is true, could
> you please check the bug in your code?
>
> If there’s anything you need us to fix, please let me know.
>
> Cheers,
> Jon
>
>
> > ------------------------------
> > Date: Mon, 11 Aug 2014 16:43:15 +0100
> > From: Marcos Hermida <marcos.hermida@xxxxxxxxx
> <mailto:marcos.hermida@xxxxxxxxx>>
> > To: Egil St?ren <egil.storen@xxxxxx <mailto:egil.storen@xxxxxx>>
> > Cc: THREDDS community <thredds@xxxxxxxxxxxxxxxx
> <mailto:thredds@xxxxxxxxxxxxxxxx>>
> > Subject: Re: [thredds] Unwanted ISO 8601 time interval format in WMS
> > GetCapabilities document
> > Message-ID:
> >
> <CAHmUWoB8onagGGPv=j47RmPrGPdBj-VdrR_=Nvtb2OD_KU7Nbg@xxxxxxxxxxxxxx
> <mailto:Nvtb2OD_KU7Nbg@xxxxxxxxxxxxxx>>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hi Egil,
> >
> > not sure if there may be something wrong in the configuration or if it
is
> > actually a bug but as workaround if you add the parameter verbose=true
(non
> > WMS standard) to your request you get all the times:
> >
> >
>
http://thredds-staging.met.no/thredds/wms/osisaf_test/met.no/ice/conc_nh_agg?service=WMS&version=1.3.0&request=GetCapabilities&verbose=true
> >
> > Hope it helps,
> > Marcos.
> >
> >
> >
> > On 11 August 2014 15:35, Egil St?ren <egil.storen@xxxxxx
> <mailto:egil.storen@xxxxxx>> wrote:
> >
> >> Hi all,
> >>
> >> The following GetCapabilities document:
> >>
> >> http://thredds-staging.met.no/thredds/wms/osisaf_test/met.
> >> no/ice/conc_nh_agg?service=WMS&version=1.3.0&request=GetCapabilities
> >>
> >> contains a <Dimension> element for time that use the time interval
format
> >> allowed in ISO 8601. This creates problems for our WMS client that has
not
> >> implemented this feature.
> >>
> >> According to the documentation at http://www.unidata.ucar.edu/
> >> software/thredds/current/tds/tutorial/AddingServices.html (search for
> >> "More WMS Configuration"), this feature should only be activated if
> >> wmsConfig.xml contains an <intervalTime>true</intervalTime> element.
> >>
> >> But our wmsConfig.xml contains <intervalTime>false</intervalTime>.
> >>
> >> Is this a bug? How is it otherwise possible to turn off this feature?
> >>
> >> Best regards,
> >>
> >> Egil St?ren
> >> MET Norway
> >>
> >> _______________________________________________
> >> thredds mailing list
> >> thredds@xxxxxxxxxxxxxxxx <mailto:thredds@xxxxxxxxxxxxxxxx>
> >> For list information or to unsubscribe, visit:
> >> http://www.unidata.ucar.edu/mailing_lists/
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL:
>
<http://mailman.unidata.ucar.edu/mailing_lists/archives/thredds/attachments/20140811/c96881fb/attachment.html>
> >
> > End of thredds Digest, Vol 67, Issue 3
> > **************************************
>
> _______________________________________________
> thredds mailing list
> thredds@xxxxxxxxxxxxxxxx <mailto:thredds@xxxxxxxxxxxxxxxx>
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
>
_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
