8e8482803b
The current code falls back to the base table for small scales. That approach has some drawbacks cause it forces the original table to share some conditions with its overviews (same SRID, alginment, scale constraints) for the rendering to work properly. What we propose is to always fall back to the highest resolution overview (lowest scale), rather than the original table, in order to avoid coupling the original table with the constraints imposed by rendering and still have them linked (in postgis raster metadata). Please note this approach is not 100% compatible as the base table won't be used. This should be no big deal because overviews can have an arbitrary resolution/scale. |
||
|---|---|---|
| .. | ||
| build.py | ||
| pgraster_datasource.cpp | ||
| pgraster_datasource.hpp | ||
| pgraster_featureset.cpp | ||
| pgraster_featureset.hpp | ||
| pgraster_wkb_reader.cpp | ||
| pgraster_wkb_reader.hpp | ||
| README | ||
| TODO | ||
PostGIS Raster input plugin for mapnik ====================================== This plugin shares directives with the "postgis" one, with the following differences: - "raster_field" replaces "geometry_field" - "raster_table" replaces "geometry_table" - "prescale_rasters" replaces "simplify_geometries" - "use_overviews" introduced - "clip_rasters" boolean introduced, defaults to false - "band" introduced, with same semantic of the GDAL driver Credits ======= The plugin was initially developed by Sandro Santilli <strk@keybit.net> with support from CartoDB.