Some times ago, I had the same idea. I think the problem is not to have a JDBC Feature Source creating geometry objects in memory based on double columns in the database.
The real problems are all the spatial predicates (intersecs, isWithin, overlapy, isWithinDistance, .......) which you have to formulate in normal sql qeuery syntax. This is the challenge. Using mysql, I would try the following. 1) add a geometry column to your table 2) create an index for it 3) create a trigger which holds your geometry consistent with your double values As far as I know, mysql does not support coordinate systems, so you are finished. Hope it helps christian Guy Mac writes: > Greetings, we (uahirise.org) are considering using geoserver+geotools as a > back-end to google maps or open layers clients, serving target box corner > coordinate data. Our DB is Mysql5, however we do not use the geometry > type, instead using separate columns for the lat, lon of each corner. We > have a lot of tools built around this schema, and it seems impractical to > maintain a copy of that data in another table or DB. Is it possible to > write a JDBC feature source with this type of data storage and get > reasonable performance? Are there any examples available? Thanks in > advance. ------------------------------------------------------------------------------ _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
