Closed govvin closed 5 years ago
Fixed - names removed in building features, in the following changesets:
A public comment was made in the latest changeset of the following editors, who actively contributed to these edits:
Suspicious accounts, discovered on 2019-01-21:
Another mapper, freebeer, left a comment on a changeset, and said that it should be reported to DWG for full redaction from the database.
Email sent to DWG, 23rd December.
Editing activities resumed today, and no feedback was received from comments left on their changesets or the direct messages sent to them.
Request database redaction of names removed from these changesets (by DWG):
Will request DWG for a temporary block, to get the editors' attention.
@maning posted this issue in talk-ph: https://lists.openstreetmap.org/pipermail/talk-ph/2019-January/006348.html
DWG has acted on this request, and has temporarily blocked their accounts:
Recently added names were again redacted by the DWG from the database.
An extended block was given to a user, for ignoring the requests for feedback, and by continuing to add personal information to recent edits:
DWG warned all users that ignoring this block will result in a permanent block for said users.
Block expired today, and continue to add personal and private data on the map. Also ignored the public changeset comments and direct messages sent to them.
Rolled-back most recent edits, removing personal and private information:
A new user with a similar editing pattern. I reverted the 2 chnagesets created so far.
A new user with a similar editing pattern. I reverted the 2 chnagesets created so far.
* https://www.openstreetmap.org/user/Edmichael/history#map=17/14.53798/121.10783
Good catch, Maning. I updated the overpass turbo query to include this uid.
Another user observed to be doing the same editing patterns in that same area: https://openstreetmap.org/user/MrSpade
Note.
After 4 weeks from our first attempt to get in touch, somebody from the group of accounts editing in the area responds to a direct message we sent them. Will update for details, as soon as we have any to share.
Response from user Marianne received last Friday, 22nd March.
New editing activities noticed 23rd March, and the following users
Their affected changesets has been rolled-back:
The user Marianne has been in touch over the weekend, and has explained that the mapping effort is being conducted by the barangay (village) registry department, to record information related to their issuance of "certificate of lot occupancy", and also to create public DRR maps, to inform the community about their local hazards and vulnerability.
They agreed to hold an online meeting to discuss the privacy-related issues they've had earlier, and is willing to work with the OSM community to ensure that they can comply with community guidelines.
Official contact has been made with the person responsible for initiating the mapping effort, Ms. Marianne Mores of Barangay Santa Ana, Taytay, Rizal. We were also able to get in touch with their Barangay Registry Division chief, Katherine Belano.
They agreed to have an online meeting on 27th March to discuss the issues identified by the community, and suggestions were offered to enable them to pursue the project without violating community guidelines on data privacy rights of the individuals, and other suggestions to improve the quality of the data they're adding, which they agreed to implement ASAP.
Among other things, they disclosed that this effort is related to their barangay's registry for issuing "Certificates of Land Occupancy", but the data will also be used to create community hazards and vulnerability maps in the future.
The editors who were adding data back in December were interns doing their OJT for the barangay.
They were encouraged to publish details about their project, as expected for organized editing activities under OSMF guidelines: Lupang Arenda Community Mapping wiki page.
We have been in close contact with the barangay staff in charge of the community mapping effort, and they are planning to meet with some advocates in June, to:
More details to be posted as soon as they've been finalized.
The activity is scheduled on July 7, unless it rains.
Original intent of this ticket is done. Moving to: https://github.com/OSMPH/papercut_fix/issues/54
Issue raised by Maning in Telegram.
I left a few changeset comments, but I'm fixing this now without waiting for a response from the editor.
For reference, the OSM policy regarding private information: Limitations on mapping private information
Major concerns about these edits:
Other concerns:
Overpass Turbo query
Overpass Turbo query for edits in the last 7 days in this particular area.
OsmCha filter
Who Did It