[OSM-dev] ESRI article sent by a friend
Stefan de Konink
stefan at konink.de
Mon Jul 12 06:11:36 BST 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Op 12-07-10 06:57, Alan Mintz schreef:
> At 2010-07-10 14:55, John Smith wrote:
>> On 11 July 2010 07:32, Thomas Emge <temge at esri.com> wrote:
>> > ...
>> Some like to think there is 2 types of importing, implopping is where
>> people blindly upload data without checking what they are importing or
>> what already exists,
>
> ...which is unacceptable in any area or type of data for which there may
> be existing data in OSM. A good example was the import of the EPA
> superfund data, which was poorly geo-referenced, not discussed with
> other users, woefully incomplete (for some unknown reason), and
> duplicative of existing data. It was eventually reverted.
So why is this /so/ unacceptable? The renderer decides what to render.
If we end up in rendering only a specific subset of data, for example
from a list of users that we trust. Then any import is just ignored,
until something thinks its good enough to be used.
Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEAREKAAYFAkw6pAgACgkQYH1+F2Rqwn01UQCeMvtUUtxmsJ710PLXEMYtkRW1
R8wAoI5Zn3S8ndDsIoVYn7XxBG0DQG2V
=ukIX
-----END PGP SIGNATURE-----
More information about the dev
mailing list