Configuration File tab

This tab lets an administrator modify the WCSConfig.xml file, which lets you configure WCS logging, GDAL parameters, and GetCapabilities responses (ServiceIdentification and ServiceProvider).

• Logging attributes can be configured: log level, log file size limit, and number of log files.

• Log rotation is supported based on the file size. By limiting the number of files, you can limit how much disk space the log files will take. Log files are generated inside the directory referenced by the sdows java property, and they have names in the form wcs_n<data source name>.log, wherewcs_0.log has the most recent log messages; and when it has reached its file size limit, the oldest file is removed and all log files are renamed to let wcs_0.log be used for the next set of log messages.

• Log level can be SEVERE, WARNING, INFO (default), CONFIG, FINE, FINER, FINEST, or ALL.

• Log size limit is file size limit in megabytes (default 10).

• Log file count is the maximum number of log files.

The GDAL database connection is configured using the gdalParameters element as follows:

• <gdalParameters user="<user>" password="!<password>" connectionString="<db_host:port:sid>" temporaryDirectory="<directory>" />

• The specified user must have privileges to read all GeoRaster objects that are published as coverages. Is recommended that this user be the same as the WCS user.

• The password must be encrypted by the server. You must add an exclamation point (!) character at the beginning of password attribute, to make the server encrypt the password.

• The temporary directory should point to a writable directory to be used by GDAL to generate output files. Example: /tmp

