-
Notifications
You must be signed in to change notification settings - Fork 819
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
Plans for supporting Mapnik 2 #2198
Comments
If the stylesheets can't be used by tilemill then we decrease the pool of contributors and decrease the opportunities to reuse the styles. Tilemill is still the only CartoCSS design tool that has proper releases and windows support. Kosmtik is a source-only install and doesn't have any windows builds. I'd love to see a mapnik 3 version of tilemill, but I don't know if that's likely to happen. Does anyone know if there are any forks or non-mapbox versions in development? If we assume Tilemill isn't an option, what will we suggest to developers and end-users that they use instead? Kosmtik is fine if you don't mind command-line parameters and doing everything in separate text editors but it's a huge step back for those who enjoy various features of Tilemill. |
Tilemill has been supporting Mapnik 3 already since October 2014, see https://github.com/mapbox/tilemill/commit/818826c3f32162dd4a337f9fcb1c8ca60d29ba1b. The only thing that needs to be done, as far as I know, is tagging a new release and perhaps compiling binaries. |
I wanted to note that it is anyway necessary with mapnik - but from what I see it is also fixed in an unreleased tilemill (https://github.com/mapbox/tilemill/issues/190)
And making ppa with packages. There is no tilemill package for Ubuntu 16 - and MapBox is not going to make one. So it makes TileMill source-only install in recent Ubuntu. |
Speaking as a TileMill user... Re TileMill vs Kosmtik, the documentation at https://github.com/kosmtik/kosmtik seems to have improved considerably since I last looked at it but it still isn't where the "TileMill Crash Course" is. It's that, rather than any reliance on an external editor (which you tend to have to use in TileMill anyway with any reasonable number of layers) or command line options (likely needed anyway for file extract processing) which is what will be most missed, but that I guess is "simply a matter of documentation" :) Re TileMill and Ubuntu 16; support for 14.04 LTS is good until 2019 or so, so it's not too immediate an issue. Windows support might be to some people (although I never could get TileMill on Windows working with a remote database on Linux, so it's not an issue for me). |
I think with a bit of effort it is possible to e.g. bring Kosmtik to npm and therefore decrease the effort when installing and using it. Also I think having regular releases is more a matter of policy than of anything missing in the software. |
Is the new Windows Subsystem for Linux that Microsoft unveiled, of any relevance here?: http://www.theverge.com/2016/3/30/11331014/microsoft-windows-linux-ubuntu-bash https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overview/ |
Tilemill has been pulled from Github: https://github.com/mapbox/tilemill/ is 404. |
No worry, it was just moved out of the Mapbox profile: https://www.mapbox.com/blog/fall-cleaning/ |
Superseded by more general #2458. |
Currently this style works both in Mapnik 2 and Mapnik 3.
But some rules that are available in Mapnik 3 are not present in Mapnik 2. Using them would cause Mapnik 2 renderers to fail.
How long we want to support Mapnik 2? Most likely at least untill openstreetmap/chef#39 is completed.
Note that stopping to support Mapnik 2 means that using current TileMill version to render the style will be impossible. Given that TileMill is officially abandoned by Mapbox it would require to either drop TileMill support or to fork TileMill to release a new version.
Kosmtik would continue to work fine.
At least some rules were renamed - for example to achieve on points/areas effect of
text-min-distance
in 2.3 it is necessary to usetext-margin
in 3.0. As result it is impossible to support 2.3, 3.0 and usetext-min-distance
/text-margin
effect at once.The text was updated successfully, but these errors were encountered: