Each Directions API response should include the provided map boundary by default. Including this in the PolylineResult object would provide an extremely useful access point and save some minor but unnecessary additional processing on the client device.
Additional suggestion, since this library is built specifically to use the GCP Directions API, it would also be great if it used the LatLng object provided here: 'package:google_maps_flutter_platform_interface/src/types/location.dart' by default - instead of a custom implementation. It would reduce boilerplate mapping coordinates between the polyline request and the map itself.
This seems like a simple request from my research, and if I had more time I would submit a PR with the changes. If you agree with this feature request (or both) could you do your best to provide a timeline for release so that I can plan development accordingly.
Thanks for your time, and also for providing this package. :)
See this stack overflow link for reference: https://stackoverflow.com/a/66667385
Each Directions API response should include the provided map boundary by default. Including this in the PolylineResult object would provide an extremely useful access point and save some minor but unnecessary additional processing on the client device.
Additional suggestion, since this library is built specifically to use the GCP Directions API, it would also be great if it used the LatLng object provided here: 'package:google_maps_flutter_platform_interface/src/types/location.dart' by default - instead of a custom implementation. It would reduce boilerplate mapping coordinates between the polyline request and the map itself.
This seems like a simple request from my research, and if I had more time I would submit a PR with the changes. If you agree with this feature request (or both) could you do your best to provide a timeline for release so that I can plan development accordingly.
Thanks for your time, and also for providing this package. :)