Releases: BrilliantPlugins/wp-geometa-lib
Releases · BrilliantPlugins/wp-geometa-lib
0.3.2
- WP_GeoUtil::is_geom now has a shortcircuit for strings that don't even look like WKT
- Updated documentation!
- WP_GeoUtil::run_spatial_query now uses a non-warning-generating method to detect if a value is spatial or not
- Updated WP_GeoUtil::is_geojson to detect non-GeoJSON without trying to parse it.
- Improved metaval_to_geom
- Improved handling of MySQL geometry function call results, wrapping bare geometry GeoJSON with {"type":"Feature", "geometry": {the geometry}}
- Split out creation of tables from creation of custom SQL functions.
- Added filter to allow plugin devs to include their own custom SQL function files.
- Standardized filter name prefixes to wpgm_ (old filters will stick around for a few versions, even though I don't think anyone is using them).
- Standardized internal callback functions to use the same name as the filter that they're callbacks for.
- Tests are now included and work within WP-GeoMeta-Lib instead of in WP-GeoMeta.
- Allow WP_GeoUtil::get_capabilities to be run without accessing the options table and without caching the results.
- Cleaner loader file, working towards using spl_autoload_register in a future release.
- Only loads geoPHP if it's needed.
0.3.1
First tagged release as a library.
- 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.
- Broke out WP_GeoUtil::geom_to_geojson() to its own function.
- Enhancements to WP_GeoUtil::is_geojson()
- WP_GeoUtil::metaval_to_geom() no longer converts geometry from single to multi automatically.