{place}, {state} if state is set, where state is the abbreviation like CA. E.g. San Ramon, CA.
{place} if it's a country, e.g. Israel.
Note that neither scheme includes the country code. There are two issues with this:
Risk of international collisions if the same place appears with the same state/province abbreviation in >1 country
Useful information to the user: they may want to know the country in e.g. search
The Place ID is relevant in these places:
URL for the city details page
Header in the city details page
Scorecard title
Search value
When fixing this, we should decide if the Place ID should use abbrevations for the state & and country.
--
We should also revisit how to store states. Right now, we store it as California, CA, which is a little redundant but it is also useful in table view to let you include CA in all the CA values. Should we store the place ID as California, including the URL? If we do that, we need a new attribute like isState. (We already implicitly have isCountry by not setting state at all.)
Right now, Place IDs follow this scheme:
{place}, {state}if state is set, where state is the abbreviation like CA. E.g.San Ramon, CA.{place}if it's a country, e.g.Israel.Note that neither scheme includes the country code. There are two issues with this:
The Place ID is relevant in these places:
When fixing this, we should decide if the Place ID should use abbrevations for the state & and country.
--
We should also revisit how to store states. Right now, we store it as
California, CA, which is a little redundant but it is also useful in table view to let you include CA in all the CA values. Should we store the place ID asCalifornia, including the URL? If we do that, we need a new attribute likeisState. (We already implicitly haveisCountryby not settingstateat all.)