Change Details

After the extension of the `geosearch` API to support relevance sort and a follow-up discussion with the search team there was the conclusion that we should rather use the `nearcoord:` keyword from the `search` API to get the results for the nearby feature. See {T309857} and {T306894} So let's change the current implementation to use `search` instead of `geosearch` and filter the area by using the `nearcoord` keyword. See also the POC for this https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Kartographer/+/786847

After the extension of the `geosearch` API to support relevance sort and a follow-up discussion with the search team there was the conclusion that we should rather use the `nearcoord:` keyword from the `search` API to get the results for the nearby feature. See {T309857} and {T306894} So let's change the current implementation to use `search` instead of `geosearch` and filter the area by using the `nearcoord` keyword. See also the POC for this https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Kartographer/+/786847 What still needs to be done to make the POC work is calculating a sane radius from the bounding box data we have about the current map.

After the extension of the `geosearch` API to support relevance sort and a follow-up discussion with the search team there was the conclusion that we should rather use the `nearcoord:` keyword from the `search` API to get the results for the nearby feature. See {T309857} and {T306894} So let's change the current implementation to use `search` instead of `geosearch` and filter the area by using the `nearcoord` keyword. See also the POC for this https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Kartographer/+/786847 What still needs to be done to make the POC work is calculating a sane radius from the bounding box data we have about the current map.