Greetings — I’m running a WP site that uses geolocation extensively. We currently run the MapPress plugin, but there are of course others, e.g. Comprehensive Google Map. I’d assume each of these plugins has its own custom tables to store location metadata. Then there are the built-in geolocation features in the WP mobile app, which (at least in the iOS case) adds the following custom fields in wp_postmeta: geo_latitude, geo_longitude, geo_public.
The result of this can be a mess, if we have multiple users contributing to a site from multiple devices, or if we want to move from one plugin to another. Basically, there seems to be no rhyme or reason behind how/where the geolocation metadata are stored. I’ve read of attempts to follow the W3C specification at least for visitors (see this plugin), but not sure if this is the way to resolve these differences.
I would sure appreciate hearing from those in the WP community who are more knowledgeable than I am on this! I’m gearing up for a rather large educational development that would need to resolve the above if we are to move forward on the WP platform.
That’s interesting, I wasn’t aware of the geolocation features in the mobile app. That’s good to know. I’ve been working on mapping/geolocation plugins for a while now (nothing released publicly so far), and I’ve been using my own geotag fields. I’ll have to add support for geo_latitude, geo_longitude and geo_public, too.
Thanks for the heads-up.
Viewing 1 replies (of 1 total)
The topic ‘common structure for geolocation metadata’ is closed to new replies.