Updates on October 31, 2025 (Release 1314)

  • :hammer_and_wrench: You can now search activities by date; it supports YYYY-MM-DD searching as well as the individual parts e.g. 31 will search for all activities on the 31st day & 2025 will search for all activities in 2025, and it also supports month-name-based searching where October will search for all activities in any year within the month of October
  • :hammer_and_wrench: Route Builder no longer has an undo limit
  • :hammer_and_wrench: 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)
  • :hammer_and_wrench: Cities with 10k+ streets can only be synced once every 7 days
  • :hammer_and_wrench: The chart on our profile page (far right tab) now excludes streets in nested cities
  • :hammer_and_wrench: Similarly, various stats throughout the site (mostly on the homepage) are now scoped to non-nested cities
  • :hammer_and_wrench: The LifeMap Poster purchase notification email will always be sent; previously it wouldn’t send if you viewed the notification in-site
  • :hammer_and_wrench: Way records that are tagged as planned are no longer included in CityStrides
  • :hammer_and_wrench: The contact form now includes a hacky captcha because of the amount of spam that was getting through
  • :newspaper: The In The News page has some new additions
  • :paintbrush: The billing section in the Settings page now displays the number of months left & end date for Prepay Supporters
  • :paintbrush: The main user list and the Leaderboard pages were merged into one more compelling/useful page
  • :nerd_face: I reworked some Node data storage to make it easier to work with
  • :nerd_face: 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.
  • :nerd_face: I’m currently also testing a way to speed up reprocessing after activity deletions
  • :nerd_face: Various software updates
13 Likes

Two issues I noticed, possibly related to the release (started on or about the 31st):

  1. maps don’t display on mobile (iphone, happens with both firefox and chrome)

  1. 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.

1 Like

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.

21 posts were merged into an existing topic: Streets spanning two cities with one node in one city

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.

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.

:person_facepalming: 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. :person_facepalming:

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 … :grimacing:

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

Thank you. That worked like a charm

I have experienced the same behavior - problem is my iPhone is not iOS26 compatible. I wonder whether a chance we could have a webGL1 fallback ?

it wasn’t that my phone wasn’t on ios 26 beta - you don’t need ios 26 for this to work.

it was that my phone was on a very old ios 18 beta.

Thanks for the note Steve. I believe WebGL2 is not supported after 17 - my phone doesn’t get to iOS 18. Yes - time for an upgrade - but on one level the hardware is fine for what I use it for.