Closed WeatherGod closed 2 years ago
Hi @WeatherGod , this repository is no longer under active development and will be archived when we end support for TDS 4.6.x.
TDS 5.x uses edal-java for wms, which is forked from this external repo. Most wms-related bugs will need to be reported there.
However, we are aware of the timeInterval
parameter not working as expected and are looking into it.
Thanks, I'll track it down in edal and see if it is the same cause or not and open an issue there.
Actually, I'm not clear how capabilities_xml.jsp
finds getTimeStringForCapabilities(). The tld file associates this function with the class defined here, but I don't see the function there.
Shall I go ahead and just open an issue in edal-java
and let you all figure it out, or what would you advise?
Yes, either open an issue on the main edal-java
repo or the tds
repo (if your issue is a thredds problem)
https://github.com/Unidata/ncWMS/blob/8f66cd953a32e1b44e8bbd9367a39442962d64e4/src/java/uk/ac/rdg/resc/ncwms/util/WmsUtils.java#L547
The algorithm here works by joining together contiguous intervals of equal time as measured by milliseconds. This results in "weird" lists for monthly datasets because only December-January and July-August are equal in time.
As an example, for my monthly dataset, even though "timeInterval" is set to
true
inwmsConfig.xml
, I get the following in my capabilities document, which is mostly a list which is likely to cause confusion.As a side note, it appears that setting
timeInterval
tofalse
doesn't do anything? I get the same result either way (using tds 5.4-snapshot docker image)