New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which-road-am-I-on is picking up footways when in driving mode #2227
Comments
The current road name label relies on querying the map for the road feature under the user location. Since the style can be arbitrarily customized, Lines 42 to 50 in cd56a39
The line layer needs to have a source layer of
|
We should also investigate whether the SDK is querying for features based on the raw location or the snapped location. In principle, this issue would be much less likely to reproduce if the query point is a snapped location. The filtering above would still help with situations like an elevated rail line running on a viaduct above a roadway. |
It seems to be nearly perpendicular to the road at both endpoints. |
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. |
Street names will be available from NN as part of EH work. cc @mskurydin |
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. |
Android API: Unknown
Mapbox Navigation SDK version: Unknown
Steps to trigger behavior
When navigating, the "current road" label can sometimes show the name of a nearby footway.
In this example, "100 Steps" is referring to this path: https://www.openstreetmap.org/way/166468142 which is adjacent to the road.
Expected behavior
When navigating using a Driving profile, foot-accessible paths should not be considered for detecting the current road name.
Actual behavior
Looks like we're simply picking the name of the nearest map feature to the current position - if there's position error, the displayed name can be incorrect.
The text was updated successfully, but these errors were encountered: