HI again Paul, there is only so much the app can do without a human brain to discern and parse actual location names. To help you out with the logic, here's what I programmed:
COUNTRY = the LAST entry in a location, after the final comma.
PLACE NAME = the FIRST entry in a location, before the first comma.
SO, for example, for Bellevue, Sandusky, Ohio, United States, the COUNTRY = United States, the PLACE NAME = Bellevue.
For Bellevue, Ohio, then COUNTRY = Ohio, and PLACE NAME = Bellevue.
(as you discovered)
When you Colour by Place Name (whether you use Birth locations or Death locations, same logic applies), there are two options you can use.
The default is to use COUNTRY SHADING, that will show Bellevue, United States as a separate colour (in the same range of colours as all the rest of the places in the United States), and also a Bellevue, Ohio (in the same range of colours as any other places whose "country" = Ohio)
If you switch to UNIQUE COLOURS, then it ONLY looks at the first name, and will colour ALL Bellevues the same.
For deep charts going back many generations, past multiple names for countries over time, this Unique Colours option will keep all of the same place coloured the same, regardless of what the country was called.
However, you have discovered the one issue my logic cannot solve (without introducing a third variable at least), and that's the difference between Bellevue, Ohio, US and Bellevue, Pennsylvania, US, etc..
I will add it to my list of possible options for the next revision - but would like feedback on how large a problem this is to help me prioritize this change.