EVOLUTION-MANAGER

Edit File: frmt_georaster.html

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
 <title>GeoRaster --- Oracle Spatial GeoRaster</title>
 <meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8">
 <meta name="GENERATOR" content="OpenOffice.org 2.4 (Linux)">
 <style type="text/css">
	</style>
</head>
<body bgcolor="#ffffff">
<h1>Oracle Spatial GeoRaster</h1>

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, it's name should be specified in the form:


georaster:&lt;user&gt;{,/}&lt;pwd&gt;{,@}[db],[schema.][table],[column],[where] 
georaster:&lt;user&gt;{,/}&lt;pwd&gt;{,@}[db],&lt;rdt&gt;,&lt;rid&gt;
Where:

user &nbsp; = Oracle server user's name login 
pwd &nbsp; &nbsp;= user password 
db &nbsp; &nbsp; = Oracle server identification (database name) 
schema&nbsp;= name of a schema &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
table &nbsp;= name of a GeoRaster table (table that
contains&nbsp;GeoRaster columns) 
column = name of a column&nbsp;data type&nbsp;MDSYS.SDO_GEORASTER 
where &nbsp;= a simple where clause to identify one or multiples
GeoRaster(s) 
rdt &nbsp; &nbsp;= name of a raster data table 
rid &nbsp; &nbsp;= 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&gt;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&nbsp;TNSNAME will be&nbsp;used.
Note: If &nbsp;the query results in more than one GeoRaster it will
be treated as a GDAL metadata's list of sub-datasets (see bellow)
<h3>Browsing the database for GeoRasters
 
</h3>
By providing some basic information the
GeoRaster driver is capable of listing the existing rasters stored on
the server:
To&nbsp;list all the GeoRaster table
on the server that belongs to that user name and database:
%
gdalinfo georaster:scott/tiger@db1
To list&nbsp;all the GeoRaster type columns that exist&nbsp;in that
table: 
<div style="margin-left: 40px;">%
gdalinfo georaster:scott/tiger@db1,table_name</div>
That will list all the&nbsp;GeoRaster objects stored in that table.

<div style="margin-left: 40px;">%
gdalinfo georaster:scott/tiger@db1,table_name,georaster_column</div>
That will list all the GeoRaster existing on that table according to
a Where clause.

<div style="margin-left: 40px;">%
gdalinfo
georaster:scott/tiger@db1,table_name,georaster_column,city='Brasilia'</div>
 
Note that the result of those queries
are returned&nbsp;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
<h3>Creation Options</h3>
<ul>
 <li>BLOCKXSIZE: The number of pixel columns
on&nbsp;raster block. </li>
 <li> BLOCKYSIZE: The number of pixel&nbsp;rows
on&nbsp;raster block. </li>
 <li> BLOCKBSIZE: The number of
bands&nbsp;on&nbsp;raster block.</li>
 <li> BLOCKING: Decline the use of blocking (NO) or request an automatic blocking size (OPTIMUM).</li>
 <li>SRID: Assign a specific
EPSG projection/reference system identification to the GeoRaster.</li>
 <li>INTERLEAVE: Band interleaving mode, BAND, LINE,
PIXEL (or BSQ, BIL, BIP) for band sequential, Line or Pixel
interleaving.&nbsp;</li>
 <li>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.:</li>
</ul>
%
gdal_translate -of georaster landsat_823.tif
geor:scott/tiger@orcl,landsat,raster \ 
&nbsp; -co DESCRIPTION="(ID NUMBER, NAME VARCHAR2(40), RASTER
MDSYS.SDO_GEORASTER)" \ 
&nbsp; -co INSERT="VALUES (1,'Scene 823',SDO_GEOR.INIT())"
<ul>
 <li>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.:</li>
</ul>
%
gdal_translate -of georaster landsat_825.tif
geor:scott/tiger@orcl,landsat,raster \ 
&nbsp; -co INSERT="ID, RASTER VALUES (2,SDO_GEOR.INIT())" 
<ul>
 <li>COMPRESS: Compression options, JPEG-F,
DEFLATE or NONE. The two JPEG options are lossy, meaning that the
original pixel values are changed.</li>
 <li>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.</li>
 <li>GENPYRLEVELS: Define the number of pyramid levels to be generated.
