mapbox / mapbox/mapbox-navigation-android
MapBox doesn't have information of most of the sidewalks & crosswalks
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
**Android API: 29**
**Mapbox Maps SDK version: 9.6.1**
**Mapbox Navigation UI SDK version: 1.5.1**
I was exploring **MapBox Direction API** using **Walking profile** and experienced the following issue
**It has been observed, MapBox Direction API doesn't have an information of most of the sidewalks & crosswalks, and therefore, MapBox doesn't consider nearby walkways during navigation, but we can see that sidewalks & crosswalks are actually present using 3D view in Google Maps.**
### Steps to trigger behavior
1. Check Chicago's location based on below coordinates
2. Most of the sidewalks & crosswalks information is not available.
**Location: Chicago, USA**
Start Coordinate - 41.884503160906085, -87.62781068288511
**[Note: There are lot many routes that doesn't have sidewalks & crosswalks in Mapbox Map]**
### Expected behavior
**Mapbox Map shall have information of sidewalks & crosswalks, in order to provide pedestrian & safer paths while using Mapbox Direction API with Walking profile.**
### Actual behavior
As Mapbox does not have enough information on sidewalks & crosswalks, therefore, it doesn't consider pedestrian paths while using Mapbox Direction API with Walking profile. Mapbox draws routes on main streets that is more prone to accidents for Walking profile.

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Mapbox Direction API behavior for the walking profile at the reported Chicago coordinates, using Android API 29 with Mapbox Maps SDK 9.6.1 and Navigation UI SDK 1.5.1. Confirm whether the missing sidewalks and crosswalks are routing-data coverage or an SDK integration issue; done means the cause and an actionable project change are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100