Normalise for a very small database?
For a small database with just a few rows, you might say that the design is whatever you can maintain and sustain. However, a few things to think about include:


Remember that the first implementation is not the future implementation.  Planning ahead just a little can save headaches in the future.  
If the database should scale up in the future you might find yourself refactoring tables and code.
Since in Table3 the columns are named GFA(m2), Residential units, et cetera for whatever you are measuring you, you are committing to changing that table repeatedly as new measures are added.


By the way, I note that your values(float) of 200.3 becomes 200 in the final table. (Maybe just a typo.)  But be sure to keep the data types of the columns defined to fit the data you are storing.

And, yes, if I was delivering this to someone I would normalize it further.