<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
regarding JOSM the following would be interesting: <br>
<br>
* graphical visualization of object history<br>
JOSM currently provides a very simple and crude view on an objects
history. A graphical visualization would provide a more intuitive view <br>
on an objects history and the evolution of its key attributes on a
timeline:<br>
- the objects "weight", how it grew and shrinked in the past
(with respect to number of tags or number of children like nodes and
relation members)<br>
- the objects "churn", i.e. how often and when it was modified <br>
- the objects "ownership", i.e. who was editing the object <br>
A "watch list" for interesting objects (i.e. large relations) would
be interesting too.<br>
<br>
* user interface for reverting individual objects to a previous version<br>
* user interface for reverting a changeset (similar to what the perl
scripts currently do, but with a nice user interface) <br>
* next generation support for resolving conflicts:<br>
- classify conflicts according to "type of conflict" (state
conflict, tag conflict, position conflict, etc.)<br>
- classify conflicts according to "severity" <br>
- visualization and manipulation of these conflict classes <br>
- provide functionality to select and resolve batches of
conflicts with a certain type and a certain severity <br>
<br>
* detecting, visualizing and resolving "map anomalies"<br>
see <a href="http://josm.openstreetmap.de/ticket/4509#comment:12">http://josm.openstreetmap.de/ticket/4509#comment:12</a><br>
<br>
Regards<br>
Karl <br>
<br>
<br>
Am 10.03.2010 09:52, schrieb Graham Jones:
<blockquote
cite="mid:6c50fdc51003100052od8733tc95d31f28ba4ff0a@mail.gmail.com"
type="cite">Hi Folks,<br>
<br>
We have submitted an application for OSM to participate in this year's
Google Summer of Code, so next week the people from Google will be
reviewing the application and our project ideas list to chose which
organisations to include in the programme.<br>
<br>
Looking at the project ideas list (<a moz-do-not-send="true"
href="http://wiki.openstreetmap.org/wiki/GSoC_Project_Ideas_2010">http://wiki.openstreetmap.org/wiki/GSoC_Project_Ideas_2010</a>)
I am a bit surprised that there are no suggestions for student projects
on the 'core' OSM databases. The things I wondered are:<br>
<ul>
<li>Are there any areas for development of API version 0.7 that
could be turned into a project for someone to work on?</li>
<li>Would it be worth working on the XAPI server? We had trouble
last year with them being down, so I wondered if it would be worth
developing a more 'conventional' postgresql version of the server that
we could start-up easily if the others fail again? I started to look
at this at the time, but didn't get far because I got tied up in
regular expressions rather than writing a parser myself.....</li>
<li>Without wanting to re-open the acrimonious debate again, could
we turn development of the OSM web site into a project? (would have to
check the GSoC rules for this, because there might not be much 'code'
involved).</li>
<li>How about the main editors - JOSM and Potlatch - are there any
potential projects there?<br>
</li>
</ul>
Please give this a bit of thought, and add any ideas to the Wiki
page! If you don't have chance to do that, an email to me will do and
I will add it.<br>
<br>
Thanks<br>
<br>
<br>
Graham.<br>
<br>
-- <br>
Graham Jones<br>
Hartlepool, UK<br>
email: <a moz-do-not-send="true" href="mailto:grahamjones139@gmail.com">grahamjones139@gmail.com</a><br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
talk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstreetmap.org/listinfo/talk">http://lists.openstreetmap.org/listinfo/talk</a>
</pre>
</blockquote>
</body>
</html>