c4684e09cd
refs #2551 Postgis raster_columns view is returning NULL values for raster overviews with large scale factors. That issue in postgis is described in http://trac.osgeo.org/postgis/ticket/3006 This causes two main problems: - The first overview with scale = NULL is wrongly chosen for rendering always - The messed up scaling factor causes the render symbolizer to spent an insane amount of CPU and memory to render a messed up tiles. The patch in postgis is expected to be released with the new version, a few months from now. |
||
|---|---|---|
| .. | ||
| 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.