One idea i had while implementing stored queries for wfs 2.0. Just like
rendering transformations in sld are the bridge between wms and wps,
storied queries could the bridge between wfs and wps. I think they line up
pretty well...stored queries essentially give you a way to call a known
procedure plugging in parameter values. Anyways, just a thought, surely
something that would have to be fleshed out and unfortunately would only
work for wfs 2.0.
On Fri, Jun 15, 2012 at 10:03 AM, Andrea Aime
<andrea.a...@geo-solutions.it>wrote:
> On Fri, Jun 15, 2012 at 3:35 PM, <christian.muel...@nvoe.at> wrote:
> > Hi Andrea
> >
> > I am with you, the first target is to be compliant to the specifications.
> > WPS would be a clean solution.
>
> Mind, I'm not saying that WFS should be left out of the game, but that
> there should be
> some solution that cleanly extends WFS and open the door to all kind
> of transformations,
> instead of having an increasingly brittle set of extra addressing all
> the possible use
> cases where WFS fails to satisfy the user needs.
>
> One example is rendering transformations, we set them up to allow
> mixing processing
> and styling in an open ended way and it is bearing fruits, other
> people is adding
> support for heatmaps, point clustering, on the fly scattered point
> interpolation and
> so on based on such mechanism.
>
> Something similar for WFS would imho be acceptable, a convenience to apply
> on the fly one of many available processes to the WFS output, transforming
> its
> structure into something different.
>
> Could be seen, for example, as a custom output format, configurable in
> some way,
> like for example the discussions we have seen in the past where people
> would
> like to have a XSLT based output format for GeoServer. It's not there yet,
> but
> it's not bad per se, because it's an open ended mechanism that allows
> for future growth.
> What would worry me would be an output format that does a custom
> transformation instead,
> because we'd end up with a billion of them (anybody is free to
> implement the custom
> one btw, it's just not material for the public GeoServer code base imho).
>
> Cheers
> Andrea
>
> --
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
