There are two separate topics here:
-
The ‘old vs new’ decision…
Should we delete https://citystrides.com/cities/38121 in favor of Toronto, Ontario - CityStrides
Should we delete https://citystrides.com/cities/40069 in favor of Ottawa, Ontario - CityStrides -
The ‘parent vs child’ decision…
(I’m purposefully throwing a lot of terminology out the window for this one. I don’t care what people define a “city” as, or “neighborhood”, or “suburb”, etc - there are too many varying terms around the world to keep up for the purpose of this particular conversation. For this conversation it’s just a city and its components - a simple parent/child structure.)
For most cities, it’s not worth bringing their components into CityStrides. This is because most cities are on the smaller side, and the next “layer down” is something along the lines of a neighborhood.
For some cities, Los Angeles is an extreme example, the strictly-defined city is massive & for the purposes here in CityStrides it can make sense to import its components.
This ‘parent/child’ topic was also brought up in The municipality problem and Manhattan is weird now
Anyway - I don’t think a decision on the first topic affects a decision on the second. We can opt to delete the ‘old’ versions of a city, and also opt to keep the ‘child’ data.
My take is that - if the city is big enough - it’s ok to have a single huge ‘parent’ city (Ottawa) and all of its next-level-down ‘child’ “cities” (e.g. Goulbourn) in CityStrides.