Updates on July 28, 2025 (Release 1261)

Announcements
1

It’s been way too long since I’ve posted in this category, so I’m going to add two posts to get caught up - the previous one that went to the end of 2024 & this one to bring things up to date in 2025.

This isn’t a complete list of changes, since that would be way too much to write, but it should cover most of the impactful stuff that happened this year.
The dates listed are when I did the work, not when I released it … so those might not match your experience using the site.

:nerd_face: various infrastructure improvements/upgrades
added various entries to the In The News page
2025-07-28 :paintbrush: improve route arrow display
2025-07-25 reorder Overpass street query for performance
2025-07-25 allow highway=trunk only if also tagged foot=yes in Overpass street queries
2025-07-24 add sorting EVERYWHERE
2025-07-22 rework routes index page to a map view that allows displaying multiple routes
2025-07-21 add Challenges to the Supporter Features page
2025-07-17 add mid-route editing (click/drag to adjust the drawn route) to Route Builder
2025-07-16 add “x of y” to onboarding emails to help keep people from freaking out about email
2025-07-07 remove internal status page, the feature that made it possible is no longer available
2025-06-20 add activity resync feature where possible
2025-06-03 improve chart interactions (hover legend to highlight it, right axis for progress)
2025-06-02 add chart to city page
2025-05-27 add challenge stats to activity
2025-05-01 add buttons to activity page (that vertical three dot button must be invisible)
2025-04-06 fix Runkeeper dupe checking
2025-03-24 skip automatic city updates on weekends
2025-03-24 remove access=permit roads
2025-03-15 add collaborative map for those Challenges
2025-03-08 improve some tracking service logos in dark mode
2025-03-07 don’t show total lifetime count on challenge page
2025-03-04 also reprocess Challenges after city update
2025-03-03 add a retry system for Overpass (city updates)
2025-03-03 dynamic overpass server selection to distribute load
2025-02-24 add more running/walking types to Runkeeper
2025-02-12 update routes annotations
2025-02-11 include pagination at the bottom of all pages
2025-01-13 Node Hunter v2
2025-01-04 skip streets tagged area=yes

Some notes on the highway=trunk changes, since it has been questioned a couple times…

The addition of trunk roads was intentional - The Trouble with Trunk Roads - #22 by JamesChevalier - and it sounds like this is highlighting some OpenStreetMap tagging issues in various locations.

Ways in OSM tagged highway=trunk are only allowed into CityStrides if they are not also tagged foot=no … In Austria, Belgium, Denmark, France, Hungary, Slovakia, and Switzerland the rule is a little different due to their local handling of this tag - in those locations foot=yes is required.

That decision came from some research I did which led me to OSM tags for routing/Access restrictions - OpenStreetMap Wiki … That explains the worldwide default as well as per-country defaults & the UK default is foot=yes for highway=trunk

If you need any help with OSM edits, or want to request edits made for you, I’d suggest posting in Support > City/Street/Node Issues

7 Likes
2

After this update there’s a couple of areas/types that now have nodes which didn’t previously.

First one, shopping centre which requires paying for parking after 3 hours:

The roads in this area have the following tags in OSM:

fee=yes
fee:conditional=no @ (stay < 3 hours)

The second one is an old drive-in theatre that’s now used as a market on weekends:

This one has the following tags in OSM:

access=permissive
highway=pedestrian
area=yes

3

Thanks for the links!

It looks like one of the adjustments I made to the street query actually knocked out 5 filters instead of combing them. :person_facepalming: I’ll be able to get this updated later today. I’ll send that city in for a sync after I’m done.

That fix is released now & City of Knox is being synced again.

4

Thanks James, looks good now.
Appreciate the effort you put into this site, as a fellow programmer you do an amazing job. Even more so solo.

5

@JamesChevalier Will (can this) this include expressway=yes

2025-07-25 allow highway=trunk only if also tagged foot=yes in Overpass street queries

6

Yeah, expressway & motorroad are excluded

7

First of all many thanks for all you do for this website and developments. I was wondering why trunk roads are now included. This is now causing me quite a few issues with Birmingham, UK as the OSM didn’t specify pedestrian access “not specified” for major dual carriage ways without pavements but they are now appearing as incomplete. I am going through OSM to update these as pedestrian access as “no”. Could you check that the code does require a “yes” for pedestrian access please as this doesn’t seem to be the case. In an ideal world I would prefer trunk roads to be excluded as before as it seems like the rules of the game have changed mid game.

Many thanks

8

Yeah, the addition of trunk roads was intentional - The Trouble with Trunk Roads - #22 by JamesChevalier - and it sounds like there are some tagging issues in OpenStreetMap near you.

Ways in OSM tagged highway=trunk are only allowed into CityStrides if they are not also tagged foot=no … In Austria, Belgium, Denmark, France, Hungary, Slovakia, and Switzerland the rule is a little different due to their local handling of this tag - in those locations foot=yes is required.

That decision came from some research I did which led me to OSM tags for routing/Access restrictions - OpenStreetMap Wiki … That explains the worldwide default as well as per-country defaults & the UK default is foot=yes for highway=trunk

It sounds like you’re comfortable with OSM editing, but if you need any help with edits, or want to request edits made for you, I’d suggest posting in Support > City/Street/Node Issues

1 Like
9

Many thanks, I will get tagging.