Map View for models

[rclark]

Show the model on a map:

• [ ] Routes
• [ ] Segments
• [ ] Trailheads
• [ ] Points

Basically, each model should expose itself as a Leaflet layer

[davidtheclark]

How about this:

• Trailheads, points, segments, and regions have an active state (triggered by clicking the item, search-inputting a name, or some other means) that involves the following:
  • highlighting the item,
  • opening a popup containing information about the item, and
  • making the sidebar list -- the route list -- display routes associated with the item.
• Routes have two active states:
  • one (very similar to the above), triggered by search-inputting the route by name, involves
  • highlighting the route,
  • opening a popup containing information about the route, and
  • making the route list display routes nearby.
  • two (unique to routes), triggered by clicking a route in the route list associated with a search, involves
  • highlighting the route, and
  • opening the route item in the route list, accordion-style, to reveal more info about;

[davidtheclark]

Mobile map-view idea:

The interactive map itself is a full-screen display and only, really, a full-screen display. This avoids the problem of scrolling around pages with maps that large enough to interact with. User can move and zoom on this map and clicking a feature will open that feature's popup. Each popup has a button to view routes associated with that feature -- opening the route list.

The route list is a different view, then: at the top is a static map showing the active item (this map, if clicked, will re-open the interactive map); beneath it is a view for the active item; and beneath that is the route list. Routes open accordion-style, and part of the info for each route is a static map-image representing it. Clicking this map will also open the interactive map -- this time with the selected route highlighted (everything else, all other interactions, the same).