Geometryless JDBC data store

Details

Type: New Feature
Status: Open
Priority: Minor
Resolution: Unresolved
Affects Version/s: 2.1.M0, 2.1.0, 2.4-M0, 2.4.0
Fix Version/s: 2.4.6
Component/s: unsupported
Labels:
None

Description

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.

LocationsXYDataStore
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.

To do:
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

Issue Links

depends upon

GEOT-2505 GML bindings ignore all attributes

is related to

GEOT-103 create csv datastore module

Options
- Show All
- Show Open

Sub-Tasks

1.	Implement GeoAPI filters	Closed	Unassigned
2.	Use common connection pooling, allowing simple JDBC standard connections	Closed	Unassigned
3.	Support nonBBOX geometry filters	Closed	Unassigned
4.	migrate functionality to app-schema and remove module	Open	Rob Atkinson

Activity

Ascending order - Click to sort in descending order

James Macgill made changes - 03/Sep/04 5:42 AM

Field	Original Value	New Value
Link		This issue is related to ~~GEOT-103~~ [ ~~GEOT-103~~ ]

Hide

Permalink

Chris Holmes added a comment - 04/Sep/04 10:19 AM

A more advanced option that would be nice to offer at some point would be wkb in clobs or blobs. User should be able to configure which columns to parse, perhaps in the parameters for the factory, perhaps a richer semantic is needed, which is probably needed if we are to do the AS and join stuff right. Deegree has a bit of interesting stuff on how they set up configuration.

Show

Chris Holmes added a comment - 04/Sep/04 10:19 AM A more advanced option that would be nice to offer at some point would be wkb in clobs or blobs. User should be able to configure which columns to parse, perhaps in the parameters for the factory, perhaps a richer semantic is needed, which is probably needed if we are to do the AS and join stuff right. Deegree has a bit of interesting stuff on how they set up configuration.

Jody Garnett made changes - 04/Oct/04 4:11 PM

Fix Version/s

2.1.x [ 11266 ]

Rob Atkinson made changes - 06/Oct/04 11:20 PM

Description

A new DataStore to handle databases with no spatial geometry types. Initially restrict to point (location) data with x,y (easting northing, long/lat) columns but could be extended to allow WKT representations packed in Strings - though this would probably require some smarts in terms of a bounding box creation and post filtering using the full geometry.

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.

Ideally we'll be able to detect or configure the jdbc driver to use - as opposed to most relational DataStores which are tightly bound to specific jdbc drivers.

Rob Atkinson has an implementation under way which will be posted soon. This will be limited in the first instance - may not even include geometry support - because its to support other work extracting complex GML from multiple related tables.

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.

LocationsXYDataStore
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.

To do:
1) solve limitation that x,y columns need to be last columns in result set
2) register this as a module in the issue tracker ?
3) test /implement write access
4) allow basic jdbc drivers to be used with a generic connection pool
5) write up a how to use for this data store

James Macgill made changes - 21/Jan/05 11:04 AM

Fix Version/s		2.1.M3 [ 11468 ]
Fix Version/s	2.1.x [ 11266 ]

Justin Deoliveira made changes - 26/Jan/06 11:00 AM

Fix Version/s		2.1.2 [ 12303 ]
Fix Version/s	2.1.1 [ 11907 ]

Cory Horner made changes - 15/Nov/06 1:58 PM

Fix Version/s

2.1.2 [ 12303 ]

Hide

Permalink

Rob Atkinson added a comment - 04/Jan/07 10:54 PM

No plans are in place to support for Geotools 2.2 and 2.3. Should be relatively simple to enable for these builds if required.

Show

Rob Atkinson added a comment - 04/Jan/07 10:54 PM No plans are in place to support for Geotools 2.2 and 2.3. Should be relatively simple to enable for these builds if required.

Rob Atkinson made changes - 04/Jan/07 10:54 PM

