Lucena, Ivan wrote:
That would reduce the complexity a lot. It would be *just* 80 files. I probably don't even need a separate then in folder. I
could also generate pyramids overlay on those. That would increase the data storage a little:
80 files
80x720x360x250x2x2=20736000000
Does anybody advocate Geoserver, Mapserver, ArcServer, Imageserver, tile cache, openlayers or others? Or should I use raster
or database for that?
I think the subject of this thread is the real problem?
Raster DATA. Raster information is only images. They require some sort of
processing to extract any data from them?
Data overlays for raster images will help to provide methods of searching for
features and then displaying the correct area of the raster image? Timestamp
data to identify a sequence of images would also be best stored in a database,
with features and locations extracted from particular images stored along with
links to the correct raster image.
So the raster images are stored as files, and the data relating to them in a
database?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
_______________________________________________
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
