<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
In Australia all property boundaries are not the centreline of the
road there is always a road reserve as Andrew pointed out. So
simple do not make boundaries the road.<br>
<br>
Likewise be very careful assuming the boundary is the centreline of
a river. eg the NSW Victoria border along the Murray River. If you
don't know it's actually the southern river bank.<br>
<br>
Realistically with these boundaries if you move them to align with
any physical feature then you are corrupting the data. Also if
you make the boundary part of a physical feature without checking
the full length of the boundary then you are corrupting the data
again.<br>
<br>
It's really much cleaner and easier to just import/trace the
boundary. If this shows up where a road/railway/whatever should be
then trace it from the imagery as a separate way and tag it
appropriately.<br>
<br>
Cheers<br>
Ross<br>
<br>
<br>
<div class="moz-cite-prefix">On 25/01/16 08:53, Ian Sergeant wrote:<br>
</div>
<blockquote
cite="mid:CALDa4YJjxGshNO0E1HLFd-L-j9ED0-HZDHeWCo=_72hiJupUnw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 25 January 2016 at 09:29, Andrew
Davidson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:u887@internode.on.net" target="_blank">u887@internode.on.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> The boundaries of the parks and forests are not
going to be roads as they consist of a number of
property lots that get declared for that purpose.
Property boundaries don't run down the middle of the
road, they'll be offset (at times the existing road
isn't within the road reserve anymore). Property
boundaries can be rivers (bank or thalweg depending) or
the MHWM (also known as the "coast" in OSM). <br>
<br>
</div>
</blockquote>
<div><br>
</div>
<div>If OSM was only a colouring-in exercise, then this
would be straightforward.</div>
<div><br>
</div>
<div>However, roads in OSM are a vector representation of
the road. And is is very common for the boundary of an
area to be the road itself, that is there is no small gap
between the area and the road.</div>
<div><br>
</div>
<div>When the boundary of an area *is* the road, then I
think it's entirely correct to include the ways that make
up the road in the multi-poly that defines the area. Even
though the vector nature of OSM slightly expands features
that are 2 dimensional when they are adjacent to features
that are 1 dimensional. The data is correct.</div>
<div><br>
</div>
<div>Of course, if the boundary isn't defined by the road,
but just happens to be close to it, then that's different.</div>
<div><br>
</div>
<div>Ian.</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Talk-au mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-au@openstreetmap.org">Talk-au@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-au">https://lists.openstreetmap.org/listinfo/talk-au</a>
</pre>
</blockquote>
<br>
</body>
</html>