Hi Piano Player; You are certainly getting a lot of background information here; I would love to see some of this captured on the wiki. I think this is more on the design of the coverage api than I have seen in a while. Once you have had time to digest all of this perhaps you can help me make sense of it? I am mostly interested in making sure the APIs between implementor and client code are solid.
I really liked Adrians missive on the importance of the "GridCoverage" abstraction; actually acquiring one is the part I want to see cleaned up. I belive everyone is happy with the (now ISO based) core abstraction that is GridCoverage. For reference the "best" practise followed by most projects is documented here: - http://docs.codehaus.org/display/GEOTDOC/01+Format In actual fact most people dodge the "Format" and make direct use of a constructor to create a GridCoverageReader. - http://docs.codehaus.org/display/GEOTDOC/02+GridCoverageReader Ciao, Jody ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
