Design database table for property listing

I want to design a database for a listing website, this is the first time I design the database, so I am not sure if I in the correct path. Here is the fields that needed in a listing, 1. title - Character 2. pub_date -Timestamp 3. modi_date -Timestamp 4. ex_date - Timestamp 5. desc - Character 6. thumb - Character 7. office_no - Integer 8. mobile_no - Integer 9. email - Character 10. web - Character 11. status - Character 12. state - Character 13. city - Character 14. address - Character 15. postcode - Character 16. lat - float 17. lng - float The lat (latitude) and lng (longitude) are used for searching, eg, searching nearby listing by comparing the lat and lng. So these fields will be queried often. My question is should I separate the *lat* and *lng* into another table (normalization) since these fields will be query a lot. Or I just leave it in one table.