GeoDjango? I'm not sure if this is an example of what you have in mind, but we currently have a NASA-funded project to demonstrate a web service that serves estimates of wildfire emissions. It uses geodjango as the base 'framework' to do some basic geoprocessing (intersecting burned areas with a fuels map) and interfaces with a separate (non-spatial) model that estimates fuel consumption and emissions. Parameters that are used to filter the results (i.e. geometric mask, time boundaries, etc.) and drive the fuel consumption and emissions models (i.e. moisture conditions, burn intensity, percent canopy consumed, etc.) are specified as part of the URL. So rather than using WPS, we are working towards a RESTful interface (with resources like burned areas, fuel consumption, and emissions) that serves back the results in a variety of geospatial formats (geotiff, netcdf, shapefile, kml, html with OL, etc.). Currently it is read-only, but in the future we might allow user to POST their own areas of interest to the server.
So I would consider geodjango to be a framework that can be used for geoprocessing. (But I am not sure if missed the point of what you are asking...) And I suppose geodjango could be configured to respond to WPS requests, but I'm not aware of any examples of anyone currently doing this. - Tyler On Oct 15, 8:41 am, Sean Gillies <[email protected]> wrote: > Hi all, > > I launched this group soon after chatting with a bunch of different > folks about feature processing. Mainly in the context of WPS services. > I don't do a lot of what GIS people call "geoprocessing" these days, > but enjoy thinking about it. I wonder if we might be able to move past > one-off scripts to frameworks for processing like we've moved past one- > off CGI scripts to web frameworks. What would a geoprocessing > framework look like? Does anyone have one they'd like to introduce? > FWIW, I think a WPS service isn't a framework by itself, but could be > backed up by a framework. > > Cheers, > > -- > Sean
