<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Adam, thank you</p>
    <p>Anderton and Adlington parishes are next to each other on the
      ground - a good example of read across error which needs to be
      avoided.</p>
    <p>Euxton Parish Council have published a recent LCC notice on their
      website - <a class="moz-txt-link-freetext" href="http://www.euxtoncouncil.org.uk/news.php?id=83">http://www.euxtoncouncil.org.uk/news.php?id=83</a></p>
    <p>which refers to PUBLIC FOOTPATHS EUXTON 37 & 38, CHORLEY
      BOROUGH .</p>
    <p>Separately on Chorley Borough Council website, a modification
      order
<a class="moz-txt-link-freetext" href="https://democracy.chorley.gov.uk/ecSDDisplay.aspx?NAME=SD2280&ID=2280&RPID=6590173">https://democracy.chorley.gov.uk/ecSDDisplay.aspx?NAME=SD2280&ID=2280&RPID=6590173</a>
      refers</p>
    <p><span style="left: 106.452px; top: 642.073px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.831416);">Add </span><span
        style="left: 152.446px; top: 642.441px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.607242);">to </span><span style="left: 178.834px; top:
        642.652px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.761622);">the </span><span
        style="left: 218.568px; top: 642.97px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.668821);">Definitive </span><span style="left:
        290.901px; top: 643.549px; font-size: 20.0006px; font-family:
        monospace; transform: rotate(0.458356deg) scaleX(0.849927);">Statement
      </span><span style="left: 386.122px; top: 644.31px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.711223);">for </span><span
        style="left: 416.649px; top: 644.955px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.825226);">Croston </span><span style="left: 491.451px;
        top: 645.553px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.697106);">the </span><span
        style="left: 530.033px; top: 645.862px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.715023);">following:</span></p>
    <p><span style="left: 104.712px; top: 685.662px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.744024);">Restricted </span><span
        style="left: 211.724px; top: 686.518px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.971731);">Byway </span><span style="left: 276.409px;
        top: 687.035px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.795164);">26 </span><span
        style="left: 311.145px; top: 687.313px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.851927);">from </span><span style="left: 353.475px;
        top: 687.652px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.751969);">a </span><span
        style="left: 377.864px; top: 687.847px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.659321);">junction </span><span style="left:
        450.709px; top: 688.43px; font-size: 20.0006px; font-family:
        monospace; transform: rotate(0.458356deg) scaleX(0.707023);">with
      </span><span style="left: 493.762px; top: 689.174px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.92983);">Back </span><span
        style="left: 546.25px; top: 689.594px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.841927);">Drinkhouse </span><span style="left:
        654.49px; top: 690.46px; font-size: 20.0006px; font-family:
        monospace; transform: rotate(0.458356deg) scaleX(0.92693);">Lane
      </span><span style="left: 706.217px; top: 690.874px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.651271);">at </span><span
        style="left: 732.447px; top: 691.084px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(1.15804);">SD </span><span style="left: 762.154px; top:
        691.721px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.985732);">4853 </span><span
        style="left: 813.169px; top: 692.13px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.94103);">1838</span><span style="left: 106.636px; top:
        712.079px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.782025);"> running </span><span
        style="left: 177.221px; top: 712.644px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.571685);">in </span><span style="left: 199.508px; top:
        712.822px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.759145);">an </span><span
        style="left: 231.998px; top: 713.082px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.795625);">approximately </span><span style="left:
        353.404px; top: 714.053px; font-size: 20.0006px; font-family:
        monospace; transform: rotate(0.458356deg) scaleX(0.739424);">easterly
      </span><span style="left: 428.961px; top: 715.058px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.692222);">direction </span><span
        style="left: 509.104px; top: 715.699px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.814026);">along </span><span style="left: 562.997px;
        top: 716.13px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.741181);">an </span><span
        style="left: 595.488px; top: 716.39px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.823626);">enclosed </span><span style="left:
        673.399px; top: 717.013px; font-size: 20.0006px; font-family:
        monospace; transform: rotate(0.458356deg) scaleX(0.731223);">track
      </span><span style="left: 720.964px; top: 717.794px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.645391);">to </span><span
        style="left: 748.029px; top: 718.01px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.744968);">pass </span><span style="left: 800.427px;
        top: 718.429px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.799826);">through </span><span
        style="left: 106.768px; top: 738.482px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.725723);">bollards </span><span style="left:
        182.576px; top: 739.088px; font-size: 20.0006px; font-family:
        monospace; transform: rotate(0.458356deg) scaleX(0.628863);">at
      </span><span style="left: 209.497px; top: 739.304px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.926419);">SD </span><span
        style="left: 251.847px; top: 739.642px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.970531);">4854 </span><span style="left: 290.768px;
        top: 740.354px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.93193);">1838 </span><span
        style="left: 340.359px; top: 740.35px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.92803);">and </span><span style="left: 380.763px; top:
        741.074px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.757724);">continuing </span><span
        style="left: 477.556px; top: 741.848px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.654512);">to </span><span style="left: 504.621px; top:
        742.065px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.778425);">terminate </span><span
        style="left: 591.373px; top: 742.759px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.62965);">at </span><span style="left: 618.294px; top:
        742.974px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(1.15804);">SD </span><span
        style="left: 646.55px; top: 743.6px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.975331);">4859 </span><span style="left: 697.928px;
        top: 744.011px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.95023);">1838 </span><span
        style="left: 748.191px; top: 744.413px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.63627);">at </span><span style="left: 774.421px; top:
        744.623px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.678841);">a </span><span
        style="left: 797.835px; top: 744.81px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.718123);">junction</span><span style="left: 106.478px;
        top: 764.481px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.67905);"> with </span><span
        style="left: 148.898px; top: 764.82px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.845327);">Drinkhouse </span><span style="left:
        254.81px; top: 765.668px; font-size: 20.0006px; font-family:
        monospace; transform: rotate(0.458356deg) scaleX(0.94913);">Road
      </span><span style="left: 307.698px; top: 766.091px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.872928);">between </span><span
        style="left: 388.623px; top: 767.138px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.743624);">properties </span><span style="left:
        483.21px; top: 767.895px; font-size: 20.0006px; font-family:
        monospace; transform: rotate(0.458356deg) scaleX(0.771321);">17
      </span><span style="left: 519.43px; top: 768.185px; font-size:
        20.0006px; font-family: monospace; transform:
        rotate(0.458356deg) scaleX(0.904829);">and </span><span
        style="left: 550.502px; top: 768.833px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.959131);">19 </span><span style="left: 578.83px; top:
        768.66px; font-size: 20.0006px; font-family: monospace;
        transform: rotate(0.458356deg) scaleX(0.831727);">Drinkhouse </span><span
        style="left: 685.24px; top: 769.911px; font-size: 20.0006px;
        font-family: monospace; transform: rotate(0.458356deg)
        scaleX(0.909729);">Road.</span></p>
    <div class="moz-cite-prefix">It seems clear that LCC have no formal
      nomenclature reference rules, so the method described by you and
      your reasoning is that which we in Lancashire should adopt.</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">I'd  like to see the data supplied to
      you made more widely available - as that public availability was
      part of my original question. I shall send to Rob the data I
      extracted from the data supplied.<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Regards <br>
    </div>
    <div class="moz-cite-prefix">Tony<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 26/11/2019 21:12, Adam Snape wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKw83WSN+QdXmK6MLOUAfOmMfj6+SbfBGLW7pXL8F09J3SvmyQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">
          <div>Hi,</div>
          <div><br>
          </div>
          <div><br>
          </div>
          <div>Firstly, Tony, I think 9-4 is Anderton and 9-1 is
            Adlington.<br>
          </div>
          <div><br>
          </div>
          <div>As part of the original FOI/EIR/Re-use request for the
            GIS dataset, I also requested (and was supplied) the
            council's scanned copies of the Definitive Statements along
            with permission to use them under the OGL. They appear to be
            complete as of when they were scanned (Early 2000s) but
            don't include any subsequent modification orders (like many
            councils Lancs don't frequently update the Map/Statement
            themselves, the documents have to be read in conjunction
            with any relevant modification orders)..  If Tony or anyone
            else is interested in the Statements I can send a download
            link. If anybody knows anywhere where they could be hosted
            to be publicly accessible in the long term then that would
            be great. With the statements the Council also supplied and
            OGL licensed scans of the county's surviving original parish
            survey cards which were used as part of the process for
            drawing up the draft definitive maps/statements. The same
            applies to these (though beware that these only cover a
            fraction of the County (the Rural Districts of Lancaster,
            Fylde, Wigan, West Lancs and Chorley).<br>
          </div>
          <div><br>
          </div>
          <div>The paper Definitive Maps and Statements for Lancashire
            don't go as far as naming the paths or supplying a
            definitive reference and as Robert suspected I've not seen
            any pre-digitisation records which use anything like 9-4-5.
            Parishes are not numbered on either the map or Statement.
            Paths are numbered individually and colour coded by status
            on the maps. The format varied over time but most of the
            statements are tabulated by (named) parish with column
            headings 'path number', 'kind of path', 'position',
            'length', 'any other particulars', there is no section for
            path name or reference, though where the statement for one
            path it refers to another path it is usually in the form of
            parish, path type, path number. <br>
          </div>
          <div><br>
          </div>
          <div dir="ltr">Whilst there is a pretty much de facto standard
            when discussing rights of way to use the format parish, path
            type (often abbreviated), path no., I'm really not sure we
            need to be overly bothered about the (perceived) formatting
            preference of each county (I've never heard of a coucnil
            actually having a preference on path referencing format). In
            this context differences in formatting don't change the
            meaning 'Rivington FP3' is synonymous with 'Rivington
            Footpath 3', is synonymous with 'Public Footpath Number 3 in
            the Parish of Rivington'. It is much more meaningful to have
            national consistency than to slavishly following what we
            imagine to be the formatting preference of each individual
            authority.<br>
            <div><br>
            </div>
          </div>
        </div>
        <div>Kind regards,</div>
        <div><br>
        </div>
        <div>Adam</div>
        <div><br>
        </div>
        <div>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Tue, 26 Nov 2019, 16:04
              Robert Whittaker (OSM lists), <<a
                href="mailto:robert.whittaker%2Bosm@gmail.com"
                target="_blank" moz-do-not-send="true">robert.whittaker+osm@gmail.com</a>>
              wrote:<br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">On Tue, 26 Nov 2019 at
              14:32, Dave F via Talk-GB<br>
              <<a href="mailto:talk-gb@openstreetmap.org"
                rel="noreferrer" target="_blank" moz-do-not-send="true">talk-gb@openstreetmap.org</a>>
              wrote:<br>
              ><br>
              > On 26/11/2019 12:01, Tony OSM wrote:<br>
              > >  to the preferred prow_ref format  Adlington FP
              5.<br>
              ><br>
              > As previous, this is not the preferred format. The
              format should be as<br>
              > supplied by the LA, the organisation which has the
              *authority* to name<br>
              > PROWs.<br>
              <br>
              My reading of the original post is that Tony is saying
              that the<br>
              Council themselves are inconsistent in how they refer to
              their PRoWs.<br>
              In which case, I think we should use the format that is
              most prevalent<br>
              on the underlying legal documents (i.e. the Definitive Map
              and<br>
              Statement) rather than any electronic working datasets
              that are<br>
              produced from these. The onilne map at<br>
              <a
href="https://www.lancashire.gov.uk/roads-parking-and-travel/public-rights-of-way/public-rights-of-way-map/"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true">https://www.lancashire.gov.uk/roads-parking-and-travel/public-rights-of-way/public-rights-of-way-map/</a><br>
              uses the "9-5-FP 23" style numbers, but probably doesn't
              have any<br>
              legal force. I can't find any actual Definitive Statements
              online for<br>
              Lancashire, but there are what seem to be some Definitive
              Map extracts<br>
              in their DMMO register at<br>
              <a
                href="http://www3.lancashire.gov.uk/corporate/dmmoview/"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true">http://www3.lancashire.gov.uk/corporate/dmmoview/</a>
              . These mostly look<br>
              to just use the "FP 34", "BW 45" numbers, without an
              explicit parish.<br>
              My guess would be that the parishes are named in the
              Definitive Map<br>
              and Statement, rather than using reference numbers (which
              are probably<br>
              an artefact of digitisation). So unless the council has
              officially<br>
              adopted the electronic version with the "9-5-FP 23" style
              numbers as<br>
              it's legal Definitive Map, we should be looking at
              accepting parish<br>
              names in the official reference numbers. The question then
              is how does<br>
              the council itself refer to the Rights of Way when using
              named<br>
              parishes rather than IDs. What is *their* preferred
              format?<br>
              <br>
              If we can agree on the appropriate prow_ref format to use
              in OSM, then<br>
              I can load the GIS data into my tool at<br>
              <a href="https://osm.mathmos.net/prow/progress/"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true">https://osm.mathmos.net/prow/progress/</a>
              and have it display the refs in<br>
              the agreed format. Tony, if you've got a CSV file that
              converts<br>
              between the ID numbers and named districts/parishes that
              you could<br>
              send me, that would be really helpful, whichever format we
              end up<br>
              agreeing to use in OSM. It will also automatically produce
              a table<br>
              like <a
                href="https://osm.mathmos.net/prow/progress/essex/parishes"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true">https://osm.mathmos.net/prow/progress/essex/parishes</a>
              with the<br>
              parish names and numbers for anyone to reference.<br>
              <br>
              Best wishes,<br>
              <br>
              Robert.<br>
              <br>
              -- <br>
              Robert Whittaker<br>
              <br>
              _______________________________________________<br>
              Talk-GB mailing list<br>
              <a href="mailto:Talk-GB@openstreetmap.org"
                rel="noreferrer" target="_blank" moz-do-not-send="true">Talk-GB@openstreetmap.org</a><br>
              <a href="https://lists.openstreetmap.org/listinfo/talk-gb"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk-gb</a><br>
            </blockquote>
          </div>
        </div>
      </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>