Hi Baskar,
First, please do a "svn up" on trunk, I did some enhancements giving
the jdbc driver a chance to cache prepared statements.
Second, there is a misunderstanding of the Oracle Georaster concept.
Oracle does the tiling and mosaicing for you. Looking at the test
setup, there is one table called "raster" with two attributes "name"
and "image". There is only one row in it. The image itself is already
tiled and has pyramids.
The raster data table is called raster_rdt and is created and
populated by Oracle itself.
SQL> select count(*) from raster_rdt;
COUNT(*)
----------
1029
There 1029 tiles in the db for pyramid levels 0,1,2
SQL> desc raster_rdt;
Name Null? Type
----------------------------------------- --------
----------------------------
RASTERID NOT NULL NUMBER
PYRAMIDLEVEL NOT NULL NUMBER
BANDBLOCKNUMBER NOT NULL NUMBER
ROWBLOCKNUMBER NOT NULL NUMBER
COLUMNBLOCKNUMBER NOT NULL NUMBER
BLOCKMBR MDSYS.SDO_GEOMETRY
RASTERBLOCK BLOB
Looking at these attributes, you see what Oracle is doing for you.
Oracle itself does the mosaicing and cropping for a given pyramid level.
One big image is stored as one Oracle Raster Object.
Btw, do you know www.gdal.org. This is the swiss army knife for image
handling.
You can use gdal_merge.py to create a big image from your tiles and
import it like I do it in the GeoRasterOnlineTest class
Download gdal from http://fwtools.maptools.org/, this is easiest way.
Your concept is more like this one
http://trac.osgeo.org/postgis/wiki/WKTRaster
One Table is one image, each pyramid level has its own table.
I hope I could clarify these different architectures.
And finally, there is nothing bad the way you did it, but you are not
using the full power of Oracle Georaster.
Christian
Quoting "ba...@geotools" <dbas...@firstam.com>:
>
> Hi christian,
>
> I tested your code with my sample data. The committed code does not properly
> mosaicing the image for me. I analysed your code and found few things that I
> want to share with you. I am not expert in this spatial domain since I am
> working below a year in this domain. So if anything I am wrong in below
> statements then please correct me.
>
> GeoRaster mosaicing means mosaicing 'n' number of Georaster data available
> in a particular table. For eg, if table has 5 rows Georaster table then the
> code has to mosaic all the 5 georaster object and mosaiced into single
> image. But your code is not doing this work rather its retrieving a single
> georaster from the table and displays in openlayers window. "coveragename"
> in the xml config file determines the georaster object to be retrived from
> the database. you know I did this some six months back before started woking
> on mosacing georaster.
>
> So as per my understanding the plug-in is not mosacing the georaster rather
> simply it retrieves single georaster object from database and shown it in
> openlayers.
>
> Please let me know your suggestion for above things.
>
> Regards,
> Baskar
>
>
> --
> View this message in context:
> http://osgeo-org.1803224.n2.nabble.com/Proposed-Mosaicing-GeoRaster-Module-tp4942991p5001818.html
> Sent from the geotools-devel mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Geotools-devel mailing list
> Geotools-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
