<html>
<head>
<style type="text/css">
<!--
body { margin-left: 4px; margin-right: 4px; font-variant: normal; margin-top: 4px; margin-bottom: 1px; line-height: normal }
p { margin-top: 0; margin-bottom: 0 }
-->
</style>
</head>
<body style="margin-left: 4px; margin-right: 4px; margin-top: 4px; margin-bottom: 1px">
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Markus, </font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">What's the standard (OGC?) part of this, just the calling structure, and consequent responses? It looks like anything can be on the backenda s the processor, and the only enforcements are in the calling and results for the getcapabilities, maybe in the service(s) requests as well . . . Still looking . . .</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">bobb</font> </p>
<br> <br><br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> Markus Neteler <neteler@osgeo.org> wrote:<br> </p>
<div style="margin-right: 0; margin-left: 15px; margin-top: 0; border-left: solid 1px #050505; margin-bottom: 0; background-color: #f3f3f3; padding-left: 7px">
<p style="margin-bottom: 0; margin-top: 0">
On Mon, Aug 24, 2009 at 6:20 PM, Bob Basques<Bob.Basques@ci.stpaul.mn.us> wrote:<br>> Landon,<br>><br>> Just had another thought . . .<br>><br>> What about setting up a (openSource) tool set specifically for handling<br>> Raster images for pre-processing purposes.  Might even be something that<br>> publishers could re-distribute with their datasets, as in this processor<br>> stack works with our data.<br><br>Try this :)<br><a href="http://pywps.wald.intevation.org/">http://pywps.wald.intevation.org/</a><br><br>Markus<br>_______________________________________________<br>Discuss mailing list<br>Discuss@lists.osgeo.org<br><a href="http://lists.osgeo.org/mailman/listinfo/discuss">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
</p>
</div>
</body>
</html>