I'm running into an issue with Cities (#18) where there will be a number of them with multiple spellings or variations and I don't want to have multiple entries in the database and splintered versions of the City. Here's an example:
- St. Louis
- Saint Louis
- STL
We will already have East Saint Louis and unincorporated areas of the City in the database and I don't want multiple variations of the actual city name. By not allowing user input and forcing all Address input to run through Google Places Autocomplete (#30) we are eliminating some of this problem. I do need to find out the variation that Google Places uses for the City name and maybe still provide some alternates in a separate table similar to the approach with Alternate Email Addresses on the User model (TIPOFF/authorization#20).
I'm running into an issue with Cities (#18) where there will be a number of them with multiple spellings or variations and I don't want to have multiple entries in the database and splintered versions of the City. Here's an example:
We will already have East Saint Louis and unincorporated areas of the City in the database and I don't want multiple variations of the actual city name. By not allowing user input and forcing all Address input to run through Google Places Autocomplete (#30) we are eliminating some of this problem. I do need to find out the variation that Google Places uses for the City name and maybe still provide some alternates in a separate table similar to the approach with Alternate Email Addresses on the User model (TIPOFF/authorization#20).