Re: [Geotools-devel] ContentDataStore and the Query API

2015-01-16 Thread Jody Garnett
MemoryDataStore would be best (for speed and low effort setting up test cases). -- Jody Garnett On 16 January 2015 at 09:41, Torben Barsballe wrote: > Where would be the best place for test cases for these changes: > Looking through the ContentDataStore/ContentFeatureSource test cases, the > moc

Re: [Geotools-devel] ContentDataStore and the Query API

2015-01-16 Thread Torben Barsballe
Where would be the best place for test cases for these changes: Looking through the ContentDataStore/ContentFeatureSource test cases, the mocks used are not fully functioned and would not really support tests of the feature reader bounds query reprojections. Would it make more sense to expand the m

Re: [Geotools-devel] ContentDataStore and the Query API

2015-01-15 Thread Jody Garnett
AbstractDataStore had a ForceCoordinateSystemIterator and there is a ForceCoordinateSystemFeatureReader

Re: [Geotools-devel] ContentDataStore and the Query API

2015-01-15 Thread Torben Barsballe
In order to fix the problems with ContentFeatureSource, changes are required to ContentFeatureSource.getBounds(Query) and ContentFeatureSource.getReader(Query). Fixing getBounds is relatively easy, but it looks like getReader is a bit more difficult. Basic reprojection is handled by ReprojectFeatu