Yeah - an ongoing effort, with a focus that pairs both A) the most active cities in CityStrides and B) the most actively updated cities in OSM probably makes the most sense.
One concern that I have is that by bringing this closer to daily (from monthly/quarterly) starts to shift a bunch of my ongoing focus from development and into infrastructure - unless I can get it right the first time.
- I have to build the correct Overpass queries, and handle the XML response properly
- I have to rebuild my Overpass server to include attic data, so that I can actually run these queries
- I have to build out an infrastructure that can handle whatever load is required to do this work
- I have to set up the system that automates this effort
My current perspective is that the Overpass query & response handling will be the biggest effort. The OSM & CityStrides data aren’t 1:1 matches, so I’ll need to figure out how to handle the changes in a way that makes sense within CityStrides.
I don’t think there’s a ton of effort in the Overpass rebuild or the infrastructure setup, but there’s definitely some costs involved that I’ll need to keep a hold of.
The automation effort seems like it’ll be the second biggest effort, mainly around keeping a balance between good update progress and keeping server load in check.