mapnik/plugins/input
Rafa de la Torre af4c2620aa Ignore overviews with 0 scale in pgraster
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.

Conflicts:
	plugins/input/pgraster/pgraster_datasource.cpp
2014-12-04 12:29:16 -05:00
..
csv update copyright year 2014-11-20 15:25:50 +01:00
gdal make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
geojson feature_collection_grammar : allow passing start_id at parse time - #2582 2014-11-24 12:26:11 +01:00
occi update copyright year 2014-11-20 15:25:50 +01:00
ogr update copyright year 2014-11-20 15:25:50 +01:00
osm update copyright year 2014-11-20 15:25:50 +01:00
pgraster Ignore overviews with 0 scale in pgraster 2014-12-04 12:29:16 -05:00
postgis update copyright year 2014-11-20 15:25:50 +01:00
python silence boost warnings 2014-10-21 16:37:27 -07:00
raster make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
rasterlite make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
shape update copyright year 2014-11-20 15:25:50 +01:00
sqlite use four letter abriviations to determine datatypes (https://www.sqlite.org/datatype3.html) 2014-11-25 11:09:42 +01:00
templates don't call *params.get<std::string>("type"), instead use static datasource::name() 2014-06-26 10:51:24 +01:00
topojson update copyright year 2014-11-20 15:25:50 +01:00