
<html>

  <head>

    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

  </head>

  <body>

    <div class="moz-cite-prefix">On 22/04/2022 14:30, Jez Nicholson

      wrote:<br>

    </div>

    <blockquote type="cite"

cite="mid:CALBgsija6GKxkQcB+Rq=bBN01Gm9zJ+3LNkZ8_FLzbQQ=cua7w@mail.gmail.com">

      <meta http-equiv="content-type" content="text/html; charset=UTF-8">

      <div dir="ltr"><a

href="https://config-web-standard.oscptiles.com/standard.json?token=3ccdd26ed2478c4c6557329522decf6e06a19a737929ca4d951e3cf2b19fba97d39e7432a989db83fd73f5f30e24ecfc8b012beb3c97bea5e03f4d85de5e7e42"

          moz-do-not-send="true">beb3c97bea5e03f4d85de5e7e42</a>

        <div id="gmail-:12f" class="gmail-Am gmail-aO9 gmail-Al editable

          gmail-LW-avf gmail-tS-tW gmail-tS-tY" aria-label="Message

          Body" role="textbox" aria-multiline="true" tabindex="1"

          style="min-height:85px" aria-controls=":15n">It is not

          possible for a developer (i.e. OS) to exclude private paths or

          style them differently....unless Mapbox include processing of

          access=private across their worldwide OSM extract.</div>

      </div>

    </blockquote>

    <p>If that is the case they could, of course, find a different map

      supplier.  However, other Mapbox customers do include

      "access=private" information in their maps (not always very

      effectively, but it is there).<br>

    </p>

    <p>Best Regards,</p>

    <p>Andy</p>

    <p><br>

    </p>

  </body>

</html>