Building for Proj > 8.0 and GDAL > 3.2 #4232
Comments
|
This is really important for mapnik future |
|
With #4202 proj 8 should be supported and I have build mapnik with proj8 ( only with cmake and not with scons) |
|
The problem is that's on master and most distro's are on 3.x still because there's still no 4.x release... I've pushed the branch I use for the Fedora builds to https://github.com/tomhughes/mapnik/tree/fedora which includes my backport of the proj6 fixes. |
|
I just noticed that this not being in v3.1.x will somewhat break things for me on the soon upcoming Ubuntu 22.04 next LTS release as that release is switching form proj v7.x to v8.x ... :o |
unfortunately this will be an LTS release that we'd either need to skip, or return to building Mapnik for ourselves as 22.04 switched from v7 to v8 of the Proj library which none of the released mapnik versions can be built against yet, only the unreleased "master" branch so far ... see also mapnik/mapnik#4036 and mapnik/mapnik#4232
|
I just installed ubuntu 22.04 and my program chokes on proj support. This is the bug I filed: https://bugs.launchpad.net/ubuntu/+source/mapnik/+bug/1987559 Please let me know if there is a guide to installing mapnik with proj support on ubuntu 22.04. Could I just re-compile a newer version of mapnik, if the problem is already solved? |
|
Latest mapnik master has a dependency on proj >7. |
|
Debian 12 is released and comes with proj 9.1.1! |
|
Proj9 is already supported on latest master. |
@kachelmann - could you describe exactly what's the issue? |
|
I got an upgrade to Debian 12 on my render toolchain. Now the renderprocess is running but produces only empty tiles. The renderjob works with mapnik xml stylefiles. The Datasource is a shapefile in EPSG:4326. |
|
It could be the lan/lot vs lon/lat issue https://gis.stackexchange.com/questions/434038/order-of-latitude-and-longitude-in-epsg4326 |
|
I'm running into the same with maposmatic/ocitysmap: works fine on Debian 11, but when trying to upgrade to Debian 12 I'm getting "merc: Invalid latitude". I'm at 52°N, 8.5E; so even if the two were swapped they would still be in each others valid range. |
|
So where are we with this when it comes to v3.1? I could build v3.1.x branch on Debian 12 after applying the patch @tomhughes mentioned here two years ago, but I' so far failing with the python bindings due to Boost changes, and as far as I can tell from this pull request the Python side has not really received the necessary adjustments for newer Proj versions yet either? So I'm currently stuck with Debian 11, which is OK for now but a bit ... suboptimal ... |
|
Guys, people here are getting the same error and suggest the problem is with mapnik.Projection or projection.Forward. Can someone who knows the low level details of those functions comment here? Thanks. I want to move forward in solving this using mapnik master and python-mapnik master. Edit: I've worked around the problem (which still exists) in my python code - see my comment at mapnik/python-mapnik#246 (comment) |
There doesn't seem to be any way to build mapnik with a modern version of Proj/GDAL this poses an issue when building on systems that no longer provide older versions of these dependencies, as well as issues for any other software which is dependent on newer versions of these dependencies.
Are there any plans to make a release for newer versions of Proj? I've seen issues/commits related to the issue (and tried to compile from those commits without succes) but the last release was in Jan.
Currently building on RHEL 8 is proving quite a bit more difficult than I expected.
The text was updated successfully, but these errors were encountered: