Currently we are building a composite locator: Streets, addresses, cities, cities with post codes as an example.
the composite locator works just fine in arcgis pro 3.1.2:
Looking for Berlin gives me 2 results with the Main city Berlin with a rank 1 marked as "A" in AGS Pro:
![RiccardoKlinger_0-1720542097080.png RiccardoKlinger_0-1720542097080.png](https://community.esri.com/t5/image/serverpage/image-id/109210iEBB8081B373D3989/image-size/medium?v=v2&px=400)
The results are sometimes errativ in ArcGIS pro but most often it is just the two results. So far: when I am publishing this service as a gecoode service to my ArcGIS Server the suggest endpoint finds all strange addresses with a "Berlin" in it's name but struggles to use the rank field to provide me with the first city name instead. Yet, the order might be of interest:
![RiccardoKlinger_1-1720542243470.png RiccardoKlinger_1-1720542243470.png](https://community.esri.com/t5/image/serverpage/image-id/109212iD72ED5B4EEDBCE36/image-size/medium?v=v2&px=400)
So, from this perspective I seem to be also more interested in Point_PA (real Adresses) compared to Ort_PA (cities with only city names)
Is the suggest endpoint build to respect the rank of the results?