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

Config update to take advantage of new boundaries code. #196

Merged
merged 2 commits into from
Sep 11, 2015

Conversation

zerebubuth
Copy link
Member

Depends on tilezen/TileStache#46.

Added example screenshot in parent #140.

@nvkelso could you review, please?

@nvkelso
Copy link
Member

nvkelso commented Sep 11, 2015

In keeping with the manta less layers, more stuff in the layers, I think these should end up in the same water layer they source from.

I'll have a separate comment about the kind transformations.

@zerebubuth
Copy link
Member Author

The new features stay in the water layer, since I removed the new_layer_name parameter. See tilezen/TileStache#46.

@nvkelso
Copy link
Member

nvkelso commented Sep 11, 2015

  • List of features matches those we test for in mz_calculate_is_water.
  • Result goes back into the water layer.
  • We add a new boundary=yes property.
  • Decision about kind property value substitutions.

@nvkelso nvkelso assigned zerebubuth and unassigned nvkelso Sep 11, 2015
zerebubuth added a commit that referenced this pull request Sep 11, 2015
Config update to take advantage of new boundaries code.
@zerebubuth zerebubuth merged commit 828c210 into master Sep 11, 2015
@zerebubuth zerebubuth deleted the 140-add-explicit-water-boundaries branch September 11, 2015 17:39
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.

None yet

2 participants