Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapnik 2.0 and PostGIS 2.0 #956

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

Mapnik 2.0 and PostGIS 2.0 #956

eightysteele opened this issue Nov 16, 2011 · 4 comments

Comments

@eightysteele
Copy link
Contributor

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
Copy link
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
Copy link
Contributor Author

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

kkaefer pushed a commit to kkaefer/mapnik that referenced this issue Feb 16, 2012
…ting code) and fixup other debug output - closes mapnik#893 and closes mapnik#956
@springmeyer
Copy link
Member

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

@eightysteele
Copy link
Contributor Author

Excellent.

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

No branches or pull requests

2 participants