Taxonomy hierarchy not intuitive for users

From an end user perspective there is no logical difference between a county sub division and a place. When a user does a hierarchical search, they have no idea how to find a target location (for example: Boca Raton).... would they look under Places or under Broward County... or would it be Dade County?

From a usage perspective the user would not even think to look under "County" for Boca Raton.... The proposal is for all County Sub Divisions to be shown under Places. The open question is whether this should be done in the location file (by renaming County SubDivisions to Places and reparenting them to the appropriate State) or whether this should be done by the UI. If it is done by the UI this would mean the issue is still going to be a problem for API users.

(p.s. Boca Raton is an example - I do not know if Boca Raton is actually a county sub division or a place in the current taxonomy since this is only something that is intuitive to Census people).