Hello Lucatoni,
I think you should start with stating your entities and attributes related before you can decide, you need to make more analysis as the calculated fields should not stored in the database.
You need to organize the thinking as a county shall have many cities and a city will have some properties like the ID and some other details you may choose then you need to relate the cities to the population if you intend to allow the user to enter Persons names and gender after so you need to calculate the men population and women population or whatever you like.
and if you intend to store the populations per city or for each city
i think you can try to think in that manner a county is having many cities and a city belongs to one county so the relationship is one county to many citeis so a table for counties and a table for the cities having a field as FK of the countyID you created also the city table may have the other fields like toal population and total number of men and so on ...etc.
i hope i made it clear and give you a start point.