Latest Contributions by ChrisSnyder

You certainly can run multiple scripts/processes at once. Here's a link to an example using the subprocess moodule: http://forums.arcgis.com/threads/33602-Arcpy-Multiprocessor-issues?p=177418&viewfull=1#post177418 ... View more

Thanks Jason... In the docs I saw the part about the with statement "guarantee close and release of database locks and reset iteration", and thought that sounded good, but as long as the cursor executes successfully I guess that does that anyway. ... View more

Many (most/all?) of the scripting users were accustomed to using the file-based .prj definitions. Some issues I see: 1. The SR properties .name, .PCSName and/or .GCSName do not necessarily match the allowable spatial reference token keywords�?� For example the factory code of 2927 (the projection for all WA State Govt. agencies) has a .name and .PCSName property of 'NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet', however the spatial reference token keyword is actually 'NAD 1983 HARN StatePlane Washington South FIPS 4602 (US Feet)'. So the effect of this issue is that this works: arcpy.env.outputCoordinateSystem = arcpy.SpatialReference('NAD 1983 HARN StatePlane Washington South FIPS 4602 (US Feet)') and this DOES NOT work: arcpy.env.outputCoordinateSystem = arcpy.SpatialReference('NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet') Perhaps my projection (WA SPS NAD83HARN USFEET) is the exception here, but it would be nice to have a SR property that would yield the correct sr token keyword. 2. The Help system topics (Project tool, Project Raster tool, arcpy.env.outputCoordinateSystem, etc) do not adequately describe the disappearance of the file-based .prj files and it's impact on script-based use of the geoprocessing tools, nor does it describe the proper syntax of the factory codes (or how to search for them in projected coordinate systems .pdf reference doc), fails to mention the arcpy.ListSpatialReferences() method, and fails to mention a way to retrieve the proper sr token keywords. Also, script examples for the arcpy.env.outputCoordinateSystem method have the wrong syntax for using the spatial reference token keywords (Help provided example of arcpy.env.outputCoordinateSystem = "Coordinate Systems/Projected Coordinate Systems/UTM/WGS 1984/Northern Hemisphere/WGS 1984 UTM Zone 18N.prj" results in an error. 3. There are no file-based .prj files anymore. This threw me for a big loop! I suppose you can make some with the .exportToString() method, but that's kinda a pain... Seems like some of the legacy tools such as Project Coverage required .prj files... Not sure why the help system mentions .prj files anymore if there aren't any to speak of! I liked the .prj file folders because they were easy to search... Other than the directory tree in the the coordinate system parameter GUI in the projection-related toolbox tools, I don't really see an easy way to browse and retrieve the factory codes or SR token keywords (which you now need to reference when specifying coordinate systems in a script).    Getting rid of the file-based .prj definitions is a pretty big change... Like everything else though I'm sure we'll all get used to it. ... View more

Oh see what's different... The "sR.name" property appears to be slightly different than the "official" syntax compliant name that uis given by the arcpy.ListSpatialReferences() method. Is there any sR property that yields the "syntax compliant" name? sR.name property of 'NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet' vs. compliant name of 'NAD 1983 HARN StatePlane Washington South FIPS 4602 (US Feet)' ... View more

Thanks Jason - That did work... For example: >>> srList = arcpy.ListSpatialReferences("*washington*south*", "PCS") >>> for sr in srList: ...  print sr Projected Coordinate Systems/State Plane/NAD 1927 (US Feet)/NAD 1927 StatePlane Washington South FIPS 4602 Projected Coordinate Systems/State Plane/NAD 1983 (CORS96) (Meters)/NAD 1983 (CORS96) StatePlane Washington South FIPS 4602 (Meters) Projected Coordinate Systems/State Plane/NAD 1983 (CORS96) (US Feet)/NAD 1983 (CORS96) StatePlane Washington South FIPS 4602 (US Feet) Projected Coordinate Systems/State Plane/NAD 1983 (Meters)/NAD 1983 StatePlane Washington South FIPS 4602 (Meters) Projected Coordinate Systems/State Plane/NAD 1983 (US Feet)/NAD 1983 StatePlane Washington South FIPS 4602 (US Feet) Projected Coordinate Systems/State Plane/NAD 1983 HARN (Meters)/NAD 1983 HARN StatePlane Washington South FIPS 4602 (Meters) Projected Coordinate Systems/State Plane/NAD 1983 HARN (US Feet)/NAD 1983 HARN StatePlane Washington South FIPS 4602 (US Feet) Projected Coordinate Systems/State Plane/NAD 1983 NSRS2007 (Meters)/NAD 1983 NSRS2007 StatePlane Washington South FIPS 4602 (Meters) Projected Coordinate Systems/State Plane/NAD 1983 NSRS2007 (US Feet)/NAD 1983 NSRS2007 StatePlane Washington South FIPS 4602 (US Feet) >>> arcpy.env.outputCoordinateSystem = arcpy.SpatialReference(srList[6]) >>> This also works (not sure what I was doing wrong before): arcpy.env.outputCoordinateSystem = arcpy.SpatialReference('NAD 1983 HARN StatePlane Washington South FIPS 4602 (US Feet)') ... View more

