It's 1) "cool" - makes Wikipedia look more like the modern cutting edge web and 2) useful - it allows for more target exploring for tourists and such. --Piotrus (talk) 02:52, 26 November 2013 (UTC)
I really like this!
I really like this feature! It's great to see the nearby places of interest and having the pictures in the menu is a great idea.
Two comments:
it's not easily discoverable. I had to spend about a minute looking at the en:London article before I saw it. Places I looked first: (1) the coordinates at the top of the article -- I expected text here, not a Google-like icon, which I didn't see because I wasn't looking for it and it got lost in the cluster of other icons there, and (2) in the text menu at the left side of the page
there's no effective filtering by importance in cases where the number of nearby articles is very largem as is the case for the en:London article. Ideally, there should be some sort of page ranking algorithm to determine the relative importance of nearby articles.
What would you suggest would be a good way of determining importance of nearby articles in this situation? Currently it is purely based on proximity but theoretically I guess we could filter it to be pages which have images / pages which are over a certain length / pages which have been featured (although that said I'm not sure what is feasible) Jdlrobson (talk) 19:22, 26 November 2013 (UTC)
Yes, that's the sort of thing I'm thinking of -- some combination of topic relevance, article quality and distance. Size and precision of features should also play a part here. For example, where an article is about a state, the most relevant articles are probably the nearby states, not, for example, buildings which are near the geographic centre of the state. This is obviously a matter for future research. By the way, I think the recent improvements to the display of this feature are really good. -- The Anome (talk) 12:12, 1 December 2013 (UTC)
What would you change about Nearby Pages?
Latest comment: 10 years ago47 comments24 people in discussion
Is this feature useful? Should we work more on it and use it as the basis to build it into a replacement for tools like Geohack? What's missing?
Close button misleading in current form
The "close" button doesn't work. It just brings me back one step if I've opened a file. It only actually closes the interface if I'm at the main screen. --MarkTraceur (talk) 19:27, 20 November 2013 (UTC)
Yeh the design could be improved here but basically you are creating new windows and closing the top window. Maybe I could make them look stacked to make this clearer. Jdlrobson (talk) 19:05, 22 November 2013 (UTC)
Every article found nearby takes a huge space on screen. Why take up so much space? The distance could have been at the same line as the title, probably it could go first. The icon is fine, but it is necessary? --FocalPoint (talk) 16:30, 23 November 2013 (UTC)
It would be nice to know the radius of the catchment area, i.e. "The following pages are with x meters of the geographical location of y article." It would also be fun to be able to change the radius to increase or decrease the number of pages brought up. Dleit Ḵaa (talk) 02:09, 22 November 2013 (UTC)
I totally agree with this comment. I'm not sure, but I gather that WP must be taking the GPS coordinates for a thing with a very specific point assigned to it and then listing all other entries tied to a point within a certain distance. So, for example, when you open Charleston, South Carolina, the feature directs you to several dozen articles about lots of things (mainly historic buildings). But, when you search for Adams Run, South Carolina (a small town), there is only one tie-in. Assuming that is what's going on in the background, it would be very nice to be able to set the radius at a specific amount. For example, if I were in downtown Charleston, I might want to set the range to just 0.5 miles to see if there are interesting locations nearby. But, if I'm way out in the country in Adams Run, I might want to set the range at 10 miles since I'd probably be in a car. That sort of thing.
Same in Port Morris, Bronx, which has a long list. Better to list the nearest 5 or 10 (fancier, let me choose how many) and say the range. Jim.henderson (talk) 23:29, 24 March 2014 (UTC)
Confusion of what the feature is
In fact I could not see any reaction. I've activated the feature, but where is this feature? How do I access to it. I see nothing. --Parzi (talk) 03:28, 22 November 2013 (UTC)
I've added a screenshot to the feature page hopefully this will help. There is also problems with it not showing in places it should but I'm working on this now Jdlrobson (talk) 19:05, 22 November 2013 (UTC)
If you mean "Show location on interactive map", you first should communicate this on this page, and second translate this button title in other languages than English. Regards Parzi (talk) 03:36, 22 November 2013 (UTC)
It seems geo coordinate templates are inconsistent across projects as on German Wikipedia this format is used (FWIW I actually prefer this formatting):
I'd say don't rely on the template, instead, use the information generated by parser function {{#coordinates}} ? TheDJ (talk) 10:52, 26 November 2013 (UTC)
Maps
It would need to support the case of pages with multiple geographic references, such as lists of monuments in a given area or about a given topic. Klipe (talk) 09:58, 22 November 2013 (UTC)
Actually I'm a bit surprised to see that such a feature is not implemented as a map. I prefer the maps that we can already access from the top right corner (i.e. same location as the Nearby Pages user interface) of geocoded articles on the English and French Wikipedia's, through similar although slightly different features. Alongside with the geographic coordinates, links (globe with a down arrow in en:WP, word "carte" on fr:WP) open pop-ups where the current and nearby Wikipedia pages are located on a map. See for example the page fr:Herbeumont and en:Herbeumont. These features support zooming in and out and mention pages containing multiple coordinates (such as fr:Liste du patrimoine immobilier classé de Herbeumont). The feature on en:WP allows for a short summary of linked pages to appear as overlay and is available also for any coordinates inside a page. The feature on fr:WP is available only for pages geocoded with one set of coordinates, but it provides an option to show thumbnail images on the map. Finally, both provide options to show the nearby pages from Wikipedia's in other languages. These features are not perfect (in particular, none of them is available in "mobile view") but at least they could inspire the designers of the Nearby Pages feature. Klipe (talk) 09:58, 22 November 2013 (UTC)
I agree. This should be made a lot less obtrusive. The WikiLove button on user pages is a good idea of what it should look like. Jackmcbarn (talk) 18:09, 27 February 2014 (UTC)
Replacement? No way!
The question on the top of this section reads ..."Should we"... "use it as the basis to build it into a replacement for tools like Geohack?". My answer is "No way". Even if we are happy on how it works, it is complementary to existing tools and not an adequate replacement. --FocalPoint (talk) 16:18, 23 November 2013 (UTC)
In current form of course it is an inadequate replacement. My concern about this feature is that if you provide yet another button into exploring geo data which will be confusing to end readers. I was curious whether there was an opportunity/motiviation to expand on this feature to do other things that are provided by geohack. Jdlrobson (talk) 19:15, 23 November 2013 (UTC)
First you need to answer - what is geohack? w:Wikipedia:Geohack doesn't answer it well, so I am not even able to answer your question. If you mean the links from GPS coordinates, I'd say no. It's not as useful, not yet; or rather - it does something else. --Piotrus (talk) 02:54, 26 November 2013 (UTC)
They are highly different functions, so cannot easily be compared. I'd say that for most people currently, when they are reading, I think they are interested in 'Where is this thing? show me' (geohack, wikiminiatlas). Nearby as used by this beta feature is more an 'I know where this is, show me other stuff around this'. So I would say: build out OpenStreetMaps/WikiMiniAtlas, use the nearby information to show surrounding articles in that map (WMA already does this). From both of those tools add a link to geohack, to give ppl more mapping options but stop making it the primary entry point. Then use the near by information as input for a separate "related articles" feature. My opinion is that Near by as a feature for a page makes less sense to me. It is a data point that you should feed features with, it is less a feature for a page in itself. Special:Nearby is a feature on it's own (show me what is around me), but nearby on an article isn't/shouldn't. TheDJ (talk) 11:31, 26 November 2013 (UTC)
Thanks for this User:TheDJ. I guess my question was "what would a geoservice" for mobile look like and would this be part of it and you have lots of interesting thoughts around that :-)
When loading, the message "Loading topics near your current location" is shown. This is misleading as it implies that the pages are near where you are, not where the page you are looking at is. Something like "Loading topics near [pagename]" or the current header line ("The following pages are related to [pagename] by their geographical location") would be better:Jay8g (talk) 17:58, 23 November 2013 (UTC)
The non-Vector version is far inferior to the Vector version
The version when using the Vector skin is much nicer than the version when using other skins. It would be nice if they all could use the Vector version. Is there a major reason why they use different versions?:Jay8g (talk) 17:58, 23 November 2013 (UTC)
I thought I had only enabled this feature for Vector but it seems something went wrong. I only wrote the initial version for Vector and it wasn't suppose to be applicable to other skins. I will look at this. Jdlrobson (talk) 19:11, 23 November 2013 (UTC)
It works, mostly, in non-Vector skins, and even seems to have been programmed to work with them (different button text, button placement). It just works less well:Jay8g (talk) 01:33, 24 November 2013 (UTC)
Make it easier to add GPS coordinates to articles
Since this tools relies on GPS coordinates, to make it even more useful, you need to make adding GPS coordinates easier. Even I, an experienced Wikipedian, find things described at w:Wikipedia:Obtaining geographic coordinates way to complex and difficult to do easily. The easiest way would be to code a tool that extracts GPS from Google Maps. Imagine that for articles that are categorized as geographical features and are missing the GPS coords) we would have an (opt-in?) button (red version of the current button) that one's clicked would ask the editor to feed it the Google Map link for that location, then convert it into a coord template. --Piotrus (talk) 03:05, 26 November 2013 (UTC)
Search Radius
I have been trying this on both Wikipedia and Wikivoyage. On Wikipedia it looks useful because there are often other articles about sites within a few 100m of the current one. But on Wikivoyage, it is of limited use, because the next article is usually about a town or city 10km or more away. It would be good if the nearest five pages were listed (maybe with an upper limit of say 200km for isolated islands). --AlasdairW (talk) 23:21, 2 December 2013 (UTC)
More comments
Hi all! Why don't u put all the coordinate data right into the Wikidata, and then make the "Nearby Pages" just access these information there and bring it to the articles on the many Wikipedia or, even better, into OSM maps also! Once in the Wikidata, projects like OSM could easily access them also! Sturm (talk) 21:53, 26 November 2013 (UTC)
I'm sure there are wikidata people looking at doing this at a massive scale. From the frontend it doesn't really matter if the data is in wikipedia or wikidata I think. TheDJ (talk) 22:10, 26 November 2013 (UTC)
Button placement
The button for opening this feature should not be placed directly under the article headline, because it is to conspicuous. It should be placed somewhere at the right side, near the coordinate-section. This feature is also somehow redundant to that one on the GeoHack-site, so I doubt if it should be placed on the article page at all.--Sinuhe20 (talk) 11:30, 24 January 2014 (UTC)
Close button placement
Why is the close button in the upper-left, where (1) it is the first thing the eye sees (for left-to-right language readers) instead of something useful/important and (2) it is unlike roughly every other close button ever? 69.181.106.21820:15, 2 March 2014 (UTC)
Phrasing
"The following pages are related to Pioneer Race Course by their geographical location" - why not the simpler, cleaner "The following pages are about things near Pioneer Race Course"?
What bugs or issues have you found using Nearby Pages?
Latest comment: 10 years ago98 comments56 people in discussion
Note bug fixes will take at least 1 week to surface due to the existing software deployment system.
Button placement
I like the feature. However, I don't think the icon gives enough of an idea as to what it does. I appreciate that, since it is going across projects, text is probably no good. But I feel fairly certain that a better image could be devised. The other thing is that it seems to be only taking co-ordinates from the co-ordinates template. Some articles have the co-ordinates in an infobox instead. FormerIP (talk) 00:52, 22 November 2013 (UTC)
The button overlaps the top icons, especially in featured articles(with the FA top icon). I think the location of the button should be fixed. Or isn't it a problem? Hard to see top icons(protected, FA, GA, etc.) -Priviet (talk) 14:42, 22 November 2013 (UTC)
The placement of the button definitely needs work. There is so many things up there that it makes it hard to know where to put it. Should it maybe be a tab next to Page and discussion? Ideas welcomed. Jdlrobson (talk) 19:07, 22 November 2013 (UTC)
I agree that the icon should not retain it's current placement. That area is already in use by existing UI elements. Kaldari (talk) 15:09, 27 November 2013 (UTC)
I also think that the icon needs to move. As to where - probably just a little to the left (about the icon's width) would do it I think, just far enough so it doesn't overlap other icons.--NHSavage (talk) 23:06, 18 December 2013 (UTC)
I hope this is the right venue, but I thought it worth mentioning that the "near this page" beta feature is interfering with Twinkle's ability to revert to an earlier version of a page. Oddly enough, the "compare selected revisions" button looks different, and then using the "restore this version" button causes the following error to appear: "Grabbing data of the earlier revision: parsererror "OK" occurred while contacting the API." Richard BB (talk) 08:52, 22 November 2013 (UTC)
It seems (in the sense that it works without Nearby, and not with Nearby), that Nearby breaks the category expansion in Category view (achieved through CategoryTree?). Clicking the "+" expander displays “Problem loading data. Please wait a moment and try again.”. (Firefox 25/Ubuntu 12.04). Jean-Fred (talk) 20:46, 22 November 2013 (UTC)
The Nearby Pages icon overlaps with the VisualEditor save button.
When editing a short page, or at the top of a page, using VE, the Nearby Places icon partially covers VE's Save button. FF 25, Mac OS 10.8. The Interior (talk) 23:57, 22 November 2013 (UTC)
In English WP, this new feature produces on my Laptop (Win Vista, Firefox 25.0.1) a semi transparent table containing pictures, names of articles and distances of nearby articles. But this table overlaps large parts of the current article. I switched off all personal modifications in my simple.js and simple.css, but the bug is stil there. — In German WP, this feature doesn't work at all, but produces a bug: After a page is fully loaded, the back links in references (↑) disappear. --DF5GO (talk) 00:10, 23 November 2013 (UTC)
Note: This is likely in monobook. I have had the same issue myself, when on articles with long lists, after scrolling down. Also, as you can also see on that screenshot, the text is very small, probably the typical monobook issue that has affected other extensions. Jay8g (talk) 02:26, 23 November 2013 (UTC)
On ENWP, Vector I also get the backlinks in references sections disappearing. Extraordinary. Took me a long time to find this was the cause. On a hard refresh the backlinks are there and then disappear later on in the page redrawing. With Javascript disabled, the backlinks are OK. Thincat (talk) 17:42, 28 November 2013 (UTC)
Twinkle
Hi again,
Seems either this or Media Viewer feature is causing Twinkle not to work? parsererror "OK" occurred while contacting the API.
All day it's not worked for me & as soon as I disable both beta features it works....
Cheers Davey2010 (talk) 00:42, 23 November 2013 (UTC)
This beta feature conflicts with the English Wikipedia gadget Twinkle. Twinkle attempts to make API requests using $.ajax, however these fail with error code "parsererror".
The reason for this seems to be that this beta feature includes MobileFrontend, which contains the following code (in javascripts/common/api.js):
// TODO: this might be dangerous and cause conflicts with other code
// should we move it to Api#ajax?
$.ajaxSetup( {
url: apiUrl,
dataType: 'json',
data: {
format: 'json'
}
} );
Near this Page is a great feature. It would be enhanced if it indicated whether each page was in my watchlist. That way it can be used to look for relevant articles that are not being monitored. The perfect solution would be a clickable icon (like the little blue/white star in some skins) that allows adding to watchlist without needing to load the whole page first. Zero0000 (talk) 23:22, 23 November 2013 (UTC)
Nearby Pages doesn't work on many wikis: no button to see
It works for me on english WP, but not on german WP: no Nearby button, nothing. Checked it by activating it twice, first time when the beta feature was announced and second time just now (all with cache cleaning), it doesn't show up. Frankly, this is not a tragedy since we already have Kolossos OpenStreetMap tool at the same spot, which provides a map with pointers to articles nearby (for years now!). I rather find the inactivity to support this established and successful OSM tool frustrating, see bug 33980. This should really be prioritized! --Atlasowa (talk) 14:48, 24 November 2013 (UTC)
Cswiki here, doesn't seem to work here either. So what must be changed where so that Nearby Pages can work on cswiki too? As suggested by others, just Extension:GeoData doesn't seem to be the answer. --12:16, 27 November 2013 (UTC), Utar (talk)
Working for some time now. --12:31, 21 January 2014 (UTC), Utar (talk)
Me and my students added coordinates to w:Jewelry Museum. But it tells us "there's nothing nearby", not picking up the city coordinates from w:Iksan (and vice versa). If there's a database lag, this should be noted somewhere. --Piotrus (talk) 03:00, 26 November 2013 (UTC)
Would you have any good ideas on how that should be noted ? I think that we should just make sure the database lag goes down at some point, because I think that a 'note' will not really help us much TheDJ (talk) 13:40, 14 December 2013 (UTC)
Disrupts footnote linking from reflist to article footnotes
Fixed
Normally the numbered footnotes in the reference section have ^ buttons between the footnote numbers and the footnote annotations. These ^ buttons allow us to go to the footnote in the text. When "Nearby Features" is activated, these ^ buttons do not appear. They are useful buttons, and should remain active. I hope you can fix. Thanks. Srich32977 (talk) 06:46, 23 November 2013 (UTC) PS: I'm using my Chrome browser on my Mac laptop. 06:50, 23 November 2013 (UTC)
The same BUG exists in other browsers and in the German Wikipedia, where the more fancy ↑ suddenly disappears. → disabled again. -- 32X (talk) 16:15, 23 November 2013 (UTC)
This HAS NOT BEEN fixed on English Wikipedia as of few seconds ago, I just traced this problem to this extension and was about to report it, but I see it is known. It's rather annoying, I hope this can be fixed quickly. --Piotrus (talk) 05:14, 29 November 2013 (UTC)
A fix has been prepared but it has not been deployed to wikipedia yet as there was no deployment this week during the Thanksgiving holiday in the USA. It will be fixed as soon as the next update to the site occurs. Jdlrobson (talk) 19:19, 2 December 2013 (UTC)
With nearby enabled, i get styling overrides for many of the various buttons throughout the UI.
This is caused by the following block in mobile.bridge module
Especially the border-radius is annoying, since it switches the buttons from the OS default appearance, to a styled appearance (which looks ugly). I'd like my native buttons back please :D TheDJ (talk) 09:42, 26 November 2013 (UTC)
For example when reading the article sv:Dalkarlså and clicking on the Nearby Pages button the article "Dalkarlså" (i.e. the same place) is suggested (but 10 meters away). The exact same thing happens also in other geographical articles in swwp. I am using Firefox 25.0.1 on Windows 7. Best, John Andersson (WMSE) (talk) 14:51, 26 November 2013 (UTC)
Even when it is fixed in the code, the new code still needs to be pushed to the language.wikipedia.org servers. I wonder this to, and asked it twice already, but never got an answer, so here's the question again: When are the bugfixes pushed to the wikis? --2003:63:2F21:B200:410D:736:68DA:274319:51, 3 December 2013 (UTC)
If I have this beta feature enabled, the watch star in the vector tabs of a page, animates with the rotating spinner, instead of the star shaped spinner when you click it to (un)watch a page. This is caused by the usage of !important in the mobile.bridge block:
Clicking the icon automatically scrolls my window to 1 pixel below the top of the view frame. First, it shouldn't be messing with the scrolling to begin with. Second, it's especially annoying that even if you are already at the top of the page, it scrolls 1 pixel down. Using Firefox 25 on MacOS. Kaldari (talk) 15:14, 27 November 2013 (UTC)
I get parse errors constantly when trying to welcome new users; rollback vandalism; or leave user page templates behind since turning the beta on. GenQuest (talk) 17:33, 6 December 2013 (UTC)
fireattack Does this happen all the time ? Does it happen immediately when you open the list, or does it take a short while ? I was not able to reproduce with FF 24.0 TheDJ (talk) 13:30, 14 December 2013 (UTC)
It has a dependency on tablet.styles, which defines: @media all and (min-width:768px){#content .navbox,#content .vertical-navbox{display:inherit} Which creates problems like seen in this screenshot. TheDJ (talk) 09:36, 10 January 2014 (UTC)
Broken full-article links, with span tags leaking into the URL
When I go to Nearby Pages, then click on a page, and then click on "Read this page in full", the link is always broken, because the page name is surrounded in a spurious <span></span> tag. For example, the link to en:Hinds House is generated as https://en.wikipedia.org/wiki/<span>Hinds_House</span>, which obviously doesn't work. I think this only started in the past day or so. --Delirium (talk) 06:22, 11 January 2014 (UTC)
The patch was applied, and if I'm reading things correctly, will be in MediaWiki 1.23wmf12, which is scheduled to be deployed on February 6. --Delirium (talk) 23:12, 30 January 2014 (UTC)
When opened can't get closed
When I open Nearby by clicking the blue button, it won't close, because the cross in the up-left corner is not responding to my clicking. Happens in cswiki, at all pages. I'm on Vector, many beta tools and several gadgets have turned on, and using Firefox 26 @ W7. Contact me at my talk page on cs, if more data is necessary. Thanks for improving Wikis. --YjM (talk) 23:13, 17 January 2014 (UTC)
There's a fix on the current deployment train. It should make it to cswiki on Monday and be fixed then. Sorry for the inconvenience Jdlrobson (talk) 23:24, 17 January 2014 (UTC)
I have a related (?) issue, when I open nearby and click on a link, the next article will open with its own nearby list already open and the dismiss button is not clickable. --DarTar (talk) 05:53, 18 January 2014 (UTC)
Sorry for bothering, but this issue hasn't been fixed so far. So if the fix should have been in the current verion of MediaWiki, then it's not on cswiki yet. --YjM (talk) 21:15, 21 January 2014 (UTC)
When I click on Nearby on the w:London article, I only get one link in the list (w:Timeline of London history), which per se is quite confusing. However, when I go ahead and click on this link, the target page doesn't load and the Nearby list opens with a list and two links with text "Read this page in full" --DarTar (talk) 05:53, 18 January 2014 (UTC)
Incidentally, each of these two links points to a page title wrapped in span tags as noted above.
Slow Unresponsive Scrolling
Even on short articles, I experience very slow, unresponsive scrolling, using GNU icecat 24.0 (unbranded firefox). The effect is much less noticeable in firefox 24.2 ESR; not noticeable in konqueror. So I guess this could also be a JS regression in firefox. Melikamp (talk) 17:38, 9 February 2014 (UTC)
Icon disappears after visiting "View history"
The icon of this function does not show up again after visiting "View history" and coming back to the article itself. I observed this anomalous behaviour in Chrome under Win7 (in Opera it works correctly). Tested on plwiki. Gżdacz (talk) 16:10, 5 February 2014 (UTC)
This tool often produces counterintuitive results.
The first problem is the ambiguity of the notion "near". If the user enters a name of a town, he/she might want to get either the objects inside of the town, which are definitely geographically very close to it, or, quite to the contrary, objects which are not in the town itself (ask yourself "Is Central Park located near New York?" For me the answer is "No, it is IN New York").
The second problem is the technique used to assess what is "near" - calculating the distance between reference points. According to this method, objects inside of a town are located near it, even if it probably contradicts the intuitions of many readers.
However, then there come two basic anomalies of the tool itself.
Small irregular spatial objects.
I did test on pl:Trzemeszno, which describes a small town in Poland, of rather irregular shape. The result is that the list of nearby locations contains interspersed objects inside the town and outside of it. E.g., two nearby villages pl:Niewolno and pl:Bystrzyca (powiat gnieźnieński) appear to be closer to Trzemeszno than the railway station in Trzemeszno.
Large spatial objects.
I did a test on Warsaw. Given the high density of objects in Warsaw, which are described in Wikipedia, the tool produces a list of objects which are close to the reference point (chosen in a more-or-less arbitrary way) rather to Warsaw understood as a whole. So instead of a list of major objects in the town (say: town hall, parliament and government buildings, etc.) I got a random list of locations of minor importance, which appear close to the reference point.
Unfortunately, this isn't fixable with the way articles are currently geocoded in Wikipedia: articles are tagged only with points, and geographical features of different size or shape than small point features aren't distinguished. There is some discussion of medium-term linking to OpenStreetMap shapes that describe larger and/or more complex features (rather than reinventing the GIS wheel in-house). --Delirium (talk) 13:13, 27 February 2014 (UTC)
I know it is not easily fixable. However:
The structure of categories can be of some help. Imagine that an article (in enwiki) is tagged with category Cities and towns in Poland (or a subcategory thereof). Then the tool might look for nearby articles in the same category and in the subcategories of Category:Villages in Poland, only, avoiding listing objects inside of the town. Of course, this would require creating a mapping, assigning to each category that may contain geocoded objects the list of categories in which nearby object should be searched for. Probably an optimal solution would be to create specific (perhaps hidden) categories just for that purpose. Of course, it is a tremendous amount of work, but very much along the lines of Wikipedia: any complaint that the result of the query is not satisfactory could be answered "Anyone can edit Wikipedia. Go ahead and make the corrections". With the present tool we can only answer "Unfortunately, this isn't fixable".
More generally, is it a good idea to release a tool, which is doomed to fall short of the promise its name makes? WMF should answer this question before making the tool default for everybody.
Wikipedia will create articles for individual buildings if they're on a historic register, house famous museums, have received extensive media coverage or are otherwise notable in some manner. Wikivoyage will not. The base-level article in Wikivoyage is an entire mid-sized city. This seems to result in the "nearby" tag finding nothing at all... from voy:Ottawa it doesn't find Hull (voy:Gatineau), from voy:Prescott (Ontario) it doesn't find voy:Ogdensburg - where these are adjacent pairs of towns facing each other across a river. K7L (talk) 15:12, 1 March 2014 (UTC)
I wonder if there's a way to adjust the minimum distance for something to be considered "nearby". From looking at voy:Manhattan/TriBeCa the distance is at least 2.1 km currently, which is fine for Manhattan but not so great for most destinations on Wikivoyage. In fact, I'd daresay it needs to be a sliding scale; 2km, then 10km, then 50km, then 250km, moving up to the next category if none are found at the smallest range. (Also, is there any way to display the distances in feet/miles and not just meters/kilometers?) LtPowers (talk) 13:38, 3 March 2014 (UTC)
Currently the max setting for nearby is 10km of the location unfortunately. It is clear that this is not enough for WikiVoyage. Originally it was capped at this for performance reasons, I poked @MaxSem to see if we can increase the radius for this project to make it more useful.. Jdlrobson (talk) 17:02, 18 March 2014 (UTC)
For the past few days (at least since Monday) the nearby feature is not working for me. I tried two different computers, two different browsers, and several different Wikipedias. Upon clicking on the blue square the windows appears and is stuck on the "waiting" circle clock-like symbol. PS. It's the same problem as reported by Tsca just above, his screenshot matches the problem I am describing. --Piotrus (talk) 07:14, 13 March 2014 (UTC)
How do you use Nearby Pages?
Latest comment: 10 years ago2 comments2 people in discussion
There's a fix on the current deployment train. Some code was leaking from the mobile site into the desktop site. Should be fixed by Monday Jdlrobson (talk) 23:25, 17 January 2014 (UTC)
Latest comment: 10 years ago1 comment1 person in discussion
Now, I'm satisfying with the location of the button, but I think it is better for the button to be a toggle button.-Priviet (talk) 07:09, 13 February 2014 (UTC)
A suggestion
Latest comment: 10 years ago1 comment1 person in discussion
Although there is a "x" button to shutdown the box, I still suggest you to make the blue button able to do this.Click it on,click it off.(A little hard to recognize the "x" button at the first time......)Zhu yihan (talk) 09:10, 23 February 2014 (UTC)
Nearby don't work
I followed the steps for the installation of the nearby, is correctly installed in "version" page but do not see the special page
Fixed 
![[3]](https://www.copy.com/s/WenRakWHtH7d/Szablon_Ewolucja_%E2%80%93_Wikipedia%2C_wolna_encyklopedia_-_2014-01-12_17.33.51.png){kind=link}