I think I figured it out. It looks like I skip creating a node if its OSM ID already exists in CityStrides, but that means I’m not creating a node if it was already added for a different street.
I haven’t yet figured out why some nodes are associated to different streets, but I’m guessing that it’ll be some similar logic where I’m not taking into account which street I’m currently working on during this update process.
Update those nodes on Solitude were created in 2019 during the initial import, so I’ve manually deleted them. I’ll have a new version of the update code to try later today.
Want to carpool (or run?!) to the docks in Boston?
I’m deeply impressed by your greater Boston map! FYI, it is possible to get the two streets you are missing in Cambridge now. Aberdeen Way is easy – it just had a few nodes added that go around the bend.
Dawes St is harder, because there is a huge amount of construction around there, and the road itself is actually closed. However, there is a pedestrian walkway that will get you far enough to capture the node.
I would suggest running Jacobs St, too, which I added to OSM a while ago.
Nice to see updates making it in. Can you update cities/95511 and cities/96515 if I’m not to late to the party? If you get this working perfectly, would future changes be updated automatic, manually or once every month/year?
While your updating…if you want to do my 3 cities I have made OSM changes on.
Will this update also take out the nodes that are not in cities borders?
Thanks
Well, you’re only including streets with a name, so that excludes the vast vast majority of driveway scenarios. But in general, I think you probably don’t want to be sending people down driveways.
Thanks for the tips. I was going to get Aberdeen the other day, but I think I strained a core muscle while trail running so I’m nursing that at the moment. I may wait until the construction is done to get the others. We’ll see.
To say I’m a bit obsessed with this site is an understatement. It’s been a great motivator when not training for a race. I’ve been a user for about 5 years now I think? Having been furloughed during the pandemic has accelerated my progress in Boston much further than I had planned.
i have the same issues. squares seems to have excessive numbers of nodes all around the border of the square, which makes it hard and often almost impossible because buildings will cause GPS drift along those borders more easily.
So I go to my activity dated October 13, 2017. (Back then the road was not constructed yet, but may have been in progress.) Double Brook Road existed in CityStrides and it placed it in my “Completed Street List” but shows that I only hit one node for that street.
I will return to run Double Brook Road and the three other streets that extend off of it. We will see if the remaining nodes turn green and if the completed date changes.
It does look the same to me from a private/incognito window. As you can see, I have never run near the nodes on that street except for the first one. I agree, it may have been an issue that I didn’t catch back in 2017, but I think it goes further then that. Something isn’t being address during an update.
I just found something that may help. I went to Bedford, NH and it is still showing 100% completed after the update. Last year, I ran Indian Rock Rd which was under construction, and I attempted. to hit the nodes for Boiling Kettle Lane & Governor’s Row, which I missed badly but did hit at least one node. All three Streets were not part of the CityStrides Street list back then. Now they have been added to City Strides and are in the “Completed Streets List”. I would not have realized that a street had been added if I didn’t remembered that I attempted to run new streets before they were added to CityStrides and went to check. Could it be that if at least one node has turned green that the update is not processing the street correctly?
Two of these streets don’t have the required 90% of nodes hit.
! I was not the first though, that honour goes to 
