Hi,
this week I'll be participating in the Bolsena code sprint
and the topic of my work will be... WPS!
Rough ideas for the week:
- a simple demo tool to browse existing processes and build a request
point and click style (yes, I want a GUI, don't even think of making
me fiddle with the enormous WPS request xml documents eh?)
- raster data as input and output (eventually just small scale, not
sure I'll get to make them stream so that they can handle bigger
rasters data sets)
- see if I can update/improve the Sextante integration
The above are kind of appetizers. The rest of the week I'd like to
work on the "integrated WPS" concept (the WPS is in there with other
OGC services, let's make those beasts talk and work together):
- integration level 1: access directly raster and vector data
- integration level 2: process to save the output as a new layer (insert data into the default store or something)
- integration level 3: save a process as a dynamic or cached data source
(probably by having a custom WPS data store that takes process
definitions as the feature type definitions)
- INSPIRE inspired vector reprojection service
- complement WFS (generalization, grouping, aggregation)
Of course I won't be able to do all the above in just one week... it's
more of a set of directions. But I hope to get enough done to start
pushing for WPS as an extension module :-p
- a simple demo tool to browse existing processes and build a request
point and click style (yes, I want a GUI, don't even think of making
me fiddle with the enormous WPS request xml documents eh?)
It is not point and click but there is a wizard in gt-swing for this purpose; it allows you to choose from the list; enter some parameters and go.
I could have it point to a local properties file if you wanted to submit a feature collection? I did not have a WPS that could handle feature collections previously.
- integration level 2: process to save the output as a new layer (insert data into the default store or something)
- a simple demo tool to browse existing processes and build a
request point and click style (yes, I want a GUI, don't even think
of making me fiddle with the enormous WPS request xml documents
eh?)
It is not point and click but there is a wizard in gt-swing for this
purpose; it allows you to choose from the list; enter some parameters
and go. I could have it point to a local properties file if you
wanted to submit a feature collection? I did not have a WPS that
could handle feature collections previously.
I see... humm... I actually want something that can build the
xml request for me and allow me to specify each parameter in
multiple formats. For example, I want to be able to say that I want
to use an internal WFS layer as a source and maybe also specify a filter
for it. Or paste a GML collection, or choose a zipped shapefile on
the file system (a property file would work as well, too)
- integration level 2: process to save the output as a new layer
(insert data into the default store or something)
Or onto your new FTP site?
No no, with admin powers to execute it, I want it to store the
result in a datastore as a new feature typer and to configure
it in GeoServer as a newly available layer.
No FTP, if you want to download the result
in a comfy way I guess the usual zipped shapefile output should
do.