Latest Contributions by MarcinGasior

One approach may be: - convert Polygon To Line (if you don't have ArcInfo license, use ET GeoWizards) - calculate Euclidean Distance from lines (distance will be calculated from both sides of a line, when line will have 0) Example: [ATTACH=CONFIG]12697[/ATTACH] ... View more

In my configuration ESC works well (AG10+SP2, WinXP_pro+SP3). Anyway, I prefer turning off 'heavy' layers and see the effect of those minor changes:) ... View more

I was not sure which coordiate system I had. I think, it's essential to know which coordinate system you have (at least if it's geographic or projected) when importing X,Y data. @2) It's hard to say what you do wrong. I suppose, you should follow the georeferencing help. There is step by step instruction how to georeference raster. ... View more

Are your X,Y data in geographic (longitude, latitude) or projected (eg. meters) coordinates? If XY data are in geographic coordinates you should select Geographic Coordinate System when creating shp (most probably WGS 1984). If it doesn't work, check if the coordinates in table are correct (numeric, do not have any spaces or other strange characters). ... View more

In file A there must be more than one POI in the same location. It's easily to imagine that in one place there's a bar and a shop. So the selection result is ok. You can separate unwanted POIs by Attribute Query or by Definition Query (in layer properties) before selecting by location. ... View more

Congrats for script debugging - it's first step to dive into Python;). (I'm also at the beginning of the journey with Python.) I edited my last post and added 2 lines at the end of the code which make it working as it should. I think that just removing a join can be more efficient solution than making and deleting feature layer (especially when therere larger datasets). ... View more

You can force legend to create multiple columns by selecting 'Place in new column' for layer which should be in new column and leaving number of columns=1. Look at this picture: [ATTACH=CONFIG]12545[/ATTACH] Only the FC4 is selected to 'Place in new column' and number of columns in 'Columns:' field is left default (1) for each layer. All the layers below FC4 (in 'Legend Items:' list) are placed in this new column. If you for example addictionaly select FC7 to 'Place in new column', there will be 3 columns in legend: 1: FC1,FC2,FC3; 2: FC4,FC5,FC6; 3: FC7,FC8. You can achieve this same effect by setting numbers of columns in 'Columns:' field to 2 for FC4 and leaving 'Place in new column' unselected: [ATTACH=CONFIG]12546[/ATTACH] ... View more

Aha, you have one input feature class, and want to make 10 new? Or just add data to one input feature class? In first case, try code (it wasn't tested, but it's quite simple so you should be able to follow what's going on): import arcpy arcpy.env.overwriteOutput = True from arcpy import env import os arcpy.env.workspace = r"C:\Project\Project.gdb" model_nodes = "model_nodes" spField="SP" dataTable = "DeltaWL" #create Feature Layer for input feature class arcpy.MakeFeatureLayer_management(model_nodes, "model_nodes_FL") #loop through possible classes and for each create TableView for sp in range(1,11): #range (1 to 10)     whereClause = 'spField = ' + str(sp)     tableViewName = "Delta_WL" +str(sp) #name is based on 'sp' iterator     arcpy.MakeTableView_management(dataTable, tableViewName, whereClause)         #join data from Table View with 'Add Join' tool     #"KEEP_COMMON" parameter cause preserving only maching records     arcpy.AddJoin_management("model_nodes_FL","ID", tableViewName, "Cell_ID","KEEP_COMMON")     #save feature layer with joined data     arcpy.CopyFeatures_management("model_nodes_FL", "model_nodes_joined"+str(sp))         #remove existing Join to allow make new join with new subset (the second parameter is join name, which is name of joined data table)     arcpy.RemoveJoin_management("model_nodes_FL", "DeltaWL") EDIT: Code corrected. ... View more

1. Converting CSV to table/geodatabase table, as Mathew suggested, greatly simplyfies processing. 2. To display Table View content you can create a Search Cursor on it or create "normal" table with 'Copy Rows' tool. 3. I created the following script which joins all fields from CSV data tablein GDB to separate feature classes based on value in SP field: import arcgisscripting gp = arcgisscripting.create(9.3) gp.workspace = r"Z:\Work\AttrFromCSV_to_FC.gdb" csvDataTable = r"Z:\Work\AttrFromCSV_to_FC.gdb\CSVdata" #Create list of feature classes in current workspace #ASSUMPTION: feature class layers share part of name with SP value: eg. layer_1 for SP=1 fcLst = gp.ListFeatureClasses() #loop through possible classes and for each create TableView for sp in range(1,11): #range (1 to 10)     whereClause = '"SP" = ' + str(sp)     gp.MakeTableView_management(csvDataTable,"csv_" + str(sp), whereClause)     #for corresponding feature class in workspace create Feature Layer     fcName = "SamplePoints_" + str(sp) #name of input Feature Class     if fcName in fcLst:         inputFLName = "inputFC_" + str(sp) #name of temporary Feature Layer         gp.MakeFeatureLayer_management(fcName, inputFLName)                 #join data from Table View with 'Add Join' tool         #"KEEP_COMMON" parameter cause preserving only maching records         gp.AddJoin_management(inputFLName,"ID", "csv_" + str(sp), "Cell_ID","KEEP_COMMON")                 #save feature layer with joined data         gp.CopyFeatures_management(inputFLName, "Joined_"+fcName)         print "Joined_" + fcName + " created" If you have AG10 or ArcInfo license with AG9.3: Instead of using AddJoin and CopyFeatures, you can use JoinField_management tool which is able to join specified list of fields to oryginal feature class (without creating new one). ... View more

How the specified angle is measured? From north (as in picture) or in another way? [ATTACH=CONFIG]12472[/ATTACH] Is the point grid regular? If you don't have to many points, you can try do it manually: - Create quite long line which can intersect lake boundary from each point. - Copy this line and snap to point. Repeat for every point. - Cut lines layer with lake layer in geodatabase - one of attributes of each line will be Length. ... View more

In last part of the script try: for pt in pts:         if pt.Trace in singlelst: instead of: for pt in pts:     for i in singlelst:         if pt.Trace == int(i): I simulated similar script situation with this code change and for feature class with over 550 000 rows, ~13 000 rows were deleted in less than 4 minutes. ... View more

ListFeatureClasses() has optional parameters: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//000v0000001n000000 So you can add "*_vw_*" as a wild_card or specify geometry type. ... View more

I think, I've found the problem. The list should be in parentheses: '... IN ({3, 4, 5, 7, 8, 9, 13, 18}) ...' It seems to be undocummented behavior, isn't it. ... View more

Unfortunatelly it solves the problem in Raster Calculator only. I tried to run this expression in Single Output Map Algebra (SOMA): CON((D:\tmpGIS\C_br_Diff.img == 0), 0, CON((IsNull(D:\tmpGIS\C_br_2050.img IN {3, 4, 5, 7, 8, 9, 13, 18})), 20,10)) SOMA throws an error: ERROR 010394: Map Algebra expression: Syntax error at location 53 (around D:\tm) of expression... I tried several combination of spaces and patentheses but didn't help. Also data in different source doesn't help. But when I delete 'IN {3, 4, 5, 7, 8, 9, 13, 18}' the whole expression runs ok. So there is still some problem with IN statement. Any help will be appreciated. ... View more

Thank you, Bill. Your answer solves the problem:) ... View more