1)
About the documentation:
http://docs.geotools.org/latest/userguide/library/coverage/jdbc/index.html
Please note the "Details" block, especially "Custom JDBC Access for Images"
Here is Oracle Georaster
http://docs.geotools.org/latest/userguide/library/coverage/oracle.html
2) I also think tha
Ciao Christian,
please, read below...
Regards,
Simone Giannecchini
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8
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
afterwar
On Sat, May 28, 2011 at 10:01 AM, wrote:
> Yep, I will examine this if I see the concrete differences. Another
> question,
> for jdbc database without spatial support the referencing info is stored in
> 4 double attributes minx,miny,maxx,maxy. I have to generate a geometry with
> a geometry descr
Quoting Andrea Aime :
> On Sat, May 28, 2011 at 8:49 AM, wrote:
>> Hi Simone, I did some investigations about integrating the jdbc stuff
>> into your module.
>>
>> The main difference is that imagemosaic is using SimpleFeatureType
>> and the jdbc module uses sql native. As I started with the j
On Sat, May 28, 2011 at 8:49 AM, wrote:
> Hi Simone, I did some investigations about integrating the jdbc stuff
> into your module.
>
> The main difference is that imagemosaic is using SimpleFeatureType
> and the jdbc module uses sql native. As I started with the jdbc
> module, the new jdbc-ng m
Hi Simone, I did some investigations about integrating the jdbc stuff
into your module.
The main difference is that imagemosaic is using SimpleFeatureType
and the jdbc module uses sql native. As I started with the jdbc
module, the new jdbc-ng modules did not exist, and the existing db2
im