Ya - i guess that's how it would work via scripting. Sure is a pain to find the "codes" since the .pdf is not well structured like the Coordinate Systems directory tree. Only way I could find the right code was by using v10.0, getting the sr object, and spitting out the "factory code" such as: >>> arcpy.env.outputCoordinateSystem = r"C:\Program Files\ArcGIS\Desktop10.0\Coordinate Systems\Projected Coordinate Systems\State Plane\NAD 1983 HARN (US Feet)\NAD 1983 HARN StatePlane Washington South FIPS 4602 (US Feet).prj" >>> arcpy.env.outputCoordinateSystem.factoryCode 2927 So, my new syntax in v10.1 is this: arcpy.env.outputCoordinateSystem = 2927 #WA_SPS_NAD83HARN_USFEET Note that (contrary to the Help topic) this syntax DOES NOT appear to work for me: >>> arcpy.env.outputCoordinateSystem = arcpy.SpatialReference('NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet')Traceback (most recent call last):   File "<interactive input>", line 1, in <module>   File "C:\Program Files\ArcGIS\Desktop10.0\arcpy\arcpy\geoprocessing\_base.py", line 505, in set_     self[env] = val   File "C:\Program Files\ArcGIS\Desktop10.0\arcpy\arcpy\geoprocessing\_base.py", line 557, in __setitem__     ret_ = setattr(self._gp, item, value) RuntimeError: <unprintable RuntimeError object> Note sure why the .prj files went away... Dawning of a new age of fully integrated seamless geospatial technology I guess... Sigh... COMPLAINT TO ESRI:The v10.1 Help topics that cover to projection-related stuff via Python scripting could use some further explanation about the new code/name based syntax. Script example syntax relating to using spatial reference names to set the SR appears to be incorrect. ... View more

Thanks Kim... http://forums.arcgis.com/threads/43644-UTM-Conversion-in-Python?p=222580&viewfull=1#post222580 Good ole' .prj... you will be missed! ... View more

Okay one last stab... Note the #comments... import arcpy arcpy.SetProduct("ArcInfo") #or whatever lic level you are using myFC = arcpy.GetParameterAsText(0) #IMPORTANT: In the toolbox GUI, this parameter should be a type of 'FeatureLayer' var1 = arcpy.GetParameterAsText(1) #Toolbox type of 'String' var2 = arcpy.GetParameterAsText(2) #Toolbox type of 'String' arcpy.AddField_management(myFC, "FIELD1", "TEXT", "", "", "50") arcpy.AddField_management(myFC, "FIELD2", "TEXT", "", "", "50") updateRows = arcpy.UpdateCursor(myFC) for updateRow in updateRows:     updateRow.FIELD1 = var1     updateRow.FIELD2 = var2     updateRows.updateRow(updateRow) del updateRow, updateRows ... View more

How about: nameList = [r.Name for r in arcpy.SearchCursor(myFC)] Then... i = 0 for name in nameList:     print "Item #" + str(i) + " = " + str(name)     i = i + 1 There is a ".index()" method of a list, but it returns the index of the FIRST occurance of the specified item. For example: test = ["john","sam","john"] >>> test.index("john") 0 You probably want to be more explicit in this case, and include a counter instead of the list index (which makes the assumption that all the names will always be unique). ... View more

Sorry - leave off the int() part in the CalculateField tool. No sense in converting your character string to an integer! I was under the assumption your input values were integers. Not sure why I was thinking that... This should work: myFC = arcpy.GetParameterAsText(0) var1 = arcpy.GetParameterAsText(1) var2 = arcpy.GetParameterAsText(2) arcpy.AddField_management(myFC, "FIELD1", "SHORT") arcpy.AddField_management(myFC, "FIELD2", "SHORT") arcpy.CalculateField_managment(myFC, "FIELD1", "'" + var1 + "'", "PYTHON") arcpy.CalculateField_managment(myFC, "FIELD2", "'" + var2 + "'", "PYTHON") ... View more