Florencia, Since you are using this strategy for vector layers, I think that it could work for rasters.
You would use gdaltindex or something else to create a polygon data set that represented the 'footprints' of your raster files. http://mapserver.org/optimization/tileindex.html One of the attribute columns in a tile index is the path to the location of each individual raster file. The raster files are stored in the file system, not in the database. The database just stores the paths to the images. I don't know if you can create a tileindex directly in PostGIS, but you could import the output shapefile. I am guessing that you would then create a related table in PostGIS that stored records containing the allowed tileid and username combinations. For the tileindex, you would use pretty much the same query that you use for your vector layers. David. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of florencia.bujan Sent: Monday, November 29, 2010 10:39 AM To: [email protected] Subject: [mapserver-users] Re: Raster Data from PostGIS David, Exactly. I done this with a dynamic parameter, like this: DATA "the_geom from (SELECT l.* from lotes l, campos c WHERE c.id=l.idcampo AND l.idcampo=%param%) as lotes using unique gid using SRID=-1" but I want to do that with raster layer. Perhaps another solution is in the passage of parameters. Thanks! Florencia from Uruguay -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Raster-Data-from-PostGIS-tp5784362p5785003.html Sent from the Mapserver - User mailing list archive at Nabble.com. _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
