GetSpatialContext always return same extent on FeatureSources

[gBecker]

When adding Features to a FeatureSource at runtime and then calling the GetSpatialContext methode of the FeatureService the methode always return the same extent as it returns the first time it was requested.

That means when adding features outside of the "initial" extent of the FeatureSource the extent isn't updated. Seems to have something to do with caching of FeatureSources.

[tomfukushima]

Yes, this is as designed for performance reasons. Currently there is no API that I know of to flush an individual feature sources spatial context. If this is important for you, I suggest creating an RFC that would add the API or something else that might resolve your needs sufficiently.

[zspitzer]

there is an easy work around for this problem, simply open and save the feature source definition, either via the API or using Maestro/Studio. That will flush the cache

[jng]

Extent of the spatial context should not be used as an indicator of the minimum bounding box.

Use either the SpatialExtents() aggregate function (where supported) or the special EXTENT() function (see: ​http://themapguyde.blogspot.com.au/2012/06/mapguides-undocumented-custom-aggregate.html)