To validate that GDAL was properly configured, go to the About tab in the Oracle Spatial Web Services administration console (http://<host>:<port>/oraclespatial), which shows the GDAL version if it was properly configured.

ServiceIdentification and ServiceProvider can be configured by uncommenting the appropriate element and specifying the desired information, complying with the XML schemas at http://schemas.opengis.net/ows/2.0/owsGetCapabilities.xsd.

When you click Save Changes, the server applies the changes, and no restart is needed.

Publish Coverage tab

This tab lets you publish new coverages. It requires administrator credentials.

You can publish GeoRaster objects as coverages by providing a select query that returns a single column of type SDO_GEORASTER. All GeoRaster objects returned by the select query will be published. Use the following to specify the select query. (For simplicity, you can select any entry from “Select a raster table (schema, table, column)” and click Fill query parameters to populate these fields.)

• Column Name: An SDO_GEORASTER column name from a table listed in From Clause

• From Clause: A valid FROM clause that includes schema name, table name, and alias if required by the WHERE clause.

• Where Clause: A valid WHERE clause that can include spatial operations. If the WHERE clause is empty, the SELECT statement will return all rows of the specified table.

This page shows an HTML table with all GeoRaster objects. You can choose to publish or unpublish individual GeoRaster objects by right-clicking the desired row..

A GeoRaster cannot be published more than once in a WCS instance.

Test tab

This tab lets you send post requests. The Test tab is initially empty, in which case you need to send a GetCapabilities request to populate following elements:

• Operation: An HTML select element with all operations discovered on last GetCapabilities response.

• Coverage: An HTML select element which is populated with content of last GetCapabilities response. It contains all Coverage IDs from GetCapabilities response received.

Create Request: Populates the request test area with a request to the specified operations, coverage IDs, and operation URLs.

Request: A text area whose content will be sent in a post request to the Operation URL. This element can be populated by clicking Create Request, and you can edit that request as needed.

Operation URL: The URL where the request is to be sent. This element can be populated by clicking Create Request, and you can edit that request as needed.

Send Request: Sends an HTTP post request to the Operation URL using the content of the request. The response of the HTTP post request will be shown in the Response.

Response: A text area populated with the response of a Send Request operation.

Log tab

This tab lets you visualize and download WCS log files. Log files are generated inside the directory referenced by the sdows java property. Using the Log tab requires administrator credentials.

All Oracle WCS log files have file names in the form wcs_n.log, where n is a consecutive number, and for the newest log files n is 0 (zero).

This tab shows the content of the wcs_<data_source_name>_0.log file, which has the most recent log messages generated by the WCS server. However, you can select other log files to see their contents. You can also refresh the display to include new log messages generated since the page was loaded or last refreshed.

Download lets you download the selected log file in zip format.

GDAL CreationOption in a GetCoverage Request

This element sends a -co parameter to GDAL on GetCoverage requests. Every GDAL driver defines its own creation option parameters.

Examples:

• XML Request:

  <wcs:GetCoverage xmlns:wcs="http://www.opengis.net/wcs/2.0"
    xmlns:gml="http://www.opengis.net/gml/3.2"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.opengis.net/wcs/2.0 http://schemas.opengis.net/wcs/2.0/wcsAll.xsd"
    xmlns:ora="http://www.oracle.com/spatial/wcs"
    service="WCS" version="2.0.1">
    <wcs:Extension>
    	<ora:CreationOption>WORLDFILE=YES</ora:CreationOption>
    </wcs:Extension>
    <wcs:CoverageId>C0005</wcs:CoverageId>
    <wcs:format>image/jpeg</wcs:format>
  </wcs:GetCoverage>
  

• KVP Request:

  http://.../oraclespatial/wcs?service=WCS&version=2.0.1&request=GetCoverage&format=image/jpeg&coverageId=C0005&CO=WORLDFILE=YES

CompressResponseFile in a GetCoverage Request

This element compresses the generated image into a zip file.

Examples:

• XML Request:

  <wcs:GetCoverage xmlns:wcs="http://www.opengis.net/wcs/2.0"
    xmlns:gml="http://www.opengis.net/gml/3.2"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.opengis.net/wcs/2.0 http://schemas.opengis.net/wcs/2.0/wcsAll.xsd"
    xmlns:ora="http://www.oracle.com/spatial/wcs"
    service="WCS" version="2.0.1">
    <wcs:Extension>
    	<ora:CompressResponseFile>true</ora:CompressResponseFile>
    </wcs:Extension>
    <wcs:CoverageId>C0005</wcs:CoverageId>
    <wcs:format>image/jpeg</wcs:format>
  </wcs:GetCoverage>
  

• KVP Request:

  http://.../oraclespatial/wcs?service=WCS&version=2.0.1&request=GetCoverage&format=image/jpeg&coverageId=C0005&COMPRESS=YES

11-053r1 OGC Web Coverage Service Interface Standard – CRS Extension

This WCS CRS Extension defines how to request and obtain a coverage in CRSs different from the Native CRS, and also how to provide a subsetting bounding box with coordinates in a CRS different from the Native CRS. A WCS server supporting this WCS CRS Extension announces the CRSs supported by listing their CRS Identifiers in its Capabilities document. For example:

<wcscrs:subsettingCrs>http://www.opengis.net/def/crs/EPSG/0/4326</wcscrs:subsettingCrs>
<wcscrs:outputCrs>http://www.opengis.net/def/crs/EPSG/0/4326</wcscrs:outputCrs>

112-039 OGC Web Coverage Service Interface Standard – Scaling Extension

This extension allows scaling of a coverage along one or more of its axes during its server-side processing in a GetCoverage request. For example:

<scal:ScaleByFactor>
 <scal:axis>E</scal:axis>
  <scal:scaleFactor>0.5</scal:scaleFactor>
</scal:ScaleByFactor>

112-040 OGC Web Coverage Service Interface Standard – Range Subsetting Extension

This extension allows extraction of specific fields, according to the range type specification, from the range set of a coverage during server-side processing of a coverage in a GetCoverage request. For example:

<rsub:RangeSubset>
	<rsub:RangeItem>
		<rsub:RangeComponent>band1</rsub:RangeComponent>
	</rsub:RangeItem>
	<rsub:RangeItem>
		<rsub:RangeInterval>
			<rsub:startComponent>band3</rsub:startComponent>
			<rsub:endComponent>band5</rsub:endComponent>
		</rsub:RangeInterval>
	</rsub:RangeItem>
</rsub:RangeSubset>

112-049 OGC Web Coverage Service Interface Standard – Interpolation Extension

This extension gives control over interpolation of a coverage during its server-side processing.

This allows the WCS client to control and specify the interpolation mechanism to be applied to a coverage during server processing. For example:

<int:Interpolation>
  <int:globalInterpolation>
    http://www.opengis.net/def/interpolation/OGC/1/nearest-neighbor
  </int:globalInterpolation>
</int:Interpolation>

112-100r1 OGC GML Application Schema – Coverages – GeoTIFF Coverage Encoding Profile

This encoding profile specifies the usage of the GeoTIFF data format for the encoding of GML coverages. For example:

<wcs:format>image/tiff</wcs:format>

Example Showing All Extensions

The following is an example of a GetCoverage request example with all extensions included:

<wcs:GetCoverage xmlns:wcs="http://www.opengis.net/wcs/2.0"
  xmlns:gml="http://www.opengis.net/gml/3.2"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.opengis.net/wcs/2.0 http://schemas.opengis.net/wcs/2.0/wcsAll.xsd"
  xmlns:scal="http://www.opengis.net/wcs/scaling/1.0"
  xmlns:wcscrs="http://www.opengis.net/wcs/service-extension/crs/1.0"
  xmlns:rsub="http://www.opengis.net/wcs/rangesubsetting/1.0"
  xmlns:int="http://www.opengis.net/wcs/interpolation/1.0"
  service="WCS" version="2.0.1">
  <wcs:Extension>
    <wcscrs:subsettingCrs>http://www.opengis.net/def/crs/EPSG/0/4326</wcscrs:subsettingCrs>
    <wcscrs:outputCrs>http://www.opengis.net/def/crs/EPSG/0/4326</wcscrs:outputCrs>
    <rsub:RangeSubset>
      <rsub:RangeItem>
        <rsub:RangeComponent>L3</rsub:RangeComponent>
      </rsub:RangeItem>
    </rsub:RangeSubset>
    <int:Interpolation>
      <int:globalInterpolation>
        http://www.opengis.net/def/interpolation/OGC/1/nearest-neighbor
      </int:globalInterpolation>
    </int:Interpolation>
    <scal:ScaleByFactor>
      <scal:scaleFactor>0.5</scal:scaleFactor>
    </scal:ScaleByFactor>
  </wcs:Extension>
  <wcs:CoverageId>C0005</wcs:CoverageId>
  <wcs:DimensionSlice>
    <wcs:Dimension>N</wcs:Dimension>
    <wcs:SlicePoint>8.16270027015798</wcs:SlicePoint>
  </wcs:DimensionSlice>
  <wcs:DimensionTrim>
    <wcs:Dimension>E</wcs:Dimension>
    <wcs:TrimLow>112.990337346209</wcs:TrimLow>
    <wcs:TrimHigh>113.028655200765</wcs:TrimHigh>
  </wcs:DimensionTrim>
  <wcs:format>image/tiff</wcs:format>
  <wcs:mediaType>multipart/related</wcs:mediaType>
</wcs:GetCoverage>

“DataSource jdbc/wcs_admin_ds not found” GetCapabilities response error message

An OWS error response may be like the following (reformatted here for readability):

<?xml version='1.0' encoding='UTF-8'?>
<ows:ExceptionReport
  xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  xsi:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd" version="2.0.1">
  <ows:Exception exceptionCode="NoApplicableCode" locator="DataSource jdbc/wcs_admin_ds not found"/>
</ows:ExceptionReport>

This means that a WCS data source is not configured or that WebLogic Server cannot connect to the database. Setting Up WCS Data Sources for information about configuring WCS data sources.

“INFO: GDAL was not found” message in WCS log file shown every time WebLogic Server starts

If no GDAL supported formats are needed, you can ignore this message. This message indicates that gdal.jar not found in the WebLogic Server libraries or that the LD_LIBRARY_PATH not properly configured.

• If java.lang.NoClassDefFoundError: org/gdal/gdal/gdal appears in the WCS log, then the gdal.jar file was not found.

• If java.lang.UnsatisfiedLinkError: org.gdal.gdal.gdalJNI.GetDriverCount()I appears in the WCS log, then the libgdal.so file was not found in LD_LIBRARY_PATH.

For more information, see Configuring GDAL for the WCS Server

GDALParameter error response

An error message like the following is generated when GDAL is not properly configured:

<?xml version='1.0' encoding='UTF-8'?>
<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd" version="2.0.1">
  <ows:Exception exceptionCode="NoApplicableCode" locator="GDALParameters">
    <ows:ExceptionText>...</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

The error indicates that the GDAL database connection parameters are not correct. See the Configuration File tab in the WCS Administration Console

Database connection error

The following message in the WCS log means that the database is not running:

SEVERE: Error discovering coverages 
java.sql.SQLRecoverableException: No more data to read from socket

“Error reading log file” message on WCS administration console Log tab

If an authenticated user does not interact with the WCS server administration console for a given period of time, the user session in the browser might have timed out. In this case, refresh the browser display, and re-authenticate to get a new session.

Document received does not conform with protocol syntax

An error message like the following indicates that the request contains XML elements or character elements that are not defined in any OGC specification:

<?xml version='1.0' encoding='UTF-8'?>
<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd" version="2.0.1">
  <ows:Exception exceptionCode="InvalidEncodingSyntax" locator="asdc">
    <ows:ExceptionText>Document received does not conform with protocol syntax.</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>