Community Wishlist Survey 2020/Wikivoyage

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Community Wishlist Survey 2020

Wikivoyage
12 proposals, 16 contributors

Go-previous.svg Wikiversity  •  Wiktionary Go-next.svg

The proposal phase has ended.
Come back on November 20 to vote on proposals!


ContentTranslation work for Wikivoyage

Edit proposal/discussion

  • Problem: Currently, it is not possible to use ContentTranslation in Wikivoyage projects.
  • Who would benefit: The entire Wikivoyage community, new users and editors interested in translating articles from other sister projects.
  • Proposed solution: Make ContentTranslation compatible for Wikivoyage
  • More comments:
  • Phabricator tickets: T106469, T105171
  • Proposer: Hispano76 (talk) 22:27, 30 October 2019 (UTC)

Discussion

  • The comments I made next may not help the project, but it may be very helpful for those who use this gadget/feature to translate: Chinese Wikiyoyage has established the Internal link helper template. --Kitabc12345 (talk) 05:25, 8 November 2019 (UTC)
this template is known as W. But it's not what we're looking for. :) --Hispano76 (talk) 20:10, 9 November 2019 (UTC)

Special page "Nearby" should show an input form and coordinate picker when geolocation is deactivated

Edit proposal/discussion

  • Problem: The special page Special:Nearby works only when geolocation is shared in browsers or with URL options.
  • Who would benefit: Everybody who looks for articles around a given position
  • Proposed solution: When geolocation ist deactivated in browsers the Special page Nearby thats available in wikis like Wikivoyage shows nothing, just an error message. It should show a form to type in coordinates or a page name instead and additional a coordinate picker to click on a map and select the coordinates. The Special page does understand URL parameters like https://de.wikivoyage.org/wiki/Spezial:In_der_Nähe#/coord/51.783214,14.316816 or https://de.wikivoyage.org/wiki/Spezial:In_der_N%C3%A4he#/page/Cottbus but it's very unhandy and user normally do not know the syntax. This special page is very prominent placed in the main menu on the mobile version and it's probably often used, but not everybody shares the location in the browser. And as a side effect you can search for pages around a position that differs from your own location. Maybe to prepare a journey, get a list of temples (if their articles exist) around a point without knowing their names.
  • More comments:
  • Phabricator tickets:
  • Proposer: DerFussi 07:54, 27 October 2019 (UTC)

Discussion

Kartographer improvements

Edit proposal/discussion

  • Problem: The development of the Kartographer tool should be continued. Beside the phabricator tasks noted below the there are some additional wishes. (1) The computing time for <maplink> calls should be reduced especially for the use with Lua. (2) Showing user's position at the map; adding a button to move the map to the user's position. (3) Adding a zoom-level control to maps. (4) The Wikivoyage mode should be available at all wikis. (5) Make mapframe available for all flagged-revs Wikipedias.
  • Who would benefit: All wikis including Wikipedia, Commons, Wikidata, Wikivoyage, etc.
  • Proposed solution: Additions to the Karthographer extension.
  • More comments: It is very difficult to estimate the developing time. But the Kartographer should be permanently improved.
  • Phabricator tickets: T141715, T141335, T140083, T180909, T192334, T190069, T190067, T190064, T190062, T183770, T183766, T191585, T208713
  • Proposer: RolandUnger (talk) 18:46, 10 November 2019 (UTC)

Discussion

Show user's current location on maps

Edit proposal/discussion

  • Problem: On Wikivoyage, when using mapframe embedded maps, it is difficult for the user to find their current real-life location on the map.
  • Who would benefit: Users using Wikivoyage while traveling, especially mobile users.
  • Proposed solution: Provide an option, maybe an icon to click, to indicate the user's current location.
  • More comments: This is an obvious feature which users expect, and not having it makes the maps significantly less useful.
  • Phabricator tickets: T208713
  • Proposer: Mx. Granger (talk) 23:35, 1 November 2019 (UTC)

