<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23588">
<STYLE></STYLE>
</HEAD>
<BODY style="FONT-FAMILY: Verdana,Geneva,sans-serif; FONT-SIZE: 10pt"
bgColor=#ffffff>
<DIV><FONT face=Arial>Hi,</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I'm a relative newcomer to contributing to OSM but trying
to get to grips as quickly as possible with the consensus on various
topics, one of which is PROWs. The emails below raise questions I've had
for a while.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I'm hoping for guidance as p</FONT><FONT face=Arial>aths
can include these two types:</FONT></DIV>
<DIV><FONT face=Arial>1. Definitive PROWs (but subject
to subsequent Orders - whether deviations or extinguishments)</FONT></DIV>
<DIV><FONT face=Arial>2. De facto paths generally thought to be
PROWs.</FONT></DIV>
<DIV><FONT face=Arial>Most of the time the two are coincident.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Where they're not coincident, is it the case </FONT><FONT
face=Arial>that we should map the de facto paths?</FONT></DIV>
<DIV><FONT face=Arial>In such a situation should the de facto paths be
tagged as PROWs and/or given the highway authority's reference?</FONT></DIV>
<DIV><FONT face=Arial>Where there's a difference should we also map the
definitive PROWs in some way (even if they go through a private house - I'm not
making that up)?</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I realise there's an important but separate issue of
copyright if the route can be determined only from the definitive map (based on
the OS map).</FONT><FONT face=Arial></FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Regards,</FONT></DIV>
<DIV><FONT face=Arial>Rob</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>----- Original Message ----- </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=colin.smale@xs4all.nl href="mailto:colin.smale@xs4all.nl">Colin
Smale</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=talk-gb@openstreetmap.org
href="mailto:talk-gb@openstreetmap.org">talk-gb@openstreetmap.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, February 05, 2017 11:33
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Talk-GB] Footpath Open Data
is not always accurate.</DIV>
<DIV><BR></DIV>
<P>My understanding is that the definitive data held by the appropriate local
authority is exactly that, definitive. There may be legitimate errors in there
of course, but where a path has been willfully and legally rerouted, that is a
different type of error - lack of currency, i.e. an order has been made to
reroute the path but they haven't yet got round to updating the Definitive Map
and the Definitive Statement.</P>
<P>Any paths that no longer follow the official route (as per the DM/DS)
should not be tagged as PROW and probably as access=permissive unless they go
across otherwise public land. The official route is still a public right of
way, it's just no longer usable as such.</P>
<P>Do you have a way of feeding these discrepancies back to Somerset CC, to
establish whether they are true errors, lack of currency or illegal
reroutings?</P>
<P>http://www.ramblers.org.uk/advice/rights-of-way-law-in-england-and-wales/definitive-maps-explained.aspx</P>
<P>--colin</P>
<DIV> </DIV>
<P><BR></P>
<P>On 2017-02-05 11:19, Dave F wrote:</P>
<BLOCKQUOTE
style="BORDER-LEFT: #1010ff 2px solid; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-LEFT: 0.4em; PADDING-RIGHT: 0.4em; PADDING-TOP: 0px"
type="cite"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<DIV
style="PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; FONT-FAMILY: monospace; PADDING-TOP: 0px"
class=pre>Hi<BR><BR>If you're using local authority data/os open data to map
paths, as a contributor current is in Somerset, please don't assume their
layout corresponds with what's on the ground or is more accurate than what's
mapped in OSM. These official ways are often outdated, being based on
redundant features such as grubbed up fences & hedgerows. Gate &
stiles occasionally get moved. These tweaks often don't make it back to the
Definitive Map.<BR><BR><SPAN
style="WHITE-SPACE: nowrap">Please verify using this data doesn't make OSM less accurate.</SPAN><BR><BR>Cheers<BR>DaveF<BR><BR><SPAN
style="WHITE-SPACE: nowrap">---</SPAN><BR><SPAN
style="WHITE-SPACE: nowrap">This email has been checked for viruses by Avast antivirus software.</SPAN><BR><SPAN
style="WHITE-SPACE: nowrap"><A
href="https://www.avast.com/antivirus">https://www.avast.com/antivirus</A></SPAN><BR><BR><BR>_______________________________________________<BR><SPAN
style="WHITE-SPACE: nowrap">Talk-GB mailing list</SPAN><BR><SPAN
style="WHITE-SPACE: nowrap"><A
href="mailto:Talk-GB@openstreetmap.org">Talk-GB@openstreetmap.org</A></SPAN><BR><SPAN
style="WHITE-SPACE: nowrap"><A
href="https://lists.openstreetmap.org/listinfo/talk-gb">https://lists.openstreetmap.org/listinfo/talk-gb</A></SPAN></DIV></BLOCKQUOTE>
<P>
<HR>
<P></P>_______________________________________________<BR>Talk-GB mailing
list<BR>Talk-GB@openstreetmap.org<BR>https://lists.openstreetmap.org/listinfo/talk-gb<BR></BLOCKQUOTE>
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="https://www.avast.com/antivirus">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/antivirus">www.avast.com</a>
</p>
</td>
</tr>
</table>
<br />
</BODY></HTML>