When node hunting dense areas it would be great to see a crumb trail to help hitting all the nodes. For instance in places like here:
Basically it means updating the map view while running but that is not possible under current workflow as the map view is taken from Garmin and such after finishing your run.
As node map is a subscription option, live updates of your run should be the a subscription feature as well.
Interesting idea. I have seen mentioned before, the idea of 3rd party apps, for planning “node runs.” I recall several mapping options were mentioned, but I don’t recall if integration into CityStrides was ever mentioned. A search may find that info.
I like the idea, but I don’t think I would ever use it. I do most of my route planning beforehand (and bring printed maps*), and might occasionally check to make sure I’m getting the nodes.
Which makes me think, there might have been an idea for an app that would alert you when you were near a node… Kind of like a radar screen.
Well I’ll vote, as I would be inclined to try it, but it might not fit in with my style… As most of the places I am gathering nodes are pretty simple.
’ * A recent area I’m working on (walking with my wife), Lipan, Texas, has very poor cell coverage on my network.
Good idea indeed, live tracking. I use it for same purposes, sharing with my wife. Also saves writing nodes that I went for a run or ride
I do the mapping on forehand indeed and use my watch for directions. This works fine for straight long roads but not so well for the rural areas with tons of nodes close to each other.
Lifemap live recording would be amazing. It’s hard to flip back and forth between the map on my watch (or strava), and Lifemap node hunter, and still be certain I haven’t missed nodes.
Having a live map (like on the Strava app) would significantly speed up my node hunting runs.
When opening your lifemap on your phone, there is a small target icon on the right hand side. Picking that enables tracking on the lifemap. If you drag the map around and lose your tracking, tap it again to re-center. Tapping it when centered disables the location.
This will require you to allow location tracking on your phone for the browser.
That combined with the supporter feature nodehunter might get you closer to what you would like to see.
I mean (and I assume the topic of this thread means) to record the track / gps route as you go. e.g. turn on recording and see the map being traced live, as in this (bad) screenshot:
Unless I’m mistaken the button you indicated just shows my current location, which is indeed very handy, but doesn’t draw the route I’ve followed.
I normally run whilst holding my phone and deciding on a route as I go, with the map in fullscreen mode and showing my current location.
It would be wonderful if there was a way to see where I have been on that particular run, which would make it easier to avoid running the same street twice by accident.
I just merged this into a 2 year old thread with the same idea (sorry for everyone else in the thread if there are notifications going out now).
I’m pretty sure the main issue I need to overcome is the fact that CityStrides is a website, and websites do not retain GPS tracking when they go into the background or when the phone is locked. So the tracked GPS lines would include straight lines during that background/locked time.
So for you this would probably work as expected, since it doesn’t sound like you keep another app in the foreground or lock your phone.
For me, I’d end up with a mostly blank track since I keep my phone locked and only look at it when I’m confused - mostly when it feels like I’ve been running for much longer than it seemed like I would, and I mostly end up being wrong
You’re right - for my use case it would be absolutely fine if it just put a dot on the map every ten seconds. If the page wasn’t getting GPS data because the phone was locked or the browser in the background or whatever, then just don’t put anything on the map.
I think that would be better than “joining the dots”, resulting in straight lines between available data points.
Looks like the W3C Sensors group recently agreed to try to progress this for the geolocation-sensor API, but I’d guess an actual implementation is years away, and would require a PWA.