mapbox / mapbox/mapbox-navigation-ios

Is it possible to get the street name when using walking navigation directions?

Open
#4,318 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
918
Forks
326
Avg merge
1h 16m
Merged PRs (30d)
3

Description

When using the default (driving) profile identifier, the primary instruction of the NavigationViewController displays the name of the street where the user will need to make a maneuver (ex: "Divisadero Street"). However, when using the walking profile identifier, the primary instruction no longer provides this information (ex: "Turn left onto the walkway").

Is it possible to have the visual instructions provided for walking emulate the driving instructions and tell the user the street/location at which they need make their next maneuver? How can I get the street information when using the walking profile?

Driving directions:

Walking directions (for the same route):

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the NavigationViewController visual-instruction behavior described in the issue and compare the same route under the driving and walking profile identifiers. Trace where the primary instruction is produced and whether street information is present in the walking route data. Done means walking instructions expose the next maneuver's street or location consistently, with coverage for both profiles.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.