back

by riordan·13y ago·view on hn ↗
OSM's been pretty hardcore about their no import policy because of accuracy issues in validation. They want to map these places themselves and don't want to trust others for accuracy, let alone the legal issues that come with importing data (ugh).

We, however are far more lenient (mostly because we can't afford to build a time machine to map the past ourselves).

On the other hand, Mike Migurski's Green Means Go [1] project is fantastic for figuring out where batch imports into OSM will be greeted with confetti and parades for filling out parts of the US without enough coverage to warrant anti-import protectionism.

[1]: http://mike.teczno.com/notes/green-means-go.html

2 comments
The OSM opinion is not quite as black'n'white as that, though they did react badly to the TIGER import in the US (with good reasons), other areas have imported other types of data on quite large scales e.g. Danish addresses from government data.

http://wiki.openstreetmap.org/wiki/Import

But most of that's importing already digitised info. Relevant to this topic, vectorising from images, there seems to be renewed work on autotracing from satellite imagery coming to the iD editor:

http://www.mapbox.com/blog/user-friendly-guided-feature-extr...

edit: just noticed you linked to that elsewhere in this thread.

I am well aware, but there is a dedicated group of very advanced OSM users using JOSM, QGIS, and manual vetting of data, so it is a semi-automated import.

That being said, thank you for throwing this up for the uninitiated. Some of the emails to the OSM-main and OSM-US list were hilarious, like people populating entire country-worth datasets. Boy, did people yell at them.

http://wiki.openstreetmap.org/wiki/Washington_DC/DCGIS_impor...

http://wiki.openstreetmap.org/wiki/Import

http://lists.openstreetmap.org/pipermail/imports-us/