>From a validation point of view does it matter if the building is not
square? Is it acceptable to square a building even though we know this
will introduce an element of approximation or error.
John, just on this one point, I'm not sure this is true. The 'element of
approximation' is inherent
>One other thing is when I start with a new task, sometimes a lot of work
is already done but also sometimes very poorly, buildings not squared or
misplaced. I wonder, should I correct that or leave it for the validators?
Hi Henk. Yes, the idea is to ensure the square is in a finished state
Further to this, for those that aren't aware, there is this 'commit' on
github, which at least changes the wording of the message even though it
doesn't deal with the other issues raised:
https://github.com/hotosm/tasking-manager/commit/86f3c14f3c4593a9ac85c2ea3b50f6f807681cf2
There is also this
John,
I've raised this also. I think there are two issues here-- 1. the plethora
of emails being sent and whether this is annoying to some people, and 2.
the wording of the email does make it sound like it's from the validator
and doesn't make clear that it's automated, leading to
ke sortable columns
and maybe adding a column or two to the mapper list to indicate their
experience level.
Thank you again for your time Scott.
Respectfully,
blake
On Sun, Oct 22, 2017 at 3:14 AM, Scott Davies <mr.scott.dav...@gmail.com>
wrote:
> There's a lot I love about TM3, and
There's a lot I love about TM3, and hats off to those that put in the hard
work to make it happen.
There are a few teething issues, though. eg. Many projects in the new TM
are still open to anyone to validate, so it's necessary to check that newer
validators are doing a good job. But this is more
