Ultimately, I need some kind of tagging to be in place to indicate that a road isn't runnable.  In the UK, there are any number of A roads in the countryside (I'm thinking like the north of Scotland here) where they're perfectly runnable.  Excluding trunk roads as a general rule is not a good one because it many places it excludes roads that are perfectly fine to run on (and I think of several in my area).  If pedestrians are not allowed on a road, a simple foot=no will cover the situation.  That's also why I'm encouraging people to tag shoulders and sidewalks as additional tagging that can be used to determine road "runability".

Lastly, there is one simple tag that would solve the issue for dual-carriageway A roads: expressway=yes.  This tag is well-used in the US for precisely this sort of situation, and can be used on the sort of road that really shouldn't be run on, even if it's technically legal.

Hello!  I try to check these forums regularly, but sometimes life gets in the way.  If you need to contact me more urgently, I can be found at the following Slack space:

Server: https://slack.openstreetmap.us/
Channel: #streetferret

For those having trouble subscribing -- it will not work if you're accessing StreetFerret on HTTP.

I've since updated the server settings, so it should always redirect you to the secure HTTPS side of the site!

https://streetferret.com

The access filters are set up by exclusion, so currently I exclude access=no,private,customers as well as foot=no,private,discouraged.

A reading of the OSM wiki for access=permissive seems like these should be OK?  Do you have a real-world example of access=discouraged where you couldn't run/jog/walk?

The issue is that there's no code in place to un-complete a street or part of a street once the system detects that it's been run.  I do this intentionally for performance reasons.  This causes a problem when a street is accidentally run, as I basically have to reset progress and re-process everything (or at least, that area).

I've got some code to reset a user's completion progress, but the request only comes up rarely, so I haven't had much opportunity to test it against live data.  It sounds like the activity data is "fixed" on the Strava side, and the way I can tell it works is if I can get your completion data in Andover to get reset.  This will give me an opportunity to go through that code and see what's missing.