Latest Contributions by ShanaBritt

@amarcz_cc What was the result of batch geocoding with multiple fields? ... View more

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. ... View more

@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. ... View more

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.   ... View more

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

@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? ... View more

@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/ ... View more

@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 ... View more

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.  ... View more

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

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

@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 ... View more

@TimHayes3 If you rebuild the locator without the FeatureID being mapped to ADDR_KEY field, enable the base address and and subaddress summary properties, then enter the base address in the Locate pane, do you get the expected suggestions? ... View more

@AndreasB I'm surprised that you did not get a warning message after building the locator about the multipart lines. The results in your screenshot looks like a StreetAddress and StreetName candidate. If you do not wish to have StreetName candidates, disable StreetName as a supported category in the locator properties. ... View more

@Brian_Wilson It looks like you built your locator with city and zip code (location), but you are not using city and zip code when geocoding the table. When using the Locate pane it uses the center of the map as the location, while batch geocoding a table does not reference the map to get the location, the location (city, zip code) needs to be included in the input table since your locator was built with city and zip code mapped. If you launch the Rematch Addresses pane to review the unmatched addresses are you getting candidates for the unmatched addresses? ... View more