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; } } }

magicKey doesn't work with custom composite locator

LeonZhong

Hi,

I published a composite locator from arcGIS Pro to ArcGIS server. Everything looks fine except magicKey.

For example, first call sugguestion:

Then call findCandidate:

I just copy the text from suggestion to SingleLine and also copy magicKey as well.

Anybody has same issue before?

Thank you,

Leon Zhong

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

Accepted answers

BradNiemand

Thanks everyone for the feedback. You have uncovered an issue with composite locators that contain locators created with the Create Locator tool in ArcGIS Pro. Unfortunately a fix for this issue was did not make it into 10.7.1 but good news is we have created a general patch that fixes this issue as well as a few other issues that were found. The patch can be found here:

ArcGIS Server 10.7.1 General Geocoding Patch

At this time the patch is only for 10.7.1.

Thanks,

Brad

All comments

PhilLarkin1

I can replicate this issue with a ArcGIS Pro 2.4 Composite locator published to ArcGIS Server 10.7. MagicKey functionality on 10.3.1 server composite locator returns correct results.

LeonZhong

Hi Phil,

My composite locator was created with ArcGIS Pro 2.3.0 and published to ArcGIS Server 10.7.

I just caught this issue when I tested Portal for ArcGIS 10.7. I set this locator as default locator for Portal, when I entered address in search box on Portal, it listed a bunch of suggestion addresses. But it returned "no location for this address" when I chose one of them.

If I ignore the suggestion and just use Enter after the address, it works. I tracked this request on ArcGIS Server and found the request string is SinglineInput="....."&magicKey="magickey".

So weird!

BradNiemand

ArcGIS Server 10.7.1 General Geocoding Patch

At this time the patch is only for 10.7.1.

Thanks,

Brad

LeonZhong

I can't believe I caught another issue for composite locator again, OMG!

Good to know ESRI has fixed this for 10.7.1 but hopefully there is a patch for 10.7 soon.

Thank you, Brad.

Leon Zhong

BradNiemand

Leon,

We typically don't patch "dot" releases once a "sub-dot" release is already out with a fix or a patch (like is the case here). That doesn't mean we can't, we just hadn't planned on it. Is moving to 10.7.1 not an option for you?

Brad

JohnFix2

Brad,

Does the patch also cover a composite locator NOT returning a suggestion for a "place name" locator? I have a composite locator with street range locator and a place name location. I can geocode by styles in the "find address candidate" method. But if I use suggestion and try the place name, nothing is returned.

I used ArcMap 10.6.1 to create the locators and published to Server 10.6.1

Thanks.

John

ChrisShaw_0-1606372173500.png

BradNiemand

John,

This patch is not for locators created with the Create Address Locator tool (in ArcMap and Pro), only for locators created with the new Create Locator tool in Pro.

I would need more details from you to understand what the issue you are having with, as we call them, the classic locators. What style did you use to build the locator? What is an example of the input data, the field mapping, the input placename you are trying to get a suggestion for?

Brad

BradNiemand

John,

I assume you used Create Address Locator to create your locators, right? If so, what locator style did you use (US Address - Dual Ranges and US Address - City State)? Is this composite locator published to ArcGIS Server or are both of the locators published to ArcGIS Server and the composite locator is not?

Brad

JohnFix2

Brad,

No, I used the “Create Locator” to create my locators. I used the “street address” style with the roads layer and the “city” style with my place names layer.

I previously created “Address Locators” with “US Address - dual ranges”, and “US Address – City State” (in ArcMap 10.6.1). I then created a composite address locators with those two locators…made an SD file via Python of the composite locator and published to ArcGIS Server 10.6.1. Using the new geocoding service I get suggestions for addresses, but I no suggestions are returned for a city/state. If I use the “find address candidate” of the service, I get results for both addresses and city/state. But as you can imagine, our web app runs off of suggestions as is the typical pattern.

Does this help?

John

BradNiemand

John,

Yes, this helps. There is an issue that will be fixed in the next release of Pro (2.5) that addresses an issue with locators created with the Create Locator tool and added to a composite locator won't show suggestions locally in Pro. If you were to publish this locator to Server, you would get suggestions.

As for the classic locators, I am unsure what is going on there but if you have the ability to move to the new locators, this would be the best approach because there are many benefits to these locators, including some enhancements to suggestions such as verifying the house number for addresses and suggestions for intersections.

Brad

JohnFix2

Brad,

I created new locators in ArcGIS Pro 2.4.1 and then made a composite address locator. I published that composite locator to ArcGIS Server 10.6.1 and I see the same error behavior (message) when using a magic key. If I remove the magic key, the input geocodes as expected. Of course, all web apps are built with suggestions.....

Will a patch be made available to ArcGIS Server 10.6.1? We just moved to 10.6.1 and going to 10.7.1 is out of the question at this time.

Thanks.

John Fix

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.