Re:New York City mapped its trees and calculated each one’s ...
by adrianN on Friday December 02, 2016 @10:22AM
(#13089250)
I like to think of OSM as striving be as complete and as accurate as possible. So I believe every correct piece of data should be added.
[ Parent
| on HN ]
Re:New York City mapped its trees and calculated each one’s ...
by maxerickson on Friday December 02, 2016 @10:57AM
(#13089619)
Sure, but a hasty import of large amounts of data that no one is around to maintain it is at odds with accuracy.
Re:New York City mapped its trees and calculated each one’s ...
by toomuchtodo on Friday December 02, 2016 @11:15AM
(#13089789)
Which is why we should be encouraging government agencies to use OSM as the canonical reference.
Re:New York City mapped its trees and calculated each one’s ...
by maxerickson on Friday December 02, 2016 @11:52AM
(#13090183)
It's probably going to take more than encouragement.
Namely, changes to open records laws to make it okay to work on data sets that are not strictly public domain.
Re:New York City mapped its trees and calculated each one’s ...
by toomuchtodo on Friday December 02, 2016 @11:56AM
(#13090211)
Is not all map data in the US not in the public domain, being works by the government?
Re:New York City mapped its trees and calculated each one’s ...
by maxerickson on Friday December 02, 2016 @11:59AM
(#13090238)
The point is that a public employee subject to open records laws can't edit OSM because OSM isn't public domain.
Here's an example. The National Park Service can't treat OSM as their canonical data store:
https://www.nps.gov/npmap/blog/nps-plus-osm-equals-places-of...
People play blame-the-ODBL, but there's not really any epically strong arguments against adjusting the public records laws to be a little more flexible.
Re:New York City mapped its trees and calculated each one’s ...
by toomuchtodo on Friday December 02, 2016 @12:37PM
(#13090597)
Thank you for sharing this!