Spoken instructions for an arrive step should include the name of the waypoint. In typical SDK usage, the developer supplies a Waypoint.name that’s either the name of a point of interest or an address. The user would find it very useful to hear the address when arriving at the destination. Arriving at a named waypoint is a basic use case, so the SDK should handle it without requiring any developer intervention.
Currently, the arrival instructions come from the Directions API, like any other instruction. In the absence of Directions API support for this feature, the SDK would need to ignore the arrive step’s SpokenInstruction objects in favor of its own homegrown instruction strings. For localization, we have two options:
/cc @mapbox/navigation-ios @mapbox/guidance
Spoken instructions for an
arrivestep should include the name of the waypoint. In typical SDK usage, the developer supplies aWaypoint.namethat’s either the name of a point of interest or an address. The user would find it very useful to hear the address when arriving at the destination. Arriving at a named waypoint is a basic use case, so the SDK should handle it without requiring any developer intervention.Currently, the arrival instructions come from the Directions API, like any other instruction. In the absence of Directions API support for this feature, the SDK would need to ignore the
arrivestep’sSpokenInstructionobjects in favor of its own homegrown instruction strings. For localization, we have two options:/cc @mapbox/navigation-ios @mapbox/guidance