I have a setup with HyperDB and would like to use WP-geometa. However, I am getting the below errors. Could somebody advise if this is a HyperDB issue or another incompatibility issue. Is there a way to fix it?
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.WP_Buffer_Point_M; expected 3, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.WP_Buffer_Point_Mi; expected 3, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.wp_buffer_point_real; expected 4, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.WP_Distance_Point_M; expected 2, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.WP_Distance_Point_Mi; expected 2, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.wp_distance_point_real; expected 3, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.wp_first_geom; expected 1, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.WP_Point_Bearing_Distance_To_Line; expected 4, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.WP_Point_Bearing_Distance_To_Line_M; expected 3, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.WP_Point_Bearing_Distance_To_Line_Mi; expected 3, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
[02-Apr-2020 20:38:58 UTC] PHP Warning: mysqli_query(): (42000/1318): Incorrect number of arguments for FUNCTION bv_main.wp_point_bearing_distance_coord_pair; expected 4, got 0 in /var/www/wordpress/wp-content/db.php on line 1230
]]>
I have MySQL5.7
The geo tables created by wp-geometa in my setting use B-Tree for spatial indices instead of R-Tree. Is this an intended behavior?
Would it be wise to use R-Tree instead?
Any hint how I could make the plugin multisite compatible?
]]>Hello,
I am using your ACF geometa plugin to store a polygon in the post meta table. This used to work just fine, but now it appears that the geometry type value being stored in the _geo table does not match the geometry type in the geojson stored in the post meta table: Polygon is being store as Multipolygon which breaks my ST_Intersects query:
Post meta:
meta_id post_id meta_key meta_value
27355 4382 delivery_area {“type”:”FeatureCollection”,”features”:[{“type”:”Feature”,”properties”:{},”geometry”:{“type”:”Polygon”,”coordinates”:[[[-478.490295,33.550337],[-478.490295,34.05017],[-477.454834,34.05017],[-477.454834,33.550337],[-478.490295,33.550337]]]}}]}
28282 4384 delivery_area {“type”:”FeatureCollection”,”features”:[{“type”:”Feature”,”properties”:{},”geometry”:{“type”:”Polygon”,”coordinates”:[[[-98.02276611328126,29.572150707406806],[-98.29605102539062,29.466988917717806],[-98.23974609375001,29.367702183906086],[-98.10997009277345,29.355191011573528],[-97.9541015625,29.407189249600243],[-98.02276611328126,29.572150707406806]]]}}]}
28371 4385 delivery_area {“type”:”FeatureCollection”,”features”:[{“type”:”Feature”,”properties”:{},”geometry”:{“type”:”Polygon”,”coordinates”:[[[-98.02276611328126,29.572150707406806],[-98.29605102539062,29.466988917717806],[-98.23974609375001,29.367702183906086],[-98.10997009277345,29.355191011573528],[-97.9541015625,29.407189249600243],[-98.02276611328126,29.572150707406806]]]}}]}
_Geo
Modify meta_id post_id fk_meta_id meta_key meta_value
edit 11 4382 27355 delivery_area MULTIPOLYGON(((-478.490295 33.550337,-478.490295 34.05017,-477.454834 34.05017,-477.454834 33.550337…
edit 12 4384 28282 delivery_area MULTIPOLYGON(((-98.022766113281 29.572150707407,-98.296051025391 29.466988917718,-98.23974609375 29….
edit 13 4385 28371 delivery_area MULTIPOLYGON(((-98.022766113281 29.572150707407,-98.296051025391 29.466988917718,-98.23974609375 29….
(3 rows) whole result
Hi
Can you give an example on how to find nearby points within 1km radius ?
Does your plugin use extra tables other than wp meta ?
Any benchmarks for millions of points ?
Not strictly support (and I think your plugin is fantastic btw).
But any ideas how to find closes post objects to a given point using you plugin when you are on mysql 5.6?
ST_distance returns a distance in degrees which is not very useful and st_distance sphere is not available…
Any help is appreciated as I’d prefere not to have to build custom tables etc and I can do a great circle calculation using plain meta but it will be slow…
]]>