nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

When I use Locator to search for intersections, why do I get less search results at ArcGIS Runtime than ArcGIS Pro?

YongYao

I package a mmpk including locator.

When I use ArcGIS Pro - Locate panel to search street intersection, I expect to get the same result in the program written based on ArcGISRuntime.WPF 100.1.0.

I found all of the intersections in ArcGIS Pro. However just a little above half of the intersections can be found in the program.

Any suggestions for how to find the issue?

Najděte více příspěvků označených jako

Accepted answers

MaraStoica4

I am looking into this trying to replicate it and I am finding some discrepancies myself between the Pro and Runtime results. Pro seems to require less information to return all the results. In my test locator, if I use just the address, Pro finds 4 results, while Runtime doesn't find any. Once I add the city, Runtime also finds 4 results. Could you maybe try to adjust your search string to include more information? Does that change the results you receive? In the meantime I'll keep researching this, see what I can find out.

All comments

MaraStoica4

Hi Sara,

Could you post the code where you're calling the locator please.

Mara

YongYao

var geocodeParams = new GeocodeParameters();
geocodeParams.OutputSpatialReference = SpatialReferences.Wgs84;

IReadOnlyList<GeocodeResult> addresses = await locator.GeocodeAsync(userTypedAddress, geocodeParams);

foreach (GeocodeResult match in addresses)
{

...

}

MaraStoica4

YongYao

Hi Mara, thank you for your reply. It really helps. And I am able to explain this weird issue to customers.

In my case, even I add the city name, it doesn't change the result.
If you find out any other tricks can help locator get more result in Runtime, please let me know. Thanks.

edit.PNG

DritanZhuja

Hello Mara,

Based on this discussion, has there been any work to match the ArcGIS Runtime locator requirements to that of ArcGIS Pro? If so, could you please provide the BUG or ENH number where this work is being tracked.

MaraStoica4

I believe a workaround was found for this issue by disabling measures on ROADCENTERLINE feature class and rebuilding the locator.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.