User has been adding boundary data sourced from Google Maps

[seav]

User mbueza has been adding boundary relations and their changesets have the tags like source=https://www.google.com/maps/place/*.

Example changeset with a Google Maps source=* tag: https://www.openstreetmap.org/changeset/83426743

Changeset where I have commented to inform the user that using Google Maps is not allowed and so that the user can respond or acknowledge the problem: https://www.openstreetmap.org/changeset/83429816

[govvin]

Have you heard back from the contributor?

[seav]

No response.

[govvin]

We should line this up for a roll-back

[DP24PH]

ALERT | I have spotted an erratic changesets 92629649, 92627464, 92627381, 92609480, made by certain user oodiegoodie wherein the tag source=Google Street View have led me to issue the warning thru the changeset comment:

Unfortunately, for copyright reasons, any third-party sources (i.e. Google Street View) is strictly forbidden on OpenStreetMap, and only Mapillary, Maxar, other donated data are authorised sources for the OSM.
Kindly revert into previous version to avoid such copyright-related infringement cases, ...

Also, due to indiscriminate use of access=private tagging into highway=residential, the following warning message is hereby issued:

... cease and desist all access=private tagging into highway=* to avoid further navigation issues. Use access=private only on barrier=gate/lift_gate.

Take-down has been made by @DP24 via changeset 93046246 thru reverter_plugin/35556;JOSM/1.5 (17084 en). #Mapping101 ALERT will commence thru the next #Mapping101 Thursdays episode (29 October 2020), DP24 Radio (via Spotify, iTunes on immediate release). Likewise, if you need a complete copyright investigation report, kindly DM @DP24 thru FB Chatbot, IG, OSM.

[TagaSanPedroAko]

I've been looking at "oodiegoodie"'s latest edits, but I'm stuck with another unsaved major edit involving CAVITEX-C5.

@DP24PH FYI, access=private on nodes is a dated recommendation introduced by schadow1, no longer applicable as most routing apps can already route on roads with access=private. Access= on roads should be fine, BTW.

Instead of hijacking this thread, better create another ticket. This issue is on boundary info sourced from Google, not every instance where someone adds info from Google.

[DP24PH]

I got it, @TagaSanPedroAko. I'll create another #papercut_fix ticket in case there would be another user adding infringing info from Google Maps/Street View. But for now, this ticket will be focused on the boundary data.

CC: @seav @govvin