Latest Contributions by RonnieRichards

‎02-02-2023

Hello, Where in arcpy for ArcGIS Pro can you obtain the workspaces from the map or layers? I cannot find this property in documentation? Specially I am looking for the name and path of the SDE connection file. This was very helpful when resourcing maps as we use standardize SDE connection names so we migrate maps to other environments we easily find and replace the workspace connection locations & names. In arcpy.mapping for layers in MXDs there is a property which returns the workspacePaths for the layer. The reference is below. https://desktop.arcgis.com/en/arcmap/latest/analyze/arcpy-mapping/layer-class.htm In the ArcGIS Pro this help has an example of using the updateConnectionProperties method. For Enterprise Geodatabases, how does one obtain this connection string so this can be achieved? https://pro.arcgis.com/en/pro-app/latest/arcpy/mapping/updatingandfixingdatasources.htm There is an info tip in the Layer help stating there is no reference to the .sde connection file. https://pro.arcgis.com/en/pro-app/latest/arcpy/mapping/layer-class.htm Tip: Enterprise geodatabase layers in an ArcGIS Pro project do not retain the path to the database connection file (.sde) that was used to create the layer. Without the original workspacePath/connection string how is it possible to read the .SDE connections from the map and update them programmatically using updateConnectionProperties?

‎12-07-2022

Thanks for this info @AliciaShyu I am curious though, what is the source of your locators? In our situation, they are file based locators and published to servers so not sure how a script stopping/starting the service would even have access to the published locator unless the server resource directory is shared.

‎12-04-2022

Has this been resolved in anyway? I have been experimenting with the result objects and they seem to have the same problem with the limited output with the start and stop times, same as GetMessages() ? What would also be helpful are the additional runtime messages from the 10.x tools just like the author posted. It does not seem the result object contains these messages. Executing: Select E:\lidar_derivatives\processing_data\rs_hydro_processing\fishnet.shp E:\lidar_derivatives\processing_data\rs_hydro_processing\tile_479\tile_479.gdb\tile_479 "TILE_ID = 479"

‎12-04-2022

A couple of ideas... In past versions of arcpy the .LOC was not required maybe try to add the .loc to the full locator path and see if this resolves the value error For the ArcGIS Server connection, try removing the .AGS from the connection file used for the publication. This change occurred somewhere around Pro 2.7. Was the ArcGIS Server connection file created in ArcMap or ArcGIS Pro? There is a difference mainly with how the credential is saved and believe we had to convert our connections over to the pro versions.

‎10-28-2022

Thank you @JonahLay that is very helpful to know and we will proceed with the new methods! Also thanks again @RandyCasey & @HannesZiegler for the quick responses are most appreciated! Please close this idea as functionality already exists in FeatureSharingDraft

‎10-28-2022

Thanks again for the information and one of the solutions references is using the arcpy library to create the service draft. The other is using FeatureSharingDraft which we will have to look into but why can;t these be treated the same as feature classes? I went thru our publishing products and our tables SD drafts are failing with arcpy method arcpy.mp.CreateWebLayerSDDraft. This is how all of our Enterprise GDB sourced datasets are being published to AGOL and the reason for this idea for table support in arcpy CreateWebLayerSDDraft.

‎10-25-2022

Thank you both! I will review these and see what is different with our current process. We are having challenges with our existing feature layer script breaking in the publish method when sourced as a table.

‎10-25-2022

Please add methods to ArcGIS Pro arcpy to support the Overwrite Table functionality. For some reason this exists only as a command in ArcGIS Pro but not in arcpy. https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/overwrite-standalone-table.htm We have a number of hosted tables in ArcGIS Online exposed to Open Data which originated from the Enterprise Geodatabase. At this time these updates have to be performed by the user using Pro's sharing options and we cannot automate the overwrite table service updates due to the lack of arcpy capability. Having tables automated will help us fully automate updating the hosted services. Adding the publishing of stand alone tables was the first step, now please help us automate this. Thanks for your consideration

‎09-08-2022

@ShanaBritt thank you for alerting me to the differences between the Subaddress and PointAddress results. The way this is topic is heading is much different than the original submitted idea so if there is a better location to explain this please let me know. However I am still seeing the same match score results which is confusing. To be specific when using the PointAddress type we do get a hit on the address string: 4791 PELL DR STE 1, SACRAMENTO, CA 95838 but with a 100% score. Shouldn't the extra string elements detected as a unit type and unit number reduce scoring? Are the locator output fields documented anywhere? It seemed to do so in the legacy locators with a match of 96.2 and a it shows in the scoring component return but using the "Locality" attribute: Comp_score: ;House=100; prefix=100; pretype=100; StName=100; suftype=100; suffix=100; LocalityPreDir=100; LocalityPreType=100; Locality=85.63; LocalitySufType=100; Admin=100; Postal=100 Its seems like PointAddress scoring is only reduced when other elements are not perfect like the street name or postal city, so could extra the unit information be considered in the overall match score? As illustrated it did in the legacy locators and helpful to know the input string was not an identical match to the candidate. The scoring components are also very valuable as well and hopefully they will be incorporated soon.

‎07-05-2022

This can also be caused if the Excel workbook is encrypted with a password. The same error with be thrown if the xlsx has a password. The password must be removed from the workbook to be compliant with Desktop or Arcpy in AGP v3.0.

‎06-30-2022

Hello @ShanaBritt , Sorry for the delay, this has been on our list to test and staff have just completed a big round of testing. We have created locators using 2.9.3 and still seeing the same results where the INPUT ADDRESS is not returned in the response and getting unit returns when they really dont exist. But when the units do exist in source data, the hit rate has increased significantly from our previous locators. For this idea the original concept has not been applied yet: This input candidate still gets the same match and response as reported in 10.6.1. Ideally we want to see the input address line back in the response so we can compare it to the match, especially for purposes such as this when the input DOES NOT MATCH the match, especially with a 100% match score. This is important if the new locators are going to return erroneous results with 100% match score for an address which does not exist in the source. It would be much easier to report on these if the component scores were included but those still do not seem available yet.

‎09-01-2021

Reviewing the LocateXT documentation it appears the custom attribute function solely revolves around keyword searches. Due to variations of keywords or possible ocr issues it would be much more effective to have custom attributes to be able to be pulled out using regex expressions. This would be a powerful way to pull out specific values using single statements instead of multiple keyword definitions. In addition to regex , the tool might also benefit being able to run a custom python function or arcade expression. The same argument could be made for the use of regex or functions for locations. The location definition needs some work but ideally these locations would be defined by a set of regex functions. One example might be an expression to pull out zip codes or address strings and then potentially look up zip code features or geocode them against a service. The use of out of the box templates could benefit because right now there are only default templates. Once functions or regex are allowed then this could actually help others get going much quicker by sharing other libraries of templates including functions for parsing strings, regex expressions, etc... Thanks for the consideration!! Ronnie

‎08-31-2021

Agreed. Feature extraction should also be configured and able to be performed at the class level. So if we want zip codes features to be extracted ideally we could specify a regex expression , arcade expression or python and have those feature types be associated to a locator service. For the same document we might want to map any addresses mention so it would be defined we a regex which identifies address strings and want to geocode these against World Locator service? Defining 1 feature at a time as the author is running into is not sustainable and defeats the purpose of the product. It does not appear to support regex for locations or custom attributes so will likely be creating an idea for this type of support.

‎07-06-2021

Similar to: Enable Cart for multiple Open Data downloads - Esri Community Select Multiple Items in Open Data and Download as... - Esri Community Multiple dataset downloads for Open Data Portals - Esri Community

‎06-21-2021

Please create a standardize address method to an existing Geocoding Service or possibly as its own service. Look ups should support a single candidate or possibly batch candidates.There are needs to standardize address information outside of geocoding the address, sometimes when an incomplete address or only the street name has been provided. We'd like to use this to convert Next Gen 911 style street names to legacy or vise versa. To make this work with a geocoding you must severely reducing the scoring which inherently creates other issues. Ideally an address candidate could enter the standardize method and the output results includes the candidate as well as the result split into the addressing components as configured in the service. The use of geoprocessing tasks is not a realistic option as the current standardize addresses tool takes in a dataset and requires an output dataset. This is overkill for simply standardizing a list of street names from Next Gen 911 style to the legacy style.

Online Status	Offline
Date Last Visited	‎05-21-2026 12:39 PM

My Ideas

Latest Contributions by RonnieRichards

How to get workspace path for map in Pro

Re: Create Geocode SD Draft error

Re: Bring back full arcpy.GetMessages() messages in ArcGIS Pro!

Re: Create Geocode SD Draft error

Re: Add overwrite table to arcpy

Re: Add overwrite table to arcpy

Re: Add overwrite table to arcpy

Add overwrite table to arcpy

Re: Add Find Input fields to Primary Locator Role FindAddressCandidate responses

Re: ArcGIS.Desktop.Core.Geoprocessing.GPItem

Re: Add Find Input fields to Primary Locator Role FindAddressCandidate responses

LocateXT needs regex support, arcade expressions or python function support

Re: LocateXT Needs Gazetteer Support To Be Useful

Re: Enable a 'shopping cart' experience for data downloads

Create a Standardize Address method for ArcGIS Server / Enterprise

Re: Compression for Vector Tile Package VTPK

Re: Upgrade from 11.3 to 11.4 broke shared instanc...

Re: Create Geocode SD Draft error

Re: Create Geocode SD Draft error

Re: How to get workspace path for map in Pro