Mathis Logemann
64054fade4
compiler independent warning ignore
...
Signed-off-by: Mathis Logemann <mathisloge@gmail.com>
2020-11-19 17:25:10 +01:00
lightmare
a0ea7db1a7
Merge pull request #3984 from lightmare/pg-app-name
...
accept explicit parameter "application_name" in postgis and pgraster datasources
2019-08-12 12:52:34 +02:00
lightmare
8c4313f1b5
Merge branch 'master' into ST_MakeEnvelope
2019-08-11 12:06:20 +02:00
lightmare
8a44f7ffbb
Merge pull request #3942 from lightmare/postgis-float-tokens
...
postgis: always put decimal point in substituted tokens in SQL
2019-08-11 11:57:44 +02:00
Artem Pavlenko
1377ec9752
remove bogus quote from ST_EstimatedExtent
SQL {#4032) via @urzhumskov
2019-03-07 11:05:33 +00:00
Mickey Rose
86e70a726d
postgres: add connect param "application_name"
2018-09-07 11:07:33 +02:00
Mickey Rose
1ddd3afc51
postgis+pgraster: substitute numbers always with decimal point
2018-07-19 22:52:55 +02:00
Sandro Santilli
69c317cd1f
Fix some comments and error messages referencing raster parameters
2018-07-16 19:27:12 +02:00
artemp
333ef9fde1
update copyright year
2017-05-05 13:02:01 +02:00
artemp
1d06afeea2
Merge branch 'postgis-quoting' of https://github.com/lightmare/mapnik into lightmare-postgis-quoting
2017-03-14 12:29:32 +00:00
Peter Hicks
f776977982
Rename PostGIS' ST_Estimate_Extent to ST_EstimateExtent
2017-02-19 20:46:30 +00:00
Mickey Rose
428ba432b1
pgraster: copy quoting and interpolation changes from postgis
2017-02-10 18:55:23 +01:00
Mickey Rose
e35c1ca106
pgraster: indentation
2017-02-10 18:55:23 +01:00
artemp
5745bedbd9
update copyright year to 2016
2016-12-20 17:57:22 +01:00
artemp
e6e468dc9e
Merge branch 'master' into develop-master
2016-11-18 09:05:19 +01:00
Tom Hughes
a3106a6a6e
Use 2D box for pgraster bounding box
...
Using a 3D box causes errors with postgis 2.3 when clipping is
enabled as ST_Clip throws an error clipping a raster to a 3D box.
2016-11-17 16:30:18 +00:00
artemp
b5c9966e4b
refactor value related objects into include/value
dir
2016-10-11 18:01:30 +02:00
artemp
31814b32d0
rename empty_featureset
=> invalid_featureset
to avoid ambiguity + add helper is_valid
method
2016-08-15 10:41:30 +01:00
artemp
bab985dd04
always return am empty featureset instead of featureset_ptr()
2016-07-13 15:17:51 +01:00
Rafa de la Torre
8e8482803b
If there're overviews, just use them for rendering
...
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.
2016-05-06 14:43:24 +02:00
Dane Springmeyer
11487e681f
amend f8a8ec616a
by fixing invalid search and replace
2016-04-11 16:45:11 -07:00
Dane Springmeyer
f8a8ec616a
c++ style: use nullptr rather than NULL
2016-04-05 15:27:32 -04:00
artemp
63df9eecff
unconditionally emit the SRID via @pnorman ( https://github.com/mapnik/mapnik/pull/3319#issuecomment-189263651 )
2016-02-26 14:14:47 +01:00
artemp
442cc281e1
use ST_MakeEnvelope
(ref #3317 )
2016-02-26 13:50:34 +01:00
Dane Springmeyer
7608040906
centralize warning suppression
2015-11-07 17:53:09 -08:00
Dane Springmeyer
324f70652b
code cleanup / c++11 usage in plugins
2015-10-09 16:07:19 -07:00
artemp
8c6bf0eef6
update copyright notice
2015-06-16 12:49:16 +02:00
artemp
1cf0a897ac
move datasource::geometry_t into separate header and rename -> datasource_geometry_t to avoid cyclic dependencies issue
...
to_ds_type - return actual datasource_geometry_t (remove optional)
update across datasources
experssions - revert to using
2015-03-24 12:13:31 +01:00
Rafa de la Torre
6cb8b6e14b
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 11:09:44 -05:00
Dane Springmeyer
83588937b9
silence boost warnings
2014-10-21 16:37:27 -07:00
Sandro Santilli
01b56c3606
Add mention of CartoDB support in pgraster input plugin code
2014-08-20 17:31:41 +02:00
Dane Springmeyer
e4c7e2419c
make sure pgraster is rebuilt if headers change inside the postgis plugin dir
2014-08-12 20:29:51 -07:00
Dane Springmeyer
e03448ecb9
port pg_raster plugin to c++11/recent 3.x changes
2014-08-12 15:14:25 -07:00
Dane Springmeyer
4e12b999f0
pull in pgraster plugin by @strk from 2.3.x to master/3.x - refs #2329 #1660
2014-08-12 15:03:51 -07:00