Please be careful with this request. Not all places fit nicely in to "city, county, state, country".
Personally I hate the way FTM uses separate fields for names. Not everyone's name can be entered in 3 fields "Given names, Surname, Suffix".
Some individuals have one surname which is common in the USA and parts of Europe. Some individuals historically and in the present have "no surname". Some cases you don't know the surname of the person, which is different than having "no surname". Some individuals have their surname first, some last, some in the middle of their written name. In some places individuals have multiple surnames such as South America, Spain and Portugal. Each of these names must be indexed as distinct surnames.
FTM does not deal with this very well using only 3 fields for any of these instances. I'm sure that doing the same for places will be no better. For names the better solution is to allow the user to tell the software what each name part means then store it that way for later recall. This requires a better interface and database.
Personally I hate the way FTM uses separate fields for names. Not everyone's name can be entered in 3 fields "Given names, Surname, Suffix".
Some individuals have one surname which is common in the USA and parts of Europe. Some individuals historically and in the present have "no surname". Some cases you don't know the surname of the person, which is different than having "no surname". Some individuals have their surname first, some last, some in the middle of their written name. In some places individuals have multiple surnames such as South America, Spain and Portugal. Each of these names must be indexed as distinct surnames.
FTM does not deal with this very well using only 3 fields for any of these instances. I'm sure that doing the same for places will be no better. For names the better solution is to allow the user to tell the software what each name part means then store it that way for later recall. This requires a better interface and database.