IssueTracker

We are attempting to generate directions links for surgeon practices. We use lat/long coordinates, which usually works, but for some surgeons when the link is followed, a different nearby business is tagged. To address this, we tried adding the destination_place_id parameter, but this seems to be ignored when lat/long coordinates are used in the destination parameter.

Example 1:

https://www.google.com/maps/dir/?api=1&destination=32.7112689%2C-97.3985882

This link with only coordinates should produce directions to "Kirby Plastic Surgery: Emily J. Kirby MD, 5075 Edwards Ranch Rd, Fort Worth, TX 76109, United States" but instead displays the nearby "Bria McDowell, REALTOR - Monument Realty, 5049 Edwards Ranch Rd 4th Floor, Fort Worth, TX 76107, United States".

Example 2:

https://www.google.com/maps/dir/?api=1&destination=32.7112689%2C-97.3985882&destination_place_id=ChIJqersTkJtToYRAd4GylftLnQ

With the addition of the destination_place_id for Kirby Plastic Surgery, it should tag that instead of Bria McDowell, but the latter is still tagged.

Example 3 & 4:

https://www.google.com/maps/dir/?api=1&destination=32.711307836223%20-97.398577676092&destination_place_id=ChIJqersTkJtToYRAd4GylftLnQ

https://www.google.com/maps/dir/?api=1&destination=x&destination_place_id=ChIJqersTkJtToYRAd4GylftLnQ

If we encode the lat/long improperly (here with %20 as the separator rather than the %2C that is indicated in the documentation), or with a nonsensical destination (such as "x"), then the destination_place_id gets used, and the correct place is tagged.

It is unclear why the destination parameter is required when destination_place_id is provided, as the destination_place_id sufficiently identifies the desired location. In this case, it also appears that the destination parameter clobbers the destination_place_id if destination has been specified using lat/long coordinates.