Latest Contributions by ShanaBritt

Kyle: I don't see anything in comment you linked to that would lead me to believe the new locators and composite locators are unusable. Could you elaborate on your comment? I would definitely recommend using a multirole locator created with the Create Locator tool over a composite locator, but in a few instances you might find the need for a composite locator. ... View more

It's possible that the connection to the server is slow and not all of the locators from or on the server connection have finished loading, so when you look in the Locate pane the service looks disabled. Once the service has finished loading into the project, you leave and come back, the locator is available to use and does not show as disabled. I've seen this when there are a lot of services on a server or if the server is slow. We are aware of some of these loading issues and are working to address them in future releases of ArcGIS Pro. ... View more

See the comment here for publishing and overwrite solution via Python 3.6, the copy_data_to_server parameter is missing. https://community.esri.com/thread/245276-server-geolocator-publishing-fails-in-python-36-but-works-in-27#comment-898435  ... View more

Joe: Can you confirm what the published locators look like in the Settings tab of the Locate pane and if hovering over them gives a message or not? ... View more

Levi: Do you know if a copy of the locator that is being published is stored on the server that the 3rd party setup for you? Do you have access to ArcGIS Server manager to check for any data stores? ... View more

I don't seem to be having an issue using the following request without a comma. Do you need to use the countryCode and category parameters? http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer/suggest?text=Gordon%20st%20mackay&f=pjson ... View more

Joe: The new locators cannot be used in ArcMap unless they have been published as a service from Pro. This also means you cannot publish them from ArcMap/ArcCatalog, the error you received is expected. Are you using the steps described in this topic for publishing to standalone? Publish a geocode service—ArcGIS Pro | ArcGIS Desktop  There are times when there is a problem with the locator it looks fine in the Locators folder in the Catalog pane, but they are disabled in the Locate pane on the Settings tab. If the service is added to the project and is listed on the Settings tab of the Locate pane, but looks disabled, hover over the locator and you should get additional info. Do you have permission to the same folders? ... View more

Levi: Is the locator you are publishing a composite locator or a single locator created with the Create Locator tool? What version of ArcGIS Server are you publishing the locator to? Is it federated? Do you get the same error messages when you publish a locator created with the Create Address Locator tool using Python 3.6? Do you have a data store setup on the server you are publishing to? I'm asking this based on the info in the error code topic  001487: Failed to update the published service with the server-side data location. Please see the server's log for more …  It would be good to see what info is in the server logs. Server logs—ArcGIS Server Administration (Windows) | ArcGIS Enterprise  ... View more

Levi: If you are wanting to automate the publishing and overwrite process you will need to use Python, so using the script I mentioned is still needed for overwrite. As far as your issue with publishing the original locator created with the Create Locator tool... 1. The locators created with the tool have suggestions built in, there is no parameter to check to enable suggestions like with the Create Address Locator tool. 2. If you publish the locator created with Create Locator tool using Python 3.6 does the service and suggestions work? It is not recommended to publish locators created with the Create Locator tool in ArcGIS Pro using Python 2.7. Python 2.7 is for ArcMap, which does not support the locators created with the Create Locator tool in Pro. Once the locator is published as a service, it can then be used in ArcMap.  ... View more

ArcGIS Pro 2.5 will be the next release, which will have the ability to overwrite geocoding services on Enterprise portal and standalone ArcGIS Server through the UI like you can in ArcMap/ArcCatalog. In ArcGIS Pro 2.4 you can publish to standalone ArcGIS Server. If you have access to the Early Adopter Program, you can test out the new functionality in 2.5 beta. ... View more

The geocoding team put out a script to help automate updating a geocode service using Python that is installed with ArcGIS Pro. https://www.arcgis.com/home/item.html?id=54e8aab14f6e4c61b65b9dd9ab451503  The script is meant to automate the process described in the "Update a locator service" section of the 'Keep your locator up to date' help topic here: https://pro.arcgis.com/en/pro-app/help/data/geocoding/keep-your-locator-up-to-date.htm#ESRI_SECTION1_35E8B1CBDACB44C2AD4B5D486E9FBFEE Try using the script to see if you still encounter the problems you are having with updating the service. ... View more

I'm saying that if you build a locator with the POI, PointAddress, and StreetAddress role in the same locator that you can search for places and addresses and get candidates from each of the roles. If the data used for the POI role includes the place name and has an address associated with it  as well as a category, you can search for places by name, category, address, or a combination of name or category and parts of the address. For example, Starbucks, Orange St, Redlands or gas station, Boulder, CO. If you searched for a POI name the match result would be from the POI role. If you searched for an address that matches against both PointAddress and StreetAddress roles, the match will be to the PointAddress candidate as it's the most accurate. The composite that contains a PointAddress and StreetAddress role will return two candidates from each role. If you adjusted the supported categories for the multirole locator where only PointAddress and POI categories were supported, if you searched for an address that could only be matched to the StreetAddress role it would be unmatched or if you searched for an intersection. If you wanted to exclude addresses from matching to the Street Name when there was no StreetAddress match you would uncheck Street Name under the Address category. ... View more

Michael: The Create Locator tool allows you to create a multirole locator, where you have multiple data layers and multiple locator roles in a single locator. Creating a multirole locator with street and point address data would eliminate duplicate candidates for the same address, which is what happens with a composite. The composite will return both the point address and street address candidate, when the point address one has the highest score. If the reference data used are in different coordinate systems, then the coordinate system of the first dataset is used. Below are the Create Locator tool with multiple roles and data used as well as the properties dialog. If you create the multirole locator you can use the category settings to specify matches to specific types of categories like only Street Address and Street Intersection, but not Street Name if you have built a locator based on the Street Address role.   ... View more

Sharon: Are you able to include a screenshot that shows the status of the Rematch Addresses pane when this behavior occurs? I can't tell what's going on in the ones you've already provided. In those it's odd that you have multiple A & B candidates. Are you using a locator created with the Create Address Locator tool or the Create Locator tool? This issue may also be better addressed through Support where you can provide the exact steps and possibly data. The next release of ArcGIS Pro will be available soon and if the behavior is still reproduced in the new release submit the issue through Support. During the development cycle of the next release of Pro we addressed some odd behavior with rematch. ... View more

Agnes: It's possible that there was a field type in your table that was not supported by shapefile format, which could explain why using a file gdb for geocode output worked. ... View more