ct: Re: [OSM-talk] [Talk-us] Redacting 75, 000 street names contributed by
user chdr
Hi,
On 08/27/2017 08:51 PM, Mikel Maron wrote:
> Also, Frederik, I think your script picked up false positives. Spot
> checked in DC, and these are expansions of both the street and the
> quadrant (&qu
Hi,
On 08/27/2017 08:51 PM, Mikel Maron wrote:
> Also, Frederik, I think your script picked up false positives. Spot
> checked in DC, and these are expansions of both the street and the
> quadrant ("St NW" -> "Street Northwest"(. Can we fix the script and
> regen the list?
I have modified my
On 28 August 2017 at 08:57, Warin <61sundow...@gmail.com> wrote:
> This is a data deletion - a very different thing.
Another editor in this discussion says that they:
changed the name tag to chdr_USA_AZ_name_fixup_required
That's not merely a deletion.
It behoves DWG to adhere to their
On 28 August 2017 at 01:56, john whelan wrote:
> It has been brought to the OSMF's attention. It has been verified that
> there are "Easter Eggs" from Google are in there.
"Easter Eggs"? Do you perhaps mean "trap streets":
https://en.wikipedia.org/wiki/Trap_street ?
On 2017-08-28 13:02, Christoph Hormann wrote:
On Monday 28 August 2017, Greg Morgan wrote:
We do get to go through the five stages. We do get to express the
emotions until acceptance of our fate as part of the healing process.
There is no rubber stamping!
The essential discussion here is -- OSM communities can put together plans
ahead of this redaction, in order to minimize impact to the map. With
sufficient legal process. This seems like a perfectly reasonable thing to plan
out, rather than doing a large scale revert and scrambling to clean up
On Monday 28 August 2017, Greg Morgan wrote:
> We do get to go through the five stages. We do get to express the
> emotions until acceptance of our fate as part of the healing process.
> There is no rubber stamping!
>
> https://en.wikipedia.org/wiki/K%C3%BCbler-Ross_model
You are free to
On Mon, Aug 28, 2017 at 1:39 AM, Christoph Hormann wrote:
> In fact reading this thread i cannot really believe this discussion is
> actually happening, that there seem to be people who think that a large
> scale unauthorized use of data can be 'healed' by rubber stamping it
>
On Mon, Aug 28, 2017 at 3:16 AM, James wrote:
> As Stewart has pointed out there are some changes that are valid(name
> expansion). I think Mr.Ramm needs to revise his selection algorithm before
> mass deletion
>
I don't think that it make a difference. I certainly don't
As Stewart has pointed out there are some changes that are valid(name
expansion). I think Mr.Ramm needs to revise his selection algorithm before
mass deletion
On Aug 28, 2017 6:05 AM, "joost schouppe" wrote:
2017-08-28 10:27 GMT+02:00 Simon Poole :
>
On Sun, Aug 27, 2017 at 11:51 AM, Mikel Maron wrote:
> > we can find a good workflow for that. I wasn't expecting the community
> to start working on this pre-redaction but if people prefer that to
> fixing issues later...
>
> Absolutely, let's do this!
>
>
On Sun, Aug 27,
2017-08-28 10:27 GMT+02:00 Simon Poole :
> What surprises me most about the discussion up to now that it is
> centered around the impact on the US and Canada were the removals are
> rather small both relatively and absolute*, actually are more at the
> nuisance level than anything
Hi,
On 08/28/2017 10:27 AM, Simon Poole wrote:
> Our concern should be more about Mexico, Brazil and other countries
> where it is at least not obvious to me if the local communities are
> aware of the issue and if we have any plan at all how we possibly could
> mitigate the impact. I know that
On Monday 28 August 2017, Paul Norman wrote:
>
> As the publisher of the OSM database, the OSMF has various legal
> obligations. When we become aware of data that has been illegally
> copied into OSM we need to stop distributing that data, generally by
> deleting it and redacting the old versions
What surprises me most about the discussion up to now that it is
centered around the impact on the US and Canada were the removals are
rather small both relatively and absolute*, actually are more at the
nuisance level than anything else, and can easily be added back, likely
in a couple of days
The guidelines were formulated for data additions. This should guard
against things being entered into the data base that are questionable.
This is a data deletion - a very different thing. In this case it is
required, ethically at least.
I have looks at some 6 in 'my area' and they all
>I haven't seen any compelling evidence or discussion about whether or not
the data in question was illegally copied into OSM. All we have to go on is
the first paragraph of Frederik's initial post. I'm not questioning
Frederik's (or any DWG members') passion or dedication to the project, but
we
On Sun, Aug 27, 2017 at 7:20 PM, Paul Norman wrote:
> On 8/27/2017 10:29 AM, Ian Dees wrote:
>
>>
>> I strongly disagree. As a group of people who have received
>> extra-judicial powers in the OSM community, they should be expected to
>> follow community guidelines to a higher
On 8/27/2017 10:29 AM, Ian Dees wrote:
I strongly disagree. As a group of people who have received
extra-judicial powers in the OSM community, they should be expected to
follow community guidelines to a higher degree than the rest of the
community.
As the publisher of the OSM database, the
John,
Once the way names are redacted, I will revise for Québec following the naming
rules different from the english part of Canada. ToDo / JOSM should help for
this.
regard
Pierre
john whelan wrote :
I suspect Jamie could wave a magic wand for Quebec.
The odbl=clean could be a way to exclude road names from the removal,
though sources from the info should be given, whether Canvec, Mapillary,
OpenStreetCam or local survey
On Aug 27, 2017 3:29 PM, "john whelan" wrote:
> There are a couple of issues here. The first are
On Sun, Aug 27, 2017 at 12:01 PM, Nicolás Alvarez wrote:
> I don't understand what people mean with 'verifying' objects. We're
> not trying to find factually-incorrect data. The data is legally
> tainted. It's questionable whether looking at the current names
>
There are a couple of issues here. The first are our users, we don't
normally think about them but deleting the names at the wrong point in
OSMAND's cycle could mean missing street names for a period of time.
Second is the problem of some data might be incorrect as a result of the
source
Friedl; Tod Fitch; talk...@openstreetmap.org
Subject: Re: [OSM-talk] [Talk-us] Redacting 75, 000 street names contributed by
user chdr
> we can find a good workflow for that. I wasn't expecting the community to
> start working on this pre-redaction but if people prefer that to fixing
&g
: Talk Openstreetmap; talk...@openstreetmap.org
Subject: Re: [OSM-talk] [Talk-us] Redacting 75, 000 street names contributed by
user chdr
I don't understand what people mean with 'verifying' objects. We're
not trying to find factually-incorrect data. The data is legally
tainted. It's questionable whether l
I don't understand what people mean with 'verifying' objects. We're
not trying to find factually-incorrect data. The data is legally
tainted. It's questionable whether looking at the current names
imported from GMaps, comparing to another source, seeing they match
and marking them as "verified"
> we can find a good workflow for that. I wasn't expecting the community to
>start working on this pre-redaction but if people prefer that to fixing issues
>later...
Absolutely, let's do this!
Also, Frederik, I think your script picked up false positives. Spot checked in
DC, and these are
On Sun, Aug 27, 2017 at 10:55 AM, Martijn van Exel wrote:
> Happy to help. All we'd need for MapRoulette is a list of locations and a
> proper description of the work we'd expect people to do. Anyone can create
> the challenge but I'd be happy to do it.
>
> Martijn
>
On Sun, Aug 27, 2017 at 10:29 AM, Ian Dees wrote:
>
>
> On Aug 27, 2017 11:58, "Yves" wrote:
>
> a écrit :
>
>
> Frederik,
>
>
> Thanks for notifying us about this. I hope that you treat this as an
> import or automated edit and follow
Frederik just answered Steve, but no message was received from Steve on the
talk list. Bad documentation of the thread and difficulty to follow discussions
coming from two lists, talk and talk-us. I then suggest that this thread be
only on talk.
>From the list that Frederik provided earlier
On Sun, Aug 27, 2017 at 6:49 AM, Frederik Ramm wrote:
>
> Here's a list of way IDs affected, with country and state:
>
> http://www.remote.org/frederik/tmp/chdr.details
>
>
Frederik,
I looked a small sample of the list. For example, way 10012342 [1] in Texas
was only touched
Steve:
thank you for your work. I'll save your list. It appears that others
might be eager to do the same, maybe we can find a good workflow for
that. I wasn't expecting the community to start working on this
pre-redaction but if people prefer that to fixing issues later, it is of
course an
On Aug 27, 2017 11:58, "Yves" wrote:
a écrit :
Frederik,
Thanks for notifying us about this. I hope that you treat this as an import
or automated edit and follow the rules you would expect to see the rest of
the community follow
Ian,
To lessen the
Hi Ian,
On 08/27/2017 06:23 PM, Ian Dees wrote:
> Thanks for notifying us about this. I hope that you treat this as an
> import or automated edit and follow the rules you would expect to see
> the rest of the community follow.
Sorry for not being clear about this. I posted this with my DWG hat
a écrit :
Frederik,
Thanks for notifying us about this. I hope that you treat this as an import or
automated edit and follow the rules you would expect to see the rest of the
community follow
Ian,
To lessen the burden of the DWG, I would say that this thread is
Indeed, with the geometry still remaining it will be easy to create a
maproulette task(s) to repair the damage
+1 for name tag redaction
On Aug 27, 2017 12:26 PM, "Ian Dees" wrote:
> Frederik,
>
> Thanks for notifying us about this. I hope that you treat this as an
> import
Frederik,
Thanks for notifying us about this. I hope that you treat this as an import
or automated edit and follow the rules you would expect to see the rest of
the community follow. Please post samples of your changes, make a wiki page
for posterity, and thanks for working to get buy-in from
37 matches
Mail list logo