City and Airport Terminal tables in dimensional modelling

Hi,

We have City and Terminal as 2 separate reference tables around Order fact in Star Schema. Products like Hotels, restaurants are reported at city level and granularity for products like Flight is at terminal level.

Both City and Terminal tables have few common attributes like City_Name, Country_Code, Country_Name, Continent_Code etc. Is there any way to have relationship between these tables to avoid data duplication? or have only one table?

I have thought of common table between City and Terminal which can hold common attributes and keying back to respective tables but that is more like normalized way rather than dimensional/star schema approach.

Can you please suggest/advise any other way? Thx in advance.

Thx,
Amar

Why not just call it 'Location' and put everything in one dimension? Add a type code so you know what a row represents and populate attributes appropriate for the type. There isn't that much difference in the data and, even if you have every town and airport terminal in the world, its not going to be that much data. When you can get a GPS system that covers North America (with landmarks, hotels, gas stations, ATM machines, etc...) that you can hold in the palm of your hand, how much data could there possibly be? Sure, a GPS only stores a name once, but for a database, repeating a name 1,000 times is no big deal.

Thx for inputs. Location entity makes sense. Let me design in that way.