This forum is closed for new topics. However, you can still search for a solution in the old topics. For technical support related to the Feature Requests premium extension please open a new premium support ticket.
Using WordPress native database tables is not always the best solution. Few example of why having a custom table for GEO my WP is the ideal method:
1) If not using a custom table and using one of WordPress’s tables we will need to use the post_meta table. Means we will save the location data in custom fields.
If that is the case instead of having 12 location fields ( street, apt, city, state… ) in a single table row we will have 12 extra row in the post_meta table, row per address field. adding 12 rows per each post will make the table grow bigger much faster effecting performance in the future.
2) When doing the search query based location, Instead of having a single table JOIN to search for coordinated the query will be a more complex by joining the post_meta table twice . Once for latitude and once for longitude. That will effect the performance of the search query specially when the post_meta table is bigger as described in point 1.
3) In a custom table, since all the location fields of a post exists in a single row, it is more efficient and faster to get the location information then if each field saved in its own row.
The custom table method won’t change but I will look into a solution for the future.
What Kind of integration are you looking for? What exactly is that you are trying to accomplish with GEO my WP and WPGEO together?