[fdo-internals] RE: FDO Function SpatialExtents

[Haris Kurtagic]

SDO_TUNE.EXTENT_OF has few limitations like schema access and only works for particullar number of dimensions
and still takes some time to calculate.

I think Autodesk.Oracle provider is calculating from SDO_ROOT_MBR data only (it is not exact extent in any case ).
I am hoping that formula will be shared here :)

Haris

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Tuesday, November 18, 2008 10:28 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RE: FDO Function SpatialExtents

What does 

SELECT SDO_TUNE.EXTENT_OF('TABLENAME','GEOMCOLUMN') FROM DUAL

Give you for a geodetic table?

This post makes it look like retrieving the MBR of geodetic CS from the index metadata table is non-trivial:

http://kr.forums.oracle.com/forums/thread.jspa?threadID=523315

Jason

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Haris Kurtagic
Sent: Tuesday, November 18, 2008 13:20
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RE: FDO Function SpatialExtents

SDO_ROOT_MBR is not even close to layer extent for geodetic CS.

Any clue how Autodesk.Oracle provider is calculating index extent from that SDO_ROOT_MBR  for geodetic CS?
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals