JDBCFeatureReader featuer building code limits scalability
--
Key: GEOT-2033
URL: http://jira.codehaus.org/browse/GEOT-2033
Project: GeoTools
Issue Type: Improvement
Reporte
Shapefile renderer reads all DBF attributes when only a subset is needed
Key: GEOT-2034
URL: http://jira.codehaus.org/browse/GEOT-2034
Project: GeoTools
Issue Type: Imp
Shapefile renderer needlessly clones style elements
---
Key: GEOT-2035
URL: http://jira.codehaus.org/browse/GEOT-2035
Project: GeoTools
Issue Type: Improvement
Reporter: Andrea Aime
Hey all,
We had hoped to generate this documentation earlier in the summer but
better late than ...
The page http://docs.codehaus.org/display/GEOTDOC/08+Grid+Coverage
and the first few subsections hold our first draft of an explanation of
how the coverage module works at a programmatic level. Pro
This is great - thanks Adrian !
I just had a very quick look and I've already learned something (that
I don't have to go down to JAI level to do a crop).
I'll read it properly later today and see if there's anything useful
that I can contribute to it. I've been working on some raster
algorithms
Adrian Custer wrote:
> That said,
> svn co -r 30106 http://svn.geotools.org/trunk
> works perfectly for me. Of course it does not build because we depend on
> geoapi snapshots and not releases which seems like an increasingly bad
> idea from my point of view. But you know that already.
>
Than
Reading the notes about operations from the perspective of a relative
beginner, it's not clear to me what the reasons / pros / cons are for
invoking an operation via Operations.DEFAULT (as with the resample
example on the Use a GridCoverage page) versus using the
DefaultProcessor.doOperation method
Thanks Adrian; I added a {children} macro to that page so people can see
the contents.
Jody
Adrian Custer wrote:
> Hey all,
>
> We had hoped to generate this documentation earlier in the summer but
> better late than ...
>
> The page http://docs.codehaus.org/display/GEOTDOC/08+Grid+Coverage
> and
