[gdal-dev] FileGBD vs OpenFileGBD, a few of questions

[Even Rouault]

> So each thread needs to build its own DataSource and associated in memory
> spatial index,
> and keep them alive for as possible in order to reuse the index?
> Sorry for all these questions, trying to figure out if there is a way to
> keep the index alive
> long enough to be useful in an application like GeoServer, where each
> thread serves one request
> in a stateless manner. I'm guessing maybe one would have to setup some sort
> of DataSource
> pooling, not unlike a connection pool for databases.
> Are there other file formats that would benefit from such a thing?

OpenFileGDB is certainly one that would benefit the most from datasource 
pooling, but all others can also, like the ones ingesting the dataset in 
memory, or having to do an initial full scan to determine the feature schema 
(GeoJSON)

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com