Latest Contributions by ShanaBritt

Which tool was used to create the locators that are in the composite? The bug is related to locators based on polygon features that are published as services and not zooming to an appropriate scale or extent in the Map Viewer compared to the local composite in ArcGIS Pro. It was reported at 10.9.1. If you are up to date on maintenance you should be able to search for the bug number in myesri or the Support site. The only workaround found was to convert the polygons to points and rebuild the locator with the point data, but this might not be feasible for some.   polygon based locator published as a service and used in ArcGIS Pro and the map not ... View more

In order to rename the "locator" in the web map rename the layer in the Contents pane in ArcGIS Pro before configuring it for search and publishing the map to the portal. Regarding the zoom behavior, were you experiencing this with a local locator in ArcGIS Pro or with the locator published to Enterprise portal used in the web map or? If published was the published locator used in ArcGIS Pro. If it was published was it a single role locator that referenced polygon data or a composite locator that consisted of locators based on polygon data? I'm asking to try and figure out if you are running into BUG-000162951, which is not reproducible with Enterprise 11.2. ... View more

@ChelseaRozek The new locators do not have an option to specify additional recognized input field names. I'd suggest submitting/posting an enhancement on Ideas thread.  Since it's not possible to add more recognized field names for the input field names of the locator, you will have to manually select the field that contains the data (address, parcel PIN) that you want to geocode in the table when using the Geocode Table or Geocode Addresses tool. If you build a multirole locator with PointAddress and Parcel role, the input address field is always going to be 'Address' in the batch geocoding tools. If you wanted to add recognized field names for input fields, so that Geocode Addresses tool automatically  populates the 'Address' input field, create a composite locator that contains individual role locators or a multirole locator and modify the recognized field names for 'Address'. I would also update Region to add 'State' and Postal to add 'zip' , 'zipcode' , and 'zip5', or whatever field name is used for the postal values in your data.       ... View more

@ChelseaRozek If we use the data from my reply on 12/3/2020 and created a multirole locator that include PointAddress and Parcel role, the input table could look like the following. Then you could use multiple input fields and map Address, City, State, Zip or use single input field and map FullAddress. You could even use multiple fields and just map FullAddress to Address. The same would go for your composite. In both cases you don't need a ParcelID field for input, the parcel is considered the address and does not need it's own input field. If you used the Locate pane to search for the address or parcel PIN you will get candidates back. Is this more clear with the illustration? In the Geocode Addresses tool the first field to map is called "Address or Place", so the field that you map to it can contain only addresses, only places, or a mix of addresses, places, asset IDs, etc.     ... View more

@ChelseaRozek I think a better solution would be to build the multirole locator that included point addresses and parcels, then set up the table you are geocoding with a single field that contains the full address (380 new york st, redlands, ca)  or Parcel ID and use this single field when geocoding the table. You can also use an address field that contains the ParcelID or address (380 new york st) and  use the city, state, zip fields, which could be empty for the Parcel ID records.  Does that make sense? The following image shows different table formats.       ... View more

To  clarify, for reverse you want an address returned and not the xy? When I interactively reverse geocode in ArcGIS Pro I get the xy coordinate returned as part of the result whether it's a StreetAddress or StreetName match for reverse. Are the REST requests from using the REST endpoint or requests in applications? Are you able to provide an example of the app using the REST requests? ... View more

Locators do not support wild card searches, that is more of a query than geocoding. Suggestions provide candidates based on the tokens (strings) that are typed at the beginning like an autocomplete of typing the beginning of the value in the data. What you have described is more like what is described in the following topic for layer search. The layer used in configured layer search can be shared as part of a web map and used for searching using the contains search mode.  - https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/find-places-on-the-map.htm - https://enterprise.arcgis.com/en/portal/latest/use/configure-feature-search.htm Another option is to create multiple Feature or POI locators based on the  zone_id, site_id, site_name, description fields and add them to a composite locator. For the description field, you would need to type the exact string or the beginning of the string to get find results or suggestions. The description could be added as a custom output field for the POI locators and this value would be returned in the geocode results. Custom output fields were added to the Create Feature Locator tool in ArcGIS Pro 3.2. ... View more

For location do you want the xy coordinate or the street address returned? Is this locator going to be used in a web map, mobile app, in ArcGIS Pro, or via REST requests? ... View more

@TonyContreras_Frisco_TX So are you expecting to get the result in the ValideSide image when the input location for reverse is on the side of the street that has no house number range? If there is no house number range (0 or empty) for one side of the street I would expect the reverse match to be a StreetName addr_type instead of a StreetAddress type with "0 Street Name" or "0-0 Street Name". There are no locator settings to control this behavior. Which version of ArcGIS Pro and Enterprise are you currently using? I'm not sure how the current behavior affects Next-Gen e911 compatibility, I'd have to look into that. ... View more

@Mike_Quetel Regarding multirole locators, you are correct that each primary or alternate name role can only be used once in a multirole locator. So if you had multiple point address sources you would have to merge them together to build the multirole locator with the PointAddress role as described in this tutorial for a POI locator, https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator-with-more-than-one-dataset-of-same-role.htm. The same would be true for the alternate street name table, the data for the point address and street address roles would need to have the same join id value to link to the street name from any primary role to the alternate name table role. ... View more

@Mike_Quetel Is creating a multirole locator an option for you rather than using a composite locator for the service? Do you have any differences when using location when not using SingleLine and just using Address or Place? https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/combine-multiple-layers-into-a-single-locator.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-multirole-locator.htm   ... View more