To clarify: I assume you want to create one layer composed of all your images. The images do not overlapp but have different resolutions. Additionally, there are some areas not covered by your image data.
1) About different resolutions. The whole imagemosaicJDBC plugin does not support tiles with different resolutions. For such situations you can implement your own access logic, look here http://docs.codehaus.org/display/GEOTDOC/Customized+JDBC+Access+for+images Oracle Georaster is an implementation of the above concept. I can assist you here. The access logic will have to interpolate the fetched tiles to a common resolution, mosaic and interpolate again for the resolution the client requested. Heavy stuff. Do you see a chance to use gdal_translate to prepare your images having a common resolution. This would make your job much easier. gdal_translate is mentioned in the Oracle documentation, look here http://download.oracle.com/docs/cd/E11882_01/appdev.112/e11827/geor_operations.htm#CIHFJFFJ 2) About sparse imagery Oracle Georaster is able to store images compressed. I see no problem here. 3) About updating AFAIK since Oracle 11 you can do a partial update of a georaster object. (SDO_GEOR.updateRaster) Look here http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28398/geor_ref.htm#CACHBIAE Oracle updates your georaster and rebuilds the pyramids. Summary If it is possible to prepare your images (gdal_translate) having a common resolution, the solution seems to be one georaster object. If this is not possible you have to implement your custom access. Anyway, I am wondering how you want to mosaic your images with different solutions. Hope this helps Christian Quoting "Hall, Bryan D Civ USAF AFSPC 38 CEG/MSH" <[email protected]>: > Christian, > > Please explain why one big mosaic set of pyramid images composed of > sparse imagery of various resolutions is better than multiple separate > pyramid images. At this time I can't see any benefit to doing that. > > IMHO, just the overhead of having to regenerate that mosaic for each > addition / change seems like a major problem. Plus the georaster mosaic > function won't work unless the source images all have exactly the same > resolution, which does not sound likely for a non-equal area projection > like 3785. > > Have a great day, > > Bryan > Lon/Lat: -97.3587, 35.4025 > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Tuesday, December 07, 2010 8:11 AM > To: Hall, Bryan D Civ USAF AFSPC 38 CEG/MSH > Cc: [email protected] > Subject: Re: [Geoserver-users] ImageMosaic-JDBC setup for Oracle > GeoRaster- How? > > The benefits of using Oracle Georaster is to delegate the mosacing job > to the Georaster code. Additionally Oracle Georaster gives you the > possibility to create pyramids. > > At the end of the day, you should have ONE Georaster object holding > all your georeferenced 500 images and all the needed pyramids. > > These jobs have to be done with Oracle Tools. > > For the plugin itself, only ONE db row is necessary, holding the huge > georaster object and a name corresponding to the <coverageName>. > > Creating individual pyramids for your 500 images is not correct, since > building a pyramid often requires the neighbors images. > > Hope this helps > > > > > Quoting bryanhall <[email protected]>: > >> >> >> >> mcr wrote: >>> >>> The data source name is completely independent but it must be >>> configured in the servlet container you use. Which one do you use ? >>> The content of the <coverageName> element from the xml file must be >>> the same as in your sql table, attribute NAME. In your case >>> "CIP_ORTHOS". >>> >>> Looking at the stack trace, this seems to be a connection problem. >> >> Connection - right. Not sure why that is, I tried both the XML > specified >> settings as well as the JNDI connect setting. >> >> The container is currently OAS 10.1.3.1.0, hitting both a 10gR2 db > (vector >> info) and 11gR2 db (new raster data). >> >> Yes, I now understand the coverageName. It's set for LANG currently to > match >> the NAME entry for one row. So - from what I gather, for 500 images, I > would >> either need 500 coverages or one huge mosaic of them all? >> >> -- >> View this message in context: >> > http://old.nabble.com/ImageMosaic-JDBC-setup-for-Oracle-GeoRaster---How- > -tp30366634p30396219.html >> Sent from the GeoServer - User mailing list archive at Nabble.com. >> >> >> > ------------------------------------------------------------------------ > ------ >> What happens now with your Lotus Notes apps - do you make another > costly >> upgrade, or settle for being marooned without product support? Time to > move >> off Lotus Notes and onto the cloud with Force.com, apps are easier to > build, >> use, and manage than apps on traditional platforms. Sign up for the > Lotus >> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d >> _______________________________________________ >> Geoserver-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geoserver-users >> > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
