From: Andrea A. <and...@ge...> - 2011-04-16 07:01:56
|
On Sat, Apr 16, 2011 at 5:49 AM, Michael Bedward <mic...@gm...> wrote: > Hi all, > > For some time I've been thinking about how to ease the pain that some > users experience when coming to grips with GridCoverage2D and its > friends. My impression, based on questions on the user list over the > last couple of years, plus my own learning experience, is that the > coverage module is: Agree with most of what you say below, using current grid coverages is painful, so having a simpler way to work with them is going to be an improvement. Back at the times when I started working with those I was frustrated and complaining too. What worries me is that all the code we have around in GeoTools and GeoServer uses the current coverage classes: reading, writing, coverage manipulation operations (reprojection, cropping and so on), processes. So my first question is, do you intend to rewrite all of the above code? Don't think so? Do you foresee a way to bridge or transform between the two then? Like a "simple" wrapper around a GridCoverage2D to give it a friendly face, and a wrapper around the simple ones to give them a GridCoverage2D face so that they can be written out to disk or chewed by existing processes? Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 333 8128928 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- |