Now Testing: City street/node updates

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.