I think commas in names should be avoided. It causes trouble when trying
to identify the different parts of a string like "Earth, Texas, United
States". Each of the parts separated by comma should have a separate entry
in the database. And in the case of "Earth, TX", when automatically adding
the admin1 name, you get "Earth, TX, Texas". Texas is the admininistrative
division, so it doesn't belong in the name field.
In the database there are 18,604 names containing a comma, and most of
these (if not all) should have been rewritten in my opinion. Take for
instance "Armstrong, Mount", "Argyle, City of", "Annaburg, Stadt" and
"Barkell, Lake". These should be "Mount Armstrong", "City of Argyle",
"Annaburg" and "Lake Barkell". Sometimes it is also a good solution to put
what is behind the comma in parenthesis instead.
In my implementation of Geonames, I simply filter out all names that
contain a comma. :)
--
Best regards,
Even Scharning
Netburn Web Solutions
Time.is - exact time for any time zone and any location in the world
(except those with a comma in their name)