Open shreya-ja opened 3 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This is a data issue in OpenStreetMap rather than something specific to the Android navigation SDK. I’ve invited OSM community members to contribute more sidewalks in OSMUS Slack (invite yourself), but unfortunately there’s nothing else we can do in the navigation SDK itself in this repository.
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
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.