1. Exploring Spatial Database Systems to Handle Remote Sensing Imagery Lubia Vinhas Karine Reis Ferreira Based on the work presented at the XVI Brazilian Symposium on Remote Sensing in 2013

2. Spatial DBMS and Raster Data?! Not: – Raster data tend to be more static, no need for frequent updates – Raster data have simple values – Raster data is (very) large Yes: – Uniform access – Access from different applications – Reliability – Scalability

3. Spatial DBMS and Raster Data?! The “Yes” approach has never been discarded: RASDAMAN TerraLib TerraServer … Spatial extensions: having native raster datatype and functions Oracle GeoRaster PostGIS Raster

4. Oracle GeoRaster sdo_georaster sdo_raster

5. PostGIS Raster (2.0) raster : WKB representation

6. A motivation application Can we do Remote Sensing applications with raster types in Spatial DBMS?

7. A motivation application

8. Some conclusions With a minimum knowledge of their SQL API, is possible to build a remote sensing image database in PostGIS Raster as well as in Oracle GeoRaster. But there SQL is very differente. Both systems are able to do basic raster/vector processing, for example, to compute pixel value statistics on areas delimited by vector polygons. But not everything… Clipping operation in Oracle Spatial: minimum bounding box approximation and could not process data in two different spatial reference systems. Tile size is crucial for efficiency. As a final conclusion, we believe that raster support in spatial extensions has a great potential to be largely used in geographical applications. However, this support has not reached the same maturity level as has the vector support.

9. Discussion mobile spatial data servers producers We need to exploremore efficiency and flexibility