Hello Simone

The deprecation of GeneralGridRange in favor of GeneralGridEnvelope was a step 
toward the replacement of OGC 01-004 by ISO 19123. GridRange (from OGC 01-004) 
duplicates totally GridEnvelope (from ISO 19123). The former was flagged with a 
warning since GeoAPI 2.0:

http://geoapi.sourceforge.net/2.0/javadoc/org/opengis/coverage/grid/GridRange.html

Admitly the warning saids "this class will change", not "will be removed". But 
given the complete duplication, keeping GridRange doesn't seem necessary.

I proposed this change on Geoshaver mailing list on June 11 (GeoAPI and 
GeoTools 
was not in cc - I forgot it). I applied the change and announced it on GeoTools 
mailing list on June 20 under the "GeoAPI update needed" title.

I could have opened a JIRA task for that and posted more emails on GeoAPI and 
GeoTools for increasing the chances that peoples don't miss it. The issue is 
how 
to find a balance, or in other words when a change is big enough for deserving 
an email.

Maybe this change was big enough for deserving more emails than the two above 
mentioned ones. I though that it was not so major, and covered by the 3 years 
old warning in the GridRange interface. But I may very well have been wrong.

If you wish I can revert the change, or undeprecate GeneralGridRange. Just tell 
me what you wish and I will do it.

        Regards,

                Martin

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to