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
Update to a new Mapnik and Kosmtik versions #3717
Comments
This change is needed to finally merge long awaited #3399. |
If we require a new mapnik version we should be doing that in a major release |
It's either master or the latest (version) tag, it cannot be both :) Does OSMF Operations already run the latest version? Logistically it would probably be easier if they bump their version first, before we release a version requiring the new Mapnik. |
On my local machine, it renders correctly. But I have deleted all .index files for the shapefiles. I suspect these files make problems because there is a version missmatch between the Mapnik version that generates the index files (either the downloaded index files or these you might re-create locally using your distribution's Mapnik package) and the node-mapnik version used by Kosmtik. If you delete the index files, does it render correctly? |
I have upgraded my system to Ubuntu 19.04 and the whole environment is not working, currently I have: $ node -v $ npm -v Maybe I will try to downgrade them to a node v8.10.0 and npm 3.5.2, as before. |
|
This is a consequence of a change in CartoCSS which outputs now much more warnings than before, but still generates the very same XML result. Its consequences for openstreetmap-carto have been discussed in #3183 and it has been considered a non-issue. |
Closing as we use higher Mapnik and Kosmtik versions now. |
Expected behavior
After upgrade to newest Kosmtik version from git master (see kosmtik/kosmtik#295) rendering should not change.
Actual behavior
There are some warnings and the rendering is broken.
Links and screenshots illustrating the problem
Example warnings:
Luxembourg - after:
The text was updated successfully, but these errors were encountered: