Redoing the Canadian City DB for OOTP

[kq76]

Originally Posted by Muzamba

...

Unless someone can definitvely clarify which of these places are their own municipalities and which are merely neighborhoods, I'd personally prefer that they be listed as unique entries in the database.

Originally Posted by Muzamba

...

For now, though, I'm most interested in continuity. So if it's determined that Mississauga is the administrative equivalent to Mesa and York is the equivalent to Hollywood. I'd like to see that reflected in the revised database, with Mississauga a separate entry and York not.

All I know is I think suburbs of Vancouver like Burnaby, Surrey, Richmond and even North Van should be listed separately. Reason being that if you want a more local league then all those would have teams. What I'm unsure of however, is whether distinct neighbourhoods like say Kits of Vancouver should be listed separately. Part of me wants to say yes because like with the Australian Football League there are 8 or so teams in Melbourne alone, just from different neighbourhoods. I could easily see someone wanting to do something like that too.

Anyway, I don't see a problem with listing suburbs or even neighbourhoods (it doesn't hurt anything does it?), but the bigger question is should Vancouver be listed with its population that includes all its suburbs (the GVRD) which makes it a fairly populated city or should it just be the city proper? It'd depend on what the league creator wants, but OOTP should have a default of some sort. I lean more to using the larger #, but I don't have a real strong reason for that. I guess I just suppose we should assume that most people won't be making more localized leagues, that they'll be more doing national or international leagues.

[Le Grande Orange]

Originally Posted by Muzamba

Now, when it comes to player origins, I can see it both ways.

Your point is well taken. I thinking of the city DB primarily in terms of team location and not player origin.

I think perhaps there ought to be two DBs, one for team location (which could include other factors besides population to better represent the economic potential of a given location) and another for player origin. (Really, if a DB list is being used just for player origin, is the population count really necessary? Seems to me just the latitude and longitude would be needed.)

[kq76]

Originally Posted by Le Grande Orange

...(Really, if a DB list is being used just for player origin, is the population count really necessary? Seems to me just the latitude and longitude would be needed.)

You don't want the same # of players coming from Hicktown, USA as from NYC do you?