OvertureMaps / OvertureMaps/data

Norwegian Microsoft ML Buildings - More harm than good?

Open
#458 1 comment 0 reactions 3 assignees View on GitHub

@atiannicelli is already working on this.

Since Jan 30, 2026.

buildings
Dominant language
Python
Stars
1.2k
Forks
47
Avg merge
3h 42m
Merged PRs (30d)
1

Description

Discussed in https://github.com/orgs/OvertureMaps/discussions/455

Originally posted by Johannes-Andersen January 27, 2026
Hey!

Has there been any analysis of false positives, and are there any benefits to using GlobalMLBuildingFootprints in Norway? Given that Norway is a coastal country, it seems like false positives around docks are even more prominent.

Also, based on a few random samples, the data appears to be from around 2015, which means many footprints refer to buildings that have since been demolished. Is newer data available? If not, I would have expected OSM editors to have mapped most buildings by that time making the data even less reliable.

I’d be interested to hear whether it’s worth keeping this dataset enabled. Flying around my local area in Rapid Editor and reviewing the ML building recommendations seems to yield very few valid suggestions. That said, this could be confirmation bias, and it might be more valuable in other parts of the country.

My main issue with the dataset is that there doesn’t seem to be a way to remove features or provide feedback so that bad, non-existent buildings get filtered out over time.

Boat as buildings - example 1. Screenshot 2026-01-27 at 10 55 10 Screenshot 2026-01-27 at 10 55 26
Boats as buildings - example 2. Screenshot 2026-01-27 at 10 52 43 Screenshot 2026-01-27 at 10 54 51
Out of date - example 3. Screenshot 2026-01-27 at 11 01 20 Screenshot 2026-01-27 at 11 01 12 Screenshot 2026-01-27 at 11 00 51

Thanks,
Johannes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.