Latest Contributions by ShanaBritt

@DEWright_CA Does the multirole locator you are building contain only the PointAddress and StreetAddress roles? Where is the data stored that you are using to build the locator with, on a network drive, SSD drive on your local machine? Can you provide a screenshot of the parameters used in the Create Locator tool such as the Country or Region and Language. Thanks, Shana

@JohnNergeBrooklynPark If you use the Create Locator tool to build a POI role locator for the city park names you have the option to include the address of the park, which would get returned with the park name. If you have different categories of parks like skate parks, dog parks, regional parks you can search on the category name and get all of the parks that are in that category. An example of this with some test inputs can be found in this tutorial, https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator-with-more-than-one-dataset-of-same-role.htm. You have different search options that are available for the POI role as illustrated in the following role description https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/introduction-to-locator-roles.htm#ESRI_SECTION1_CE2B24E7AC144C71B645937363ECBCE5. You can include the POI role in a multirole locator along with your address point data using the PointAddress role you are already using, you would not be able to include the feature role locator in the multirole locator. If you use the Create Locator tool you can include custom output fields that contain other attribute info that you want returned with the park name result. This option is available in the Create Feature Locator tool starting in ArcGIS Pro 3.2.

@MariaGiarrusso What type of locator are you using to geocode your table, local or service? Do the addresses include the city or zip code? Is the locator you are using a multirole locator? What is the precision of the locator you are using? (You can see this in the locator properties) What are you comparing the offset to, the data the locator is built from?

@Amarz What was the result of batch geocoding with multiple fields?

If you build a locator that supports the StreetAddress role you will be able to search for street blocks like 100 block of New York St, Redlands, CA or 200-500 block Taylor St, San Francisco and new for ArcGIS Pro 3.3 you can search for streets in between other streets,for example, 5th St between Victoria Ave & Roberts St, Highland, CA or I-10 W between Exit 75 and Exit 76, Redlands, CA.

@KyleGruber The locator is going to require a few characters after the intersection connector (/, &, @) to return intersection suggestions, otherwise you would start to see street name suggestions. If I am understanding you correctly you are wanting the locator to facilitate a query like you would using select by attributes or the layer search functionality. The locator doesn't behave like this.

There is data for administrative areas on Living Atlas that can be used for your query or if you found other opensource data it can be published to ArcGIS Online or Enterprise portal as a feature service. Here is an example of querying a feature service: services.arcgis.com/P3ePLMYs2RVChkJx/ArcGIS/rest/services/USA_Boundaries_2022/FeatureServer/2/query?where=name%3D%27new+haven+county%27&objectIds=&time=&geometry=&geometryType=esriGeometryEnvelope&inSR=&spatialRel=esriSpatialRelIntersects&resultType=none&distance=0.0&units=esriSRUnit_Meter&relationParam=&returnGeodetic=false&outFields=*&returnGeometry=true&returnCentroid=false&returnEnvelope=false&featureEncoding=esriDefault&multipatchOption=xyFootprint&maxAllowableOffset=&geometryPrecision=&outSR=&defaultSR=&datumTransformation=&applyVCSProjection=false&returnIdsOnly=false&returnUniqueIdsOnly=false&returnCountOnly=false&returnExtentOnly=false&returnQueryGeometry=false&returnDistinctValues=false&cacheHint=false&orderByFields=&groupByFieldsForStatistics=&outStatistics=&having=&resultOffset=&resultRecordCount=&returnZ=false&returnM=false&returnExceededLimitFeatures=true&quantizationParameters=&sqlFormat=none&f=pjson&token= This is the query example from the dataset United States County Boundaries - Overview (arcgis.com) in Living Atlas.

@AndreasB The behavior you are describing is not currently possible, but we are looking at resolving that in a future release of ArcGIS Pro.

@KyleGruber Can you provide a screenshot of how the data is formatted in the street layer, specifically the StreetName, PrefixType fields? It's likely that having the prefix types of County Road (CR), State Route, US Route (USHWY) as part of the street name field instead of parsed into the prefix type field is contributing to the types of suggestions you are getting. You can build a multirole locator that supports PointAddress, StreetAddress, Street Intersections, Street Names, Street MidBlock, but what is the goal of the locator you are trying to build? What is the purpose of getting a list of intersection suggestions?

@DanielDormont Using ArcGIS Pro was just one method of getting the layer into your org or portal, here are other methods https://doc.arcgis.com/en/arcgis-online/manage-data/publish-features.htm. You maybe able to use query for the feature service. https://developers.arcgis.com/rest/services-reference/enterprise/feature-service/ https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service/

@AaronManuel2 The following help topic references the best practice for updating a locator and the geocode service. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/keep-your-locator-up-to-date.htm#ESRI_SECTION1_12AA5C7DF3B44701B13DD015F6D1BA02

The ArcGIS Geocoding service is always going to return a point location. Depending on your application, you could use a polygon feature service for searching and it would return a polygon. For example, in ArcGIS Pro you could take an admin boundary layer and configure it for search in a map, then share the map as a web map to your organization and set the search feature to the polygon service for that web map.

@AndreasB It is not currently possible, but it is something we will look into for a future release of ArcGIS Pro.

@leahmaps Do you get any results returned when using the published locator via findAddressCandidates or suggest REST endpoints for the geocode service?

@TimHayes3 I believe we spoke about this, but wanted to post a response here in case someone else came across your post. In order to return the subaddress candidates as suggestions after typing the base address of "3300 Capital Ave" or "3300 Capitol", the locator must be created in ArcGIS Pro 3.0 and published to Enterprise 11.0. The only subaddress suggestions that would be available to you with a locator built in ArcGIS Pro 2.9.12 and published to Enterprise 10.9.1 is partial subaddress, which requires you to type the full base address, then part of the subaddress. The note in the share locator topic lists locator properties and the versions of ArcGIS Pro and Enterprise that they are supported in. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/share-a-locator.htm

Online Status	Offline
Date Last Visited	10 hours ago

My Ideas

Latest Contributions by ShanaBritt

Re: Major performance bomb in Building Locators in 3.3?

Re: Create Locator vs. Create Feature Locator

Re: Locate & Geocoder using same Published service returning difference results?

Re: Locate & Geocoder using same Published service returning difference results?

Re: Fuzzy Geocoding

Re: Locator - Intersections - Too Much Text Required For Suggestions (Geocoding)

Re: How to get administrative boundaries from geocoded result

Re: Locator doesn't return correct results

Re: Locator - Intersections - Too Much Text Required For Suggestions (Geocoding)

Re: How to get administrative boundaries from geocoded result

Re: Rebuilding geocoder published to portal

Re: How to get administrative boundaries from geocoded result

Re: Locator doesn't return correct results

Re: Locator with suggestions not happening

Re: Locator with suggestions not happening

Re: Create Locator vs. Create Feature Locator

Re: How to get administrative boundaries from geoc...

Re: Creating Locator with Parcel data

Re: Creating Locator with Parcel data

Re: Create locator: visualizing the search result