Implement functionality from THREDDS client about siphon

[dopplershift]

Thanks for the suggestion; I’m a little hesitant to add an external dependency if we don’t have to. A side-by-side comparison of something implemented in beautiful soup vs. Etree may convince me otherwise.

Looking over your code, what is clear is that I like some of your catalog API more than our own—more user-friendly. That begs the question—would you be interested in combining forces on Siphon? We’ve got two people from the THREDDS team working on Siphon (as part of our jobs at Unidata), and we’ve got plans to make Siphon a full-featured Python client for THREDDS; not just catalog parsing, but reading data from various TDS endpoints, like NCSS and CDMRemote. With your help we could accomplish even more, and avoid fracturing the community.

[cehbrecht]

the threddsclient is just a little part on my todo list ... so my hope was, when siphon is ready i can take yours :) but i keep an eye on it ...

[dopplershift]

Ok, good to know. If nothing else, knowing specific needs you have will help us know where we still need to work. :)