Skip to content
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

Support Layout and Format nodes in text and shield symbolizers #62

Closed
wants to merge 2 commits into from

Conversation

hollinger
Copy link
Member

This is a potential addition, which corresponds with mapbox/carto#358. The goal is to support definition of layout and format nodes in carto, as discussed in mapbox/carto#347.

What is being added here is child element types (currently layout and format), along with their attributes, that can be defined inside of text and shield symbolizers in mapnik XML. Also added are css pseudo-elements that can be used to create and define these elements in carto. In mapnik, format and layout elements can be contained within text and shield symbolizers, and they can also be nested inside of each other. The child-elements lists are used to control which types of elements can go where.

Along with the proposed changes to carto compiler (mapbox/carto#358), this is designed to allow for expansion to other xml tags that can be defined inside of a symbolizer. In particular, a 'placement' element type could easily be added to define alternate placements for list placement mode (see #45 and mapbox/carto#238).

…nd shield symbolizers.

Properties are defined for child elements in the same format as symbolizer properties.
Each element contains data about one or more psuedo-elements that can be used to create the
element with carto css. An array is defined inside of each symbolizer and element that can
potentially contain child elements to specifiy which types of elements they support.
@springmeyer
Copy link
Member

on my radar to help review and land soon as part of Mapnik 3.x release.

@springmeyer springmeyer closed this Mar 5, 2016
@springmeyer springmeyer mentioned this pull request Mar 5, 2016
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants