Latest Contributions by curtvprice

I would prefer not to have the outRaster name as a parameter, but rather would like all the rasters saved as Weight_%Name% and have the output location as a parameter.  Does setting the input workspace take care of the location Yes, if you do a raster save without specifying a full path, the current workspace is used. How can I save all the rasters like this automatically? You not only want to save using a generated name, but also have the output appear when the script is run in ArcMap or in ModelBuilder appear as an output to link to further processes. (Just like a regular tool.) This is done using a derived script parameter with the SetParameterAsText method. In the toolbox script tool properties, set the fourth parameter as data type "Raster" and parameter type "Derived". Be careful with your raster naming, grids can only have 13 characters! import os arcpy.CheckOutExtension("spatial") from arcpy.sa import * wks = arcpy.GetParameterAsText(0) # input workspace Risk1 = arcpy.GetParameterAsText(1) # input raster layer Weight1 = arcpy.GetParameterAsText(2) # input raster layer arcpy.env.workspace = wks out1 = Raster(Risk1) * Raster(Weight1) outRaster1 = "Wt_" + os.path.basename(Risk1) out1.save(outRaster1). arcpy.SetParameterAsText(3,outRaster1) ... View more

%f seems to force it to understand the points as a string? So I'll need to play around with it a bit more. %f is a Python string substitution code that formats a number into a text representation of floating point numbers. >>> "%f %f" % (1,2) '1.000000 2.000000' Python is moving toward a new method for substituting strings in situations like this. This new method was implemented at 2.4 and future versions of 3.x will stop supporting the old C-style string substitution, so we might as well start using it, especially since the new method is a bit less cryptic. originCoordinate = "{0} {1}".format(pxy.X,pxy.Y) ... View more

Some positive feedback... I was just messing with with 10.1 background GP and really like how when you double click on the background icon the results window opens up and shows you the current processing there. Some tools simply can't give you a percent because the process doesn't lend itself to estimates - but this is a nice improvement. Would be nice if more tools provided an estimate even if it's an inaccurate one, just so we know it's working. Followers of this thread may want to know that Esri plans to add 64 bit background processing as an optional additional install for Desktop 10.1 SP 1, which will let you run models and scripts in 64 bit. This could be pretty useful, especially for big geospatial data processes that can crash 32-bit geoprocessing because of memory requirements. ... View more

Robert has pretty much covered it, but I just wanted to point out it's not false advertising - the help page you linked to is not for the raster calculator. It's for map algebra in the arcpy Spatial Analyst module. The 10.x functional equilvalent of MOMA is to simply type the statements in the Python window. In some ways this is vastly superior to MOMA because you get integrated intellsense and tool help as you type. In ModelBuilder, you can place multiple Raster Calculator tools in a single model, which is a similar workflow to what MOMA provided in 9.x. ... View more

This is a great example of a case where building a process in modelbuilder and exporting to Python is not the optimal approach. The code you get is just too convoluted and does not take advantage of Python map algebra. The translation may have gone (a little) easier if you had used the Raster Calculator tool instead of many Times tools, but not much. Rather than fix the code, I recommend a rewrite. I'll do it here with just two rasters input and you can expand it from there. arcpy.CheckOutExtension("spatial") from arcpy.sa import * wks = arcpy.GetParameterAsText(0) # input workspace Risk1 = arcpy.GetParameterAsText(1) # input raster layer Weight1 = arcpy.GetParameterAsText(2) # input raster layer outRaster1 = arcpy.GetParameterAsText(3)  # output raster arcpy.env.workspace = wks out1 = Raster(Risk1) * Raster(Weight1) out1.save(outRaster1) ... View more

I used to have an AML that went through a workspace looking for potential red-flag issues and presented warnings (recommended changes) or errors (show-stoppers) for suspect field and dataset names, missing metadata or coordinate system, etc.  (We wrote this tool when we were converting from the old Prime platform and we wanted to make sure the export files would be valid when we tried to import them on the new platforms.) I agree it would be great to have a tool in the data management toolbox that does this for a dataset, along the lines of the map analyzer in ArcMap. ... View more

Here is the correct where clause: for dat in datelst:   arcpy.SelectLayerByAttribute_management ("hotspots", "NEW_SELECTION", "\"date\" = " + "'" + dat + "'") Python string substitution makes this kind of thing a LOT easier to write and and debug: whereExpr =  "\"date\" = \'%s\'" % dat  # I use outside double-quotes always for stylistic reasons whereExpr =  '"date" = \'%s\'' % dat    # but this is equivalent, using ' to preserve " inside the string arcpy.SelectLayerByAttribute_management ("hotspots", "NEW_SELECTION",whereExpr) The "new" way to do this in Python is to use the .format method. whereExpr = "\"date\" = \'{0}\'".format(dat) I prefer the "old" "% syntax" way myself for simple expression creation. Both are still fully supported. In arcpy (and also when using gp = arcgisscripting.create(9.3)), you shouldn't need to use the "\" things in SQL expresions anymore I think it's still good practice to double quote field names. If you have field names that cause SQL heartburn, the quotes will protect your field names from being parsed as SQL code and breaking your expression. Note when you're working with personal geodatabases, you need to use special field name delimeters ([]). ArcPy has a handy AddFieldDelimiters method to make your expressions .mdb-safe ("wks" below is the workspace where the table view you are querying against lives): whereExpr = "{0} = \'{1}\'".format(arcpy.AddFieldDelimiters(datefield,wks),dat) Depending on the wks type, you get from this something like: gdb, shape: "DATE" = '2012-01-02' mdb:  [DATE] = '2012-01-02' One more thing, since you were mentioning dates: be wary of date fields, they have all kinds of gotchas. More details: Arc 10 help: SQL reference for query expressions used in ArcGIS ... View more

unfortunately the result of always comes as "<Field object at 0x55c7f90[0x577c590]>" and I never get the field name. Sorry about that, fabl is right, you need to pull out that name attribute, his suggestion: str([field.name for field in arcpy.ListFields(inMemInt)]) is right on. One thing that may be tripping you up is if you go through shapefile format at some point in your processing, Shape_Length is more than 10 characters, so it can get truncated to SHAPE_LENG. ... View more

Although this thread never really answered my question on how to uninstall Python 2.7 it is helpful for trying to understand some reasons to keep it around. If you interactively launch the Setup.msi and choose "modify" you can uninstall Python, like any other piece of the system. I did this yesterday and it worked fine. I'm sure there is a way to batch this using msiexec if you need to. Otherwise it appears that the script provided by Curt can be used to take advantage of the normal Python 2.7 installation.  I'd much rather have a regular version of Python on my machines then the "private" installation that comes packaged with ArcGIS 10.1. I'm pretty sure there is nothing different about the Esri "private" python/numpy (+matplotlib in 10.1) package from the 2.7.2 you'd download from python.org except it is the exact version they test all the tools against. If you want to install it separately the install packages are in the Python folder in the ArcGIS install media. The only thing that makes it "Esri" I think is the default location (Python27\ArcGIS10.x), its packaging with ArcGIS in Add/Remove Programs, and the .pth file the ArcGIS installer drops in the site-packages folder so you can see arcpy. Esri folks have told me  they expect any 2.6.x python to work with ArcGIS 10 and any 2.7.x python to work with ArcGIS 10.1. But of course the versions they release with ArcGIS are best practice of you have no special need for a different Python version. ... View more

Just did a bit of research, and I believe that the Python in your system PATH will be used by default to run files from the command line, but the file association (as shown in your post) defines which Python is used when double clicking a file in Windows Explorer. I'm pretty sure the file association is used at the command line as well. See the help for the ftype command: > ftype /? ...     ASSOC .pl=PerlScript     FTYPE PerlScript=perl.exe %1 %* would allow you to invoke a Perl script as follows:     script.pl 1 2 3 I tried clearing my path to see if it would help just in case. Unfortunately it did not help. For some reason the system is still launching my EPD python (E:\python27_epd32\python.exe) instead of the ArcGIS one (D:\Python27\ArcGIS10.1\python.exe). I'm wondering if the Python installer set something in the registry that is overriding the file association. A clue: WingIDE is also opening EPD unless I explicitly set the project properties to open the ArcGIS Python. Note PYTHONHOME is not set (it would have come up with the "set py" command below). >set py PYTHONPATH=D:\ArcGIS\Desktop10.1\ArcToolbox\Toolboxes\USGS_EGISTools\scripts > set PATH=. > set path Path=. PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1 > x.py 2.7.3 |EPD 7.3-2 (32-bit)| (default, Apr 12 2012, 14:30:37) [MSC v.1500 32 bit (Intel)] hello there Traceback (most recent call last):   File "E:\work\x.py", line 4, in <module>     import arcpy ... View more

If you only need to use Python without any ArcGIS tools this will work just fine. However, you will be completely unable to use Arcpy from that separate Python. I have successfully worked around this with the Enthought Python Distribution by starting EPD with a bat script that adds ArcGIS paths to the PYTHONPATH: :: start EPD32 python prompt with arcpy available @echo off set EPDPATH=E:\python27_epd32 set AGSPATH=D:\ArcGIS\Desktop10.1 :: save paths set PATHENV=%PATH% set PPATHENV=%PYTHONPATH% :: set paths EPD with access to arcpy set PATH=%EPDPATH%;%EPDPATH%\scripts;%PATH% set PYTHONPATH=%PYTHONPATH%;%AGSPATH%\bin;%AGSPATH%\arcpy;%AGSPATH%\ArcToolbox\Scripts cmd /c %EPDPATH%\python.exe :: restore paths set PATH=%PATHENV% set PYTHONPATH=%PPATHENV% :: delete variables set EPDPATH= set AGSPATH= set PATHENV= set PPATHENV= ... View more

Now that Python is no longer on my machines it is no longer an issue and I am a happy camper. Somehow, I doubt your users are as happy as you are. Without Python you are disabling many useful ArcGIS tools. For example, there are many ArcGIS tools that are Python scripts that assist with repetitive actions. By disabling Python you are seriously hobbling your users' productivity (especially with GIS data development, which often involves repetitive task flows). My two cents, based the last 30 years on both sides of the security fence: Computer security must be a balance between allowing people to get their work done and keeping systems as safe as possible. Users are the most important part of the security picture (think, email attachments, account security, social engineering) and are less likely to be team players when you lock down their systems to the point that you are making it difficult to do their work. Furious users may be a much bigger security threat than anything you read about on the CERT bulletins. ... View more

I'd try importing the toolbox into arcpy. That may be all you need to do: arcpy.ImportToolbox("path/MobileTools.tbx") ... View more

gp.CalculateField_management(inMemInt, "Traffic", "[AGADT2005] * [Shape_Length]", "VB", "") This looks fine - so I would make sure that your fields are all there and named exactly as you expected them by inserting this line right before the CalculateField: arcpy.AddMessage(str(arcpy.ListFields(inMemInt))) ... View more