Hi Jerry,

I am not sure i completely understand what you are trying to do, it
might fall into the realm of WPS ( Web Processing Service ) which ( and
someone correct me if i am wrong here ) can take some data ( like from a
wfs server ) and do some sort of operation or processing on it.
Returning the result in some sort of exchange format, like GML.

There have been a few people that have implemented a WPS based on
GeoServer but nothing has been really been contributed back and
available for use.

Depending on the scope of the transformations you want to provide WPS
may be overkill. One thing we are shooting for in GeoServer is allow
people to write custom services, or write customzations to exiting
services like wfs or wms.

One popular one is the idea of an output format which takes a bunch of
"features" and encodes them in a particular exchange format like gml,
various image formats, etc... Could you implement your system as a
custom output format in geoserver that would take the features, do a
bunch of transformations on their geometries, and then give some new
features back to the client?

Just an idea, not sure if its a good one :). With a bit more info about
the specifics I can probably be more useful.

-Justin

Swan Jerry wrote:
> (Appoligies to those who I've already inadvertantly spammed with the
> following on WFS-dev):
> 
> I'm seeking to implement a "transforming WFS adaptor", i.e. a service
> that sits between an external WFS client and server and allows custom
> transformations to be performed on the geometry (the specific
> transformations to be determined polymorphically).
> 
> Internally, there are 3 adaptor components: the client (which connects
> to the external WFS server), the server (which connects to the external
> WFS client) and the transformer (which polymorphically transforms client
> output to server input).
> 
> While I've achieved this using a weakly-typed API (i.e. XML as String)
> together with XSLT, it would clearly be preferable (from an adaptor
> developer's perspective) if the API had the explicit representation of
> features as Java objects that GeoTools offers.
> 
> Any tactical advice on how this could best be achieved using existing
> GeoTools components (perhaps taking the WFSClient example from
> org.geotools.demo.example as a base?) would be greatly appreciated.
> 
> Regards,
> 
> Jerry.
> 
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses, which could damage your computer system:
> you are advised to perform your own checks. Email communications with the
> University of Nottingham may be monitored as permitted by UK legislation.
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Geotools-gt2-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
> 
> !DSPAM:1004,45e8296a309047785049143!
> 


-- 
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Reply via email to