Real position outside of LatLngBounds after route calculation (Drop-in UI)

[P-Zenker]

Hey,

I've downloaded your sample project today.

Running on a Google Nexus 6 (Android 7.1.1 | 2560 x 1440 | 5,96 Zoll (large) | 493 (xxxhdpi)) or on a Ulefone Be Touch 2 (Android 5.1 | 1920 x 1080 | 5,5 Zoll (large)) the Navigation View (Drop-in UI) looks like this, after a route is calculated:

As you can see, the real position is a bit further away:

My suggestion is to include either the real position (but then the route start position could be outside of the bounding-box) or to add the real position to the bounding-box too.

PS:
I've made more tests:
Samsung Galaxy S3 (GT-I9300) (Android 4.3 | 1280 x 720 | 4,8 Zoll (large) | 306 (hdpi)) -> bounding box is fine

MOBISTEL Cynus E4 (Android 5.1 | 800 x 480 | 4 Zoll (normal) | 240 (hdpi)) (similar behaviour with Samsung Galaxy S3 mini (GT-I8200N) | 4.2.2)

Best regards,
Patrick

[cammace]

Hey Patrick, thanks for checking out the testapp sample. I assume you are speaking about the camera zooming in too close? The screen you are referring to wasn't actually built out inside the SDK. In the future, we plan to offer an Overview screen for navigation which will handle viewing the entire route and giving the options one would desire before starting a navigation session.

[P-Zenker]

camera zooming in too close

Yes.

Ok, great!