Hi Martin,
[...]
> It make sense, the GridCoverage2D constructor may invokes some RenderedImage
> that trigs the tile computation. However each tile should be computed only
> once,
> unless there is no TileCache or the TileCache is full.
>
> I would suggest to first make sure that there is a Tile
Hello Andrea
andrea antonello a écrit :
> After getting my RenderedOp as result from my operation, this, as I
> expect, is waiting for someone to pull the data out of it.
>
> This happens usually by triggering methods like getWidth, getData, getTile
> etc.
> The rendereop is the result that I wa
Ok, I will start to guess some by myself.
After getting my RenderedOp as result from my operation, this, as I
expect, is waiting for someone to pull the data out of it.
This happens usually by triggering methods like getWidth, getData, getTile etc.
The rendereop is the result that I want to dump
2008/11/27 Simone Giannecchini <[EMAIL PROTECTED]>:
> Check JAI TiledImage and hsaring the backbuffer. It can be a bit risky though.
> In the long run it might be better to have a real writeablegridcoverage class.
Ciao Simone,
That is what I have been doing and haven't had any problems yet. When
Thanks for the info. It is important to know that at some point
investing in some additional tailored component will help, but we are
on the right trail :)
I would like to go on in this thread to solve some problems related to
JAI operations.
I am porting some morphological operations to jai oper
andrea antonello a écrit :
> Why would it make sense to use tiles when using a writable raster?
> I mean, it was created in memory and therefore taking just tiles is
> the same as taking it all?
Probably in most cases. But it would also be possible (not sure if useful, but
at least possible) that
[...]
>> GridCoverage2D coverage2D = factory.create(name, writableRaster,
>> writeEnvelope, new GridSampleDimension[]{band});
>
> A possible approach is to keep around the WritableRaster that you gave to this
> constructor. Because GridCoverage2D will wrap it (not copy it), any changes
> you
> mak
Hello Adrea
andrea antonello a écrit :
> I am tempted to use:
>
> GridCoverage2D coverage2D = factory.create(name, writableRaster,
> writeEnvelope, new GridSampleDimension[]{band});
A possible approach is to keep around the WritableRaster that you gave to this
constructor. Because GridCoverage2D
Check JAI TiledImage and hsaring the backbuffer. It can be a bit risky though.
In the long run it might be better to have a real writeablegridcoverage class.
Simone.
---
Eng. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via C
You mean that in your opinion it would be better to work with
WritableRaster until the end and then create the GridCoverage?
Thanks,
Andrea
On Thu, Nov 27, 2008 at 12:36 PM, Simone Giannecchini
<[EMAIL PROTECTED]> wrote:
> Check JAI TiledImage and hsaring the backbuffer. It can be a bit risky th
Hi, I need to create a gridcoverage, on which I am going to then write.
I am tempted to use:
GridCoverage2D coverage2D = factory.create(name, writableRaster,
writeEnvelope, new GridSampleDimension[]{band});
At some point then I need to extract my writable raster.
Is that the way to do it throug
11 matches
Mail list logo
