Hi Bruce,
Here I am again...
Randy suggestion are pretty valuable and very well based but I have a
especial interest on storing raster on databases so that is why I asked
about it.
Yes, raster is chunky and not very fluid but I love to hear from
successful experience like Bruce's. And as Br
IMO:
Hi Randy,
Thank you for your informative post. It has given me a lot to follow up on
and think about.
I can see an immediate need that this type of solution could well be used
for. I like it.
I suspect that in many larger corporate types of environments, it could
well be used effective
Hi Ivan,
The most common advice I've seen says to leave raster out of the DB.
Of course footprints and meta data could be there, but you would want to
point Geoserver coverage to the image/image pyramid url somewhere in the
directory hierarchy.
Brent has a nice writeup here:
http://docs.c
Hi Randy, Bruce,
That is a nice piece of advise Randy. I am sorry to intrude the
conversation but I would like to ask how that "heavy raster"
manipulation would be treated by PostgreSQL/PostGIS, managed or unmanaged?
Best regards,
Ivan
Randy George wrote:
Hi Bruce,
On t
Randy, what an informative email.
It is almost a "Howto for OSGeo hardware and performance tuning". I'm
not aware of anyone who has written something similar (although I admit
I have not looked).
I'd love to see it incorporated into an easily referenced resource -
maybe a chapter in
http://w
Hi Bruce,
On the "scale relatively quickly" front, you should look at
Amazon's EC2/S3 services. I've recently worked with it and find it an
attractive platform for scaling http://www.cadmaps.com/gisblog
The stack I like is Ubuntu+Java+ Postgresql/PostGIS + Apache2 mod_jk Tom
Dear all,
I'm happy to inform you that the hacking event in Bolsena will take
place! Enough people have confirmed their participation for me to
decide to make the booking :-)
Those participating, you will need to make and advance payment of 100
Euro to me to guarantee your place. Please c
