[HOT] some issues about the HOT task manager
oliver.richters at uni-oldenburg.de
Tue Jun 9 16:20:05 UTC 2015
thanks for your information, Tyler Radford answered to my mail to
info at hotosm.org and suggested me to send my question to the mailing
While it is obviously true that its not a problem if people are mapping
the stuff outside the district, it may create confusion if some people
think it should not be mapped (because it may cause mapping conflicts
with other tasks where this district is included) and others do.
I have put tasks as ready because everything within the district was
mapped, but others opposed that. I would therefore prefer that you
simply state somewhere that one should also map outside the boundaries
of the district to have a policy for that.
Thanks for all your work!
Am Dienstag, den 09.06.2015, 16:13 +0000 schrieb Pierre Béland:
> Hi Oliver
> If you look at the Task Manager issues on Github, these various
> problems (ie polygon and comments) have been
> We have to work with these limits when we prepare a new task. If I use
> a polygon to define a new Job, I myself look at the squares once I
> published it. I usually indicate as completed the squares that are
> outside of the Imagery available.
> But for Nepal TM#1043, even if part of the box is outside the
> District, it does not create any problem to map if the Bing imagery is
> available. For this reason, we provide no instruction and let the
> contributors map it.
> De : Oliver Richters <oliver.richters at uni-oldenburg.de>
> À : hot at openstreetmap.org
> Envoyé le : Mardi 9 juin 2015 2h12
> Objet : [HOT] some issues about the HOT task manager
> Dear HOT activists,
> I have a question and a comment concerning the task manager:
> In the case of the Nepal mapping, the relevant area for a task is
> usually following administrative boundaries. Due to the process of
> setting the squares, the square at the borders usually contain lots of
> space from outside the task area. Should mappers map the square or only
> the marked area (blue)?
> Sometimes, because of splitting, it may happen that squares lie
> completely outside the area of the task. Map it or not?
> I don't care what policy you prefer, but it would be great to know!
> Second, one comment:
> It would be a big improvement if the comments and edit history did not
> vanish after splitting a task. If you receive a comment per private
> message and the task has been deleted although it was just split up,
> it's nearly impossible to find it.
> If you split a task, the new parts should inherit the data generated
> before and the old task should stay and link to the 4 new ones. Would
> help a lot...
> Taken the two things jointly: if you split a task and one of the squares
> lies outside the boundary and should not be mapped therefore, it should
> vanish at best.
> Thanks for all your work,
> Kind regards,
Theoretische Physik / Komplexe Systeme, ICBM
Carl von Ossietzky Universität Oldenburg
Tel: 0441 - 798-3505
More information about the HOT