Open
Conversation
Also clarify wording
Query: does opacity allow expression?
Make name usage uniform
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Additions relating to PRs
mapnik/mapnik#4493
mapnik/mapnik#4132 (flagged as experimental since feature may be unstable)
mapnik/mapnik#4031
mapnik/mapnik#3782
mapnik/mapnik#3474 (only comp-op documented - CartoCSS won't support the nesting component)
There were some minor queries, e.g. it wasn't clear how
angled-pointmarkers would work with polygons, but I think this covers 90% of the documentation and the rest can be tweaked.There may be other PRs that change the rendering feature set that I have missed?
I haven't documented the geobuf data source (#3715).