-
Notifications
You must be signed in to change notification settings - Fork 91
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
Crash with old Proj library and ProjTransform() #273
Comments
hholzgra
added a commit
to hholzgra/ocitysmap
that referenced
this issue
Mar 30, 2024
See also python-mapnik issue #273 mapnik/python-mapnik#273
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is somewhat related to issue #246:
Using mapnik.ProjTransform instead of mapnik.Projection to convert from Lat/Long WGS84 to Google Mercator and back works with both old and new Proj library versions, but only when keeping the mapnik.Projection instances that the mapnik.ProjTransform was created from in scope.
When not doing so things work fine on Debian 12 with the new Proj version, but not on Debian 11 that still uses the older Proj version / API.
The following works on both Debian 11 and 12:
But when creating the ProjTransform instance in a function, with the actual Projection instances being local variables that get out of scope at the end of the function, this only works with the new Proj library version on Debian 12, but not with the older one on Debian 11.
So the below code works on 12, but segfaults on the forward() method call on 11:
The text was updated successfully, but these errors were encountered: