Contributors: dshanske
Tags: geolocation, geo, maps, location, indieweb
Stable tag: 3.0.1
Requires at least: 4.7
Tested up to: 4.7
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Adds geographic location support to pages and posts.
Supports adding geo coordinates or textual description to a post, and will be supporting saving a location as a venue for reuse. Offers choice of map displays.
It supports retrieving location using the HTML5 geolocation API. As it stores the GeoData in a WordPress standard format, Geodata can also be added from other plugins.
Offers the opportunity to change the displayed timezone on a per-post basis for those posts from far off locations and set this based on the coordinates of the location.
API Keys are required to use Google Static Maps or Mapbox Static Maps. If not provided there will be no map displayed regardless of setting.
The Development Version as well as support can be found on Github.
Venues are locations stored as a custom taxonomy in WordPress using the Term Metadata functionality added in Version 4.4 of WordPress. Venues as taxonomies have the advantage of supporting an archive page of all posts from that location and giving the location a permalink on your site. To add anything more than a basic location you will have to create a venue unlike in earlier versions of the plugin.
WordPress Geodata is an existing standard used to store geodata about a post, user, comment, or term.
It consists of four fields: latitude, longitude, public, and address.
Recommend backup before upgrade to Version 3.0.0 due to the start of venue support. Full location data will not be saved in the post and old posts will be converted. The display name will be saved if set, otherwise a display name will be set from the coordinates. An API key will now be required to show maps for services that require API keys.
* Some quick fixes on the release. Due to issues with the removal of the old location data, it will no longer be removed. Instead only the extra display metadata will be removed.
* If there is no geo_address set and there are coordinates a geo_address will be automatically set along with timezone
* New Version Takes Advantage of new WordPress Term Metadata to create Venues (Feature disabled until future release)
* The most Javascript I've ever used in a WordPress plugin. Retrieving location information is now done without page refresh.
* Timezone Override is set by location lookup.
* Google Map Services will now require an API key to be provided.
* MapBox is now the static map provider if you are using OSM maps and an API key must be provided
* You Can Now Choose Map Providers but not reverse lookup providers which may come in future
* Full Address data is no longer stored in the post. You will have the choice of either a textual description and coordinates in the post
or assigning a venue which can have full data. Venue support in future version and is disabled here.
* Warnings no longer showing in debug logs.
* Displayed name and timezone are now set if Micropub plugin provides geo coordinates
* Revamp in Text Display Parameters, now offering three levels of Detail
* Coordinates will now display and Location will link to map if set for full address
* Google Static Maps now link to Google Maps
* Nominatim now defaultly tries to retrieve in the language of the blog
* Fixed formatting on timezone feature as it was not displaying the proper
date formatting and falling back to default
* Option to override the displayed timezone on a per post basis for posts
made at a location other than the default
* Complete Rewrite with improved scoping
* Google Maps is now a provider of static maps
* Maps providers are built with a common interface to allow multiple providers
* Some refinements to the presentation
* Initial Release
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent