Tag Info

New answers tagged

2

ModelBuilder is old, clunky, and is not getting any significant updates with ArcGIS Pro, if this tweet is any indication. I have never been a big fan of it (though begrudgingly still use it when I have to), so you might consider this answer as a sidestepping of the question and a recommendation to look at alternatives. FME is arguably the most obvious ...


1

You are on the right track. You just need to use MakeFeatureLayer to convert the feature class to a layer. I created a version and did an edit and then tried the following: >>> arcpy.env.workspace = r'Database Connections\gisadmin.sde' >>> arcpy.MakeFeatureLayer_management(r'Database Connections\gisadmin.sde\GISADMIN.Buildings', 'fl') ...


2

In Arcgis the dataset version is set at Workspace level. As you have mentioned in your question, you should create a connection file for that version and change the handle to the featureclass or table. something like this: worspace = "c:/connectionFiles/version1.sde/" layerName = "parcel" fc= worpspace+layerName arcpy.da.SearchCursor(fc,...) ##to change ...


2

The introduction of Python toolboxes at ArcGIS 10.1 for Desktop invalidates your four year old statement that all: Toolboxes, and thus their models, are binary. Standard toolboxes are binary but Python toolboxes (*.pyt) are text files. Consequently, I think Python toolboxes should be considered if version control of source code trumps the requirement ...



Top 50 recent answers are included