A brief update for the list and Steve...
I've proposed to merge the process module working branch into trunk.
This will provide vector to raster conversion for users with the
constraint that generated coverages have to fit into memory.
I've begun building a disk-based tile cache for the
Ciao Michael,
please, see below
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob:+39 333 8128928
Hi Simone
Mmmmhh, I am not sure that would make any difference, at least if you
are planning on using the default TiledImage since it simply keep a
hard reference to all its tiles, locking them in memory.
If you want to support something different you'd need to implement a
different thing,
I know at least one implementation of FileBasedTileCache, I need to
clarify a bit the licensing issues. If you are interested I can purse
that.
Otherwise we can build our own.
Simone.
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner -
Would that be the one in this project ?
http://code.google.com/p/mobile-trail-explorer/
If so it's GPL. But a quick look at the code there suggests it's not
a big job to make such a class from scratch. Perhaps a DiskTileCache
class for jai-tools class :-)
Michael
I have finally got the vector to raster code into the process module.
The new code is still on the 2.6.x_Process branch at the moment. The
relevant package is here:
http://svn.osgeo.org/geotools/branches/2.6.x_Process/modules/unsupported/process/src/main/java/org/geotools/process/raster/
Steve:
That sounds fine; Michael when you add this code to the module can you
make a note of the pulic domain code in the review atp document?
Jody
On Wed, May 27, 2009 at 5:48 AM, Steve Ansari steve.ans...@noaa.gov wrote:
Hi Michael,
I had to run this through the NOAA channels and there was some
2009/5/27 Jody Garnett jody.garn...@gmail.com:
That sounds fine; Michael when you add this code to the module can you
make a note of the pulic domain code in the review atp document?
Yep - no worries Jody.
Thanks very much for the legwork Steve - it'll will be great to have
your code in the
Hello folks,
Somewhere back in this thread I mentioned contacting Steve Ansari
about some nice vector to raster code that he posted on the user list
last year. Steve is happy for this code to go into the library (Jody
suggested it join the raster to vector code in the process module) so
I pointed
Super, thanks Jody.
Steve - let me know if that's ok with you and, if it is, I'll move
your code into the library and let the users know about it.
cheers
Michael
2009/5/22 Jody Garnett jody.garn...@gmail.com:
Hi Michael:
We encountered this before; with respect to the contributions of
Yes, I guess was thinking of something similar to the DataUtilities
class but I'm fine about doing it another way - whatever works best is
best.
Regarding the process module - yes, it is cumbersome for hands on use.
I must admit that I've bypassed it when I've used the raster to
vector function
Yes I am ... I think we proposed a naming convention right from the
get go. By convention we could make the process available using a
static method to help with test cases and direct from Java use.
// how about this?
features = RasterToVector.process(raster, band, outsideValues, monitor);
Can we make the code more useful where it is? In the process module
The process interface is useful for advertising functionality to
dynamic applications; but not so friendly for hands on java hacking.
For a utility class there are actually a couple of ways to do it;
would you want to just
13 matches
Mail list logo
