Hi all, trying to get up to speed a litlle bit late :-)... On Wed, Jun 11, 2008 at 1:30 PM, Martin Desruisseaux <[EMAIL PROTECTED]> wrote: > > Jon Blower a écrit : >> One of the key factors affecting our work in GeoShaver (and actually >> in another project I'm involved in too) is the Coverage concept and >> its implementation. I understand that things are changing with >> ISO19123, but I was wondering if someone could summarize the current >> state of GeoAPI and GeoTools with respect to the new Coverages. How >> long will it take to have stable Coverage APIs in GeoAPI and stable >> implementations in GeoTools? > > ISO 19123 interfaces was wrote by a mix of (if my memory serve me right) > Simone, > Daniele, Bryce and myself. I believe that all interfaces are there (maybe > Simone > could tell us if I'm forgetting any). We still have a few unresolved open > issues > flagged by "todo" javadoc tags. They are visible in the javadoc (unfortunatly > we > don't have an automatically generated summary of all "todo" at this time).
it was actually Alessio I believe who spent some time a while ago in finishing the iso 19123 interfaces, but I am not 100% sure the work has been completed. > > Most interfaces from the legacy OGC 01-004 have been deprecated, but not yet > removed. The GeoTools implementation still implements the legacy > specification. > It is not clear at this time which interfaces will really be removed and which > one will be un-deprecated. For example in the referencing module we have > reused > a few intefaces from the legacy OGC 01-009 when ISO 19111 had nothing > equivalent > (MathTransform, AuthorityFactory...). > > So I would said: > > * I believe that the Coverage interface is stable except the few methods > flagged > with "todo", but even those would probably have only minor modifications. > > * We will probably try to retrofit GridRange (from OGC 01-004) into > GridEnvelope > (from ISO 19123). GridRange would be removed, but from user eyes the change > would probably be only class/method renaming with same functionalities. > > * I'm not sure about GridGeometry. This class is crucial in current > GridCoverage > design, and I dont know yet if it can be retrofited in existing ISO 19123 > constructs. If there is no ISO 19123 equivalent, we may keep it. I share this view, we should try to retrofit the grid geometry related classes since they ahve proven ot be life-saver utilities, at least IMHO. > > * I don't know what to do with ColorInterpretation, ByteInValuePacking and the > like. There is nothing equivalent in ISO 19123. However we can infer the > same > information from Java RenderedImage API. So maybe we could just remove them. > The way I see it, 19123 does not mention color intepretation at all since it seems (going from memory) to focus only on values, which would probably map well with Raster or DataBuffer in java. This might lead to discuss a little bit over the various view types that have been introduced lately in geotools (daniele should send an email anyway) > * The future of GridCoverage is unsure. My guess is that the DataBlock related > methods will either be removed, or move to GridValuesMatrix. I think that > the > only really useful GridCoverage method is "getGridGeometry()" - the other > ones > are inherited from Coverage. So my guess is that: > > - GeoTools GridCoverage2D implementation will not have major change. It will > keep its implementation-specific methods like getRenderedImage(). I completely agree. even though I think that we should relax a bit the need for specifying categories and the like at construction time, but that requries discussion anyway. > > - GeoAPI GridCoverage interface may be removed - it depends what we decice > to do with the above points (especially GridGeometry). > We might even move them to geotools as part of our implementation, just a random thought. > - GridCoverage2D would probably implements a few ISO 19123 interfaces in > replacement (or in addition) of GridCoverage. I'm not sure which ones. > I would see CoverageStack, with a few modifications as a good condidate for being the base class for 19123 implementation. GridCoverage2D would probably become part of our implementation but not part of GeoApi interfaces. Simone. > >> For many projects, GridCoverages are the most important things for now >> (CV_RectifiedGrid and CV_ReferenceableGrid I think). How much work is >> there still to do in this area? > > Maybe one or two months, once we are able to work on it. Right now we are > stuck > in other projects, so unfortunatly it is very difficult to give a timeline... > > Martin > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups > "GeoShaver" group. > To post to this group, send email to [EMAIL PROTECTED] > To unsubscribe from this group, send email to [EMAIL PROTECTED] > For more options, visit this group at > http://groups.google.co.uk/group/geoshaver?hl=en-GB > -~----------~----~----~----~------~----~------~--~--- > > -- ------------------------------------------------------- Eng. Simone Giannecchini President /CEO GeoSolutions S.A.S. Via Carignoni 51 55041 Camaiore (LU) Italy phone: +39 0584983027 fax: +39 0584983027 mob: +39 333 8128928 http://www.geo-solutions.it ------------------------------------------------------- ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
