Extension talk:GeoData
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Filter results server-side? | 0 | 11:56, 17 November 2014 |
| Database error | 2 | 01:18, 21 May 2014 |
| Lua ? | 0 | 14:31, 2 April 2014 |
| Greater distances? | 1 | 02:02, 19 February 2014 |
| Extra parameters | 2 | 17:59, 31 July 2013 |
| Filing a possible bug? | 0 | 13:50, 11 February 2012 |
Hi, I'm using the "geosearch" end-point to find cities at certain coordinates. However due to the limit on the number of search results it happens quite often that no cities are returned in favour of landmarks and other results. It would be great if at least filtering for one/many types of coordinates could be done on the server instead of sending lots of data around.
So, are there already plans for this and would you consider patches for this functionality?
Hi, when I save a page, I get this error:
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: (SQL query hidden) from within function "GeoDataHooks::doSmartUpdate". Database returned error "1054: Unknown column 'gt_lat_int' in 'field list'
Any fix for this?
Yes, I run the update script without any error... seems not to create gt_spatial index. I found a solution to the bug here Bug 62127, but it is not explained how to set up the tables...
Any chance of increasing the maximum search radius? 10km isn't much use in places like Scotland because there just isn't the density of population/articles. I'd happily trade half the maximum number of articles in return for the search radius going up to 30km or even 50km.
What is to do if a name contains spaces or underscores?
I have the same question as Roland. What if the name has spaces or underscores?
Max, the author of the extension, set me right after I submitted an ugly urlencode hack :)
To use spaces and underscores for name, do something like this:
{{#coordinates:40.7820|-73.9660|type:landmark_region:US|name=Central Park Boathouse}}
