A script that updates geocoding services with the latest version of the locator. A brief summary of the item is not available. Add a brief summary about the item.
Code sample
by
Item created: Jul 3, 2019 Item updated: Dec 9, 2019 Number of downloads: 1,440
Description
An in-depth description of the item is not available.
Layers
Tools
Tables
Basemap
Project Contents:
Solution Contents
Contents
Layers
Screenshots
Terms of Use
No special restrictions or limitations on using the item's content have been provided.
Details
Dashboard views: Desktop
Source:
Creating data in:
Published as:
Other Views:
Dependent items in the recycle bin
Applicable: 2d
Size: 4.537 KB
ID: 54e8aab14f6e4c61b65b9dd9ab451503
Image Count: 0
Image Properties
Layer Drawing
Using tiles from a cache
Dynamically from data
Share
Owner
Folder
Categories
This item has not been categorized.
Comments (9)
Follow this video on how to implement https://community.esri.com/t5/devsummit-conference-videos/updating-your-locator-service/m-p/976744
Is this still a relevant code example?
Awesome! Thank you for pointing me in the exact direction I needed. Frustrating morning trying to track this very python example down. :)
You can now overwrite geocode services in the Pro UI. If you want to automate this process, you can still use this script or the code sample provided here: https://pro.arcgis.com/en/pro-app/latest/arcpy/functions/creategeocodesddraft.htm
For federated servers does it matter if the AGS connection is to the web adaptor or directly to the server on port 6443?
Thanks again. I seem to be having a problem by adding a simple loop of AGS connections to this script. What sort of dependencies does this script have on the ArcGIS Pro installation? It does not seem to work when not signed into a portal and if signed into a portal the script will not work looping thru connections. Can I contact your team or tech support to show simple examples of failures? Changing 6 lines of codes to this script to support a loop of connections fails with ERROR 999999 everytime on the 2nd publication. line 61: def main(connection) line 210: ags_connection = connection line 264: arcpy.env.overwriteOutput = True federatedConnections = [r'\\server\share\server on test (admin).ags', r'\\server\share\server on prod (admin).ags'] for connection in federatedConnections: main(connection)
You should still be able to create the AGS connection against server/6443. But if the server is federated, you'll need to enter the credentials to the Portal that is federated to the server. You can always double-click in ArcMap and it will tell you if the AGS connection you created is valid.
Thank you victor7669 what if we turn off server administrative option thru the web adaptor? In this scenario should we connect directly to server/6443?
For a federated server, create the AGS connection using ArcMap through the web adaptor. Double-click the newly created AGS connection in ArcMap to ensure that it is valid. For the AGS file credentials, enter in the credentials for the portal that is federated to the server you are trying to connect to.