- RfC draft for the old maps working process
- Wikimaps Trello collaborative planning
- Future Wikimaps Hangouts and documentation of past events
2014: Design & Development
These are the activities outlined for the project for the year 2014, with people who are working on the topics. Please add your name if you wish to be participating.
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.
Wikimaps Warper: Integrating the tool into OSM iD, access through OAuth, reading from different sources, saving data into Wikimedia projects and OHM.
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.
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
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.
OpenHistoricalMap: Changes to iD and Mapnik to allow the display of temporal change, research of connecting OHM data with Wikidata, maintenance of the platform
The Wikimaps Nordic project: providing content and use cases, researching needs.
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.
|WP1||Wikimaps Warper: OAuth, OHM integration, code refactoring. OHM: Basic setup||2014||User:Chippyy|
|WP2||Warper & iD & Search UX, design task||2014||User:Susannaanas|
|WP3||Warper upgrade, development||2014||User:Chippyy|
|WP5||GLAM-Wiki Toolset Integration + other housekeeping||2014||User:Artturimatias|
|FOSS OPW||OHM: Time slider for the iD and OHM website||Example||Jaime Lyn Schatz, Robert Warren|
|Nordic SE||Template:Map||Ongoing||User:André Costa (WMSE)|
|Nordic SE||Wikimaps Gadget||Ongoing||User:André Costa (WMSE)|
|Nordic EE||Nordic map project: Tartu||Ongoing||WMEE|
|Nordic FI||Aerial images tools study||2014||WMFI, City of Helsinki, Finnish Land Survey|
|Nordic FI||Wiki Loves Maps & #Hack4FI||February–March 2015||WMFI, City of Helsinki, AvoinGLAM.fi|
|Nordic SE||Nordic map project: Umeå||December||WMSE|
Work packages, plans and follow-up
Work package 1
Work plan for the first Wikimaps development phase (1 / 5)
- 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
- 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
- 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
- OpenHistoricalMap Support
- get back up
- maintenance and general assistance
- addition of Wikimaps project text to supporters / partners page
- around 1 week spread over
- 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.
- 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.