WP-GeoMeta

A spatial foundation for WordPress. Store and search spatial metadata like you do any other metadata, but using MySQL spatial indexes. WP GeoMeta lets you take advantage MySQL's spatial data types and spatial indexes when storing and searching spatial metadata. It detects when GeoJSON metadata is being stored, and transparently stores a copy in a spatial meta table. WP GeoMeta also adds support for spatial search operators. When a spatial search operator is used, WP GeoMeta will make sure that the spatial table is used, taking advantage of indexes and spatial relations. WP GeoMeta isn't just a plugin, it's also a library which other plugins can take advantage of. It's meant to be a spatial platform that other GIS and mapping plugins can build on to allow spatial interoperability between plugins.

Install this plugin in the usual WordPress way, then go to your WordPress dashboard to Tools::WP GeoMeta to see the status of your spatial data and to use the included tools.

1. Upload the plugin files to the /wp-content/plugins/wp-geometa directory, or install the plugin through the WordPress plugin screen directly.
2. Activate the plugin through the 'Plugins' screen in WordPress.
3. Go to Tools::WP Geometa

0.3.4

• Fixed accessing property of null object on dashboard.
• Added GeoJSON import utility.
• Use and detect hashes in dashboard URL so page reload can go back to original tab.

0.3.3

• Updated wp-geometa-lib to 0.3.3
• Updated Readme
• Updated documentation and copyrights to reflect company name change from Cimbura.com to LuminFire
• Tested with WP 4.8

0.3.2

• Not released on WP.org
• ???

0.3.1

• Support for custom MySQL functions (User Defined Functions and stored functions).
• Built-in support for some functions which may be useful for working with Lat/Lng distances and bearings.
• Fixed issue where duplicate function names would appear in get_capabilities result set.
• Fixed OSM tiles to not be hardcoded to http://
• Added button to rebuild known spatial function list cache

0.3.0

• Moved core functionality to a library (wp-geometa-lib) so it can be used in other plugins.
• Most of the previous changelog is no longer applicable to this plugin, but to wp-geometa-lib
• Fixed issue that made plugins using WP-GeoMeta as a library to be activated twice.

0.2.2

• Added built-in support for the WordPress Geodata standard
• Added filter and action to handle arbitrary lat/lng pair metavalues
• Added documentation for hooks and filters
• Leaflet is now loaded locally instead of from the CDN

0.2.1

• Handle multi-feature GeoJSON correctly in MySQL 5.7 (convert to GEOMETRYCOLLECTION)
• Use ON DUPLICATE KEY UPDATE to combine added and updated postmeta handlers.

0.2.0

• Upgrading no longer truncates and rebuilds the meta tables.
• Fix for joins so user meta should work again (umeta_id vs meta_id key name issue).
• A beautiful dashboard!
• Plugin activation hooks so that deactivating/activating without upgrading will recreate database tables
• Translation ready!
• Portuguese translation!
• Code documentation!
• Changed geometry type so that all geometries are stored as multipoint to work across MySQL versions

0.1.1

• orderby should now work
• Much cleaner joins
• Minor fix for when upgrades occurs

0.1.0

• Will now work as a library or a plugin.
• Additional functions for getting data back into GeoJSON format.
• Working well enough to submit to the plugin repo.
• Support for single geometry functions in meta_queries.

0.0.2

• Improved meta query capabilities. Now support sub queries, and uses standard meta-query syntax
• Whitelist of known spatial functions in meta_query args. Allowed args set by detecting MySQL capabilities.
• We now delete the spatial index on activation so that we don't end up with duplicate spatial keys
• Populate geo tables on activation with any existing geojson values
• Submitted ticket to dbDelta SPATIAL INDEX support: https://core.trac.wordpress.org/ticket/36948
• Conform to WP coding standards
• Explicitly set visibility on properties and methods

0.0.1

• Initial Release