If GENPYRAMID is not informed the resample method NN (nearest neighbor) will apply.</li>
 <li>QUALITY: Quality compression option for JPEG 
ranging from 0 to 100. The default is 75.</li>
 <li>NBITS: Sub byte data type, options: 1, 2 or 4.</li>
 <li>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.</li>
 <li>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.</li>
 <li>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.</li>
</ul>

<h3>Importing GeoRaster</h3>
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&nbsp;georaster:scott/tiger,,landsat,scene
\ 
&nbsp; -co
"DESCRIPTION=(ID NUMBER, SITE VARCHAR2(45), SCENE
MDSYS.SDO_GEORASTER)" \ 

&nbsp; -co "INSERT=VALUES(1,'West fields',&nbsp;SDO_GEOR.INIT())" \ 
&nbsp; -co "BLOCKXSIZE=512" -co "BLOCKYSIZE=512" -co "BLOCKBSIZE=3" \ 
&nbsp; -co "INTERLEAVE=PIXEL" -co "COMPRESS=JPEG-F"
Note that the create option DESCRIPTION
requires to inform&nbsp;table name (in bold). And column name
(underlined) should match the description:
%
gdal_translate -of georaster landsat_1.tif&nbsp;georaster:scott/tiger,,landsat,scene
\ 
&nbsp; -co
"DESCRIPTION=(ID NUMBER, SITE VARCHAR2(45), SCENE
MDSYS.SDO_GEORASTER)" \ 
&nbsp; -co "INSERT=VALUES(1,'West fields',&nbsp;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.&nbsp;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&nbsp;georaster:scott/tiger,,landsat,scene
\ 
&nbsp; -co "INSERT=VALUES(10,'Main building',&nbsp;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” 

<h3>Exporting GeoRaster</h3>
A GeoRaster can be identified by a Where clause or by a pair of RDT
&amp; 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 

<h3>Cross schema access</h3>
As long as the user was granted full access the GeoRaster table and the
Raster Data Table, e.g.: 
 
% sqlplus
scott/tiger 
SQL&gt; grant select,insert,update,delete on gdal_import to spock; 
SQL&gt;
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 &gt;
100" 
% gdalinfo
geor:spock/lion@orcl,scott.gdal_import,raster,t.raster.rasterid=101 
 
Extracting: 
 
%
gdal_translate&nbsp;geor:spock/lion@orcl,scott.gdal_import,raster,t.raster.rasterid=101 out.tif 
%
gdal_translate&nbsp;geor:spock/lion@orcl,gdal_rdt,101
out.tif 
 
Note: On the above example that&nbsp;acessing by RDT/RID doesn't
need schame name as long as the users is granted full acess to both
tables. 
 
Loading: 
 
%
gdal_translate -of georaster input.tif geor:spock/lion@orcl,scott. 
%
gdal_translate&nbsp;-of georaster
input.tif geor:spock/lion@orcl,scott.cities,image \ 
&nbsp; -co INSERT="(1,'Rio de Janeiro',sdo_geor.init('cities_rdt'))" 
<h3>General use of GeoRaster</h3>
GeoRaster can be used in any GDAL command line tool with all the
available options. Like a image subset extraction or re-project: 
 
%
gdal_translate -of gtiff geor:scott/tiger@dbdemo,landsat,scene,id=54
output.tif \ 
&nbsp; -srcwin 0 0 800 600 
 
%
gdalwarp -of png geor:scott/tiger@dbdemo,st_rdt_1,130 output.png -t_srs
EPSG:9000913 
 
Two different GeoRaster can be used as input and output on the
same operation: 
 
%
gdal_translate -of georaster
geor:scott/tiger@dbdemo,landsat,scene,id=54
geor:scott/tiger@proj1,projview,image -co INSERT="VALUES (102,&nbsp;SDO_GEOR.INIT())" 
 

Applications that use GDAL can&nbsp;theoretically read and write from
GeoRaster just like any other format but most of then are more inclined
to try to access files on the file system so one alternative is to
create VRT to represent the GeoRaster description, e.g.: 
 
%
gdal_translate -of VRT
geor:scott/tiger@dbdemo,landsat,scene,id=54 view_54.vrt 
% openenv view_54.vrt 
 
 
<h3></h3>

</body></html>