<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I am wondering about having imagery analysis functionality built into
the database? I think that a layer between the database and the viewer would be
where those functions would work best. For example GeoServer,
http://geoserver.sourceforge.net/html/index.php, can act as a WFS/WMS server
layer connected to PostGIS as one of its possible datastores. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> I
noticed some interesting alpha work going on over at the GeoTools/GeoServer
project. One of the capabilities in the works is adding
StreamingRenderer/GridCoverageRenderer which allows reprojection of imagery as
a WMS query.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>
There is a screen shot here: <a
href="http://udig.refractions.net/confluence/display/UDIG/Screenshots"
title="http://udig.refractions.net/confluence/display/UDIG/Screenshots">http://udig.refractions.net/confluence/display/UDIG/Screenshots</a>
in the second row </span></font><font size=2 face=Verdana><span
style='font-size:10.0pt;font-family:Verdana'>“<font color=black><span
style='color:black'>Example of rendering from GeoServer reprojected in CRS
EPSG:42103 (WGS84 / LCC <st1:place w:st="on"><st1:country-region w:st="on">USA</st1:country-region></st1:place>)”</span></font></span></font><font
color=black><span style='color:black'> which shows an example of
reprojected WMS query under a WFS query.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt;color:black'>
</span></font>This is a long way from the type of MapCalc operations you are
talking about but the same layered approach would be better than trying to make
PostGIS something more than it should be. The imagery could be stored either in
the file system or in a database - PostGIS … MapCalc functions would be
part of the server layer which could point to either type of datastore …
output view format selection could be part of the query allowing multiple
viewers to connect to the results either offline or online.<o:p></o:p></p>
<p class=MsoNormal style='text-indent:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>Views could be merged with WFS filter queries on top.
So PostGIS tables with geometry footprints and uri pointers to geotiff
imagery would work for satellite Iconos imagery (1Gb) while some type of
blob bytea[] fields could be used for smaller images, like weather loop images
(40Kb) (<a href="http://www.web-maps.com/Hurricane/"
title="http://www.web-maps.com/Hurricane/">http://www.web-maps.com/Hurricane/</a><font
color=navy><span style='color:navy'> ) </span></font>Either approach
could have Census TIGER data shown over the top (way cool).<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> I
believe the<font color=black><span style='color:black'> OGC Grid Coverage
Service specification http://www.opengeospatial.org/specs/?page=specs is the
place to look at how analysis services could be set up in an open standard way.
<o:p></o:p></span></font></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt;color:black'>Randy</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
</div>
</body>
</html>