4 ms·
To also play devil's advocate, that could happen with a non-corporate mapper on the other side of the world, too. The solution, I think, would be a mandatory d
by jlarocco 6y ago
To also play devil's advocate, that could happen with a non-corporate mapper on the other side of the world, too.
The solution, I think, would be a mandatory date field specifying when the data was accurate, and only allowing updates with more recent data.
- MengerSponge 6y agoIt could happen, but it generally doesn't. That's the kind of thing that happens when someone is paid pennies per edit and given insufficient resources to guide those edits, which really only happens when someone points a hose of money at a contractor. I've long been a fan of a mandatory time field! Now to get Stack Overflow to implement it too :)
- ySteeK 6y agoThat, my friends, would be the first step for my dream to finally map historical data, like in the OHM, directly in the OSM without anyone feeling bothered by it.