[OSM-talk] Google Maps importing OSM data in Osage County without attribution

[Paul Johnson]

Followup to this, my changeset is
http://www.openstreetmap.org/browse/changeset/16315736 based on local
observation and the TIGER import.  pnorman in #osm-us discovered a Google
bot had made a similar change a month later on Mapmaker.


On Sat, Aug 3, 2013 at 6:51 PM, Paul Johnson <baloo at ursamundi.org> wrote:

> A few weeks ago, I converted "County Road XXXX" in (and in a few cases,
> immediately around) Osage County, Oklahoma, since these roads don't have a
> name, just a number, and as we all know, references are not names.  Didn't
> think much of it until, lo and behold, I look at a Google Maps mashup, and
> see a literally route-for-route identical conversion on Google Maps,
> including stray conversions in immediately adjacent counties.  Google is
> not attributing this data properly, and it's pretty glaring in both cases
> considering that I've only done Osage County and immediately adjacent stray
> routes like this so far, given that unlike most other counties in Oklahoma,
> there's no complicating letters in the route numbers that need to be
> handled.  How do we handle this situation?  Do we have a contact at Google
> in cases of potential plagiarism?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20130803/bf4ffe71/attachment.html>