Syncing cities with OSM

Ooh, thanks! You got one of them. I still wish there was a way to queue updates.

The sync didn’t pull my changes in OSM, so now I need to figure out why. Thanks for the help!

:thinking: The sync report indicates the last sync for Blaby completed on 2026-04-24 … those reports stick around on failures as well, so if you’ve tried syncing that city after April 24th, it seems like the sync never actually went through (which is a whole other thing that I wouldn’t expect).

Overall, the Status page is the place to look to determine when the current batch of sync work is estimated to finish up.

I’m thinking through different ways I can work some a kind of queue system that won’t completely blow everything up (I cannot use the existing queue system for this - it would be all to easy for tons of cities to get queued up and absolutely overrun the entire system with too many jobs).

Thank you for looking into it and indeed taking it seriously, as ever. I appreciate the effort that you do. Suffering, as I do, from a tiny amount of vanity, I am kind of sort of planning to let the local news know if I finish the county, so I am hoping that at that point I will be able to point to the site.

It’s really only at this late stage of nearly finishing an area that it becomes an issue, since I have 181 streets left to do, and am aware that at least ten of them should have disappeared by now, but I am also conscious that when the cities do update, I will have several new ones, since people will insist on making new roads.

Thanks for the pointers, and I will keep an eye on those pages.

Hi @JamesChevalier ! Any chance you could trigger a sync of Ottawa, Canada? Ottawa, Ontario - CityStrides
Last sync was April 6, 2026.

The current city synch queue doesn’t seem to be moving at all, and the five day processing seems very long. At least the estimated completion time has changed, as it was saying 2 minutes for days. Has something failed and blocked the queue?

Toronto is syncing

I just updated the estimate to correctly reflect the new code I’m testing

All the processing that has to happen after updating the underlying city data takes a long time
I’m working on it, but :person_shrugging: it is what it is right now

I keep getting this for the city I’ve been trying to sync. Tried several times over the last several days. Is there a way to prioritize the cities that havent been updated in the longest time? Last update was August and want to get updates applied as I have one run left to finish.

Thanks!

:tired_face: There are too many processing jobs running, please try again later”

There are many posts about this and it is issue that James is working on. I recently read that London was being updated and that was estimated to take 5 days to sync. I cant recall the priority schedule but I am sure James has posted about ont he form or in the water cooler chat

Morning All,

I was starting to wonder about this as well, as some changes I made in OSM a few weeks ago haven’t made their way across to CS.

But, confession time, although I’ve been a member for 2.5 years I’ve never actually taken notice of the sync date next to my favourite city. I also didn’t realise that clicking it doesn’t sync things but takes me to the OSM map. :face_with_peeking_eye:

I’ve also just discovered the three dots over the date gives me options to ‘sync now’ or ‘view in OSM’ - apologies, I’m not normally this slow but some things seem to pass me by! Please don’t say I’m the only one…:face_with_raised_eyebrow:

Anyway, my sync date is 3 October 2025 and pressing the ‘sync now’ gives me the same message as Dallas. I just assumed the synchronisation happened automatically every few weeks? Does pressing the button stuff up the process by overloading it?

None of this overly affects the way I use CS but I’m curious if I’m the only one here missing the sync button and/or understanding how it works.

Toodles. :disguised_face:

I don’t know how the current syncing is queued. I was able to sync a town a few months ago no problem when I finished it (and had all the roads fixed). However now it is perpetually busy for the city I’m about to finish and I don’t know if or when a manual sync will ever be available again…

It would be cool if I could at least get it queued up (I cant do this now) and then prioritize paying folks who manually queue up a city and then prioritize those manual syncs to the towns/cities that havent been updated in the longest time…so it someone updated their town a few days ago mine would go first because it looks like its was last done 4 months ago. Then if there are free processing slots do whatever the normal procedure is…

Lots more on this topic in Syncing cities with OSM

I have tried to not overload the synching by only adding a couple of cities to the synch list. This was a couple of weeks and it still hasn’t got to it. When looking at the queue for cities to be synched, I see a lot of cities from the same area regularly.

Should there be a limit on how many cities an individual can synch in a certain period of time?

Yeah, people can only bump 5/day and a city can only be bumped once per day (cities with more than 10k streets can only be bumped once per month).

Letting me do 150/month sounds like a lot.

I don’t think anyone will do 5 a day for every day in a month, what would be the point, but I sometimes want to get all of my closest cities updated, so I send in 5 one day, and maybe some more the next day. Then probably won’t send anymore that month

That’s more or less my pattern of syncing now, although last year before the issues began I would be making ~8-10 requests per week - at that time I had the bandwidth to do a lot more exploring in new areas and was making lots of OSM edits.

If there are some super-syncer users that are bogging down the queue with lots of requests, perhaps it would make sense to have some monthly limit in addition to the daily limit. I’m not sure if James tracks the user who requested the sync, could be nice if the report pulled that just for knowing usage patterns.

Hey James, are border updates currently not making their way into CityStrides? As an example, I updated the border below and it wasn’t picked up in the city update today, but the street names I added that were within the old border did (the left half of Swallow Falls Way). Fishers, Indiana - CityStrides

Border updates happen monthly … Given the current sync rate, that’s pretty much every sync right now … Fishers was last updated on 2026-06-15 so its border won’t update again until July 15+

Sheridan, IN got updated yesterday… maybe. It seems like the sync updated the border but didn’t actually update the streets. You can see it was not a trivial border update so I expected a lot of changes. I also didn’t receive a notification that the city was updated, but the date on the page changed to 8/2/2026.

Is something wrong with city syncing?

the figures suggest it’s firing on all cylinders but nothing processing now and ‘up next’ doesn’t seem to be moving?