Re: [OSM-talk] Use of "Proprietary" imagery to edit OSM

2022-10-31 Thread Greg Troxel
Minh Nguyen writes: > For what it's worth, the argument about transparency would probably be > more effective if it were actually an upfront expectation that applies > to everyone. As it is, anyone could simply set source=survey or > local_knowledge on their changeset and call it a day. > >

Re: [OSM-talk] Use of "Proprietary" imagery to edit OSM

2022-10-30 Thread Brian M. Sperlongano
On Sun, Oct 30, 2022 at 9:00 PM Minh Nguyen wrote: > Vào lúc 07:11 2022-10-30, Greg Troxel đã viết: > > But then the company doing the editing should document which company's > > imagery and which revision year they are using. Things should be as > > transparent as possible, and this doesn't

Re: [OSM-talk] Use of "Proprietary" imagery to edit OSM

2022-10-30 Thread Minh Nguyen
Vào lúc 07:11 2022-10-30, Greg Troxel đã viết: But then the company doing the editing should document which company's imagery and which revision year they are using. Things should be as transparent as possible, and this doesn't feel that way. There was a recent subthread on this issue on the

Re: [OSM-talk] Use of "Proprietary" imagery to edit OSM

2022-10-30 Thread Greg Troxel
Darafei Praliaskouski via talk writes: > This is okay. You still have the access to the reality to check if the edit > matches the reality. > > The core reason why companies can't share the imagery is that satellite > imagery providers often put a seat license on the imagery, with "publicly >

Re: [OSM-talk] Use of "Proprietary" imagery to edit OSM

2022-10-29 Thread Darafei Praliaskouski via talk
This is okay. You still have the access to the reality to check if the edit matches the reality. The core reason why companies can't share the imagery is that satellite imagery providers often put a seat license on the imagery, with "publicly available" costing ten times as much as "this specific

Re: [OSM-talk] Use of "Proprietary" imagery to edit OSM

2022-10-29 Thread Simon Poole
Am 27.10.2022 um 06:17 schrieb Michael Collinson: and note that Bing imagery is provided to us on the same basis - for use in OSM but not otherwise. Mike Bing imagery is available for inspection to everybody, for use in OSM terms are relaxed that would otherwise prohibit tracing etc. Not

Re: [OSM-talk] Use of "Proprietary" imagery to edit OSM

2022-10-26 Thread Michael Collinson
and note that Bing imagery is provided to us on the same basis - for use in OSM but not otherwise. Mike On 2022-10-27 00:08, Clifford Snow wrote: On Wed, Oct 26, 2022 at 2:59 PM Mike Thompson wrote: Concerning this changeset: https://www.openstreetmap.org/changeset/128035436

Re: [OSM-talk] Use of "Proprietary" imagery to edit OSM

2022-10-26 Thread Clifford Snow
On Wed, Oct 26, 2022 at 2:59 PM Mike Thompson wrote: > Concerning this changeset: > https://www.openstreetmap.org/changeset/128035436 > > Changeset comment: > > added missing roads according to proprietary aerial imagery > > Editing organization's follow on comment: > "Proprietary" for Lyft

[OSM-talk] Use of "Proprietary" imagery to edit OSM

2022-10-26 Thread Mike Thompson
Concerning this changeset: https://www.openstreetmap.org/changeset/128035436 Changeset comment: added missing roads according to proprietary aerial imagery Editing organization's follow on comment: "Proprietary" for Lyft meaning "provided to us for use in OSM but not the general public" Is