[OSM-dev] GSoc 2015 Queries

[Serge Wroclawski]

On Wed, Mar 4, 2015 at 9:39 AM, Nikhil Ramesh <rnikhil.2014 at gmail.com> wrote:

> OSM Anomaly Detection

I've been asked about this serveral times. I have to figure out how to
add a more full description about this project to GSoC, but here's the
description I've written about this one:


As OSM grows in contributors and prominence, we have a larger number
of edits which need to be detected and acted on, such as vandalism,
new user error and imports/mechanical edits which have not been vetted
by the community. In order to help address these issues, I've begun
working on an anomaly detection engine for OSM. The frontend uses
Javascript but the backend can use /virtually/ any technology, so I'm
open to alternate languages, though I'd give preference to languages
that I know well, such as Python, Javascript, Ruby, Perl or Clojure.
If you can make a strong case for another (such as Julia) I'd be open to
discussing it.

The requirements for this student project wanting to work on the
frontend would be very strong experience in Javascript, HTML and CSS,
and Javascript (node.js) for the server. For the backend (ie the
anomaly detection itself), the requirements would include a lot of
experience editing OpenStreetMap, as well as experience analysing
OpenStreetMap edits. You would need to be able to demonstrate a deep
knowledge of what kinds of edits would and would not be acceptable in
OSM, as well as demonstrable experience that you yourself have edited
OSM over time and can measure the quality of your own and others'
edits.



Note that this is different from the moderation queue, which has
different language and experience requirements.

- Serge