New answers tagged scripting
You can use gdal/ogr tool inside your modelbuilder : hope that helps
Use this function to return all of the feature classes in the GDB: def listFcsInGDB(): for fds in arcpy.ListDatasets('','feature') + ['']: for fc in arcpy.ListFeatureClasses('','',fds): yield os.path.join(arcpy.env.workspace, fds, fc) Now loop over that function to work with each individual feature class: arcpy.env.workspace = ...
If you have access to ArcGIS, you could use Select By Location to select census tracts that are within the city council districts. You will need ArcGIS friendly files for this (ArcGIS is not super KML-friendly, though you can convert from KML with this tool). Census Tracts are available on the the U.S. Census website. City boundary files should not be ...
The analyser likes to pick out random items and claim the script is using them, for example this post on Geonet. I got round the problem by putting the SDE connection file on a network share that the server could also see and referencing it with a full UNC path: INWorkspace = r"\\store\UTILITIES\SDE Connections\xxx_geodb.sde"
When you created your script tool you would have gone through that wizard to wire up your script to a tool interface. At the stage where you point it to the script python file (.py) there is a check box which is usually un-ticked which is Show command window when executing script, try ticking that on?
Top 50 recent answers are included