Christian,

Whereas it is possible to have multiple rows in a table where each row 
represents a different map, what we really need is to be able to mosaic more 
than one map together in this use case.

Bruce E. Thelen
bthe...@corelogic.com


-----Original Message-----
From: christian.muel...@nvoe.at [mailto:christian.muel...@nvoe.at]
Sent: Wednesday, May 05, 2010 10:43 AM
To: Thelen, Bruce
Cc: Baskar, Dhanapal; geotools-devel@lists.sourceforge.net
Subject: RE: [Geotools-devel] Proposed Mosaicing GeoRaster Module

Bruce,Baskar, and Steve, many questions, I will try to give good answers :-)

It is not true that the table has only one row. Each row is a  map. If
your enterprise has 20 different maps, you have 20 records in this
table. You can assign a different raster data table for each of this
20 rows. Oracle will create 20 different raster data tables (RDT)
holding the tiles for one map. You can look at these  RDTs, you will
have tons of rows in it.

I believe, these RDTs are exactly what you want to create yourself.
You can specify a lot of storage parameters for these RDTs like
tablespace,  blocksize of one tile,...

About the 95 % no data value. Specify a "compression= ..." storage parameter.
"compression=DEFLATE" is a simple gzip for example.

Do you use pyramids ?. If you use your own tile table and generate
pyramids for each tile, you will have a good chance to see the borders
of the tiles on your map, looking like a chess board :-)
I have this experience since I developed the gdal_retily.py utility.
Building a pyramid for one tile means also to load all 8 neighbors,
moasic the image, and crop the original rectangle. If you use your own
tile table, it is likely to loose the oracle pyramid feature.

For Oracle 10.2, I have not seen a possibilty to import an already
tiled image into a georaster object.
Is this right ?  This means you have to use gdal_merge.py

For Oracle 11.x, I have seen SDO_GEOR.updateRaster at
http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28398/geor_ref.htm#CACHBIAE

updateRaster gives you the possibility to update a part of the raster
object and the pyramids are rebuild automatically. Here you can avoid
gdal_merge.py. To be fair, I have not used it until know,
but this could be a chance.

so far, so good, hope that helped a little bit


***************************
This message may contain confidential or proprietary information intended only
for the use of the addressee(s) named above or may contain information that is
legally privileged. If you are not the intended addressee, or the person
responsible for delivering it to the intended addressee, you are hereby
notified that reading, disseminating, distributing or copying this message is
strictly prohibited. If you have received this message by mistake, please
immediately notify us by replying to the message and delete the original
message and any copies immediately thereafter.

Thank you.
****************************

------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to