-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Op 12-07-10 07:25, Alan Mintz schreef: > 1. It's not ignored if users have to stumble over duplicate data when > editing and either reconcile (which should have been done by the > importing person) or ignore it.
Editor, software, issue. A good editor selectively filters out information, so that the user doesn't get an information overload (or worse: breaks other data) > 2. If the import uses existing tags (as did my example), it _does_ get > rendered. It is pretty trivial not to render anything from a specific user. That we currently don't do such thing doesn't mean we can't. > 3. Adding lots of junk data expands the database, costing performance > and real $$ with no benefit. Everything is slower with more data - > downloads, editing, backups, etc. Also, it increases the number and > complexity of chunks you have to chop areas into because of the object > limit in the API. All with no benefit. The complete API design of OpenStreetMap sucks scalability wise. Having arbitrary limits on the length of paths, or the amount of data we /can/ import won't solve that bottleneck. Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAkw6qggACgkQYH1+F2Rqwn0JxgCeOpbWMi2X02Gc/rXQQYqMbehD Zy8An3wycA1AO1MySag1JmBIJ48ujbCn =WLkl -----END PGP SIGNATURE----- _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
