[fdo-internals] Question about FDOOGRProvider

[Jackie Ng]

Is it worth caching this extent in the provider for future calls to other
spatial context readers from this provider?

An extent of a Spatial Context isn't exactly guaranteed to be an accurate
barometer of the true bounds of a Feature Class (eg. SQL Server's spatial
context bounds are mostly just inferred from the bounds of whatever spatial
indexes have been set for their geometry columns). It seems to be just a
bounds and not *the* bounds of the Feature Class.

The brute force EXTENT() function in MapGuide is a last-resort method for
obtaining the bounds of a Feature Class. This would only be used if there
was no SpatialExtent() function support in the FDO provider (which sadly OGR
is one of). I know the MapGuide Schema Previewer is one such place that uses
such logic.

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Question-about-FDOOGRProvider-tp5131270p5131552.html
Sent from the FDO Internals mailing list archive at Nabble.com.