<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Thanks for the input on this. I have updated the text to include:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">“</span>When adding access tags to a highway that is also a PRoW you should only add the tags granted to that highway by the PRoW status – unless other access restrictions are verifiably known. In
our public footpath and service road example, the following is correct if we know nothing about any other access restrictions on the road:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">highway=service<o:p></o:p></p>
<p class="MsoNormal">foot=designated<o:p></o:p></p>
<p class="MsoNormal">designation=public_footpath<o:p></o:p></p>
<p class="MsoNormal">prow_ref=*<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You should not assume that access is or is not permitted by other transport modes. It may not even be possible to determine this from a ground survey. “<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Jon Pennycook <jon.pennycook@gmail.com>
<br>
<b>Sent:</b> Wednesday, January 6, 2021 4:04 PM<br>
<b>To:</b> talk-gb@openstreetmap.org<br>
<b>Subject:</b> Re: [Talk-GB] Public Rights of Way mapping guidance for Wiki<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hello Adam.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I agree. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jon<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, 6 Jan 2021, 15:55 Adam Snape, <<a href="mailto:adam.c.snape@gmail.com">adam.c.snape@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Hi,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In general it seems a good summary Nathan and a worthwhile effort.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">To add on to Jon's point. I'd also caution against the use of any negative access tagging where this is not clear on the ground. Definitive maps (etc.) are a positive list of rights which have been proven to exist. They purposely don't
rule out the existence of other access rights or other types of lawfully permitted access. Just because we know that, for example, a public footpath runs along a track, it doesn't mean we can safely tag bicycle=no, horse=no, access= no etc. from our armchair.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kind regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Adam<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, 6 Jan 2021, 15:41 Jon Pennycook, <<a href="mailto:jon.pennycook@gmail.com" target="_blank">jon.pennycook@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Hello Nathan.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">One thought around access - new editors often seem to misunderstand how access tags work. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Perhaps the page should perhaps encourage people to not put access=no/private plus foot=yes/designated on footways - it makes no sense. Also access=designated plus foot=yes on a track or service road which is a Public Footpath doesn't mean
what new people think it means (the foot part doesn't restrict the access part). Finally, avoid *=no if that mode of transport would be forbidden anyway for the particular highway type (I recently saw motor_vehicle=no on a new footway).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jon<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, 6 Jan 2021, 15:23 nathan case, <<a href="mailto:nathancase@outlook.com" target="_blank">nathancase@outlook.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hi all,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I recently did some updating to the UK Wiki PRoW page (<a href="https://wiki.openstreetmap.org/wiki/Access_provisions_in_the_United_Kingdom" target="_blank">https://wiki.openstreetmap.org/wiki/Access_provisions_in_the_United_Kingdom</a>)
and thought it might be useful to include (either on that page or a separate one) some guidance for mapping PRoWs.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Since I’ve started mapping PRoWs I’ve had a bunch of questions and I know there have been several threads on this list about this topic - so I thought it’d be good to collate that
information. I’ve made a first attempt at doing so. Before creating publishing this on the Wiki – I wanted to run by this list for input/suggestions (not sure if this is the best way – or if I should just create the Wiki page and have a discussion there?).<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Many thanks,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Nathan<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">----------<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Suggested text:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>Tips for mapping PRoWs</b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The best way to map a PRoW is undoubtedly to undertake a ground survey of a route and upload a GPS trace. By doing so, you can verify the route exists (e.g. checking for appropriate
signage), check its condition (and add appropriate [surface] or [trail_visibility] tags to the route), and add other items such as styles, bridges, and gates.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">When mapping PRoWs, it is important to note that any route listed in a local authority’s definitive statement, or shown on its definitive map, is by law a highway with guaranteed
legal access rights for specified users depending on its status. A highway, therefore, exists on a PRoW regardless of whether it can be seen on the ground or whether it is passable.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>PRoW runs along the same route as another highway</b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">In OSM, you should always map a highway by its highest classification. For example, if a public footpath shares its route with a service road you should map the service road and
add the appropriate designation tags to that road. Do not draw both a footway and a service road. If the two highways diverge, even for a relatively short distance, you should then map them separately.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>Impassable or blocked PRoWs</b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Some mappers may choose not to map paths that are impassable or for which there is no evidence of. Of course, this is fine. Equally, if you would still like to map this route you
can.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">By law, if a PRoW is blocked, you are permitted to take a reasonable diversion around the blockage. It is recommended therefore that you map the route with this diversion included.
However, you should split the way and omit the associated PRoW tags from this diverted part of the route. Additionally, you should add notes or other suitable tags to the route/blockage to indicate what the issue is.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Remember, blockages such as overgrown hedges or swampy ground may only be temporary/seasonal.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Especially for more permanent blockages, e.g. farm buildings or new fences, or old routes that likely haven’t been removed from the map in error (e.g. running through numerous houses
on an new-ish estate with no on-the-ground evidence), you may wish to also map the section of the PRoW that is not passable but use a suitable tagging scheme to indicate the path cannot be used. There is no consensus on how to do this but options include [highway=no],
[disused:highway=footway/ bridleway], or simply not adding the [highway] tag at all.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">It is highly recommended that you report any impassable or blocked routes to your local authority’s PRoW team, so that it can be investigated and hopefully resolved!<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Note: local authorities can issue temporary closures of PRoWs for safety reasons. In such cases, you may wish to simply not map this route until the closure is removed. If the route
is already on OSM, you can add temporary tags to indicate its closure.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>On-the-ground route differs from official route</b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Firstly, it is important to remember that digitalised versions of definitive maps, e.g. those on a local authority’s website or from PRoW data layers (see “Adding new PRoWs from
permitted sources”), are not legal records and may contain inaccuracies or be outdated. Only the definitive statement and map are legally enforceable.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">If you find that the “on-the-ground” route of a PRoW is different to that listed in the definitive statement or definitive map, there are two main options available. If the “on-the-ground”
route and the official PRoW route are close enough (though this is subjective), you may choose to map either route. If the two routes vary substantially, you may map both routes. But you must only add the PRoW tags to the official PRoW route. The “on-the-ground”
route would, by default, be a permissive path. It would also be beneficial to note this discrepancy on both ways.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>Adding new PRoWs from permitted sources</b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">If your local authority has provided a dataset of their PRoWs, with an OSM compatible licence, then you are permitted to add these to OSM (including both the route and prow_ref).
However, you must not use any restricted sources to help you add the routes to OSM – for example, you may not use copyrighted maps (such as OS maps) to help draw on the route in OSM. Additionally, you should not bulk import PRoWs as there are likely to be
conflicts with already present highways.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">One possible permitted option, but only if the local authority’s data licence allows, is to use a PRoW data layer (e.g.
<a href="https://lists.openstreetmap.org/pipermail/talk-gb/2019-November/023785.html" target="_blank">
https://lists.openstreetmap.org/pipermail/talk-gb/2019-November/023785.html</a>) in OSM to draw the PRoW route. You may need to use a permitted secondary source to add the prow_ref number. A good option for this is
<a href="https://osm.mathmos.net/prow/progress/" target="_blank">https://osm.mathmos.net/prow/progress/</a> which can also be used for identifying which paths are missing from OSM, or have other issues, in your local area.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Such “armchair” mapping is discouraged by some in the community, since you cannot add useful “on-the-ground” detail. Also, since you will be copying from digitised sources, the
accuracy cannot be guaranteed. But, so long as the data licence is permittable, you are perfectly allowed to do so. Indeed, OSM is an iterative effort. Your armchair mapped route may allow other users, who would not have known the path existed before, to explore
and improve the route in the future.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Talk-GB mailing list<br>
<a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-gb" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Talk-GB mailing list<br>
<a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-gb" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a><o:p></o:p></p>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>