Latest Contributions by curtvprice

My 2 cents: Raster attribute tables are very tricky, as they are implemented differently for different image types. For example, with raw data formats like .bil, they are stored in an .aux/.aux.xml file. With .tiffs, the raster table is an RGB colormap table stored in the image header. ERDAS .img files look like more advanced tables, but I'm not sure you can successfully modify an .img's table because it is stored in the image itself. With grids, you may have better luck, as the table is a good old INFO table stored in the info folder parallel to the grid. In general, I've found it best practice to only use the VALUE and COUNT fields and handle any other table information by joining to a separate lookup table. This generally makes more sense because most raster tools drop all variables from the output except VALUE and COUNT. Your approach looks like it could be much more efficiently done  (and perhaps with more success with non-grid formats, but I don't know...)  by creating a lookup table in the in_memory workspace, populating it with a cursor, and then doing a Add Field / Add join / Calculate Field, or Join Field to copy the data over. But IMHO the separate ancillary data table is the most reliable path. ... View more

   Because of edge effects, the tiles would need to overlap, and then the overlaps would need to be removed when joining the processed tiles back together.  It could be automated, and perhaps someone else has already written a script to do that Should be noted that the Mosaic tool (and mosaic data sets on the fly) can handle the stitching back together with averaging overlapping areas. Splitting apart, well, we still need a script for that. ... View more

Here's some reusable code: import arcpy import os def ArcGISProfile(profilePath=None):     """ArcGIS Windows user profile path"""     APPDATA = arcpy.GetSystemEnvironment("APPDATA")     if arcpy.GetInstallInfo("DESKTOP")['Version'].find("10") == -1:        path = os.path.join(APPDATA,"ESRI")     else:        path = os.path.join(APPDATA,"ESRI/Desktop10.0/")     return os.path.realpath(os.path.join(path,profilePath)) print ArcGISProfile("ArcToolbox\CustomTransformations") This returns (on XP): C:\Documents and Settings\cprice\Application Data\ESRI\Desktop10.0\ArcToolbox\CustomTransformations ... View more

There are a bunch of related NIM's on this, all having to do with the above .dll issue and metadata tools in the 10.0 Conversion toolbox. Hopefully this will be fixed in SP4. (Unfortunately I don't see any of these NIM's on the current 10.0 SP4 "issues to be addressed"...) NIM058011 NIM063624 NIM068626 NIM063624 NIM063623 NIM062944 NIM070175 Several of the NIM's mention a possible workaround if you can't do the GAC/.dll fix: try wrapping the tool inside a model and call that from Python. ... View more

. The make feature layer is the very first tool in my model and, in theory, should erase the specified fields for the rest of the tool as the subsequent parts work off this feature layer. Make Feature Layer creates a view of the data in memory that marks some fields as not visible. They still are there though. You probably want to run the Delete Fields tool on an intermediate dataset to get rid of fields you do not want. ... View more

  Please kindly help and tell me how to rename and then save the new models (with tbx extension) I created in the �??ModelBuilder�?� Save tool (i.e. I want the new models (with tbx extension) renamed and then saved in the "red" Toolbox/trunk). Models don't have a tbx extension. Models must be saved inside a toolbox (.tbx) which serves as sort of a workspace for models and scripts. If you create a model from scratch with the model button in the desktop interface, you need to save them inside a toolbox. In the save dialog at the upper right there is (now, didn't used to be!) a button to create a toolbox in the current folder. Then you can navigate into that toolbox, name the model, and hit save. ... View more

The arcpy example just posted by Jake S seems like it should address your original issue. but I think these extra quotes may cause trouble:             arcpy.MakeXYEventLayer_management('"' + fileTemp + '"', "X", "Y", outLayer) instead:             arcpy.MakeXYEventLayer_management(fileTemp, "X", "Y", outLayer) ... View more

math (sorry) is a module that is part of the standard library, ie it's in all python distributions. >>> import math >>> help(math) If you're new to Python, be sure and check out: Brief" rel="nofollow" target="_blank">http://docs.python.org/tutorial/stdlib.html]Brief Tour of the Standard Library ... View more

There's a great programmer-oriented tutorial to get started with Tkinter in the Mark Lutz's Programming Python.The biggest advantage of Tkinter is that it's the most popular -- and is part of the standard library in every Python distribution -- no extra installs! [URL=http://matplotlib.sourceforge.net/]Matplotlib[/URL] is not part of the standard library, but is also very popular, easy way to display data.  Esri is including matplotlib (and numpy, which I think was added for 9.3) in the standard ArcGIS 10.1 installation. ... View more

Looks like something you should report! If you get a NIM, please add it to this thread. I am wondering whether the issue may be data format related... is "raster" not a grid? The calculator may be doing a bad data translation on the direct read of the raster (a new capability in 10.0, in 9.3 it would convert to Esri Grid format (EGF) first).  Kind of weird that the tools would work when map algebra doesn't -- the tools are the same now under the hood. Something to try is convert your raster to EGF (using Copy Raster) and try Raster Calculator with that. ... View more

Could someone point me in the right direction on how I would do this? You can read geometry and create features using cursors. It's a little tricky (and slow) but it can be done. Here's the help on that: Arc" rel="nofollow" target="_blank">http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//002z0000001s000000]Arc 10 Help: Working with geometry in Python Be sure and avoid doing all the geometry yourself, there are some very handy functions in the standard library, especially math. Field Calculator supports a lot of calculations too - if you want store things in the attribute table: [post=169592]Common Python geometry calculations in the Field Calculator [/post] ... View more

I'm new to Python and what I want to do is very similar, only my list is of integer values (created by using range()). Using the above example, how would the query expression be changed if FIPSlist was integer instead of string (query field is also integer)? Just do it without the quotes. Also, to use the integer as part of the expression you need to convert the number to a string, using str() too: FIPSlist = range(5) # (0,1,2,3,4) for fip in FIPSlist:     query = "FIPS_PARIS = " + str(fip)     arcpy.TableSelect_analysis("Master_TAHI", FIPSpath + r"\FIPS" + str(fip) + ".dbf",query) ... View more

ArcMap 10.3 with spatial anlayst extension. Just to clarify, do you mean 10.0 SP 3? ... View more

Interestingly enough, a "zone" is processed in about 20 seconds at the outset, and then towards the end of the 800 features, it slows down to about 5 minutes to process one zone. My experience is that the gp/arcpy scratch name methods can be very slow when the workspace in which you are generating scratchnames gets full of many files. This can slow down all tools! You may get better performance if you just create an empty folder/workspace and generate names using sequence numbers. I have gotten in the habit with my general purpose script tools (like the [post=124423] NAWQA toolbox[/post]) of creating a temporary folder and workspace so I don't need to worry about file name collisions and can avoid waiting for the scratchname method! ... View more