<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 14, 2013 at 1:09 AM, Kate Chapman <span dir="ltr"><<a href="mailto:kate@maploser.com" target="_blank">kate@maploser.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Pierre,<br>
<br>
I think it is a requirement to validate tiles. Yes we haven't figured<br>
out how to get people to do it, but I think that is an instructional<br>
issue. Perhaps if the validators were given access to a greater<br>
number of tiles to validate at a time. Maybe they could pick multiple<br>
tiles at once.<br></blockquote><div><br></div><div style>To me, currently, there's no real distinction between mappers and validators. Tiles may be validated by accident. And nobody is able to put them back to the flow.</div>
<div style>I prefer to simplify things till we have a validation process correctly figured.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Long-term I'd like to see the workflow so that you can define the<br>
steps a task goes through. Meaning I could say I want all squares to<br>
go through the following phases. Map the roads -> map the buildings -><br>
validate. Then another task could have a complete different set of<br>
phases. Map the residential areas -> map the water ways -> map the<br>
roads.<br></blockquote><div><br></div><div style>You think about a task-list for each tile, right?</div><div style>But you also think about phases. Does it mean that you imagine things to be done in given order?</div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
We haven't quite figured out the validation yet, but it is important.<br></blockquote><div><br></div><div style>I agree that it's important since we the data to be as qualitative as possible.</div><div style> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
-Kate<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Mon, Jan 14, 2013 at 4:30 AM, Pierre GIRAUD <<a href="mailto:pierre.giraud@gmail.com">pierre.giraud@gmail.com</a>> wrote:<br>
> Ok, I've gone further with my experimentations.<br>
> I'm really not satisfied with the validation workflow and I've tried to<br>
> change it completely.<br>
><br>
> I'm convinced that it's not really a requirement to be able to "validate"<br>
> tiles. It appears (looking at the statistics) that very few tiles have been<br>
> marked as valid in the past jobs. I suppose that's because validation itself<br>
> is not easy. It's easy to tell that a tile in invalid though. Thus, it's<br>
> really a requirement to be able to "invalidate" tiles.<br>
> In the version currently installed on dev server, the "validation" button<br>
> doesn't exist anymore. The tiles can now take only 2 statuses "done" or "not<br>
> done". Colors have been changed too. They're now more "common" to people's<br>
> habits and they match the buttons colors too.<br>
> Also, there's no need to lock a tile to tell it's invalidate. I think this<br>
> should be a quick process.<br>
><br>
> I intend to add a "message box". Users could for example receive messages<br>
> from the application to be informed that a tile they previously worked on<br>
> has been invalidated.<br>
><br>
> One other thing I changed is the "users tab". I simplified things by<br>
> removing the numbers telling how much the users worked. As someone already<br>
> told me, this is not a race. We don't need a winner.<br>
> What I added though is the availability to see which tiles the given users<br>
> worked on by highlighting them on the map. This feature has been asked<br>
> several times.<br>
><br>
> Once again, feedbacks are welcome.<br>
><br>
><br>
> On Sun, Jan 13, 2013 at 6:43 PM, Augustin Doury <<a href="mailto:augustin.doury@hotosm.org">augustin.doury@hotosm.org</a>><br>
> wrote:<br>
>><br>
>> Sorry for this second email, I just want to add something about this point<br>
>> of my last email :<br>
>><br>
>> 1) Limit how many times you could split the tasks, for a zoom level of 17,<br>
>> maybe not more than once.<br>
>> > sometimes tasks are splitted twice or more, it really slows the mapping.<br>
>><br>
>> On the "users" page,the number of tiles done by a contributor could depend<br>
>> on the size of the tiles he has done :<br>
>> - if he did not split tiles, show "1" for one tile<br>
>> - if he did, show "0,25" for one tile which is from a tile splitted once.<br>
>><br>
>> Augustin<br>
>><br>
>> On Sun, Jan 13, 2013 at 5:11 PM, Augustin Doury<br>
>> <<a href="mailto:augustin.doury@hotosm.org">augustin.doury@hotosm.org</a>> wrote:<br>
>>><br>
>>> Hi! Couple things I realized this morning using the Tasking Manager :<br>
>>><br>
>>> 1) Limit how many times you could split the tasks, for a zoom level of<br>
>>> 17, maybe not more than once.<br>
>>> > sometimes tasks are splitted twice or more, it really slows the<br>
>>> > mapping.<br>
>>><br>
>>> 2) Make it easy to find which task you're working on,<br>
>>> In the current version all "current worked on" tasks are highlighted in<br>
>>> orange, maybe the task linked to your OSM account could be highlighted in an<br>
>>> other colour.<br>
>>><br>
>>> 3) It's too easy to delete a task, it could be great to add one step more<br>
>>> for security checking<br>
>>><br>
>>> Great to imagine how the new version will be!<br>
>>><br>
>>> Augustin<br>
>>><br>
>>><br>
>>> On Sat, Jan 12, 2013 at 9:39 PM, Augustin Doury<br>
>>> <<a href="mailto:augustin.doury@hotosm.org">augustin.doury@hotosm.org</a>> wrote:<br>
>>>><br>
>>>> Thanks for that Pierre! Here are some comments :<br>
>>>><br>
>>>> On Sat, Jan 12, 2013 at 8:18 PM, Pierre GIRAUD <<a href="mailto:pierre.giraud@gmail.com">pierre.giraud@gmail.com</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>><br>
>>>>> - with this in mind, tiles url (in the address bar) can be used to be<br>
>>>>> shared to someone else. This might be useful to use a tile as reference in a<br>
>>>>> discussion between mappers,<br>
>>>><br>
>>>><br>
>>>> > this is a real enhancement, especially with new mappers who want to<br>
>>>> > have their work checked or to share it easily. I would use it like every<br>
>>>> > week.<br>
>>>><br>
>>>>><br>
>>>>><br>
>>>>> - comments are now required when marking a task as done or<br>
>>>>> (in)validating one,<br>
>>>><br>
>>>><br>
>>>> > great, it could be good to have an informative message to explain what<br>
>>>> > kind of comment is expected,<br>
>>>> > maybe the person who create the job could choose this informative<br>
>>>> > message.<br>
>>>><br>
>>>>><br>
>>>>> - users have access to the tile change history.<br>
>>>><br>
>>>><br>
>>>> > this is a real enhancement too I think<br>
>>>><br>
>>>>><br>
>>>>><br>
>>>>> Please write down any problems you see and your good or bad feelings.<br>
>>>><br>
>>>><br>
>>>> Something that could be great on the Tasking Manager's "users" page :<br>
>>>><br>
>>>> By clicking on the OSMid of a contributor or a validator, be able to :<br>
>>>><br>
>>>> - know which tile he has edited<br>
>>>> - know which tile he has marked as "done"<br>
>>>> - which tile he has validated<br>
>>>> - and be able to select it easily and open it in "read-only" mode.<br>
>>>> Great for quality assurance with new mappers, and great to find which<br>
>>>> tile you have worked on yesterday.<br>
>>>><br>
>>>><br>
>>>>><br>
>>>>><br>
>>>>> Thanks.<br>
>>>>><br>
>>>>> Off topic question:<br>
>>>>> I'm not sure how important the locking is when an advanced user wants<br>
>>>>> to (in)validate the work done on a job.<br>
>>>>> How about allowing validation without any lock. Or maybe we should<br>
>>>>> rethink the validation process.<br>
>>>>> Any thoughts?<br>
>>>><br>
>>>><br>
>>>> > when a new register click on a task marked as done, he uses to<br>
>>>> > validate or invalidate it quickly and don't think to just click on<br>
>>>> > "unlock-it"...<br>
>>>> I think a new validation process could be great, let it open for<br>
>>>> everybody but be sure that all validators did it in an informed way and<br>
>>>> don't validate or invalidate a task by mistake.<br>
>>>><br>
>>>>><br>
>>>>><br>
>>>>> Pierre<br>
>>>>><br>
>>>>> [1] <a href="http://tasks-dev.hotosm.org" target="_blank">http://tasks-dev.hotosm.org</a><br>
>>>>><br>
>>>>> --<br>
>>>>> -------------------------------------------------------------<br>
>>>>> | Pierre GIRAUD<br>
>>>>> -------------------------------------------------------------<br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> HOT mailing list<br>
>>>>> <a href="mailto:HOT@openstreetmap.org">HOT@openstreetmap.org</a><br>
>>>>> <a href="http://lists.openstreetmap.org/listinfo/hot" target="_blank">http://lists.openstreetmap.org/listinfo/hot</a><br>
>>>>><br>
>>>><br>
>>>> --<br>
>>>> Augustin Doury<br>
>>>> Openstreetmap Senegal Community Mobilizer<br>
>>>> Humanitarian Openstreetmap Team (HOT)<br>
>>>> <a href="tel:%2B221773160902" value="+221773160902">+221773160902</a> begin_of_the_skype_highlighting <a href="tel:%2B221773160902" value="+221773160902">+221773160902</a><br>
>>>> end_of_the_skype_highlighting begin_of_the_skype_highlighting<br>
>>>> <a href="tel:%2B221773160902" value="+221773160902">+221773160902</a> end_of_the_skype_highlighting<br>
>>>> begin_of_the_skype_highlighting <a href="tel:%2B221773160902" value="+221773160902">+221773160902</a><br>
>>>> end_of_the_skype_highlighting<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Augustin Doury<br>
>>> Openstreetmap Senegal Community Mobilizer<br>
>>> Humanitarian Openstreetmap Team (HOT)<br>
>>> <a href="tel:%2B221773160902" value="+221773160902">+221773160902</a> begin_of_the_skype_highlighting <a href="tel:%2B221773160902" value="+221773160902">+221773160902</a><br>
>>> end_of_the_skype_highlighting begin_of_the_skype_highlighting<br>
>>> <a href="tel:%2B221773160902" value="+221773160902">+221773160902</a> end_of_the_skype_highlighting<br>
>>> begin_of_the_skype_highlighting <a href="tel:%2B221773160902" value="+221773160902">+221773160902</a><br>
>>> end_of_the_skype_highlighting<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Augustin Doury<br>
>> Openstreetmap Senegal Community Mobilizer<br>
>> Humanitarian Openstreetmap Team (HOT)<br>
>> <a href="tel:%2B221773160902" value="+221773160902">+221773160902</a><br>
><br>
><br>
><br>
><br>
> --<br>
> -------------------------------------------------------------<br>
> | Pierre GIRAUD<br>
> -------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> HOT mailing list<br>
> <a href="mailto:HOT@openstreetmap.org">HOT@openstreetmap.org</a><br>
> <a href="http://lists.openstreetmap.org/listinfo/hot" target="_blank">http://lists.openstreetmap.org/listinfo/hot</a><br>
><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>-------------------------------------------------------------<br> | Pierre GIRAUD<br>-------------------------------------------------------------
</div></div>