high complexity extracted Geographic Map View Confidence: 100%
4
Components
4
Shared
0
User Stories
Yes
Analyzed

Description

The Peer Mentor Map provides a geographic visualization of peer mentor locations within an organization, enabling coordinators to see where their peer mentors are based and identify coverage gaps or concentration. The map renders peer mentor positions using map tiles and supports filtering by status, availability, and certification. This feature is particularly important for large geographic regions where manual matching is impractical and visual proximity aids rapid decision-making for coordinators dispatching assignments or planning coverage.

Sources & reasoning

Lines 99 and 359 directly name geographic map view as a Blindeforbundet need and place it in Fase 3. Fase 3 maps to v1.1 by ordinal position. The blueprint confirms this area at v1.1 phase.

  • docs/source/likeperson.md · line 99
    Geografisk kartvisning av likepersoner for matching og oppdragstildeling (særlig store fylker).
  • docs/source/likeperson.md · line 359
    Geografisk kartvisning (Blindeforbundet)

Analysis

Business Value

Blindeforbundet explicitly identified geographic map view as a critical operational need for matching peer mentors to contacts across large Norwegian counties. Without spatial visibility, coordinators must manually cross-reference address lists to assess proximity, a slow and error-prone process. The map reduces coordinator workload and improves assignment quality by surfacing geographic context directly in the workflow. For organizations operating across sparse rural regions, faster and more accurate matching translates to better service continuity for contacts who depend on a nearby peer mentor. This feature also supports organizational planning by making coverage gaps visually obvious, enabling proactive recruitment.

Implementation Notes

Implementation uses Flutter map widget (e.g. flutter_map with OpenStreetMap or MapBox tiles via MapTileProvider infrastructure component). Peer mentor locations are stored in geographic_locations table and fetched via REST API with coordinator-scoped authorization. The GeolocationRepository abstracts location reads. Module toggle guards this entire area so it is only mounted for organizations with geographic-map-view enabled. WCAG 2.2 AA requires non-map alternatives for all interactive actions (tap-to-select peer mentor must also be accessible via list). Map tile provider must be configurable to allow switching tile sources without code changes. Offline mode should degrade gracefully by hiding the map and showing a list fallback.

User Stories

No user stories have been generated for this feature yet.