-
Notifications
You must be signed in to change notification settings - Fork 41
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
No way to compile to XML with latest Mapnik and Carto #277
Comments
Quick git bisect point to mapbox/carto@09cb77c |
BTW, workaround is to use carto 0.14.1 for now. |
Refactored to workaround mapbox/carto#20 |
@skorasaurus do you want to have a look at the refactor before I deploy? It's basically a refactor for better carto processing, but I've taken the opportunity to tackle a road issue that was here from the beginning: clashes between road casing of different colours. See some before/after: So now main paved road does not have casing anymore, while small roads and unpaved main roads still have (basically, casing creates those artifacts when casing have different colours). Also, the XML is now around 18k lines, while it was 227k before (yeah…). Oh, and also: I've switched to yml instead of mml. I'll add a script for the conversion for people still using Tilemill, but it's three lines of python or nodeJS I'll put in the README in the meantime ;) |
Yes I am very interested to do so, although I won't have be able to until
|
For reference
Old values were 227058 and 8.661s, both tests with carto 0.14.1 The reduced number of Mapnik rules should help rendering performance. |
@skorasaurus any feedback? :) (My question is: should I proceed with deploying :) ) |
not yet. I'm seeing a lot of POIs not being rendered, images forthcoming. |
Left is the online server, right is my local , compiled from 2d62518 |
You need to make sure to be using the same Mapnik version and metatile settings on both to have a valid comparison. This looks like it might be related to label clipping settings. How does it look when you display MT edges? |
I believe kosmtik master is requiring 3.4.7 (kosmtik/kosmtik@982de02) ; but my terminal reported
|
Kosmtik doesn't require mapnik, it requires node-mapnik which has its own version numbers. Can you compare the current style version and the old style version with both in Kosmtik? |
@skorasaurus about the missing POIs, are you sure your data is up to date? |
hmm... The data is from an extract just a week ago... I think it must be something on my end because I compared the online layout (to the left) with 21715c4 on the right and POIs are still missing in the right. |
Just to confirm @yohanboniface - The problem is something on my end and database. I don't know why but some data is not imported into my osm2pgsql database. I created an extract of senegal from the africa pbf The version of osm2pgsql that I have been using is 0.85.0 (a deb built at https://launchpad.net/~kakrueger/+archive/ubuntu/openstreetmap?field.series_filter=trusty ) |
@yohanboniface |
Great news! I'll update the server as soon as I am back to Paris (this week) :) |
Deployed :) |
\o/ |
Certainly linked to mapbox/carto#20
So we need to try to narrow the "guilty" changes in the mapnik/carto stack, and possibility workaround mapbox/carto#20 in poi.mss and road.mss because this style anyway has a too much verbose XML
The text was updated successfully, but these errors were encountered: