New answers tagged

1

If you have follow the steps mention in Agent Analyst tool interface will not open on ArcGIS for Desktop? and then also you are getting same problem. This is due to Refresh.exe.config file. Your system will be taking as a text file. Download this file and paste it in C:\Repast 3\Agent Analyst\Refresh location. Open this file with notepad and change the ...


1

My input field parameter needed to be type GPString instead of Field. lkLkTab = arcpy.Parameter ( displayName = "Leak Excel Worksheet Leak Field", name = "lkLkFld", datatype = "GPString", ###changed parameterType = "Required", direction = "Input") I've also found that filtering parameters based off an input table can ...


1

Blunt tool might help to solve flawed logic. So let's use result of your test to guess name by simply counting number of operations: import arcpy sausage="ID_1_12_13_14_15_16_17_18_19_20_21_22_23_24_25_26_27_28_29_30" suffix=sausage.split("_")[1:] for i in range(19): arcpy.JoinField_management("PA", "OBJECTID", "PB", "OBJECTID") lastName = [f.name ...


1

I'd also be very interested to hear of a better, definitive way to resolve this issue. But in the mean time, you can use arcpy.ListFields() to get the list of fields before and after geoprocessing, and compare the before/after lists to determine which fields are new. Eg, before geoprocessing, run: fieldsBefore = [f.name for f in arcpy.ListFields(table)] ...


1

In ArcPy you can use field mapping to determine what fields work as inputs and outputs and how they are combined - this doesn't work for JoinField_management but works for many other geoprocessing functions. This script merges ID fields into the same output field when using the merge tool in data management: layer1 = 'layer1' layer2 = 'layer2' # ...


0

Select the "island" polygons that you want to use to clip the big polygons. Use the Clip tool in QGIS, with the following settings: Input layer: Polygon shapefile Overlay layer: Polygon shapefile, Selected Features only


1

For any interested parties: I contacted ESRI tech support, who confirmed this is a known bug which was first reported, and subsequently shelved, approximately two years ago. Workarounds are to re-export the OLE-joined table to a new feature class and use that as your data-driven pages layer, or to export the OLE-joined data to a different format (e.g. ...


Top 50 recent answers are included