[Geoserver-devel] PSC: GSIP 48 (parametric sql views) ready to vote

Hi PSC members,
GSIP 48 is ready for a vote:
http://geoserver.org/display/GEOS/GSIP+48+-+Parametric+SQL+views+in+GeoServer

So far I have two +1 (me and Jody) and no feedback from the rest
of the PSC. Please jump in and let us hear your opinion :slight_smile:

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

+1.

I think this is an excellent and powerful new feature. I have been thinking about how this could be used in WFS as well, particularly app-schema, which is an adapter that consumes simple feature data stores. This approach could provide some exciting new configuration options.

Andrea, I assume this requires JDBCDataStore (NG) changes? If, could you please outline them?

Rob A, how close is this to replacing sqlview?

Nice work, Andrea.

Kind regards,
Ben.

On 25/06/10 00:24, Andrea Aime wrote:

Hi PSC members,
GSIP 48 is ready for a vote:
http://geoserver.org/display/GEOS/GSIP+48+-+Parametric+SQL+views+in+GeoServer

So far I have two +1 (me and Jody) and no feedback from the rest
of the PSC. Please jump in and let us hear your opinion :slight_smile:

Cheers
Andrea

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

Rob.Atkinson@anonymised.com ha scritto:

+1

I concur the goal is to replace sqlview store, and this is a more
comprehensive approach.

We'll need to think carefully and set up some test cases for passing
parameters from filters against complex feature schemas into
parameters in prepared statements, and I haven't had time to look
more closely into what would be involved, but hopefully we can get
the SISS team to have a look sometime..

If you look in gt-devel there is a long discussion on why we
won't be using prepared statements but plain old string substitution
instead (yes, we know there risks, but there no no money on the table
for the prepared statements approach, as it won't give the sponsor
what they want, which is, full sql snippets injection)

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Ben Caradoc-Davies ha scritto:

+1.

I think this is an excellent and powerful new feature. I have been thinking about how this could be used in WFS as well, particularly app-schema, which is an adapter that consumes simple feature data stores. This approach could provide some exciting new configuration options.

Andrea, I assume this requires JDBCDataStore (NG) changes? If, could you please outline them?

It's an extension to the VirtualTable changes I did some months ago.
I'll pass it by GeoTools-devel soon (as in, gimme ten minutes)

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

++1 very nice and cool feature

Alessio.


Eng. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584 983027
fax: +39 0584 983027
mob: +39 349 8227000

http://www.geo-solutions.it
http://geo-solutions.blogspot.com

On Fri, Jun 25, 2010 at 8:06 AM, Andrea Aime <aaime@anonymised.com1…> wrote:

Ben Caradoc-Davies ha scritto:

+1.

I think this is an excellent and powerful new feature. I have been
thinking about how this could be used in WFS as well, particularly
app-schema, which is an adapter that consumes simple feature data
stores. This approach could provide some exciting new configuration options.

Andrea, I assume this requires JDBCDataStore (NG) changes? If, could you
please outline them?

It’s an extension to the VirtualTable changes I did some months ago.
I’ll pass it by GeoTools-devel soon (as in, gimme ten minutes)

Cheers
Andrea

–
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.


ThinkGeek and WIRED’s GeekDad team up for the Ultimate
GeekDad Father’s Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo


Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Ben Caradoc-Davies ha scritto:

+1.

I think this is an excellent and powerful new feature. I have been thinking about how this could be used in WFS as well, particularly app-schema, which is an adapter that consumes simple feature data stores. This approach could provide some exciting new configuration options.

Andrea, I assume this requires JDBCDataStore (NG) changes? If, could you please outline them?

Rob A, how close is this to replacing sqlview?

Talking about replacements, the work I'm doing is still not up to
replace the geometryless store.

In theory it could be made to by creating a custom template block
that is expanded only in case of bbox query, and by starting to
accept geometries in WKT format.

Think you have your non spatial aware database and you want
to create points out of it, the following could work:

select a, b, c, 'POINT(' + x + ' ' + y + ')' as geom
from table
{bbox}where x >= %xmin% and x <= %xmax%
       and y <= %ymin% and y >= %ymax%{bbox}

where the {bbox} block is expanded only if we have a
spatial query in the mix (the string -> geometry conversion
could be taken care of by converters).

Imagine that we also roll a generic jdbc-ng datastore
targeted at non spatial databases and you have all
you need to replace the old geometryless datastore,
but sort of on steroids (you can also build LINESTRING
and other geometry types if you really want to).

On the other side that would be hard-ish to configure
and not sure if all the work needed to get there
is worth the trouble (and oh, it would be read only
too).

Just thinking out loud :wink:

Cheers
Andrrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.