Netherlands - Fix Intersecting Buildings

ENG:
Hello OSM Netherlands,

Today I would like to share a MapRoulette challenge that purpose is to identify and correct cases where building polygons overlap, ensuring a cleaner and more accurate representation of the area’s layout.

How Tasks Were Created: TomTom has generated these tasks by analyzing building data in OSM. Each task highlights a potential intersection between buildings.

Important Note: Some tasks may be false positives, meaning the buildings aren’t actually intersecting in a problematic way. If you come across a task like this, please mark it as “Not an Issue.”

You can find the challenge here: Netherlands - Fix Intersecting Buildings

Please don’t hesitate to reach out to me with any comments, feedback, or remarks about this MapRoulette challenge. I want to ensure it meets the necessary standards, and I’m more than happy to answer any questions you may have.

Thank you,
Salim

Heb je je eigenlijk al eens verdiept in hoe de meeste gebouwen in Nederland op OpenStreetMap terecht komen?

2 Likes

@JeroenHoek.

ENG: Yes, the building data in OpenStreetMap comes from the BAG (Basisregistraties Adressen en Gebouwen - the Dutch Cadastre, Land Registry and Mapping Agency’s address and building register), a publicly licensed dataset containing address and building outlines for the entire Netherlands. Our spatial analysis revealed potential issues with this data. The community should be aware of these and correct or clean the map as needed. if you think is not needed then I can simply close/archive the challenge.

Which language do you want to use? (Which languages are you capable of using without automated translations?)

Dear Salim, I’d strongly recommend you to stop using literal translations to Dutch in your messages. Most Dutch members of the OpenStreetMap community understand and speak English just fine. Even if someone doesn’t understand English, they can always use a machine translator themselves. Furthermore, the Dutch translations are confusing, and more importantly, sound awkward and even embarrassing or condescending to native speakers.

2 Likes

Deze verdient zeker geen schoonheidsprijs:

De gemeenschap moet zich hiervan bewust zijn en de kaart waar nodig corrigeren of opschonen.

English it is then…

@sbaido Finding errors is good and well, but a quick glance at that challenge shows situations like this one:

Two sheds, side by side. Mathematically, they intersect. We can’t tell with our puny human eyes, but I’m sure the algorithm used detected this correctly. Now, if someone fixes this on OpenStreetMap, that ‘error’ is gone, but it will be reintroduced the next time someone uses the BAG importer tool. That means well-meaning mappers are just wasting their time on trivial non-bugs, and their work won’t even be retained.

That seems a bit problematic, don’t you agree?

Of course there are plenty of real overlap errors. Sometimes a building part is tagged as building=* instead of building:part=* and the overlap is real. I did see some examples of that in the challenge. Do you think you could reduce the challenge to buildings with a certain minimum amount of overlap and weed out all the tiny negligible cases? Buildings in the Netherlands on OpenStreetMap don’t have to match their BAG versions, but those that don’t (for a variety of reasons) are really a tiny minority of perhaps some 2 ‰ or so.

1 Like

already removed the NLD part

1 Like

Indeed are good points you raised, let me run it with the team and come back to you soon on this and maybe narrow the tasks to the real overlaps.

Even the English in this case to me sounds a bit condescending to a non-native English speaker.

1 Like

I suggested the same here last November and never got a reply. I hope you will hear from @sbaido sooner…

1 Like

@rhhs : working on it as we speak. I will come back to you on this, meanwhile I will hide the challenge till I am able to accommodate your request

1 Like