Affects Version/s		2.4.M0 [ 12964 ]
Fix Version/s		2.4.M0 [ 12964 ]
Description	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. LocationsXYDataStore 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. To do: 1) solve limitation that x,y columns need to be last columns in result set 2) register this as a module in the issue tracker ? 3) test /implement write access 4) allow basic jdbc drivers to be used with a generic connection pool 5) write up a how to use for this data store	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. LocationsXYDataStore 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. To do: 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
Affects Version/s		2.4.0 [ 13062 ]
Affects Version/s		2.1.0 [ 11495 ]

Jody Garnett made changes - 02/Mar/07 1:03 PM

Fix Version/s		2.4.M1 [ 13260 ]
Fix Version/s	2.4.M0 [ 12964 ]

Jody Garnett made changes - 30/Mar/07 7:00 PM

Fix Version/s		2.4.M2 [ 13348 ]
Fix Version/s	2.4.M1 [ 13260 ]

Jody Garnett made changes - 30/Apr/07 3:26 PM

Fix Version/s	2.4.M2 [ 13348 ]
Fix Version/s		2.4.M3 [ 13451 ]

Cory Horner made changes - 31/May/07 3:04 PM

Fix Version/s	2.4-M3 [ 13451 ]
Fix Version/s		2.4-M4 [ 13525 ]

Jody Garnett made changes - 28/Jun/07 11:29 AM

Fix Version/s		2.4-RC0 [ 13595 ]
Fix Version/s	2.4-M4 [ 13525 ]

Justin Deoliveira made changes - 19/Aug/07 9:59 PM

Fix Version/s	2.4-RC0 [ 13595 ]
Fix Version/s		2.4-RC1 [ 13677 ]

Andrea Aime made changes - 08/Feb/08 5:06 AM

Fix Version/s	2.4-RC1 [ 13677 ]
Fix Version/s		2.5-M1 [ 13281 ]
Fix Version/s		2.4.1 [ 14069 ]

Andrea Aime made changes - 29/Feb/08 8:22 AM

Fix Version/s	2.4.1 [ 14069 ]
Fix Version/s		2.4.2 [ 14108 ]

Andrea Aime made changes - 08/Apr/08 3:32 AM

Fix Version/s		2.4.3 [ 14180 ]
Fix Version/s	2.4.2 [ 14108 ]

Jody Garnett made changes - 29/Apr/08 5:56 PM

Fix Version/s	2.5-M1 [ 13281 ]
Fix Version/s		2.5-M2 [ 14258 ]

Jody Garnett made changes - 08/May/08 12:13 PM

Fix Version/s

2.5-M2 [ 14258 ]

Andrea Aime made changes - 19/May/08 10:59 AM

Fix Version/s	2.4.3 [ 14180 ]
Fix Version/s		2.4.4 [ 14320 ]

Andrea Aime made changes - 23/May/08 9:24 AM

Fix Version/s	2.4.4 [ 14320 ]
Fix Version/s		2.4.5 [ 14338 ]

Gabriel Roldan made changes - 04/Sep/08 8:04 PM

Fix Version/s	2.4.5 [ 14338 ]
Fix Version/s		2.4.6 [ 14552 ]

Rob Atkinson made changes - 01/Oct/09 9:53 AM

Link

This issue depends upon ~~GEOT-2505~~ [ ~~GEOT-2505~~ ]

Hide

Permalink

Rob Atkinson added a comment - 01/Oct/09 9:53 AM

need to access GML attributes to make this work

Show

Rob Atkinson added a comment - 01/Oct/09 9:53 AM need to access GML attributes to make this work

Jody Garnett made changes - 02/Jun/11 9:03 AM

Component/s		unsupported [ 14729 ]
Component/s	new modules [ 10644 ]

People

Assignee:

Unassigned

Reporter:

Rob Atkinson

Vote (1)

Watch (1)

Dates

Created:

02/Sep/04 7:42 PM

Updated:

02/Jun/11 9:03 AM