-
Notifications
You must be signed in to change notification settings - Fork 27
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
[mapnik-3] mapnik-reference #118
Comments
Changes between 2.3.x and 3.xApi changes between v2.3 and v3.0 versions are summarized here. Below an exhaustive list of changes in mapnik-reference. Marked as
|
For the record: I've just found Notes for cartographers. |
Ready for CR in #119 |
About
Should we take care of it? or can we skip setting cc/ @rochoa |
I've been researching Playing with properties of
Both points are related with the differences that we can see in our test. But I've found one more using the simplest style to render text, i.e:
Both of them are slightly different, it seems that in Mapnik v3.x char-spacing is higher than v2.3.x. Not sure if we should mitigate those differences in order to be 100% backwards compatible or accept them and be aware of that. If I'm not mistaken, these changes are intended to improve text placement and so on. @rochoa, what do you think? |
Also we have different behaviours regarding Given the following style:
and query:
It should render 13 point with big ellipse markers, obviously they overlaps and some of them are hidden: The way to calculate which points are show/hidden is totally different. I've tried to dig into it, many things, such as mapnik/mapnik#1361, mapnik/mapnik#952, mapnik/mapnik#1754 seems to be related but I couldn't see the main reason of this change in the behaviour. By the way, setting |
Even though we all are aware of For this style:
and the given query:
The behaviour of how |
none
to-20037508.34, -20037508.34, 20037508.34, 20037508.34
true
tonone
true
tonone
true
tonone
true
tonone
true
tonone
local
toglobal
true
tonone
none
totext-spacing/2.0
true
tonone
#FFFFFF/white
torgb(128,128,128)/gray
PR: #119
The text was updated successfully, but these errors were encountered: