<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">I've a feeling they've been in trouble
for this sort of thing before, in Germany, but can't find the news
article I've seen.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Their access claim link, intended more
for things like nature reserves, does sound like it goes to a
human:
<a class="moz-txt-link-freetext" href="https://support.komoot.com/hc/en-us/articles/360051245231-Filing-an-access-claim-on-komoot">https://support.komoot.com/hc/en-us/articles/360051245231-Filing-an-access-claim-on-komoot</a>
<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> I see from Twitter the Royal Parks
people have done that, so hopefully it will get somewhere.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I use Komoot, and can flag specific
ways/nodes if I know where they are, but I doubt that will get
very far. I filed an issue about a forbidden right turn last year
and it's still routing that way (to be fair, so are GraphHopper
and OSRM when set to cycling but not driving:
<a class="moz-txt-link-freetext" href="https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=51.58564%2C-3.00488%3B51.58870%2C-3.00006#map=17/51.58717/-3.00236">https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=51.58564%2C-3.00488%3B51.58870%2C-3.00006#map=17/51.58717/-3.00236</a>
)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Unfortunately I don't know anyone there
any more (and anyway they weren't on that side of things; AFAICT
all mapping stuff is handled from Germany)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">From a technical point of view of the
way they're misusing the data for (some of) the UK (how this would
relate to Scottish access laws is another matter) a bit of
education seems to be needed.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Chris<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 20/09/2021 20:22, SK53 wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAELijW8nThSEoGjmGk++24ROwDh0fjX40unPFc+d9zNUYU83Wg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>I just noticed someone posting on <a
href="https://twitter.com/carlmyhill/status/1440015626421116932"
moz-do-not-send="true">twitter</a> that Komoot was routing
cyclists along trails where cycling is forbidden in Richmond
Park (fine apparently £60). Apparently Komoot treats all
highway=track & highway=path as bicycle=yes by default.
Clearly this is inaccurate in most of the UK.</div>
<div><br>
</div>
<div>The issue has been known for some time, but increased usage
of Komoot may bring OSM in the UK into disrepute as they
typically say something <a
href="https://twitter.com/komoot/status/1439948701095583751"
moz-do-not-send="true">along the lines</a> of "we only take
data as it comes from OpenStreetMap". It is getting quite
common for landowners to either complain or remove private
paths & tracks from OSM. This can be due to inaccurate
mapping (a recent case was on the Thoresby Estate), but most
often is because people are using routers which do not account
for how things are mapped here.<br>
</div>
<div><br>
</div>
<div>I wonder if we can do anything to get Komoot to correct
this behaviour?</div>
<div><br>
</div>
<div>Jerry<br>
</div>
<div><br>
</div>
<div><br>
</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>
<p><br>
</p>
</body>
</html>