Excellent. Being lazy, I really appreciate solutions that require no coding on my part. ;-)<br><br>I'll give these suggestions a try. Thanks.<br><br>JN<br><br><div><span class="gmail_quote">On 8/25/06, <b class="gmail_sendername">
Paul Ramsey</b> <<a href="mailto:pramsey@refractions.net">pramsey@refractions.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
John,<br><br>I think by following Frank's advice and using a PostGIS-hosted tile-<br>index you can do a hell of a lot by manipulating your DATA statement<br>to get the images you want for a given request. Things like temporal
<br>subsetting, etc, are all pretty easy. You don't even need to use<br>mapscript, just override your DATA statement with a parameter in the<br>mapserv CGI. (I think mapscript is largely irrelevant given the<br>capabilities of the CGI system, personally.)
<br><br>Paul<br><br>On 25-Aug-06, at 9:55 PM, Frank Warmerdam wrote:<br><br>> John Novak wrote:<br>>> I have a large number of rows containing metadata about rater<br>>> files sitting in a PostGIS table. Each row is associated with a
<br>>> georeferenced file sitting in a file system, and the row contains<br>>> polygon geometry representing the footprint of the raster. The<br>>> rows also contain many other attributes that I'd like to use to
<br>>> filter the displayed rasters.<br>>> Having the functionality of the RASTER layer, but using a PostGIS<br>>> table as a source for features rather than a SHAPEFILE would be a<br>>> very useful thing, at least in my case.
<br>> ><br>>> What's the opinion regarding<br>>> 1. the overall usefulness of such a beastie<br>>> and<br>>> 2. the complexity of actually implementing said beastie, given<br>>> that it's a combination of the functionality of a PostGIS layer
<br>>> and a RASTER layer ?<br>>> I admit I have not done my homework and really examined the code<br>>> for these two layers.<br>><br>> John,<br>><br>> It is currently possible to use a postgis table as a "tile index" for
<br>> a raster layer. To do so, configure the postgis table as a<br>> distinct layer,<br>> and use the name of that layer in the TILEINDEX keyword of your<br>> raster layer<br>> instead of the name of an external shapefile.
<br>><br>> The raster layer will do a spatial query on the tileindex table to get<br>> a list of rasters to plot.<br>><br>> I'm a bit fuzzy on how you would do other sorts of query operations.<br>> It is possible a FILTER on the tileindex layer will be preserved as
<br>> part of the tileindex query, but I'm not absolutely sure. Of course,<br>> you could put complex query logic right into your DATA statement on<br>> the postgis layer.<br>><br>> Best regards,<br>> --
<br>> ---------------------------------------<br>> +--------------------------------------<br>> I set the clouds in motion - turn up | Frank Warmerdam,<br>> <a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com
</a><br>> light and sound - activate the windows | <a href="http://pobox.com/~warmerdam">http://pobox.com/~warmerdam</a><br>> and watch the world go round - Rush | President OSGeo, http://<br>> <a href="http://osgeo.org">
osgeo.org</a><br></blockquote></div><br>