What does your data structure look like?
Do you have a list of City objects and each of those has a list of coordinate pairs?
In cases such as this is might be easiest to use two models. One derived from QAbstractListModel presenting the cities, and one derived from QAbstractTableModel presenting the coordinates for a given city.
In your current approach, with a tree model based on QStandardItem, you could try setting the same model for the table view and when selecting a city, set that model index as the table view's root index.
Cheers,
_
Bookmarks