[OSM-talk] Zero tolerance on imports

Frederik Ramm frederik at remote.org
Sun Mar 6 18:38:56 GMT 2011


Hi,

Fabio Alessandro Locati wrote:
> Have you considered that the goal of OSM is creating a free (as
> speach) map of the whole world... I think your view is not so close to
> the project goal..

It is certainly not the project goal to import every last scrap of free 
data no matter how irrelevant it is to editors. I think Russ is right; 
although I'd like to think maybe we don't need a "ClosedStreetMap.org" 
but just an easier way for people to add stuf from third-party sources 
to the maps they produce.

(The name ClosedStreetMap probably tripped you, Fabio; Russ didn't mean 
closed data, he meant data that is open but doesn't make sense to edit 
in OSM. And by almost any definition, data that cannot sensibly be 
edited by OSMers should not be in OSM.)

Bye
Frederik

> 
> 2011/3/6, Russ Nelson <nelson at crynwr.com>:
>> Peter Budny writes:
>>  > I find this discussion very distasteful.
>>
>> That's because nobody is talking about the REAL
>> solution. OpenStreetMap is the place for user-edited volunteered
>> geographic information. It's NOT the place for importing information
>> which would be nonsensical if a user edited it.
>>
>> The REAL solution is to have a ClosedStreetMap.org, which publishes
>> data in the same format under the same license using the same tag set
>> using the same API as OpenStreetMap, only it publishes read-only data.
>> Some of the imports that I've done (NYC bike racks, NYS DEC lands, and
>> NYS State Parks, which I'm currently working on), the data is
>> maintained elsewhere. It useful to have for OpenStreetMap users, but
>> not for OpenStreetMap editors. Why? Because for at least the last two,
>> the boundaries are off in the middle of sometimes very dense woods,
>> are not necessarily marked by signs, if signs are present they are not
>> authoritative, and the original source of the data is a legal
>> description, and no hand editing can change that.
>>
>> So take all these data sets, and their transformative programs, create
>> .osm files out of them, and throw them into a database. When you get
>> updates, rebuild the database.
>>
>> There's a few problems with the idea, e.g. what if somebody adds
>> something to OSM that's already in CSM? Or, what if the data, although
>> published from an authoritative source, is dirty? How does OSM
>> override data in CSM?
>>
>> But I think there are fewer problems than the current system of one
>> person dumping in megabytes for which there is no practical means of
>> updating with another import.
>>
>> --
>> --my blog is at    http://blog.russnelson.com
>> Crynwr supports open source software
>> 521 Pleasant Valley Rd. | +1 315-600-8815
>> Potsdam, NY 13676-3213  |     Sheepdog
>>
>> _______________________________________________
>> talk mailing list
>> talk at openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/talk
>>
> 

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"



More information about the talk mailing list