Discussion

  • Weak support. I'm not a big fan of geo-tracking and I don't really use mobile devices but this is definitely a hi-value feature for travelers to opt into. Even as someone who wouldn't use a Wikivoyage smartphone app while traveling, I can tell this is something that would be very handy. —Justin (koavf)TCM 19:40, 2 November 2019 (UTC)
  • This looks useful. I regularly use a local public transport apps which have similar features, and I can easily see nearby bus or tram stops; it would be very useful to find nearby museums or cafes when exploring a strange city. It would also encourage readers to keep the Wikivoyage page open when they walk to a location, rather than switching to a map app. Users can configure geo-tracking on their phone to allow or not allow a particular browser to get locations information, and the wiki could have a preference to opt out for readers who have logged in. AlasdairW (talk) 00:05, 5 November 2019 (UTC)
  • This has been desired by User:Traveler100 for a while. I support. SelfieCity (talk) 12:55, 9 November 2019 (UTC)
  • A must for a site about locations. Most users of the web are today from mobile devices, this is an expected function. Also not having this forces the use of other mapping applications. --Traveler100 (talk) 05:57, 10 November 2019 (UTC)

Wanted (by articles) pages

Edit proposal/discussion

  • Problem: Difficult to easily see what pages are really missing on the site. Current Special:WantedPages such as voy:Special:WantedPages shows a list that are mainly red links on talk and project pages not main space article pages. Takes a lot of clicking to see which pages are really needed.
  • Who would benefit: Article authors looking for ideas for pages to create. Clean-up contributors looking for problem links.
  • Proposed solution: Create a page similar to Special:WantedPages but the number of redlinks shown to only be from mainspace pages and not talk and admin pages. One alternative idea is to make the existing page a table with a column showing number of redlinks from each namespace type (mainspace, talk of article, user page, template, ....) and make it possible to reorder the table based on descending number of each source page type.
  • More comments: This is not about filtering the page type of the wanted pages but of the namespace of the source of the redlinks.
  • Phabricator tickets: T208935
  • Proposer: Traveler100 (talk) 06:18, 10 November 2019 (UTC)

Discussion

Permanent update of Wikivoyage nearby-articles data files necessary

Edit proposal/discussion

  • Problem: In order to show nearby articles on maps used at Wikivoyage JavaScript data files at tools.wmflabs.org like https://tools.wmflabs.org/wikivoyage/w/data/en-articles.js are needed by the Karthographer.js. This text file should be updated monthly or better daily.
  • Who would benefit: All Wikivoyage branches.
  • Proposed solution: The list of all articles with the coordinate and a representative image can be retrieved from the wiki's database. A cron job to update these text files should be started maybe daily. This solution does not need much computing time. A smarter way is to get this information at the process of setting-up a map and the change of zoom level in nearby mode both from the wiki's database and Wikidata.
  • More comments:
  • Phabricator tickets: T203313
  • Proposer: RolandUnger (talk) 17:49, 10 November 2019 (UTC)

Discussion

Correct pdf converter

Edit proposal/discussion

  • Problem: We need correct pdf converter
  • Who would benefit: Wikivoyage's guides users
  • Proposed solution: with title, without junk, correct convert maps
  • More comments:
  • Phabricator tickets:
  • Proposer: Digr (talk) 17:32, 10 November 2019 (UTC)

Discussion

Digr, thank you for this wish! Can you provide more information on why Wikivoyage needs a correct pdf converter? It would be great to receive more information and background on this wish. Thank you! --IFried (WMF) (talk) 03:24, 11 November 2019 (UTC)

Comments in Local Time

Edit proposal/discussion

  • Problem: Please add Comments in Local Time to Wikiyoyage. It also adds the day of the week to dates and uses common phrases to describe dates.
  • Who would benefit: In this way, the user can easily access the relevant information in this board.
  • Proposed solution: Source Code
  • More comments: Thank you!
  • Phabricator tickets:
  • Proposer: Kitabc12345 (talk) 06:07, 25 October 2019 (UTC)

Discussion

  • What prevents you from localizing? Winged Blades of Godric (talk) 13:19, 25 October 2019 (UTC)
  • Hi Kitabc12345! Thank you for the proposal. Could you provide more details around the problem? This would help us have a better understanding of the general proposal. Basically, what are the main reasons why you want to add Comments in Local Time to Wikiyoyage? Thank you! --IFried (WMF) (talk) 19:01, 25 October 2019 (UTC)
  • Hi IFried (WMF)! I think travelers (page viewers) in different time zones can more easily know when Wikivoyage volunteers will answer travel-related questions for travelers (page visitors) in order to accurately find the latest information. Kitabc12345 (talk) 09:28, 26 October 2019 (UTC)
  • In addition, on the discussion page and Travellers' pub, anyone can check the Wikivoyage volunteers' review time more conveniently and accurately. Simply put, this is just to help anyone use it more conveniently. Kitabc12345 (talk) 09:27, 26 October 2019 (UTC)
  • Create "User:Kitabc12345/common.js" over English Wikivoyage and add importScript('User:Winged Blades of Godric/comments in local time.js');; I guess this is resolved. Winged Blades of Godric (talk) 04:53, 29 October 2019 (UTC)
  • Thank you! Kitabc12345 (talk) 10:17, 29 October 2019 (UTC)
  • I asked you to copy the quoted phrase verbatim; not interpret my words. The content shall be precisely same, as over here. Winged Blades of Godric (talk) 12:37, 30 October 2019 (UTC)
  • I guess the original issue is resolved; what more do you seek? Aren't you seeing the time-stamps in your local browser-time? Winged Blades of Godric (talk) 14:38, 2 November 2019 (UTC)
  • Very Thank You!!!!!!!!!!! :P Kitabc12345 (talk) 10:17, 3 November 2019 (UTC)
  • But, I'm are Chinese user. I can't see this feature in the language I use. Also, how do I put this component in Gadgets? —The preceding unsigned comment was added by Kitabc12345 (talk)
  • Check out the little guide under "LOCALIZING THIS SCRIPT" and accordingly incorporate the Chinese names. Winged Blades of Godric (talk) 14:28, 5 November 2019 (UTC)
  • Why do you expect the folks at en-wikivoyage to agree to some gadget showing Chinese preferences? Winged Blades of Godric (talk) 14:28, 5 November 2019 (UTC)
  • I think travel websites should be personalized for people in different time zones and even different countries. English is a universal language and is the official language and common language of many countries and regions in the world. Some languages ​​have not yet done a Wikiyoyage project, and travelers need to access the material in a second language (English) they may know. Therefore, I really think this gadget is very useful. --Kitabc12345 (talk) 05:16, 8 November 2019 (UTC)

Creating a coordinate picker

Edit proposal/discussion

  • Problem: Authors need external tools to get a coordinate.
  • Who would benefit: All wikis which use coordinates.
  • Proposed solution: The picker should be written in Javascript. So it is possible to use it both as a standalone application and a Javascript function by other Javascript scripts. This app should be able to accept an empty string or an address. It should open a Karthographer map with a search field for addresses. Both the OpenStreetMap data set and Wikidata should be used for search (in case of OSM dataset like OSM's Nominatim). Additionally, the user should be able to move the map to adapt the position. The final position should be copied either to the clipboard or returned as a function result.
  • More comments:
  • Phabricator tickets:
  • Proposer: RolandUnger (talk) 18:03, 10 November 2019 (UTC)

Discussion

Importing non-GeoJSON map data to Wikimedia Commons

Edit proposal/discussion

  • Problem: All map data at Wikimedia Commons is stored in GeoJSON format. This format is not supported by many GPS devices. The import and export of common map formats like GPX and KML/KMZ to Commons and Wikidata should be added.
  • Who would benefit: Wikimedia Commons and all wikis that use Kartographer.
  • Proposed solution: Maybe as WMF Labs tools.
  • More comments:
  • Phabricator tickets: T55023, T154908, T137677, T216601, T28059
  • Proposer: RolandUnger (talk) 18:59, 10 November 2019 (UTC)

Discussion

Better fallback handling in Kartotherian's language selection

Edit proposal/discussion

  • Problem: Locations should be shown in the user's language. This is working but only if a location name is given in the OpenStreetMap (OSM) database just in the user's language.
  • Who would benefit: All Wikis which are using Kartographer and Kartotherian.
  • Proposed solution: In multiple steps, we should look for suitable labels in OSM database.
  1. Search for a label in the user's language.
  2. Search for labels in the same writing system like the user's language. For instance, French language uses the same system like English or German, Bulgarian the same like Russian or Ukrainian, Farsi the same like Arabic.
  3. In case of multiple results we select the language of the biggest weight.
  4. Additional fallbacks could be English or French labels because many readers can read and speak these languages.
  5. Last fallback is the official language -- like now.

Discussion

Add maps of sightseeing spot to help visitors find nearby sightseeing spots and information through maps

Edit proposal/discussion

  • Problem: Although we have “What's nearby?”, we can't meet the map class to find nearby attractions and information.
  • Who would benefit: When someone using map of Wikivoyage on tour road. Any reader on mobile wanting to see what Points of Interest are nearby.
  • Proposed solution: We can follow the map of the sightseeing spots of the backpacker. After the click sightseeing spots, there will be local article information to help visitors find their destination. Also see WikiShootMe.
  • More comments: Add maps of sightseeing spot to help visitors find nearby sightseeing spots and information through maps. This is a functionality any mobile user would expect. Other apps do this. Stops Wikivoyage becoming popular with mobile users, which is the largest group of internet accesses.
  • Phabricator tickets: phab:T208713
  • Proposer: ✈IGOR 〒 Tell Me What?! . Wikivoyager 15:18, 24 October 2019 (UTC)

Discussion

Little gimmick related to your proposal: https://tools.wmflabs.org/wikimap/?commons=false&project=wikivoyage&lang=zh&lat=24.82&lon=120.98 --DB111 (talk) 11:44, 25 October 2019 (UTC)
Yes, We will need like this Little gimmick, but Wikivoyage logo is wrong, by the way, if can display any listing point and information on map, I think the little gimmick is good idea.-- ✈IGOR 〒 Tell Me What?! . Wikivoyager 15:30, 25 October 2019 (UTC)
Thank you, I have to admit that it is originally a Wikipedia tool, but you're right, I fixed this. --DB111 (talk) 21:13, 26 October 2019 (UTC)
@DB111: In fact, The wmflabs have a good function is Show me where I am, but I think any point not only point name, It can add to also name, URL, E-mail, Address, Directions, Phone, Tollfree, Fax, Hours, Price and Content etc. (e.g See section of Wikivoyage). In other words, all the parameters in the list item are displayed on the map. This is convenient for tourists to use the mobile phone's Wikivoyage map to find nearby attractions or stores on the road, and click on the Point to see the contect of List items, this function is very practical and convenient. This feature is equivalent to the map of the backpacker.-- ✈IGOR 〒 Tell Me What?! . Wikivoyager 13:02, 27 October 2019 (UTC)
In addition, we can also refer to the interface design of Google Earth, we can meet the map class to find nearby attractions and information. Kitabc12345 (talk) 13:41, 25 October 2019 (UTC)
I think the most important enhancement that is needed is to have current position marked on dynamic maps in article pages (mapping listings not cities on map with users position also marked). Particularly important as most web users are now mobile users, and knowing what is near you is a crucial feature for any travel/location guide. --Traveler100 (talk) 13:58, 27 October 2019 (UTC)
However, the Point on the current map is only the picture and the name, but there is no related Point content. I think this is too rough and inconvenient. I think let the tourists only know the name and appearance of the Point, but they don't know what it is. If this is the case, at least when the visitor clicks on a nearby Point, at least the link to the list item information is required(Click Name link, It will to someitem list on local article), so that the relevant content of the Point can be known. -- ✈IGOR 〒 Tell Me What?! . Wikivoyager 14:21, 27 October 2019 (UTC)