On 19/03/10 22:22, Andrea Aime wrote: > during the NY OpenGeo code sprint last month we've designed > and coded support for what we call "virtual tables", that > is, feature types that are defined via a straight, native > sql query.
Um, Andrea, did you just invent a generic solution that supersedes the discontinued geometryless data store? That is, can you use a custom select to manufacture a spatial view from a non-spatial table? For example: SELECT id, name, url, ST_SetSRID(ST_Point(longitude, latitude),4326) as location FROM non_spatial_table; where longitude and latitude are numeric columns. The next question is: do spatial queries work if geometries are manufactured in the SELECT? We used to fall back to brute force queries (?) for geometries without indices. Since GT 2.6 they just fail. I think you also just replaced the old sqldatastore as well, all in one hit. Wow! (Count that as a +1 if you are canvassing for votes.) Kind regards, -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
