Is there a comprehensive list of map features that can/cannot intersect with buildings?

Background - I’m already working with public Estonian address dataset where I have set up a monthly script that updates changed addr:* tags for buildings. As a byproduct I get list of building footprints that are not in OSM. Some of these buildings have already been loaded to OSM through a manual conflation process with JOSM, in small chunks. But going forward, there should be an automatic process that takes building footprints and assesses whether they can be imported without manual conflation.

So, are there any validation rules that state with what kind of objects buildings cannot intersect with?

The naive solution would involve taking all ways/nodes around the building area and checking if they are inside the building or if they intersect. However, I am not satisfied with this approach since landuse/boundaries/power lines/leisure ways can intersect with buildings and POI/addr nodes can be located inside buildings.

The preferred method would be to identify a list of objects that buildings should not intersect with:

The obvious start would be from other buildings by using building tag.

Secondly, here’s a quote from wiki:

What will happen if building present in you dataset is already mapped as man_made=storage_tank without building tag?

It turns out the man_made tag has complex usage patterns. In most cases, it should not intersect with buildings, but there are exceptions. Here is a list of values where it can intersect: clearcut, cutline, quarry, wastewater_plant, water_works, works, embankment, courtyard.

highway tag - this is fortunately straightforward. Although highway=proposed is one exception.

barrier tag - I assume there shouldn’t be any exceptions with it?

natural tag - fairly complex tag. By default, it shouldn’t intersect, but with values like wood/scrub/wetland/grassland/coastline/sand/beach it can.

I assume this list isn’t complete - am I missing anything significant? Or are there better methods to validate whether a given building footprint might cause any issues with existing OSM data?

Other mandatory details when the word “import” is mentioned:

Source data quality - is already very high. In addition, I have additional methods to verify that I’m not importing non-existing buildings.
Licence - dataset licence is compatible with OSM.

3 posts - 2 participants

Read full topic

Ce sujet de discussion accompagne la publication sur