As discussed in the tech call and Jira, this is a backwards-incompatible change for indexing and exposing the full details of a geocoding stop cluster.
You can now search by any of the cluster's elements' name or code and the full cluster with primary and secondary elements is returned.
Note that this doesn't include any special handling of shared stops. Hence they will only become a cluster when they have an identical name and are closer than 100m meter to one another. Also, the primary location is chosen at random.
As discussed in the tech call and Jira, this is a backwards-incompatible change for indexing and exposing the full details of a geocoding stop cluster.
You can now search by any of the cluster's elements' name or code and the full cluster with primary and secondary elements is returned.
An example of the new JSON response is here: https://gist.github.com/leonardehrenfried/7c7140407098b64417c7ffe7506c4139
Note that this doesn't include any special handling of shared stops. Hence they will only become a cluster when they have an identical name and are closer than 100m meter to one another. Also, the primary location is chosen at random.