Hello Simone
Martin Desruisseaux a écrit :
> Martin Desruisseaux a écrit :
>> org.geotools.coverage.grid.GeneralGridGeometry
>> --
>> [...snip...]
>>
>> - reverse
>> - swapXY
>> - getEnvelope(GridRange, MathTransform, CoordinateReferenceSystem, boo
Martin Desruisseaux wrote:
> I'm very late, but I finally started to review the coverage branch merge. I
> would like to hold on the 2.3 release until I finished this review, since I
> have
> some questions.
>
That is well and good Martin:
I have been noticing some things while working on tr
Martin Desruisseaux wrote:
> Citing ISO 19107:
>
> "TransfiniteSet – a possibly infinite set; restricted only to values.
> For example, the integers and the real numbers are transfinite sets.
> This is actually the usual definition of set in mathematics, but
> programming lan
Cory wrote:
> Holy crap!
>
> I started working on this and decided to change a few deprecated
> interfaces to their opengis counterparts... hee hee :)
>
Indeed - thanks Cory - now you know why the FM branch was so difficult
(and why getting these sorts of things handled with is necessary first
Martin Desruisseaux a écrit :
> org.geotools.coverage.grid.GeneralGridGeometry
> --
> [...snip...]
>
> - reverse
> - swapXY
> - getEnvelope(GridRange, MathTransform, CoordinateReferenceSystem, boolean)
> - getTransform(GridRange, Envelope, boolea
Talking about Map in the context of Coverage, do you have an idea why ISO 19123
methods like:
Set select(Geometry s, Period t);
Are not
Map select(Geometry s, Period t);
instead? And should we consider using Map instead of Set? This bring us close
to
your "Coverage extends Map" proposa
Bryce L Nordgren a écrit :
> If there were such a thing as a Map, where the Keys were geometry objects,
> and the Values were a particular arbitrary class (possibly containing
> geometry objects); this is almost precisely the definition of a coverage
> via 19123. (Make the keys "DomainObjects" to
Jody Garnett a écrit :
> Aside: GridCoverage is deprecated on GeoAPI trunk; but no alternative is
> provided (!) If we do not have a replacement
> can we remove the deprecation please.
Yes, there is too much deprecated stuff in GeoAPI coverage interfaces. I will
look at them while performing the
I'm very late, but I finally started to review the coverage branch merge. I
would like to hold on the 2.3 release until I finished this review, since I
have
some questions.
org.geotools.coverage.CategoryList
--
The implementation before merge was looking for a "n
