Page MenuHomePhabricator

Define guidelines for positioning map controls
Open, LowPublic

Description

For now we only have a few controls on the map:

  • Zoom In/Out controls
  • Full Screen control
  • Annotations

The four corners available:

Screen Shot 2016-06-03 at 12.38.20 PM.png (363×591 px, 619 KB)

And our actions are positioned this way:

Zoom In/Out-Full Screen
---
--Annotations

However, the map already gets more crowded with the Wikivoyage implementation. The resulting map has :

  • Zoom In/Out controls
  • Explore nearby destinations control
  • Full Screen control
  • Toggle tile layers and overlays control
  • Annotations
  • Scale
Screen Shot 2016-06-03 at 12.39.31 PM.png (361×590 px, 309 KB)
Screen Shot 2016-06-03 at 12.39.31 PM.png (361×590 px, 630 KB)

To bring consistency and make interactive with the map an intuitive and seamless experience, we want to make sure that all controls in a same corner convey a similar category of messages/actions. I think we can sort these as:

  • actions impacting the current map position: zooming in and out, going back to initial position...
  • actions impacting the current map data: toggling layers, changing the data displayed on map...
  • actions not impacting the current map position/data: full screen mode, share a map...
  • informative elements: annotations, scale...

(Please help improving/defining these categories)

As a very first draft, and based on what we seem to currently have, I would suggest:

Actions impacting current position-Non-impacting actions + Actions impacting current data
---
Informative: scale-Informative: annotations

Please share your opinion :)

Event Timeline

I like how Google and Yandex have integrated the scale into the licensing area. Can we do the same?

Suggestion
Merge informative elements in a single footer. Basically show the scale on the same line as the annotation, similar to what other services do:

It would free us some space:

Actions impacting current position-Non-impacting actions + Actions impacting current data
---
--Informative: scale, annotations

Yep. Also, while doing this, lets keep in mind that one of our primary goals is to encourage people to contribute to OSM. So lets think of the best way to do that.

JGirault renamed this task from Define guidelines for positioning map controls to Design - Define guidelines for positioning map controls.Jun 3 2016, 9:05 PM

For WV, I think it might make sense (eventually) to move the nearby articles feature right next to layers, possibly above it. We could even consider moving all navigation controls into the same corner, including zoom, maximize, and undo. The extra data controls (layers, nearby articles) could be optionally shown in a different corner.

Danny_B renamed this task from Design - Define guidelines for positioning map controls to Define guidelines for positioning map controls.Jun 6 2016, 3:35 PM
Danny_B added a project: Design.

Don't forget the globe minimap T136064 that we want to add to the map - users frequently want to know what part of the world they are looking at.

debt triaged this task as Low priority.
debt moved this task from Stalled/Waiting to Backlog on the Maps-Sprint board.
debt subscribed.

Moving to backlog until such time that we can take this up again.

Moving off the sprint board - the Discovery team won't be able to do this work at this time.