Love the Route Builder - especially one detail: it shows how many streets on a route I’ve already completed, based on my lifemap.
Since that logic already exists, could it apply to saved routes on my Routes page? My workflow today is manual: open each route, toggle streets on and off to see which ones it would complete, count them, then bake that number into the route name so I can compare at a glance:
Location (streets completed / miles)
e.g. Laurel Canyon (17 / 6.25)
If each route stored that completed-street count itself, the naming convention would take care of itself.
It’s a dynamic list of incomplete streets. Once you run the route, the completed streets are removed from the list.
I can display the count in the tab, but just be ready for it to change on you. 
You also don’t need to toggle them on the map to count them, you can just count the items in the list.
I’m not following this … I can’t picture this feature / how it works as you’re describing. I recall building this in the opposite direction - showing what you have not completed.
Do you have any screenshots that display this?
Thanks James - and first, sorry for the confusion: I understand now that Route Builder shows the count of incomplete streets a route touches. What it doesn’t capture is how many streets I would actually complete (based on my LifeMap progress) on that specific route.
Some context on where I’m coming from: I’m a completionist (blame Scott Trimble!). I’m always trying to knock out as many streets per mile as I can on my routes, and I typically have several pages of routes authored. That might just be a me thing, but it’s why the at-a-glance number matters so much to me.
What I’m hoping to avoid is opening each route and working out that count manually every time I’m deciding which one to walk. Ideally the Routes page would show the current count of incomplete streets for each saved route against my Lifemap, and how many of those I would complete should I take that route. Then I could quickly compare routes at a glance and make decisions. And the count changing is exactly what I’d expect: if a route shows 17 incomplete streets today and I complete three of those on another walk, it shows 14 the next time I look.
And a related question: have you ever considered a folder structure for routes? With this many routes, being able to group them would help a lot too.
Thx for entertaining!
Dean