-
Notifications
You must be signed in to change notification settings - Fork 7
getTimeStringForCapabilities() can't handle yearly or monthly intervals properly #41
Comments
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 |
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 Shall I go ahead and just open an issue in |
Yes, either open an issue on the main |
ncWMS/src/java/uk/ac/rdg/resc/ncwms/util/WmsUtils.java
Line 547 in 8f66cd9
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)The text was updated successfully, but these errors were encountered: