The Wikimaps environment

Overall UX development to combine a maps search, the Wikimaps Warper, the iD editor for the OpenHistoricalMap project with connection back to Wikimedia.

• The wireframes
• Currently involved: User:Susannaanas

Wikimaps Warper: Integrating the tool into OSM iD, access through OAuth, reading from different sources, saving data into Wikimedia projects and OHM.

• Labs instance: warper.wmflabs.org (operating on the maps-warper2 instance)
• Codebase: Mapwarper on Wikimaps Repository on Github
• Currently involved: User:Chippyy

Maps search: Finding maps in Wikimedia Commons. Old maps only or all data and layers? Interface design & front-end development.

Imagining further: Finding out ways to use maps in and outside Wikimedia.

• Collecting maps use cases: Use cases page
• A forthcoming survey
• Technological ideas in the Wikimaps Trello Board

Wikimedia Commons

Template:Map: Work in defining the properties to be used, inclusion in GLAM Toolset, participating in how to include it in the Upload Wizard with the new revisions, using the template with GWToolset, roadmap for transition into Wikidata, discussion with GLAMs

• Resources: Template:Map, Template:Map/Proposal, User:André_Costa_(WMSE)/Template:Map, the properties to be used
• Related bugs: bugzilla:64288
• Currently involved: User:André Costa (WMSE), User:Susannaanas

Wikimaps Gadget: A tool to mark an image as a map in Wikimedia Commons. Providing a link to the Warper.

• Currently involved: User:André Costa (WMSE)

Creating a map locator map for the file page.

• Plan for a map locator map
• Codebase for WikiMaps / Jon Robson
• Demo instance
• Map overlay demo using Leaflet by Zache

Further

OpenHistoricalMap: Changes to iD and Mapnik to allow the display of temporal change, research of connecting OHM data with Wikidata, maintenance of the platform

• Codebase:
• Currently involved: User:Chippyy, Robert Warren, Jaime Lyn Schatz, User:Abbe98

The Wikimaps Nordic project: providing content and use cases, researching needs.

• See the Wikimaps Nordic subpage
• Currently involved: User:Susannaanas, User:André Costa (WMSE), User:Ainali...

Propose topics

You can add topics, and through community discussion we can fit a task into the timeline, connect people, find resources, fit in the big picture. Keep it short, link to another page if it needs a lot of explanation.

Timeline and participation

This is the VERY first draft for the working packages in 2014. The Wikimaps Nordic project can support 5 work phases of approximately one month's duration each during the year.

Work package 1

Work plan for the first Wikimaps development phase (1 / 5)

1. OAuth commons (and also OSM / OHM) OAuth Integration
   • enables the login of a commons user instead of having to create a separate user
   • will assist in the changing pages via the API later on
   • 2 to 4 days
2. OHM integration
   • make easier to digitize from the maps
   • either install iD to be able to digitize the basemap provided
   • craft links so that a warped map can be loaded directly into OHM
   • see best practices from other sites (mapbox for instance)
   • 2 to 3 days
3. Upgrade code base to Rails 4
   • make easier to develop and deploy
   • makes stronger and safer
   • essential need to be done
   • better than re-writing in another language
   • create Vagrant file for other developers to get going quickly.
   • 1 to 1 1/2 week
4. OpenHistoricalMap Support
   • get back up
   • maintenance and general assistance
   • addition of Wikimaps project text to supporters / partners page
   • around 1 week spread over
5. Remove digitizer from codebase into standalone project
   • removes cruft from codebase
   • OHM functionality is replacing the need to have embedded digitizer
   • 2 days

The following task can be carried out to the extent the allotted time allows.

1. Leaflet integration
   • remove old openlayers code
   • replace with better Leaflet code
   • lighter - better mobile support
   • easier to develop upon
   • large task - most code would probably be changed when new interface is developed.
   • around 2 weeks.