Latest Contributions by ShanaBritt

@JoeBorgione The fix to this issue did not make into the 2.8 release, but resolved in the next release of Pro. If you are part of the EAP you can test out the workflow when 2.9 Beta is available in a few weeks. ... View more

@jmcbroom What version of Pro was the locator built in? What version of Server is the locator published to? Can you provide a screenshot of the Reference table page of the locator properties? I don't seem to be able to reproduce the behavior you described in your original post for findAddressCandidates. Did something change since your original post? https://opengis.detroitmi.gov/opengis/rest/services/BaseUnits/BaseUnitGeocoder_DEV/GeocodeServer/findAddressCandidates?Address=&Address2=&Address3=&Neighborhood=&City=&Subregion=&Region=&Postal=&PostalExt=&CountryCode=&SingleLine=10+Witherell&outFields=&maxLocations=&matchOutOfRange=true&langCode=&locationType=&sourceCountry=&category=&location=&distance=&searchExtent=&outSR=&magicKey=&f=html I would recommend that you use the location parameter in your REST requests especially if your input  address does not include an administrative zone like city, zip code, state, neighborhood. The location can be the coordinates for the center of the reference data The location parameter is discussed in the findAddressCanddiates help topic. ... View more

Since this question was originally posted the Parcel role was added to ArcGIS Pro, which you could try using this role to build the locator with the parcel data. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/introduction-to-locator-roles.htm#ESRI_SECTION1_D00AD43A248E49BC939616E570CC66B9 ... View more

@Marisa_Valencia I noticed that the values that you have listed for Category does not include Street Intersection, it only includes POI, Point Address, and Street Address. The StreetAddress locator role includes the following categories: Street Address, Street Name, Street Intersection. I had a few questions about the  POI role being used for intersections. 1. Do you not get expected results for in intersection addresses when using the StreetAddress role locator or if the POI role is not included in your multirole locator? Using POI role for intersection points means  you would miss out on searching for different types of intersections as described in https://pro.arcgis.com/en/pro-app/2.8/help/data/geocoding/fundamentals-of-intersection-geocoding.htm. 2. Are the streets that participate in the intersection entered in the same order when trying to find the intersection? If not, then the POI approach would not return a match. 3. Do you get different results if you used the SingleLine parameter for ' Jackson St, Los Angeles' instead of Address for the input? 4. Does this error if the locator does not include the POI role? ... View more

What happened when you tried to geocode the csv table using the Add Item workflow? Was there an error? ... View more

There is an option to configure specific fields in specific layers that is stored in the project called 'Locate configured features or records'. Configuring records in a table was added to Pro 2.8. Is this option not feasible for your work? The configured layers are maintained when the map is shared as a webmap to ArcGIS Online or Enterprise portal and can be used for searching as described here, https://doc.arcgis.com/en/arcgis-online/create-maps/configure-search-in-apps.htm#ESRI_SECTION1_5831AD4A964741D39BF59119B9573B2E   ... View more

Is configuring the layers that you want to search not an option for you? The configuration is stored in the project or if you create a template from the project if it contains layers that you use consistently. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/find-places-on-the-map.htm#ESRI_SECTION1_8D7E58B952164AFFB41E80B3D8ABF74C ... View more

A bug that you can track for this behavior is available, BUG-000141513. ... View more

I have a few questions for you @Egeiser27 ... Does the error 10 occur when using either of the locators in the organization named  'Composite Locator' or 'Address Locator'? I noticed that the csv table includes a zip field, does the error occur when geocoding with the Address and Zip fields using the 'Address Points Full Address' locator?  Do you continue to get the error if the csv is exported to a file geodatabase table or excel spreadsheet? How did you add the 'Address Points Full Address' locator as the Input Locator to the Geocode Addresses tool? (Select from the drop-down, click browse button, copy paste the url for the service) Are you able to view the details of the locators listed in Pro when signed into the organization in a web browser ? Are you able to geocode the csv file with the Add Item workflow in the web browser  using the 'Address Points Full Address' locator or any of the other locators listed in Pro? ... View more

@Violante If your Locate button is grayed out or disabled like in the image below, make sure you have a map open in the project. Below I do not have a Map or Layout view open in the project. The locate pane requires a map as the results will add a graphic to the map if using the Locate tab and if you are searching for features in a layer, the layer needs to be added to a map. For more info about what you can do in the Locate pane see https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/find-places-on-the-map.htm   ... View more

@JoeBorgione Any luck with a locator built without city, state, or zip and geocoding with a single field? ... View more

Do you have permission to the Published locator in your organization? Is the published locator shared with the Organization? Is the published locator a geocoding utility service in your organization? It would show in the list of locators listed in the Contents pane when you sign into your organization in Pro.   It would be helpful if you could provide a screen shot of the Geocode Addresses tool with the csv and published locator selected in the tool. ... View more

Unfortunately at this time there is no way to batch unmatch matched addresses. You would need to select them and use the field calculator to change the status, score, and match_addr fields, then while the records are selected click the Auto Rematch button, which will run on the selected records. In Pro 2.7 or later you can adjust the match score in the Rematch Addresses pane by clicking the Locator drop-down and selecting Add or Modify Locator and adjust the  geocoding options. Then go back to the main view of the pane and either click Auto Rematch for all records or select the records with the low scores and click the Auto Rematch button.   ... View more

@JoeBorgione What I'm suggesting is that you build a locator w/o any zones (city, jurisdiction, zip), then geocode the table of addresses using Single Field for the input address fields. This is the recommended workflow when your input addresses don't have zones. There have been improvements to the locators built with the Create Locator tool since you could first build them in Pro 2.3. Below are my results where all 84 were matched. If your input addresses have zones or an address could fall inside of multiple zones, it is best to build the locator with zones and batch geocode the address with zones or input the partial address and select the suggestion. ... View more