

I tried researching this a bit and you are right that it’s not a Comaps-specific issue but more with the general OSM ecosystem.
It seems to be a chicken-and-egg situation in the sense that there are ways to tag temporary closures but they are not recommended for short-lived data because many apps use data offline and have long update cycles.
I’m referring to this bit in the page on key:construction
As OSM data is often used offline (and therefore may be several months old), only tag construction sites (particularly roads and railroads) if they are planned to be closed for at least six to nine months.
There is some work being done at Google Summer of Code 2025 to add road closures and more real-time events that might impact navigation. I’m looking forward to see if it pans out.



But it’s also actually a good point. There are a lot of namely European brands that have been outsourcing production out of Europe.
Should I boycott McDonald’s by not buying hamburgers made with (hopefully) meat that was sourced, prepared and cooked in Europe by local workers and then buy Prada bags manufactured in China?
With modern companies it’s so hard!
Right now I prefer to boycott McDonald’s more for the political message it sends than careful analysis of where the money flows: if enough people stop going to McDonald’s it’s easy to draw a line between “US administration starting trade wars” to “iconic US brands sales in Europe drop”, but it’s not like McDonald’s is inherently more evil than some big European brands.