<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
I agree that smaller squares are generally a better idea -
something that an experienced mapper will finish in 10 minutes
will generally take a whole mapathon for someone new.<br>
<br>
But - couple of notes of caution;<br>
<br>
Highways & other longer features. For a straight road, you
place a node at each end of the straight & then at intervals
around the curve. If your two nodes of the straight section are
each outside your square then nothing is downloaded when you
download via the Tasking Manager. When you are mapping your square
you look at part of a highway going through it, wonder why it
hasn't been mapped, and add it in - you don't realise it has
already been mapped. This is far more likely to happen close to
the corner of a square where the distances are shorter. Also far
more likely to be a problem with smaller squares.<br>
<br>
landuse=residential boundaries. <br>
If your whole square is within a number of other squares which
each have the boundary going through it, but yours doesn't because
the boundary passes through the squares outside yours, you won't
realise & will put a landuse=residential boundary around the
buildings in your square. <br>
<br>
Anyone downloading a large area containing what were lots of small
squares has a lot of work to do deleting duplicate sections of
highway and concentric areas of landuse=residential.<br>
<br>
The most successful mapping projects that I have seen approach the
mapping of an area in a staged approach - preferably with local
mappers being heavily involved in the organisation & quality
control. The process is going to vary according to urgency, skills
of the team available, and the geography of the area, but roughly
speaking you could do with;<br>
1. The main roads, rivers & other larger features such as
railway lines being present - fairly big squares or no squares at
all,<br>
2. A project to add residential boundaries & realign any
features that need it (smaller squares) & when that is
finished & validated,<br>
3a. Project for tracing buildings (squares can be very small), -
if each of these projects is for a smaller district of a bigger
town, then - at the same time<br>
3b Ground surveys for adding names, districts, etc - if the 3a
projects were small enough & only released once the previous
one is finished then the surveys will be easier to plan.<br>
<br>
Although we can do a lot with 'remote tracing' we do need to work
with the teams on the ground, and take the advice of local
mappers.<br>
<br>
& to repeat myself - for remote mapping I think smaller
squares generally are a good idea.<br>
<br>
Regards<br>
<br>
Nick<br>
On 11/12/15 10:55, Andrew Patterson wrote:<br>
</div>
<blockquote
cite="mid:CAJLBann9isOBr_f3Zxk3gvjRLQsMqO1w6TjW9ZO+9kQEQgp3Fg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-size:small">Picking up on
Jim Smith's comments about splitting tiles, I agree with the
idea of splitting tiles where the task is for buildings only -
but if highways of any form are the target for the task, I
think splitting makes it less easy. I find that for full size
areas I often need to go into an adjacent tile to make sense
of a route I'm following. Sometimes what seems to be
reasonably tagged as secondary highway suddenly turns into
little more than a track as it approaches the boundary - and
then has to be followed further to understand what its status
might be</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">Andrew</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">Andrew Patterson<br>
<br>
The information contained in this e-mail and any<br>
files transmitted with it is confidential and intended for
the addressee only.</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
HOT mailing list
<a class="moz-txt-link-abbreviated" href="mailto:HOT@openstreetmap.org">HOT@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/hot">https://lists.openstreetmap.org/listinfo/hot</a>
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
<meta name="generator" content="LibreOffice 4.2.7.2 (Linux)">
<meta name="author" content="Nick Allen">
<meta name="created" content="20131122;15273900">
<meta name="changedby" content="Nick Allen">
<meta name="changed" content="20150203;104908497914746">
<meta name="CHANGEDBY" content="Nick Allen">
<meta name="CHANGEDBY" content="Nick Allen">
<meta name="CHANGEDBY" content="Nick Allen">
<meta name="CHANGEDBY" content="Nick Allen">
<style type="text/css">
<!--
@page { margin: 2cm }
p { margin-bottom: 0.21cm }
a:link { so-language: zxx }
-->
</style>
<p style="margin-bottom: 0cm">Nick</p>
<p style="margin-bottom: 0cm">
<meta name="CHANGEDBY" content="Nick Allen">
<font style="font-size: 8pt" size="1">Volunteer
'Tallguy' for
<a
href="https://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Team"><a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Team">https://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Team</a></a></font></p>
<p style="margin-bottom: 0cm"><a
href="http://www.openstreetmap.org/user/Tallguy"><font
style="font-size: 8pt" size="1"><a class="moz-txt-link-freetext" href="http://www.openstreetmap.org/user/Tallguy">http://www.openstreetmap.org/user/Tallguy</a></font></a></p>
</div>
</body>
</html>