(Whichever tiler you use) and efficient delivery of raster data (image pyramid layer) (update2)

Subdivision of geographic data is a panacea to problems you didn’t know you had. Maybe you deal with vector data, so you pre-tile your vector data to ship to the browser to render– you’re makin’ smaller data. Maybe you use cutting edge PostGIS so you apply ST_Subdivide to keep your data smaller than the database page size like Paul Ramsey describes here. Smaller’s better… . Or perhaps you … Continue reading (Whichever tiler you use) and efficient delivery of raster data (image pyramid layer) (update2)

GeoServer and efficient delivery of raster data (image pyramid layer) (update)

A perennial favorite on this blog is “GeoServer and efficient delivery of raster data (image pyramid layer)“. I am neither the last nor the first authority on this topic (check the GeoSolutions blog for authoritative work on GeoServer and raster, also look to the GeoServer documentation), but I’ve had some good experiences with serving rasters in GeoServer, especially using image pyramid layers Read the original, … Continue reading GeoServer and efficient delivery of raster data (image pyramid layer) (update)

GeoServer and efficient delivery of raster data (image pyramid layer)

One thing I’ve learned in the last few years is that there is no theoretical reason why (properly indexed and summarized) data cannot be displayed at all scales as quickly as at any scale. This is the principle at work behind the extraordinary efficiencies of delivering data and imagery through a slippy map interface like Google, Bing, and OpenLayers as well as efficient thick client … Continue reading GeoServer and efficient delivery of raster data (image pyramid layer)