Mapnik 2.0 and PostGIS 2.0 #956

Closed
eightysteele opened this Issue Nov 16, 2011 · 4 comments

2 participants

@eightysteele

It looks like Mapnik depends on some pretty old PostGIS functions that are deprecated in PostGIS 2.0. The workaround is to load legacy.sql and legacy_compatibility_layer.sql.

@springmeyer
Mapnik member

yep, been meaning to get to this. thanks for the reminder. It is an easy fix (we already are using ST_ internally, just pulled back from using it by default for AsBinary because of performance oddities I saw long ago when first testing).

@eightysteele

Awesome! Glad to hear that it's an easy fix. cc: @tokumine

@springmeyer springmeyer added a commit that closed this issue Nov 20, 2011
@springmeyer springmeyer postgis: support PostGIS 2.x - always use ST prefix (removing old tes…
…ting code) and fixup other debug output - closes #893 and closes #956
3b72597
@kkaefer kkaefer pushed a commit to kkaefer/mapnik that referenced this issue Feb 16, 2012
@springmeyer springmeyer postgis: support PostGIS 2.x - always use ST prefix (removing old tes…
…ting code) and fixup other debug output - closes #893 and closes #956
5b94e63
@springmeyer
Mapnik member

also caught one last use of a deprecated function in 6dfb360, also backported to 2.0.x

@eightysteele

Excellent.

@horacer horacer referenced this issue in mapproxy/mapproxy Jun 4, 2014
Closed

Performance issue with PostGIS >= 2.0 #154

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment