Latest Contributions by RonnieRichards

‎02-23-2023

Hello @BartGis5 We are now running into this issue publishing locators so thanks for this tip. Can you elaborate on the language settings to check/change? Are these the language settings in the Control Panel -> Region or is this somewhere else? Thanks!

‎02-03-2023

Thanks for the confirmation @BlakeTerhune ! Your solution is perfect to obtain a path to a .sde workspace. ArcGIS Pro seems to copy or create the sde connection into the local profile. It's unfortunate the original path was not preserved but maybe this was removed due to security or other issues if source connections are exposed. On this end, we will proceed with resourcing data on what exists in the connection properties. Thanks for your response to this

‎02-02-2023

For some reason this Describe catalog path does not return the original SDE Connection used. The map document was authored using a UNC path with standardized names and a temporary .sde connection was returned. Does it return the expected .sde connection file name and path in your situation? The map was authored with data from: \\servername\publish\readuser@prodDB_web_sde.sde\web_sde.GIS.COUNTY_BOUNDARY The describe returns: C:\Users\username\AppData\Local\Temp\1\a2190f00b0450b088ca7cd2e92f9f4b5.sde\web_sde.GIS.COUNTY_BOUNDARY This might be what that little tip was indicating in the layer help but this is not at all helpful if the sde connections are always in the local profile with the orignal naming destroyed.

‎02-02-2023

Thank you @BlakeTerhune that was very quick and this is perfect! I'll have to test but does describe work on broken data sources as well?

‎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.

Online Status	Offline
Date Last Visited	Thursday

My Ideas

Latest Contributions by RonnieRichards

Re: ERROR 002901: Sharing related error during geo-processing (Unable to publish to standalone servers prior to version 10.6 - Please upgrade to a new

Re: How to get workspace path for map in Pro

Re: How to get workspace path for map in Pro

Re: How to get workspace path for map in Pro

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

Re: Create Geocode SD Draft error

Re: Create Geocode SD Draft error

Re: How to get workspace path for map in Pro

Add overwrite table to arcpy

LocateXT needs regex support, arcade expressions o...