@louisadekoya, just retrieve those address components from the geographic address and store them in your own fields. The geo address data type has many :operators (or perhaps you might call them subfields) that represent the components of the address. Play around with those in a text element to understand what is available to you (or consult Google geocoding API docs, perhaps).
Basically, when a user enters or updates their geographic address, you can decompose the parts you want and save them on some object, be it the user or your own address data type. In this way, you can avoid making tons of API calls to get :city and :state or :state_code (or whatever it’s called) at runtime. When you reference these operators on a geo address, you are actually consuming Google geocoding API calls, which is not always desirable.