<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>Hi Nathan</p>
<p>I've done some work on Chorley PROW's recently. Populated using
the style Chorley FP 1; Lancaster area uses the numbering
convention in MapThePaths eg 1-1 23. Fortunately I know the area
well having lived in the vicinity for 30 years so I can do
armchair mapping with some knowledge.<br>
</p>
<p>Robert Whittaker has responded to you and provided the link to
progress/lancs which I have been using - If find it very useful,
especially as it checks against format style of Chorley FP 1.<br>
</p>
<p>When I have found PROW which can't be walked I am making a note,
I have started a conversation with the PROW team at Lancs CC about
Chorley FP 1 and Chorley FP 9 which can't be walked because they
have build a road and bridge over them. On that particular section
I have not placed the PROW because the path does not exist and I
feel that a Definitive Map change is required. However Lancs CC
seem to be very reactive about map changes. I'm think that FIXME's
could be useful in the case where path can't be mapped to the
actual Definitive Line<br>
</p>
<p>I also find the
<a class="moz-txt-link-freetext" href="https://www.lancashire.gov.uk/roads-parking-and-travel/public-rights-of-way/public-rights-of-way-map/">https://www.lancashire.gov.uk/roads-parking-and-travel/public-rights-of-way/public-rights-of-way-map/</a>
to be useful to assist on defining the PROW, it maintains the path
reference in sight to help with reference changes particularly at
parish boundaries or path joins.<br>
</p>
<p>Where it goes through a building I would divert where
appropriate, add a FIXME and I would save the information to
contact Lancs CC so that the Definitive Map can be checked; as we
only have 6 years to get these things right I believe that Lancs
CC should be encouraged to do the right thing.</p>
<p>Regards</p>
<p>Tony Shield</p>
<p>TonyS999<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 04/05/2020 11:27, nathan case wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DB7PR01MB496686809858080F6F3B85CAD4A60@DB7PR01MB4966.eurprd01.prod.exchangelabs.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
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;}
/* List Definitions */
@list l0
{mso-list-id:170337796;
mso-list-type:hybrid;
mso-list-template-ids:-72719206 134807567 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m using the very helpful work Mapbox
tiles (from <span style="color:black">
Rob Nickerson’s email on 11 Nov 2019)</span> to map
Lancashire’s public rights of way (PROW) under the council’s
open data licence.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Generally, any existing paths already
marked on the map fit quite well with the vector files of the
PROWs. So if the already mapped route lies near enough to the
PROW line in the vector file, I leave the route as is and just
add the missing tags (e.g. designation and prow_ref).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">However;<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" type="1" start="1">
<li class="MsoListParagraph"
style="margin-left:0in;mso-list:l0 level1 lfo1">In cases
where the mapped route deviates substantially from the PROW
– should I keep the mapped route or edit to fit the PROW?<o:p></o:p></li>
</ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The mapped route could be an error (even
with GPS trails) as the original mapper may have taken the
incorrect route. Quite often this is the original mapper being
polite and walking around the edge of a farmer’s field even
when the PROW is straight through the field. Legally, the
route is through the field and not around it. Or it could be
that the way is not well signposted and the mapper has had to
guess the way (a big issue across Lancashire’s
moorlands/heathlands for the not so well trodden paths).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Equally, the mapped route could represent
the actual “on the ground” route i.e. the route shown by PROW
vector may be impassable. It’s also not guaranteed that the
vector files are correct (as they’re only copies from the
definitive map).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" type="1" start="2">
<li class="MsoListParagraph"
style="margin-left:0in;mso-list:l0 level1 lfo1">Where the
PROW goes through a building/object – should I map the route
as defined in the PROW, or re-route the PROW around the
object?<o:p></o:p></li>
</ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Unless there is an error in the PROW
vectors, the building shouldn’t be built on the PROW – though
it does seem to happen a lot, especially with farm buildings.
Obviously the path can no longer run through the building –
despite it’s legal status. When arm chair mapping (as is only
practical with such a large data set) should we instead show
the best alternative route? Or go with the legal route and
allow people following the route on the ground to find the
best route and edit in future?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for any insights!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-GB mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-GB@openstreetmap.org">Talk-GB@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-gb">https://lists.openstreetmap.org/listinfo/talk-gb</a>
</pre>
</blockquote>
</body>
</html>