Indeed, we saw many Rasdaman presentations in OGC meetings. My feeling
is that Drill + SIS (after 1 more year of development) could provide
something similar.
PostGIS rasters is a little bit different story since it stores the
pixel values in the database itself (in my understanding). This is
convenient for getting a backup of everything with a single PostgreSQL
dump. But I tend to prefer keeping the raster data in ordinary files, if
possible in their original format (except when we need to create tiles
and pyramids for performance reasons), and use the database as an index
or a catalogue. I think that it is also closer to the Rasdaman approach.
However we should be able to support both approaches and let user
chooses what (s)he prefers.
Martin
Le 10/11/15 19:20, Adam Estrada a écrit :
> Martin,
>
> This is extremely cool and much needed in the geospatial community! My
> company, DigitalGlobe, has done a lot with this and has open sourced
> many of the packages that can be found on GitHub today. Rasdaman[1]
> and PostGIS Raster are other open source examples of how to do this in
> relational databases. We have done a lot of research on how to store
> pixels and query for them in HBASE/Hadoop and ElasticSearch too. There
> are many options to this one!
>
> Adam
>
> [1] http://rasdaman.org/
