Normalise the data in table "ACS_05_EST_S1901.csv". Be clear in naming columns and corresponding variables in tables.
"Geo_ID" and "Geo.id" can be confusing in this context. My guess is that you will end up with 3 tables, including the one for meta data:
Identify fields that can be used to establish relationships between records of different tables, like "GEO_ID". Connect tables through these fields in the FM's Relationships Graph. Then everything is at hand for display in layouts.
Through a scripted import routine imported data can be moved to their appropriate tables.
There is more than one way to achieve things. All depends on how you intend to make use of the data.
Can you point me towards a scripted import routine example you know of. I would think I could make and import that says HC01... = Housing... and HC02 = Families ... and so forth this way I can just import the raw data into a table with the field names of my choosing correct?
Thanks again for you time
Unfortunately I have none at hand that is easy and instructive. Designing such an import script can start when your data model is established and is in a normalised state. This would be the basis for our discussion, walking you towards a working script.