Page MenuHomePhabricator

Special:Nearby shows no results on rowiki
Closed, InvalidPublicBUG REPORT

Description

See https://ro.wikipedia.org/wiki/Wikipedia:Cafenea#%C3%8En_apropiere . Verified on FF on Android and Windows, confirmed not working.

@Aklapper can you please help redirect to the correct team?

Quiet out here... There weren't any pages found with nearby topics.
Try creating a new page or adding location to an existing one

Event Timeline

Strainu updated the task description. (Show Details)
Aklapper renamed this task from Special:Nearby not working on rowiki to Special:Nearby shows no results on rowiki.Apr 8 2022, 3:32 PM
Aklapper edited projects, added NearbyPages; removed MediaWiki-General.
Aklapper updated the task description. (Show Details)
Jdlrobson subscribed.

Nearby is working fine. Geodata API is returning no results.

Is rowiki using the parser function in its coordinate templates?
https://www.mediawiki.org/wiki/Extension:GeoData#Usage

Is the wiki using the {{coordinates:}} parser function in its coordinates template or infobox or such?
Each page has to tell the coordinates in a machine readable format, which is done by the coordinates parser function of the GeoData extension
as linked from https://www.mediawiki.org/wiki/Extension:NearbyPages:

Special:Nearby
The page Special:Nearby lists articles that are geotagged nearest to the user's current location, as provided by their browser.

with a link to GeoData extension behind "geotagged" - https://www.mediawiki.org/wiki/Extension:GeoData

According to the database there is no much about coordinates, only from some local files

[rowiki_p]> select count(*) from geo_tags;
+----------+
| count(*) |
+----------+
|     1283 |
+----------+
1 row in set (0.00 sec)

[rowiki_p]> select page_namespace, count(*) from geo_tags left join page on page_id = gt_page_id group by page_namespace;
+----------------+----------+
| page_namespace | count(*) |
+----------------+----------+
|           NULL |      203 |
|              6 |     1080 |
+----------------+----------+
2 rows in set (0.01 sec)

Compare with enwiki:

[enwiki_p]> select count(*) from geo_tags;
+----------+
| count(*) |
+----------+
|  2395461 |
+----------+
1 row in set (1.40 sec)

[enwiki_p]> select page_namespace, count(*) from geo_tags left join page on page_id = gt_page_id group by page_namespace;
+----------------+----------+
| page_namespace | count(*) |
+----------------+----------+
|           NULL |     1489 |
|              0 |  2188269 |
|              1 |     8753 |
|              2 |   134410 |
|              3 |    10288 |
|              4 |    12299 |
|              5 |     1450 |
|              6 |     2386 |
|              7 |       30 |
|              9 |        1 |
|             10 |     9388 |
|             11 |      512 |
|             12 |        1 |
|             14 |     1273 |
|             15 |     1437 |
|            100 |    14990 |
|            101 |        1 |
|            118 |     1040 |
|            119 |        8 |
|            828 |     6478 |
|            829 |      958 |
+----------------+----------+
21 rows in set (41.50 sec)

It is a up to the local wiki community to make the nearby search working.

It used to call the parser function. Apparently I broke that a while ago, while moving to maplink, likely because my unserstanding was that maplinks also add the coordinates to the database - something i can't find any docs about today.

Closing since the count in the database is increasing. Thanks for your help.