Jody wrote on 02/11/2006 04:06:48 PM:
> I just sent an email to the geoapi list, for those that play there I > would love to know what API the coverage branch is tracking... Coverage branch currently uses OGC grid coverages. It contains Simone's/Alessio's updates to various plugins and renderers for Geoserver/WCS. It will shortly contain a 19123 implementation which should be an implementation of the 19123 stuff in geoapi/pending. > http://svn.geotools.org/geotools/branches/barbs/ > STATUS: what is this? Wind barb 1st attempt. It got unwieldy and is now waiting on coverage implementation. Due to changes in renderer, probably the only thing I can salvage is the barb MVC pattern. Will pay attention to this after 19123 done. When done, it will either be merged into coverage_branch or trunk (if coverage_branch has already been merged). > http://svn.geotools.org/geotools/branches/bdb-je/ > STATUS: what is this? Persistence of CRS out to berkley database format. I started this before Martin did his HSQL work, which took some of the pressure off. I failed to delete it because it is the only solution out there with the potential for "reverse lookup" (e.g., "Which EPSG code describes this random CRS I stumbled across") without having a full-fledged database server slaved to an application. This in turn would enhance grid coverage writers. If it's annoying, I can svn export it to my local machine until I get around to working on it again. Bryce ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
