A new DataStore to handle databases with no native spatial geometry types.
This has now been committed as a plugin called "geomteryless" that currently supports two data stores, complete with factories:
geometryless.JDBCDataStore that knows nothing about geometries and cnabe used to put a WFS (read) interface over any tabular data.
Initially restrict to point (location) data with x,y (easting northing, long/lat) columns
This is basically to support geoserver as a front end to the mass of existing location based data not using spatial dbs. Specifically, its also to support work mapping multi-table relational schema to GML application schema standards.
This implementation also supports specification of a ConnectionPool object so you can plug in any back end JDBC source where the driver provides this.
1) solve limitation that x,y columns need to be last columns in result set
2) allow basic jdbc drivers to be used with a generic connection pool
3) test /implement write access
|Implement GeoAPI filters||Closed||Unassigned|
|Use common connection pooling, allowing simple JDBC standard connections||Closed||Unassigned|
|Support nonBBOX geometry filters||Closed||Unassigned|
|4.||migrate functionality to app-schema and remove module||Open|