Short result of my weekend investigations.

Successful integration stopped at the CatalogBuilder, GranuleDescripter,....
This architecture seems not well fitted for jdbc databases since it  
will cause a lot of unnecessary IO.

First, I have to load the the set of granule descriptors and  
afterwards, fetch BLOB data for each granule.

Number of Select statements = number of granules + 1.

The current imagemosaic JDBC module does the following:

Input for  raster data fetching

1) level
2) bbox

Statement:

select location,minx,miny,maxx,maxy,rasterdata from levelTable where  
bbox intersects geom.

Result
A set of georeferenced images. This set is the basis for mosaicking,  
cropping and scaling.

We have exactly one statement. This is also possible using jdbc-ng  
SimpleFeatureTypes since BLOBs are supported.

As a consequence, the module must be able to work with a set of  
features,each feature containing minx,miny,maxx,maxy and rasterdata.  
Unfortunately, I have not found a simple solution.

We should not forget our special friend Oracle Georaster.  
Mosaicking,cropping and scaling is done in the database itself.

Any ideas ?















----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to