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
Add support for cemetery tagged as grave_yard #1175
Conversation
Results evaluating commit 6cd7acc (merged with base 45d825e as 8933781). See run details. PostgreSQL DB size in MB: 2791 ⇒ 2790 (-0.0% change)
expand for details...
|
Thanks for PR! It looks great! Maybe one suggestion, idea. Would it be possible to move the |
@TomPohys great idea! I made the change. Then, in the future, if there are other types that need to be combined, they can all go into one place. |
Thanks a lot! |
Fixes #1057
This PR adds
amenity=grave_yard
to thelanduse
layer. A unification function was implemented which encodes allclass=grave_yard
asclass=cemetery
in the tiles, which adds these features for existing users ofclass=cemetery
with no change. The unification function can serve as a basis for any other tags that we might want to unify in thelanduse
layer.Tile rendering for an
amenity=grave_yard
. (Location)Tile rendering for a
landuse=cemetery
. (Location)