# Oracle Spatial GeoRaster¶

Driver short name

GeoRaster

This driver supports reading and writing raster data in Oracle Spatial GeoRaster format (10g or later). The Oracle Spatial GeoRaster driver is optionally built as a GDAL plugin, but it requires Oracle client libraries.

When opening a GeoRaster, its name should be specified in the form:

georaster:<user>{,/}<pwd>{,@}[db],[schema.][table],[column],[where]
georaster:<user>{,/}<pwd>{,@}[db],<rdt>,<rid>

Where:

user   = Oracle server user’s name login
db     = Oracle server identification (database name)
schema = name of a schema
table  = name of a GeoRaster table (table that contains GeoRaster columns)
column = name of a column data type MDSYS.SDO_GEORASTER
where  = a simple where clause to identify one or multiples GeoRaster(s)
rdt    = name of a raster data table
rid    = numeric identification of one GeoRaster

Examples:

geor:scott,tiger,demodb,table,column,id=1
geor:scott,tiger,demodb,table,column,”id = 1”
“georaster:scott/tiger@demodb,table,column,gain>10”
“georaster:scott/tiger@demodb,table,column,city=’Brasilia’”
georaster:scott,tiger,,rdt_10$,10 geor:scott/tiger,,rdt_10$,10

Note: do note use space around the field values and the commas.

Note: like in the last two examples, the database name field could be left empty (“,,”) and the TNSNAME will be used.

Note: If  the query results in more than one GeoRaster it will be treated as a GDAL metadata’s list of sub-datasets (see below)

## Driver capabilities¶

Supports CreateCopy()

This driver supports the GDALDriver::CreateCopy() operation

Supports Create()

This driver supports the GDALDriver::Create() operation

Supports Georeferencing

This driver supports georeferencing

Supports VirtualIO

This driver supports virtual I/O operations (/vsimem/, etc.)

## Browsing the database for GeoRasters¶

By providing some basic information the GeoRaster driver is capable of listing the existing rasters stored on the server:

To list all the GeoRaster table on the server that belongs to that user name and database:

% gdalinfo georaster:scott/tiger@db1

To list all the GeoRaster type columns that exist in that table:

% gdalinfo georaster:scott/tiger@db1,table_name

That will list all the GeoRaster objects stored in that table.

% gdalinfo georaster:scott/tiger@db1,table_name,georaster_column

That will list all the GeoRaster existing on that table according to a Where clause.

% gdalinfo georaster:scott/tiger@db1,table_name,georaster_column,city=’Brasilia’

Note that the result of those queries are returned as GDAL metadata sub-datasets, e.g.:
% gdalinfo georaster:scott/tiger
Driver: GeoRaster/Oracle Spatial GeoRaster
Subdatasets:
SUBDATASET_1_NAME=georaster:scott,tiger,,LANDSAT SUBDATASET_1_DESC=Table:LANDSAT SUBDATASET_2_NAME=georaster:scott,tiger,,GDAL_IMPORT SUBDATASET_2_DESC=Table:GDAL_IMPORT

## Creation Options¶

• BLOCKXSIZE: The number of pixel columns on raster block.

• BLOCKYSIZE: The number of pixel rows on raster block.

• BLOCKBSIZE: The number of bands on raster block.

• BLOCKING: Decline the use of blocking (NO) or request an automatic blocking size (OPTIMUM).

• SRID: Assign a specific EPSG projection/reference system identification to the GeoRaster.

• INTERLEAVE: Band interleaving mode, BAND, LINE, PIXEL (or BSQ, BIL, BIP) for band sequential, Line or Pixel interleaving.

• DESCRIPTION: A simple description of a newly created table in SQL syntax. If the table already exist, this create option will be ignored, e.g.:

% gdal_translate -of georaster landsat_823.tif geor:scott/tiger@orcl,landsat,raster \   -co DESCRIPTION=”(ID NUMBER, NAME VARCHAR2(40), RASTER MDSYS.SDO_GEORASTER)” \   -co INSERT=”VALUES (1,’Scene 823’,SDO_GEOR.INIT())”

• INSERT: A simple SQL insert/values clause to inform the driver what values to fill up when inserting a new row on the table, e.g.:

% gdal_translate -of georaster landsat_825.tif geor:scott/tiger@orcl,landsat,raster \   -co INSERT=”(ID, RASTER) VALUES (2,SDO_GEOR.INIT())”
• COMPRESS: Compression options, JPEG-F, JP2-F, DEFLATE or NONE. The JPEG-F options is lossy, meaning that the original pixel values are changed. The JP2-F compression is lossless if JP2_QUALITY=100.

• GENPYRAMID: Generate pyramid after a GeoRaster object have been loaded to the database. The content of that parameter must be the resampling method of choice NN (nearest neighbor) , BILINEAR, BIQUADRATIC, CUBIC, AVERAGE4 or AVERAGE16. If GENPYRLEVELS is not informed the PL/SQL function sdo_geor.generatePyramid will calculate the number of levels to generate.

• GENPYRLEVELS: Define the number of pyramid levels to be generated. If GENPYRAMID is not informed the resample method NN (nearest neighbor) will apply.

• QUALITY: Quality compression option for JPEG ranging from 0 to 100. The default is 75.

