-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
city profiles should show a geographic aggregation level in between it and its country #114
Comments
I definitely agree, but this would require some extra data from @crisjf as well as a slightly altered database structure. Currently there is no concept of a "state level" geography. @melteng were you imagining this only for US cities? Or in the case of cities outside the US supporting the province or other mid-geographic component? For example, would the Belo Horizonte page say "Belo Horizonte, Minas Gerais, Brazil"? |
Getting this data for US cities is relatively easy, but as @alexandersimoes mentions, it would involve altering the database structure. How important is this? |
Maybe we can do it only for the US, since most of the characters are American born anyways? |
If you can send me a new Also, would it be possible to get the wikipedia URL slugs that they use as another field in that file? If you update that file please annotate the wiki as well 😄 - https://github.com/MacroConnections/pantheon2/wiki/Places |
@alexandersimoes @crisjf Hmm I do think having provincial/state info is useful in larger countries, plus it'd avoid the user having to click out of the site to google the city name. But yeah for now, let's do the US first. Then we can look at the data and see what other large countries have a lot of representation and should include regions/provinces? |
Ex. "Gary," Indiana where apparently the Jackson 5 came from.
The page title (in the tab) should say Gary, Indiana (like on wikipedia).
Where is says "United States" underneath the big "Gary" profile title, it should say "Indiana, United States."
The text was updated successfully, but these errors were encountered: