[postgis-users] Better storage strategy for 1 million tile of 50*50 pixels, 24 bands?

[Tumasgiu Rossini]

Remi,

I'm interested in the way you handled this problem.

In my opinion, the problem is on the duality of your needs.
Out-db is known to be faster for visualisation.
In-db is better for analysis.

So, a compromise should be made Maybe storing each tile per "band type" ?
So accessing data from qgis would be less painful ?




2014-03-10 10:54 GMT+01:00 Rémi Cura <remi.cura at gmail.com>:

> Hey Dear List,
>
> I would appreciate some advice about the best way to store my raster :
>
> 1 million tiles,
> 50*50 pixels each (1 m2 or less in real world), around 24 bands (mostly
> doubles)
> ,in db.
>
> About half the pixels are empty, some tiles overlaps, but most are
> regularly spaced.
>
> I would query it mainly by localisation (intersects), and also based on id
> of the tile.
>
> The use would be fast visualisation with qgis (and latest gdal),
> interpolation, classification, matching and so.
>
> What is the best strategy?
> 1 table with many lines and indexes, indb,
> 1 table, out db
> 1 table, 1 line
> multiple tables, heritage?
>
>
> Thanks for inputs!
> Cheers,
>
> Rémi-C
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20140417/198a72c5/attachment.html>