<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.m-3794363965349521681hoenzb
{mso-style-name:m_-3794363965349521681hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="NO-BOK" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I would think that similar map changes (for example, only buildings) in a contiguous geographical region would be an «optimal»
mapping style for easy reviewing. It could be a “tip” in the iD tutorial.</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Michał Brzozowski [mailto:www.haxor@gmail.com]
<br>
<b>Sent:</b> onsdag 17. januar 2018 16.14<br>
<b>To:</b> Imre Samu <pella.samu@gmail.com>; talk@openstreetmap.org<br>
<b>Subject:</b> Re: [OSM-talk] How to teach novices about optimal changeset size?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Certainly I am not intending to change the community and require every mapper to comply. If you're an experienced mapper, you're fine.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I mean new users, who are not yet integrated with the community. Their work should be checked thoroughly (in Achavi, osmcha...). All novices make mistakes, after all. Better to give them good habits. By extension, smaller number of changeset
will lead to less recycling of same changeset comments.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I made this thread because I found it difficult to convey what is best practice in short form in changeset comments.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Maybe I should simplify things when explaining to them? No need to tell all the conventions, just what is a good start - but hoping it won't backfire ;)<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">17.01.2018 3:35 PM "Imre Samu" <<a href="mailto:pella.samu@gmail.com">pella.samu@gmail.com</a>> napisał(a):<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">> one changeset per building, repeated 20 times<o:p></o:p></p>
</div>
<p class="MsoNormal">my typical use case: House numbering on the street: push the numbers & forget & go to the next house ( <span style="font-family:"Arial",sans-serif;color:#222222;background:white">fast feedback loop vs. Delayed gratification )</span><br>
- sometimes the mobil app is crashing, and I don't want to go back 100m to re-enter - the last 5-10 numbers <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">> Obviously this makes them PITA to review quickly in Achavi or whatever tool you use.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
imho: it is easier to group the changeset on the reviewer side : by user + by hour ( group by user, hour ) than change the community. <span style="color:#888888"><br>
<br>
Imre<br>
<br>
<br>
<br>
</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">2018-01-17 15:13 GMT+01:00 Michał Brzozowski <<a href="mailto:www.haxor@gmail.com" target="_blank">www.haxor@gmail.com</a>>:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Certainly not:<o:p></o:p></p>
<div>
<p class="MsoNormal">- one changeset per building, repeated 20 times<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- one changeset for 3 POIs that are 1000 km apart in different countries<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">These are real world examples. In the latter Achavi can often refuse to run.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">That's also why I asked ;-) It's not that easy to formulate the answer what is reasonable to include in a changeset.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">Michał<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">17.01.2018 2:54 PM "Tobias Zwick" <<a href="mailto:osm@westnordost.de" target="_blank">osm@westnordost.de</a>> napisał(a):<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">So, what is the optimal changeset size, and why?<br>
<br>
Tobias<br>
<br>
On 17/01/2018 14:26, Michał Brzozowski wrote:<br>
> Many new users have a habit of e.g. sending one or few objects per<br>
> changeset, resulting in a dozen or even more changesets per day.<br>
> Obviously this makes them PITA to review quickly in Achavi or whatever<br>
> tool you use.<br>
><br>
> This habit is probably caused by non-knowledge of how auto-save works in<br>
> iD (which makes the work reasonably secure), as well as just not knowing<br>
> better thus forming their own judgement.<br>
><br>
> How should we teach about optimal changeset size? This is quite tricky -<br>
> how we would define it?<br>
><br>
> Can the iD nudge users towards better practice? (Linking to Good<br>
> changeset comments wiki page would be useful as well)<br>
><br>
> Michał<br>
><br>
><br>
> _______________________________________________<br>
> talk mailing list<br>
> <a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br>
> <a href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br>
><br>
<br>
<br>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>