DB Normalization ends up with 2 similar tables
The purpose of normalization is to remove insert, update and delete anomalies from the data model.  For instance, if you have a spelling error for the name of a location or say the lat-long is incorrect, you would want a single place to go to change that information.  Your solution with two tables seems correct to me.  Each column is dependent on the key, the whole key, and nothing but the key of the table.