gistfile1.md

Website

• (John F) Make map more central to the web design
• (John F) Bring in more map tools, like openstreetbugs

Toggle between two versions, with clear purposes: 1) big map (default if not logged in). 2) activity feed (default if logged in).

Exporting / Extracting:

• Tools for taking / reusing OSM data and maps (everything from shapefiles to vector shapes)

• Export function needs design attention

• Is the bounding box -> export workflow even the right approach?

• User friendlier UI is something everyone is concerned about

• (Richard) Tools for importing large pre-existing datasets

  • Hand-curated, deliberate way.
  • There are No tools for managing/merging external vector datasources.

Social Features

• Integration with external sites vs. better community tools?
• Show who is mapping where
• OWL (OpenStreetMap watch list) shows edits
• live.openstreetmap.fr
• mapper to mapper communication
  • mailing lists are archaic and behind the scenes, so is private messages
  • Comment system
• Community/team landing pages?
• Rethink activity feed
  • There are notes somewhere (?)
• Diary? What is this? Rebrand?
• Translation is a challenge. Site copy needs to be in 74 languages
• 1/3 of users have made an edit?

Editor

• API the #1 first step, most important step. Allow people to build editors.
• iD Editor
  • Port internals from Potla 2 into Javascript
  • Make this a full-featured editor, more approachable, more intuitive
  • Very early
  • Needs to be easy for newbies to use
  • Needs deliberate UX work
  • Fork and have a play around
• Starts simple, sacrifice accuracy for simplicity. Enable advanced tools later.
• Sandbox in a contained situation

I need to spend time with all of these editors.

• Redesign a user friendly, more targeted interface for documenting tags