Skip to content

Conversation

@jonasmatthias
Copy link

closes #849

The effect of this PR is:

OSM before after
amenity=parking class: amenity
subclass: parking
class: parking
subclass: parking
shop=hairdresser class: shop
subclass: hairdresser
class: shop
subclass: hairdresser

The OpenMapTiles schema is very vague about what is a class:

If there is no more general class for the subclass this field will contain the same value as subclass

However, shop is listed as an example for the class and amenity is not.

The MapTiler OMT vector data uses hairdresser as class:

OSM tilemaker OMT before MapTiler OMT
amenity=parking class: amenity
subclass: parking
class: parking
subclass: parking
shop=hairdresser class: shop
subclass: hairdresser
class: hairdresser
subclass: hairdresser

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.

OMT schema: If there is no more general class for the subclass it should be the same value as subclass

1 participant