POST
|
Looks like I will be rewriting a lot of v9.3 code to make it arcpy compatible...
... View more
08-03-2010
10:05 AM
|
0
|
0
|
1293
|
POST
|
Not sure what's wrong... Take look at the sample code: http://forums.arcgis.com/threads/9512-Rectangle-for-Clip_management-tool-in-arcpy (my post Aug 2nd @10:25). Are you sure that your raster and shapefile are using the same projection?
... View more
08-03-2010
09:18 AM
|
0
|
0
|
229
|
POST
|
Preserving the original OID is a good idea! And the .oidfieldname property is the right one to use... The output names are given the default toll name suffix by the Toolbox GUI seemingly automatically now in v9.3+ (the default naming is not handled in a controlled fashion by the script of tool parameter settings). It wasn't this way pre-v9.2, and depending on how you look at it, it can be a good or bad thing. Personally I don't like it, since it seems to override the "default" parameter values that you assign in the tool setup dialog.
... View more
08-03-2010
09:02 AM
|
0
|
0
|
935
|
POST
|
You can build a drop down box (aka picklist) via the Toolbox GUI quite easily: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Understanding_script_tool_parameters/001500000007000000/ Although I have never done it, you can also build elaborate Python GUIs via: wxPython: http://www.wxpython.org/ TkInter: http://wiki.python.org/moin/TkInter
... View more
08-02-2010
01:20 PM
|
0
|
0
|
326
|
POST
|
Something like: inputTable = r"C:\temp\test.gdb\blah"
joinTable = r"C:\temp\test.gdb\lut"
gp.makefeaturelayer(inputTable, "FL")
gp.addjoin("FL","ID",joinTable,"ID")
updateRows = gp.updatecursor("FL")
updateRow = updateRows.next()
while updateRow:
if updateRow.getvalue("lut.ANIMAL_TYPE") == "CAT":
updateRow.FOOD_TYPE = updateRow.getvalue("lut.ANIMAL_TYPE") + " FOOD"
updateRows.updaterow(updateRow)
updateRow = updateRows.next()
del updateRow
del updateRows
... View more
08-02-2010
11:11 AM
|
0
|
0
|
839
|
POST
|
Something like: inputTable = r"C:\temp\test.gdb\blah" joinTable = r"C:\temp\test.gdb\lut" gp.makefeaturelayer(inputTable, "FL") gp.addjoin("FL","ID",joinTable,"ID") updateRows = gp.updatecursor("FL") updateRow = updateRows.next() while updateRow: if updateRow.getvalue("lut.ANIMAL_TYPE") == "CAT": updateRow.FOOD_TYPE = updateRow.getvalue("lut.ANIMAL_TYPE") + " FOOD" updateRows.updaterow(updateRow) updateRow = updateRows.next() del updateRow del updateRows
... View more
08-02-2010
11:11 AM
|
0
|
0
|
839
|
POST
|
Hmm... Maybe a bug in v10? Here's an excerpt of some v9.3 code that works for me: #Process: Creates a blank GDB fgdbName = "oesf_score_gnn_raster" fgdbPath = root + "\\" + fgdbName + ".gdb" gp.CreateFileGDB_management(root, fgdbName); showGpMessage() #Process: Extract the OESF hcpUnitFC = r"\\Snarf\am\div_lm\ds\gis\tools\sde_connections_read\ropa_gis_layer_user.sde\ROPA.HCPUNIT" oesfFC = fgdbPath + "\\oesf" gp.Select_analysis(hcpUnitFC, oesfFC, "HCPUNIT_NM = 'OESF'"); showGpMessage() #Process: Buffer the oesf oesfBufferUnits = "FEET" oesfBufferDistance = "35000" #NOTE: This MUST be the same buffer distance as in 'nso_make_path_distance_grids_v93.py' oesfBufferFC = fgdbPath + "\\oesf_buff_" + str(oesfBufferDistance) + oesfBufferUnits.lower() gp.Buffer_analysis(oesfFC, oesfBufferFC, str(oesfBufferDistance) + " " + oesfBufferUnits.upper(), "FULL", "ROUND", "NONE", ""); showGpMessage() #Process: Clip the GNN data to our area of interest gnnReadGrd = r"\\snarf\am\div_lm\ds\gis\tools\sde_connections_read\raster_gis_layer_user.sde\SHARED_LM.GNN_20100303" gp.extent = oesfBufferFC gp.extent = snapExtentToRaster(gp.extent, gnnReadGrd) gp.mask = oesfBufferFC gp.cellsize = gnnReadGrd gnnClipGrd = fgdbPath + "\\gnn_clip" gp.Clip_management(gnnReadGrd, gp.extent, gnnClipGrd, oesfBufferFC, "", "CLIPPINGGEOMETRY")
... View more
08-02-2010
10:25 AM
|
0
|
0
|
1293
|
POST
|
Check out the SpatialJoin tool. This should do exatly what you want. Make the TargetFeatures your polygons, the JoinFeatures your points. Be sure to specify the join operation as a 'JOIN_ONE_TO_MANY'.
... View more
08-02-2010
10:17 AM
|
0
|
0
|
241
|
POST
|
Yes you can, and also can do this in pre-v10. But note that you can only alter field values in the input table (not the join table).
... View more
08-02-2010
10:09 AM
|
0
|
0
|
839
|
POST
|
Try this: import arcpy arcpy.env.workspace = r"C:\Temp" raster = "some_raster" outraster = r"C:\output_raster" extentFC = r"C:\GIS_Data\test_extent2.shp" dsc = arcpy.describe(extent) arcpy.Clip_management (raster, dsc.extent, outraster) ###or if you want to mask it using extentFC as the outline: ##arcpy.Clip_management (raster, dsc.extent, outraster, extentFC, "", "CLIPPINGGEOMETRY")
... View more
08-02-2010
10:00 AM
|
0
|
0
|
1293
|
POST
|
Yes, like I said in my previous post, you need to split the contours up, and then merge them back together (using the Merge tool, not the Union, which is for polygon spatial overlays by the way).
... View more
07-31-2010
08:56 AM
|
0
|
0
|
899
|
POST
|
Probably the most efficient method would be to figure out what tile contained each line features centroid. That way you didn't have to break any of the line feature into two or more pieces. Use the FeaturetoPoint or FeatureVerticesToPoint tools and then the intersect or identity tools to identify what tile each point resides in.
... View more
07-30-2010
01:12 PM
|
0
|
0
|
1006
|
POST
|
Sometimes the countours are too big to process all at once. Try something like this to make 10ft contours at different intervals, and then merge them all together. gp.Contour_sa(grid, r"C:\temp\cont0.shp", "100", "0", "") gp.Contour_sa(grid, r"C:\temp\cont10.shp", "100", "10", "") gp.Contour_sa(grid, r"C:\temp\cont20.shp", "100", "20", "") gp.Contour_sa(grid, r"C:\temp\cont30.shp", "100", "30", "") gp.Contour_sa(grid, r"C:\temp\cont40.shp", "100", "40", "") gp.Contour_sa(grid, r"C:\temp\cont50.shp", "100", "50", "") gp.Contour_sa(grid, r"C:\temp\cont60.shp", "100", "60", "") gp.Contour_sa(grid, r"C:\temp\cont70.shp", "100", "70", "") gp.Contour_sa(grid, r"C:\temp\cont80.shp", "100", "80", "") gp.Contour_sa(grid, r"C:\temp\cont90.shp", "100", "90", "")
... View more
07-29-2010
08:56 AM
|
0
|
0
|
899
|
POST
|
Hmm... Not sure what the heck is wrong. copy features is the correct tool, but not sure why it is taking so long. I have heard about this sort of thing on the old forums (Copy Features was taking forever). Some things to try: 1) Once you make the XYEventLayer, try making a new feature layer from GWLayer using the gp.MakeFeatureLayer tool, then use the feature layer as input into the CopyFeatures tool. 2) Make a TableView out of your .mdb table (using MakeTableView tool), then run the XYEventLayer tool using the table view as input.
... View more
07-28-2010
12:45 PM
|
0
|
0
|
757
|
Title | Kudos | Posted |
---|---|---|
1 | a month ago | |
1 | 02-13-2012 09:06 AM | |
2 | 10-05-2010 07:50 PM | |
1 | 02-08-2012 03:09 PM | |
1 | 10-31-2013 02:18 PM |
Online Status |
Offline
|
Date Last Visited |
a month ago
|