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

Change generated polygon centroids label_placement to match vector tiles 1.0 #377

Closed
bcamper opened this issue Aug 4, 2016 · 5 comments
Closed
Assignees
Milestone

Comments

@bcamper
Copy link
Member

bcamper commented Aug 4, 2016

When we release Mapzen vector tiles 1.0, we should change our synthesized polygon centroid features (enabled with generate_label_centroids on GeoJSON/TopoJSON sources) to match the new terminology:

Instead of label_placement = yes, it is now label_placement = true.

@nvkelso
Copy link
Member

nvkelso commented Aug 4, 2016

👍

@dmvaldman
Copy link
Contributor

I can change this. Should we accept both true and "yes" for backwards compatibility with a depreciation warning thrown when "yes" is used? Or just peel the bandaid off all at once?

@bcamper
Copy link
Member Author

bcamper commented Aug 8, 2016

Hmm, accepting both for backwards compatibility would be nice, but it would require special handling since this feature works by just generating new feature properties that are then filtered (with the filter) like any other... so it would need special-case code :/

We can probably get away with deprecating since this feature is not in heavy use yet.

@nvkelso
Copy link
Member

nvkelso commented Aug 8, 2016

On Aug 8, 2016, at 07:49, Brett Camper [email protected] wrote:

Hmm, accepting both for backwards compatibility would be nice, but it would require special handling since this feature works by just generating new feature properties that are then filtered (with the filter) like any other... so it would need special-case code :/

We can probably get away with deprecating since this feature is not in heavy use yet.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@burritojustice
Copy link

fine to rip off the bandaid, just a couple of instances (that I know) of that are easily changed.

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

No branches or pull requests

5 participants