<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 11/16/2011 09:18 AM, Skye Book wrote:
<blockquote
cite="mid:85C732AC-4CF3-42E8-8C4C-FDCE5219720F@gmail.com"
type="cite">
<pre wrap="">I'm doing a ton of work with the data made available from the city as of late and a gripe from some people employed by the local government about OSM is that it isn't making full use of the data that the city is putting out there for consumption. Indeed, there is a ton of information that we can bringing into the dataset (streetlights, building outlines for the five boroughs, etc).
Anyone is interested in ganging up on this, or discussing the NYC data situation with researchers as well as GIS analysts would be most welcome. Any takers?
</pre>
</blockquote>
I wanted to import NYC water fountain locations, but determined the
license terms were completely inappropriate. It was a non-starter.<br>
<br>
I'm also leery of one-way imports, as the data starts to diverge. I
think the real power exists when crowdsourced corrections have a
chance of at least alerting the official agencies about bad data.
Osm as a conversation, rather than osm as a dumping ground, makes
sense.<br>
<br>
-Bryce<br>
<br>
<br>
PS: Check out "<a href="http://wiki.openstreetmap.org/wiki/Osmsync">osmsync</a>"
for a tool working in this direction. Osmsync is particularly good
for the rare situation where you have a frequently updated
authoritative data source. For example car sharing locations: there
are lots of them, and they change frequently. I use osmsync to
reconcile what is in osm with the car sharing reservation data.<br>
<br>
Each osm record is tagged with "source" and "source:pkey", so that
osm changes can be tracked back their original official record.<br>
</body>
</html>