Latest Contributions by VictorBhattacharyya

See the "Output Fields" parameter here: https://pro.arcgis.com/en/pro-app/latest/tool-reference/geocoding/geocode-addresses.htm#GUID-D92B5478-6B6E-4A79-9ECE-1C24BE984FF1 ... View more

Hi Jared, There are no tutorials but the code sample I shared above is a good start. Also, something that might be of use to everyone in this thread @RobertStevens  in the GeocodeAddresses tool we added the ability to only output certain outFields starting at Pro 2.7. You have the ALL, MINIMAL and LOCATION_ONLY options, which provides more control over which outputs are in the output of your geocoding job. ... View more

Hi Robert, You'll want to make REST calls against your the GeocodeAddresses REST endpoint for the geocoding service. Here's some documentation about using the GeocodeAddresses REST endpoint: geocodeAddresses—ArcGIS REST API: World Geocoding Service | ArcGIS for Developers  If you plan to do your geocoding against the world service, you'll need to get a token first, and pass that token in with your request. The user credentials associated with this token will be billed for the results of batch geocoding. If you are using your own geocoding service that you have stood up, you won't be charged for the results, but if the service is secure, you'll still need to pass a token. By default, the geocodeAddresses operation returns ALL of the output fields that the service has turned on. It will be your job in post-processing to keep the ones you want, and to forget about the rest. You'll want to copy the format for passing records that's described in the geocodeAddresses REST documentation above. Once you have the correct dictionary format for your input records in a recordset variable, then, you'll want to make the actual request. values = {       "addresses": json.dumps(recordset, ensure_ascii=False),       "f": "json"       "token": token } response = requests.post(geocoding_service_url, data=values) json_response = response.json() Once you get the output dictionary/JSON of the GeocodeAddresses call, you can filter and only add certain values to your output resultant feature class in Python. So, after you get your REST response, you'll want to do something like: arcpy.management.CreateFeatureclass(some_gdb, name_of_feature_class, "POINT", spatial_reference=sr) arcpy.management.AddFields(path_to_fc, list_of_fields) cursor = arcpy.da.InsertCursor(path_to_fc, list_of_fields + ['SHAPE@XY']) < loop over the results of your JSON response > < skip over the attributes you don't want in your output and only add the attributes you want to save to your list_of_attributes > cursor.insertRow(list_of_attributes) ... View more

You could also try setting the arcpy.env.workspace, and then you wouldn't need to use UNC paths, just the name of of the locator in the field mapping. All of my python tests do have a selection criteria. So I definitely would not leave that parameter blank while you're trying to get it working. ... View more

Hi Joe. The sample looks good to me other than the selection_criteria parameter. All of my CreateCompositeAddressLocator python snippets do have a selection criteria.  Here's what it looks like, if you had 2 locators and you gave them names of street_loc and Locator "street_loc #;Locator #" So, instead of passing empty string "" as the 3rd parameter to the arcpy call, I would pass, in your case,  "AddrSF #;AddrSH #;Centerline #;Parcels #"     As the string to the arcpy call for the 3rd parameter. Give that a try and let me know how it goes! Thanks, Victor ... View more

As previously mentioned, the only way to be truly HIPPA compliant would be to build your own locator and deploy your geocoder on-premises behind your Organizational firewall. Use the World Geocoding Service at your own risk. Although Esri does not store batch geocoding requests, sending customer data over the internet can break HIPPA compliance. Make sure to check your organization's data privacy requirements before sending customer data to any geocoder that's not behind your organizational firewall.  ... View more