Set Scale for Locate Results

[ChelseaRozek]

Is there a way to set the zoom level/scale that results from address locators in ArcGIS Pro appear at when you hit enter after typing them in?

Searching for an exact address comes up fine, at 1:729 so I can see the site. Searching for intersections always comes up at 1:10 or so, which is very annoying to have to keep zooming out after each search. I'm trying to save time and effort, so right clicking the results to "pan to" isn't helpful, especially because I'm constantly up and down on the zoom levels so I'm not usually what I now want to be at anyways to see the intersection. I don't want to lock down the scales in my map to certain ones as that would be too limiting in my work. 

[ShanaBritt]

@ChelseaRozek Can you provide me more details about the locator you created and the version of ArcGIS Pro used to build the locator?

1. What is the coordinate system of the street data used to build the locator?

2. Can you provide a screen shot of the field mappings for the StreetAddress role? This can come from the locator properties dialog on the Reference Data Tables tab

[ChelseaRozek]

Hi @ShanaBritt , thanks for taking a look! I'm using a composite locator I've published to our unfederated server. I get the same result when I add just the one address locator with the road centerlines (from roads in WKID 2253) to my project. It says it is Release 3.5, compatibility release 3.0. Last built earlier this month.

[ShanaBritt]

@ChelseaRozek Thanks for sharing the field mapping and coordinate system of the street centerline data used to build the locator. I see that you have a multirole locator in the screenshot, does it also include any alternate name tables that would be listed on the Alternate Name Tables tab in the locator properties?

If there are no alternate name tables that are part of the locator there is no need to map the Street Join ID locator role field. Including the FeatureID role field is only necessary when you have duplicate geometry in the primary reference data that have different attributes like different street names. When you do use the FeatureID field the field  you map to it should not contain unique IDs like the ObjectID field. Mapping the FeatureID field when you do not  have duplicate features with different attributes will increase the size of the locator, impact the time it takes the build the locator, and can affect the performance of the locator. See the following topics for more info:

- https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/collapse-duplicate-features-in-the-data...

- https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/locator-role-fields.htm

The Full Street Name field is also not necessary to map when building a locator for the USA as this field is not used for address matching.

1. What is the Precision type of the locator? This is on the 'About the locator' tab of the locator properties.

2. Have the side and end offsets been modified? This is on the Geocoding options tab > Match options section

3. Is the multirole locator from the screenshot added to a composite?

4. Does the same behavior occur with a single StreetAddress role locator?

5. Is all of the data used in the multirole locator in the same coordinate system?

[ChelseaRozek]

- yes, there is an alternate name table
- thanks for the clarification and doc links as I was unsure about the two IDs. we do have duplicate geometry as some address ranges are wildly different on each side of the street and contain odds and evens on the same side. they have the same street name. i'll remove the FEATUREID mapping.
- precision = GLOBAL_HIGH
- both offsets = 6.371, i don't remember editing this before
- yes, I have multiple locators including the multirole one added to a composite locator. using just the multirole one also zooms in very far on intersection results.
- zooming works fine on a single StreetAddress role locator. I stepped through removing parts and testing. it appears that the Parcel role is what is causing the issue. I'm not sure how that could be affecting an intersection search query. I've mapped STREET, CITY, STATE, and ZIP from the parcels.
- yes, all our data is in 2253

[ShanaBritt]

Thanks for the additional info.

1. Is the parcel data point or polygon? Are you also mapping the Parcel Name field along with STREET, CITY, STATE, and ZIP for the Parcel role? 

2. When you create a multirole locator of StreetAddress and Parcel and search for an intersection you experience the zoom issue?

3. Do  you get the same behavior if t he precision type of the locator is Local Extra High or Global Extra High?

4. If you have a composite of a StreetAddress role and Parcel role locator do you encounter the zoom issue?

Just to confirm, you are using ArcGIS Pro 3.5 to build the locators?

[ChelseaRozek]

• Polygon parcels. Apologies, to be clearer, the Parcel Name maps to PROP_STREET which has 123 Main St. We do not have separate fields for street number and street name. I have a separate locator that matches based on the Parcel PIN.
• Correct
• Local Extra High and Global Extra High: same issue 
• I noticed in these two, when I search for my address, there are 2 results, one at 1:1,276 (decent) and the other at 1:28 (bad). In the original, GLOBAL_HIGH, the two results are both decent at 1:2,834 and 1:1,276.
• Combining A (Street and Point Address roles) with B (only Parcels) into a composite locator: intersection is fine at 1:1,890, my address is okay at 1:850
• I am using ArcGIS Pro 3.5.2

So my workaround for now is to separate the locator for the parcels' street address into its own. I really appreciate your help with troubleshooting this!

[ShanaBritt]

1. If you have a multirole of StreetAddress and the Parcel roles, where ParcelName is mapped to PIN, do you experience the zoom issue?

2. What is the purpose of a Parcel role locator where ParcelName is mapped to the property address "123 Main St"? Is the same parcel polygon data used for this locator the same used for the Parcel - PIN locator?

Mapping the street address to the ParcelName field is not going to create an optimal locator using the Parcel role. The street address components should be broken up into separate fields. You can use the Split Address Into Components tool to parse the PROP_STREET field into individual address components . There are illustrations of what can be searched using the Parcel role. You also have the option to create the Parcel - PIN locator and set PROP_STREET as a custom output field so that when you search for the PIN, the PROP_STREET value will be included in the output.

When you create the composite with a mix of multirole and single role locators you should use the Result Order option in the properties that is to order the results by role and score, which gives the same fallback as a multirole locator.

[ChelseaRozek]

• With a multirole locator with parcelname mapped to PIN: yes the intersection zoomed to 1:24.8. So does an address that’s one off from mine (that doesn’t exist), which I hadn’t tried before in my testing.
• My exact address zoomed fine, but when I recreated the locator without the address points locator as that result seemed to be coming from that locator (so only parcels and road lines left), everything is zooming to 1:24.8.
• My goal for the parcel locators is to be able to search by the parcel PIN or by the PROP_STREET in the parcel layer in addition to geocoding against the roads. Thanks for the document link. I was under the wrong impression that I would need an address range to map to the house number(s) with the Parcel role. I’ve modified a copy of the parcel polygons and created a locator with a role for Parcels against it (Name mapped to PIN, House Number mapped to STREET_NUM, Street Name to STREETNAME, city, state, zip) + the normal roads role. This locator is zooming me to 1:12.31 which is bad.
• I then recreated the locator minus the roads (so only the better mapped parcels), zoomed to 1:554 which is a little better. Obviously couldn’t test intersection or “off by one” address since it's only against the parcel polygons.
• I swapped the test and left only the roads locator in. All 3 test addresses came up at 1:1,231 which is great.
• Yeah, I’ve played with the Result Order before.

I’m still wondering what controls which zoom level a result appears at, especially since these last two tests with only one role showed results at different zoom levels. I would think other users would want to be able to control this too.