• JP2_QUALITY=float_value,float_value,… Only if COMPRESS=JP2-f : Percentage between 0 and 100. A value of 50 means the file will be half-size in comparison to uncompressed data, 33 means 1/3, etc.. Defaults to 25 (unless the dataset is made of a single band with color table, in which case the default quality is 100).

• JP2_REVERSIBLE=YES/NO Only if COMPRESS=JP2-f : YES means use of reversible 5x3 integer-only filter, NO use of the irreversible DWT 9-7. Defaults to NO (unless the dataset is made of a single band with color table, in which case reversible filter is used).

• JP2_RESOLUTIONS=int_value Only if COMPRESS=JP2-f : Number of resolution levels. Default value is selected such the smallest overview of a tile is no bigger than 128x128.

• JP2_BLOCKXSIZE=int_value Only if COMPRESS=JP2-f : Tile width. Defaults to 1024.

• JP2_BLOCKYSIZE=int_value Only if COMPRESS=JP2-f : Tile height. Defaults to 1024.

• JP2_PROGRESSION=LRCP/RLCP/RPCL/PCRL/CPRL Only if COMPRESS=JP2-f : Progession order. Defaults to LRCP.

• NBITS: Sub byte data type, options: 1, 2 or 4.

• SPATIALEXTENT: Generate Spatial Extents. The default for that options is TRUE, that means that this option only need to be informed to force the Spatial Extent to remain as NULL. If EXTENTSRID is not informed the Spatial Extent geometry will be generated with the same SRID as the GeoGeoraster object.

• EXTENTSRID: SRID code to be used on the Spatial Extent geometry. If the table/column has already a spatial extent, the value informed should be the same as the SRID on the Spatial Extent of the other existing GeoRaster.

• OBJECTTABLE: To create RDT as SDO_RASTER object inform TRUE otherwise, the default is FALSE and the RDT will be created as regular relational tables. That does not apply for Oracle version older than 11.

## Importing GeoRaster¶

During the process of importing raster into a GeoRaster object it is possible to give the driver a simple SQL table definition and also a SQL insert/values clause to inform the driver about the table to be created and the values to be added to the newly created row. The following example does that:

% gdal_translate -of georaster Newpor.tif georaster:scott/tiger,,landsat,scene \
-co “DESCRIPTION=(ID NUMBER, SITE VARCHAR2(45), SCENE MDSYS.SDO_GEORASTER)” \
-co “INSERT=VALUES(1,’West fields’, SDO_GEOR.INIT())” \
-co “BLOCKXSIZE=512” -co “BLOCKYSIZE=512” -co “BLOCKBSIZE=3” \
-co “INTERLEAVE=PIXEL” -co “COMPRESS=JPEG-F”

Note that the create option DESCRIPTION requires to inform table name (in bold). And column name (underlined) should match the description:

% gdal_translate -of georaster landsat_1.tif georaster:scott/tiger,,landsat,scene \
-co “DESCRIPTION=(ID NUMBER, SITE VARCHAR2(45), SCENE MDSYS.SDO_GEORASTER)” \
-co “INSERT=VALUES(1,’West fields’, SDO_GEOR.INIT())”

If the table “landsat” exist, the option “DESCRIPTION” is ignored. The driver can only update one GeoRaster column per run of gdal_translate. Oracle create default names and values for RDT and RID during the initialization of the SDO_GEORASTER object but user are also able to specify a name and value of their choice.

% gdal_translate -of georaster landsat_1.tif georaster:scott/tiger,,landsat,scene \
-co “INSERT=VALUES(10,’Main building’, SDO_GEOR.INIT(‘RDT’, 10))”

If no information is given about where to store the raster the driver will create (if doesn’t exist already) a default table named GDAL_IMPORT with just one GeoRaster column named RASTER and a table GDAL_RDT as the RDT, the RID will be given automatically by the server, example:

% gdal_translate -of georaster input.tif “geor:scott/tiger@dbdemo”

## Exporting GeoRaster¶

A GeoRaster can be identified by a Where clause or by a pair of RDT & RID:
% gdal_translate -of gtiff geor:scott/tiger@dbdemo,landsat,scene,id=54 output.tif % gdal_translate -of gtiff geor:scott/tiger@dbdemo,st_rdt_1,130 output.tif

## Cross schema access¶

As long as the user was granted full access the GeoRaster table and the Raster Data Table, e.g.:
% sqlplus scott/tiger SQL> grant select,insert,update,delete on gdal_import to spock; SQL> grant select,insert,update,delete on gdal_rdt to spock;
It is possible to an user access to extract and load GeoRaster from another user/schema by informing the schema name as showed here:
Browsing:
% gdalinfo geor:spock/lion@orcl,scott. %gdalinfo geor:spock/lion@orcl,scott.gdal_import,raster,”t.raster.rasterid > 100”
%gdalinfo geor:spock/lion@orcl,scott.gdal_import,raster,t.raster.rasterid=101 Extracting:
% gdal_translate geor:spock/lion@orcl,scott.gdal_import,raster,t.raster.rasterid=101out.tif % gdal_translate geor:spock/lion@orcl,gdal_rdt,101 out.tif Note: On the above example that accessing by RDT/RID doesn’t need schame name as long as the users is granted full access to both tables.