NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Greetings Adam, The 4.x line of TDS uses ncwms v1, which is the predecessor to the edal-java codebase in the github repository you mention in your email (which contains ncwms v2). The next major version of the TDS (v5) is uses edal-java and ncwms (v2); the most current TDS 5 snapshot uses version 1.2.7 of edal-java, which is their latest release. We are not quite ready for a beta release of TDS 5, but we hope to have one out by the end of the month. Cheers, Sean On Mon, May 22, 2017 at 11:34 PM, Adam Steer <Adam.Steer@xxxxxxxxxx> wrote: > Hi THREDDS people > > I’m looking for a bit of future certainty/unpicking the relationship between > TDS, ncWMS and edal-java. In particular, I need to know if: > > a. TDS uses edal-java for it’s ncWMS handling > b. if so, is TDS using current versions of edal-java > > Why? Because of the issue raised here: > https://github.com/Reading-eScience-Centre/edal-java/issues/69 > > In short, we have user demand to serve both large, high resolution rasters > that suit a scanline read mode, and other data which is happily handled in > memory all at once. At present we use two slightly different TDS servers. > Ideally we would reduce our management load a bit and serve both from a > standardised TDS installation. > > (realising that I also have a touch of homework to do on the edal-java issue > listed above) > > if there’s a way to clarify the pipeline between ncwms/edal-java changes and > incorporation into TDS, it would be great to hear about it. I’m not a java > developer by any stretch of the imagination, I dive into the TDS codebase and > get thoroughly lost! > > Thanks, > > Adam > _______________________________________________ > 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/
thredds archives: