[Geoserver-users] Is Oracle Locator sufficient or do I need Oracle Spatial?

Hi all,

for an upcoming project I will store point geometries in a Oracle DB. This DB will serve as a data store for GeoServer which will be used for WMS Requests. As I understand it Oracle handles the bounding box calculations (on behalf of GeoServer), when there is a WMS request for certain features in a bbox. In Oracle there seem to be two function for this: SDO_RELATE (which is in Locator version) and SDO_GEOM.RELATE (available only in Oracle Spatial). Which one is used by GeoServer?

I found this relevant link on the question (from 2012): http://gis.stackexchange.com/questions/36751/querying-intersecting-areas-areas-oracle-locator-or-spatial In the answer it says:

I once had to trace a GeoServer WMS query in Oracle and I’m pretty sure it used the SDO_RELATE approach, but you might want to verify this using your own trace, scanning through the GeoServer source, or posting a question on the GeoServer users mailing list

Since I am not sure, I thought I’d just ask here :wink:

The project is just starting off and I need to know whether Locator is sufficient or Spatial needs to be purchased (PostGIS cannot be used for other reasons).

Best regards,

Jens

On Mon, Apr 20, 2015 at 3:30 PM, Nachtigall, Jens (init) <
Jens.Nachtigall@anonymised.com> wrote:

Hi all,

for an upcoming project I will store point geometries in a Oracle DB. This
DB will serve as a data store for GeoServer which will be used for WMS
Requests. As I understand it Oracle handles the bounding box calculations
(on behalf of GeoServer), when there is a WMS request for certain features
in a bbox. In Oracle there seem to be two function for this: SDO_RELATE
(which is in Locator version) and SDO_GEOM.RELATE (available only in Oracle
Spatial). Which one is used by GeoServer?

I found this relevant link on the question (from 2012):
http://gis.stackexchange.com/questions/36751/querying-intersecting-areas-areas-oracle-locator-or-spatial
In the answer it says:

*I once had to trace a GeoServer WMS query in Oracle and I'm pretty sure
it used the SDO_RELATE approach, but you might want to verify this using
your own trace, scanning through the GeoServer source, or posting a
question on the GeoServer users mailing list*

Since I am not sure, I thought I’d just ask here :wink:

We use SDO_RELATE. When I have to make Oracle tests, I normally do them
against a Oracle XE, which, as far as I know, does not have a full Oracle
Spatial inside, and all appears to work fine.

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------