On Sunday 06 May 2018, Ilya Zverev wrote:
>
> I wonder, how did we in our pursuit of copyright purity came from "do
> not copy from google" to "do not even decide what not to map if there
> is a google tab in your browser"?
>
> It IS using GSV for making decisions. But not for taking any data.
>
06.05.2018 11:04, Andy Townsend пишет:
As you know, the imports validator is no editor. The data is supplied
by a third party along with a full permission to use the data. Any
input in the validator only restricts which features and their
attributes are NOT imported.
That's simply not true.
Giovanni,
The whole point of this discussion is that you SHOULDN'T be using Google
Streetview for validating such imports. If you can't go there yourself,
maybe add an OSM note. Although that doesn't really work very well either.
It takes months/years for such notes to get resolved.
You can use
That's fine. AFAIK italian fuel station dataset is very accurate and
updated. I will use GSV just for "skipping" the sporadic ambiguous cases.
2018-05-06 0:59 GMT+02:00 Martin Koppenhoefer :
>
> > On 6. May 2018, at 00:08, Cascafico Giovanni
> wrote:
On 06/05/2018 08:17, Ilya Zverev wrote:
I am well aware that none of you want to have any imports to OSM.
That simply isn't true. I've personally checked and added data as part
of your "Shell" import. The problems raised with that import and even
more so with this one have been all about
Of course I am no expert, nor part of the DWG but here are my 2 cents:
I think the ToS should be applied to the mapping process itself, not only
to the data product that is uploaded to OSM. So in this case even though
there are no derived products from GSV as in new POIs added to OSM or
changed
IANAL but the Google T’s are quite clear:
https://cloud.google.com/maps-platform/terms/
(b) No Creating Content From Google Maps Content. Customer will not create
content based on Google Maps Content, including tracing, digitizing, or
creating other datasets based on Google Maps Content.
Thank you DWG for tracking the state of the imports validator.
I am well aware that none of you want to have any imports to OSM. Even
when every point is manually checked against knowledge and photos. But
this issue is about licensing, and I want you to elaborate on that.
As you know, the
sent from a phone
> On 6. May 2018, at 00:08, Cascafico Giovanni wrote:
>
> Ie: to-be-imported dataset contains a fuel station which I can spot on Bing,
> but looks dismantled in newer SV imagery; I decide to "skip" it. Have I
> violated Google terms?
as long as you
Using streetview has been discussed recently on italian ML.
I brought to attention to the fact that SV information could be used for
*not* putting the node: is this a violation anyway?
Ie: to-be-imported dataset contains a fuel station which I can spot on
Bing, but looks dismantled in newer SV
Data for Iceland seems outdated. We are not willing to accept it.
On 5.5.2018 19:02, Cascafico Giovanni wrote:
"GSV" has been just enabled in audit webgui. Few hours ago wasn't there.
2018-05-05 20:06 GMT+02:00 Andy Townsend >:
On 05/05/2018
"GSV" has been just enabled in audit webgui. Few hours ago wasn't there.
2018-05-05 20:06 GMT+02:00 Andy Townsend :
> On 05/05/2018 18:56, Andy Mabbett wrote:
>
>> On 5 May 2018 at 18:34, Andy Townsend wrote:
>>
>> It has recently been brought to the DWG's
On 05/05/2018 18:56, Andy Mabbett wrote:
On 5 May 2018 at 18:34, Andy Townsend wrote:
It has recently been brought to the DWG's attention that the North American
part of this import (at the very least)
http://audit.osmz.ru/project/navads_fuel_na is using Google Street View
On 5 May 2018 at 18:34, Andy Townsend wrote:
> It has recently been brought to the DWG's attention that the North American
> part of this import (at the very least)
> http://audit.osmz.ru/project/navads_fuel_na is using Google Street View as a
> source (see screenshot at
>
On 28/03/2018 21:17, Ilya Zverev wrote:
Please take another look at the import.
It has recently been brought to the DWG's attention that the North
American part of this import (at the very least)
http://audit.osmz.ru/project/navads_fuel_na is using Google Street View
as a source (see
Hello Ilya,
thanks for the validation tool and the statistics you published at [1].
The Community has looked at 6% of petrol stations and found that the
failure rate is almost 15%. For professional data, I would expect a
value of significantly less than one percent. It is therefore
understandable
Hi Ilya,
Am 28.03.2018 um 22:17 schrieb Ilya Zverev:
> Thanks for you comments on the last iteration. I have also seen local
> discussions in french and german communities, with strong voices towards
> rejecting the import in their countries. So I ask you to consider the
> next iteration.
The
And now, my personal point of view:
If you can use your conflation tool with a larger area to remove most of
the duplicate fuel_station, I think it could be interested to have a
separate layer with only these nodes which we could manually review
before the import.
Stéphane
Hi Ilya,
I did expressed the opinion on this list that Imports or QA projects should be
split in smaller territories to let the communities monitor these changes.
Following discussions on the France and Germany since lists you have split the
imports for these areas. I dont think that this is
19 matches
Mail list logo