You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the logical way to read the spec as it goes down the table and takes the first condition that is met, but it's not ideal since landuse=reservoir natural=water would have a kind of the generic water.
The text was updated successfully, but these errors were encountered:
Another example is the sites layer where there can be objects tagged with matching military and amenity tags. For this one it might make sense to have the object appear multiple times, or it might make sense to define a priority order.
The
water_polygons
layer contains a number of features with definitions that can overlap because they're coming from different OSM keys.As an example, something with
landuse=river natural=water
would meet the criteria for kind ofriver
and ofreservoir
.The osm2pgsql-themepark implementation is
This is the logical way to read the spec as it goes down the table and takes the first condition that is met, but it's not ideal since
landuse=reservoir natural=water
would have a kind of the genericwater
.The text was updated successfully, but these errors were encountered: