It does at least add a useful feature: being able to state a location to search from. The Wikipedia page (unless there is one other than https://en.wikipedia.org/wiki/Special:Nearby that is more flexible) will only work off your current location, which is completely turned off on my work machine. Also upon checking on my phone, even with “desktop site” forced, the map looks to be an additional feasure too.
You can put the coordinates of any location in the URL. One way to get that is in google maps, when you right click and click on the coordinates. Paste it where the coordinates go in the URL and remove the space after the comma.
It appears to limit itself to 50 results though, which only got me results up to 930 m away from the location I picked near me.
I like this feature a lot, but I do not know how it is implemented and whether it would be possible to have users change the range. Maybe it is hardcoded for some performance reason, I have honestly no clue. But I am giving below a few paths that could help one eventually improve the system.
The page https://en.wikipedia.org/wiki/Special:Nearby is powered by the MediaWiki extension https://www.mediawiki.org/wiki/Extension:NearbyPages .
The source code is https://gerrit.wikimedia.org/g/mediawiki/extensions/NearbyPa... (GitHub mirror https://github.com/wikimedia/mediawiki-extensions-NearbyPage... ).
Issues/bugs are tracked at https://phabricator.wikimedia.org/tag/nearbypages/ , it is possible a similar request already exists there.
Do note I am not in the development / product side and I have no view about their backlog or whether they have the bandwidth to review such an incoming review request or a patch.
That extension exposes a public API that allows setting any search radius up to 10 km ( https://en.wikipedia.org/w/api.php?action=help&modules=query... ), so presumably there's no barrier to making the search radius smaller, but maybe there'd be performance issues if you allowed making it larger.
(NearbyPages just embeds a Vue app into the page that makes a client-side fetch() call to invoke that API with a hard-coded radius.)
Now I'm not sure if switching the language pulls in more results or just changes the article language...
Oh, it doesn't try to fall back to geofencing, hmm?