You can now search activities by date; it supports YYYY-MM-DDsearching as well as the individual parts e.g.31will search for all activities on the 31st day &2025will search for all activities in 2025, and it also supports month-name-based searching whereOctoberwill search for all activities in any year within the month of October- Route Builder no longer has an undo limit
- The single activity sync button will now show error message for people trying to sync MapMyFitness routes (it canât sync routes, it can only sync activities)
- Cities with 10k+ streets can only be synced once every 7 days
- The chart on our profile page (far right tab) now excludes streets in nested cities
- Similarly, various stats throughout the site (mostly on the homepage) are now scoped to non-nested cities
- The LifeMap Poster purchase notification email will always be sent; previously it wouldnât send if you viewed the notification in-site
- Way records that are tagged as
plannedare no longer included in CityStrides - The contact form now includes a hacky captcha because of the amount of spam that was getting through
The In The News page has some new additions
The billing section in the Settings page now displays the number of months left & end date for Prepay Supporters- The main user list and the Leaderboard pages were merged into one more compelling/useful page
I reworked some Node data storage to make it easier to work with- This is somewhat ongoing, but Iâve reworked the city sync process to use a filtered Planet.osm file instead of Overpass ⊠Overall, this has helped make it much more efficient, but Iâm still battling the bottleneck of post-sync data processing.
- Iâm currently also testing a way to speed up reprocessing after activity deletions
- Various software updates
12 Likes
Two issues I noticed, possibly related to the release (started on or about the 31st):
- maps donât display on mobile (iphone, happens with both firefox and chrome)
- the update city option is missing
In iOS, all browsers use the same underlying engine so I wouldnât expect any of them to behave differently from each other. Itâs largely just a âskinâ difference between them (and whichever ecosystem features theyâve added) - thereâs not likely to be any rendering differences.
It looks like your device either isnât compatible with WebGL2, or something is set/configured in a way that blocks it. Can you tell me if this page - WebGL Report - displays ââ This browser supports WebGL 2â for you?
The city sync feature is currently disabled due to a full rework Iâm testing now. I only âquietlyâ announced this in Water Station because itâs not a widely used feature & the testing is going to run a while.
This is kind of crazy - I get this (no content) for both webgl 1 and 2 on both mobile browsers (works on ff/osx desktop)
Thereâs definitely something going on at the browser level. Have you also tried plain Safari?
This page does a similar test, but I think itâs a bit clearer & also provides its own next-steps (sorry, couldnât find it when looking earlier) - https://get.webgl.org
honestly, at this point Iâm convinced that the issue is something on my end. Iâm sorry I wasted your time with it.
Wow, Quite some updates over there. Just pulling on strings here, if this is connected.
There were some updates to the map of Burlövs Kommun in SkĂ„ne Region, Sweden. Some two âstubborn streetsâ, each with one node, and 0 distance popped up on the map, and unfortunately not completed in my case. These ghost nodes do not show on the map, even when I
- activate the node finder,
- try to âshowâ, or âgoâ to the street
- Check another profile, for someone who seems to have covered them.
I have seen these 1 node streets before, and they usually are at a border of cities. I couls find the streets in the neigboring city (Malmö), connected to the current city, but it is clear that I should have covered them.
I just cannot find them. Any tips, to have them cornered?
quick update on my webgl issue
turns out I was running the ios 18 developer beta, from a project that I donât even remember.
probably the only guy on earth who was.
(the current developer beta is ios 26)
they did some sort or release on that which broke everything. switched to 26 and maps works again.
I recognize this problem, both of them are streets in Malmö that extend into neighboring Burlöv. But as they are completely straight from the border to the end in Burlöv thereâs only one node (the end node) on the Burlöv side. And it seems CS have problems handling that. I have previously solved such cases by inserting two new nodes, one on each side of that border. Then you get two nodes in Burlöv, in this case, and also an âend nodeâ for Malmö. Iâm not sure what the OSM etiquette is for doing this thoughâŠ
Burlövs kommun, SkÄne lÀn - CityStrides has CityStrides and CityStrides
In both cases, the streets donât actually have any nodes. Iâd expect the sync process to remove those, so Iâm re-syncing it now. While thatâs running, Iâll look into whether the code is working as expected.
Update: Iâve got some lingering bad data from the old sync code. Iâve updated the new sync code to automatically clean that up. The sync that just finished for https://citystrides.com/cities/105897 has removed those streets, as well.
@JamesChevalier Iâm curious why the part of Strömgatan extending into Burlöv should not be in CS, as far as I can see it has one node at the end?
Ah, itâs because the new city sync code doesnât allow single-node streets & thatâs all thatâs present in Burlöv.
1 Like
Oh, I see, you solved it that way!
Something seems to be wrong with the notifications now. A just got an update note for Sollentuna looking like this. Deleted streets just show 0. Looking closer at some of the new streets I find that PumpvÀgen and SolbackavÀgen are just name corrections, used to be PumphusvÀgen and SolbacksvÀgen. So these old names should be seen under Deleted streets. Same thing for JÀrfÀlla that was also updated today.
Iâve got a fix for the â0â deleted street names. Notifications after the next release will properly display names instead of â0â. The issue was that the data store Iâm using for sync progress notes is strongly typed, and I requested the list of names as integers instead of strings.
I think that weâll find a number of cases where a street appears in deleted & created. Iâll look into whether I can spot those & move them into updated.
This is because the sync process is totally rewritten to a more âdiffâ like process, so some changes are seen as deletions/creations.
Update: I can pull the streets from the âupdatedâ list if they appear in the âcreatedâ list (this happens because new street creation happens earlier, and then new node creation - which can include nodes on new or existing streets - happens later & I toss that info in the âupdatedâ list) ⊠I canât make the same comparison between created/deleted, but I think it kind of makes sense that PumphusvĂ€gen was deleted and PumpvĂ€gen was created ⊠kinda ⊠
Yes, I agree on that. Would be more confusing if it was listed as updated. Would that be the old or the new name listed? Totally fine if old name is deleted, new name is created!
The deleted section would display the old name and the created section would display the new name. To that end, youâd have to click through the name to figure out which mapped to which - if it wasnât somewhat obvious from the listing page.
1 Like