[postgis-users] Rasters

[Obe, Regina DND\MIS]

What was the chip thing that we have already in the database.  I thought
those were designed for storing raster data in postgis granted I haven't had
a reason to store raster data myself and the concept seemed a little
complicated to load to implement.

Actually the only benefits I can see for storing raster data in the database
is

1) primarily to centralize storage of gis data - becuause keeping up with
network paths is kind of cumbersome.

2) to create a dispenser of raster data to anyone in the organization who
needs it.

For example the pgsql2shp is very nice because I can give people a small set
of files to copy to run it, a sample batchscript and they can dump out
select geographical regions they want for their purposes.

Something similar for raster would be nice like a pgsql2raster that would
say dump out a geotiff of a selected region would be nice.


-----Original Message-----
From: Paul Ramsey [mailto:pramsey at refractions.net] 
Sent: Thursday, September 29, 2005 11:40 AM
To: PostGIS Users Discussion
Subject: [postgis-users] Rasters


OK, raster people.  My problem is that I cannot envision the use  
cases for raster in the database, so, make it easy for me! :)

- What is the atomic unit of storage for rasters in the database?  Is  
it complete scenes?  Something else?
- What is some SQL I would apply against my raster tables?  Make up  
some descriptive function names and show me some example SQL and tell  
me what it does.
- How do vector data and raster data interact?  Note the atomicity  
question above.

P.
_______________________________________________
postgis-users mailing list postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users