Latest Contributions by MarcCusumano

I suppose that would work but we already have the code set up to do a quick copy of a handful of features to a new file gdb, delete the old, and rename the new. I just need a quick way to handle an exception where the shutil.rmtree command cannot execute due to a file lock. ... View more

If it is OK to have the buildings stacked as a single point in the center of their respective administrative polygons, you could run this process: 1) Convert all administrative polygons to points using Feature to Point tool. 2) Calculate X / Y values on administrative boundary points. 3) Calculate new field in your buildings feature to equal feature name (administrative code) : see http://mappingcenter.esri.com/index.cfm?fa=ask.answers&q=1529 (9.3, you may need to research how to do this in 10) 3) Join your buildings feature with administrative boundaries feature based on administrative code. 4) Export Join, which will now have admin X / Y. 5) Right click the "SHAPE" field in your newly exported feature, select Python, click "Show Codeblock" and enter the following into the Pre-Logic Script Code: def XYsetVALUE( shape, X_value, Y_value):    point = shape.getPart(0)    point.X = X_value    point.Y = Y_value    return point Enter the following into the "Shape" box: XYsetVALUE ( !SHAPE!, !X!, !Y! ) Click OK. Your building points will move to their respective administrative boundaries. ... View more

Great news! I got the script working. Here is the final code: ==================================================================================================== import arcpy from arcpy import env env.workspace = "E:\GasLeaksProject\2012\GasLeaks.gdb" mxd = arcpy.mapping.MapDocument("CURRENT") df = arcpy.mapping.ListDataFrames(mxd, "Layers")[0] Layer = arcpy.mapping.ListLayers(mxd, "ImplausibleReads", df)[0] #arcpy.MakeFeatureLayer_management("Gas_Selection", "ImplausibleRead") # Create a search cursor, iterate through the Implausible Reads Feature, getting and zooming to respective extents and exporting layout to JPEG. rows = arcpy.SearchCursor("E:/GasLeaksProject/2012/GasLeaks.gdb/Gas_Selection", "", "", "OBJECTID") #rows = arcpy.GetCount_management("Gas_Selection") currentState = " " # Iterate through the rows in the cursor for row in rows:       [INDENT] if currentState != row.OBJECTID:[/INDENT]            [INDENT][INDENT] currentState = row.OBJECTID             where_clause = "\"OBJECTID\"=" + str(currentState)             arcpy.SelectLayerByAttribute_management (Layer, "NEW_SELECTION",  where_clause )             df.zoomToSelectedFeatures()             df.scale = 6914             arcpy.RefreshActiveView()             arcpy.SelectLayerByAttribute_management (Layer, "CLEAR_SELECTION",  "" )             arcpy.mapping.ExportToJPEG(mxd, r"E:\GasLeaksProject\JPEG\OBJECTID" + str(currentState) + ".jpeg", df_export_width=1500, df_export_height=1200, resolution=300, jpeg_quality=70)[/INDENT][/INDENT] del mxd ==================================================================================================== Thanks again! ... View more

OK I made the changes you suggested and also changed my data sources to a local drive whereas before it was a remote connection. I also changed the SearchCursor method to specify the OBJECTID field, and also modified the "SelectLayerByAttribute" query to simply search for OBJECTID = 1 just to see if I could get it working. Here is the code I am now running: ======================================================================================================== import arcpy from arcpy import env env.workspace = "E:\GasLeaksProject\2012\GasLeaks.gdb" mxd = arcpy.mapping.MapDocument("CURRENT") df = arcpy.mapping.ListDataFrames(mxd, "Layers")[0] Layer = arcpy.mapping.ListLayers(mxd, "ImplausibleReads", df)[0] # Create a search cursor, iterate through the Implausible Reads Feature, getting and zooming to respective extents and exporting layout to JPEG. rows = arcpy.SearchCursor("E:/GasLeaksProject/2012/GasLeaks.gdb/Gas_Selection", "", "", "OBJECTID") currentState = " " # Iterate through the rows in the cursor for row in rows: [INDENT]if currentState != row.OBJECTID:[/INDENT] [INDENT][INDENT] currentState = row.OBJECTID arcpy.SelectLayerByAttribute_management (Layer, "NEW_SELECTION", ' "OBJECTID" = 1 ' ) df.zoomToSelectedFeatures() arcpy.RefreshActiveView() arcpy.mapping.ExportToJPEG(mxd, r"E:\GasLeaksProject\JPEG\OBJECTID" + str(currentState) + ".jpeg", df_export_width=1500, df_export_height=1200, resolution=300, jpeg_quality=70)[/INDENT][/INDENT] del mxd ======================================================================================================== This works and exports the extent of the feature with OBJECTID = 1, but then continues exporting the same feature only with a larger extent. When I try adding the "currentState" variable to the SelectLayerByAttribute line, it does not work, and returns <type 'exceptions.SyntaxError'>: invalid syntax (JPEG.py, line 20) Failed to execute (Script). I'm oging to continue playing around with it to see if I can get it working. Thanks for your help ... View more

That is what I figured. I will need to come up with a way to do this without using DDP. Here is what I have so far (this is solely to emulate the DDP functionality inside ArcMap for now; once it is working I will modify it to work from a standalone Python script). "ImplausibleReads" is the layer I am trying to export as DDP, which is built on the "GAS_SELECTION" feature class. import arcpy from arcpy import env env.workspace = "H:\SP1G0\Gas Leaks\GasLeaks.gdb" mxd = arcpy.mapping.MapDocument(mxd = "CURRENT") df = arcpy.mapping.ListDataFrames(mxd, "Layers")[0] Layer = (mxd, "ImplausibleReads", df)[0] # Create a search cursor rows = arcpy.SearchCursor("Gas_Selection") currentState = " "   # Iterate, select and zoom to each row in the cursor and export to JPEG   for row in rows:        [INDENT]if currentState != row.OBJECTID:[/INDENT]             [INDENT][INDENT]currentState = row.OBJECTID[/INDENT][/INDENT]             [INDENT][INDENT]arcpy.SelectLayerByAttribute_management(Layer, "NEW_SELECTION", ' "OBJECTID" = currentState ' )[/INDENT][/INDENT]             [INDENT][INDENT]df.zoomToSelectedFeatures()[/INDENT][/INDENT]             [INDENT][INDENT]arcpy.RefreshActiveView()[/INDENT][/INDENT]             [INDENT][INDENT]arcpy.mapping.ExportToJPEG(mxd, r"H:\SP1G0\Gas Leaks\JPEG\Connection_Obj__" + str(currentState) + ".jpeg", df_export_width=1500, df_export_height=1200, resolution=300, jpeg_quality=70)[/INDENT][/INDENT] del mxd This results in an error "<type 'exceptions.RuntimeError'>: Object: Error in executing tool Failed to execute (Script)." ... View more

Thank you Jeff, that will make the process a lot cleaner. I am trying to automate this, so that when data is dumped into a feature class the script will create the data driven pages automatically and export to JPEG. Is there a way to build data driven pages without doing it manually through ArcMap? ... View more

Can "Clip to Graphics Extent" be used in a python script utilizing the ArcPy.ExportCAD_conversion method? We are trying to export DXF tiles based on a grid layer and providing an extent makes a selection of features passing through, but does not clip the output to the proper extent, resulting in features running way outside the boundaries of each tile. ... View more

Yes I had the table in a .dbf, reference data in a shapefile and the address locator inside a folder. ... View more

Has anybody else been experiencing this issue? Even copying the table to a .dbf and the reference data into a shapefile outside of a file geodatabase the process is very slow, often requiring up to 48 hours to geocode a reasonable number of addresses (<200K). The process is always run on either a new SSD or a RAM Disk. I even got the MultiProcessGeocode python script running and it is still taking forever. Before SP3 this process would take no longer than an hour... ... View more

No I've not tried copying the locator into a folder. The operation from this morning is still running but once it's done I'll try that. I won't be able to provide you with the data as it is confidential, but thanks for the help anyway. ... View more

Thank you for your timely response, Brad. The address locators I am using were built by myself yesterday. I built three separate address locators: -One using the latest TeleAtlas street routing data, using US Address - Dual Ranges (v10 locator) and US Streets with Zone (9.3.1 locator) -One using a polygon feature class of parcels. using US Address - Single House (v10 locator) and US One Address with Zone (v9.3.1 locator) -And finally one using our customer service points, using the same locators as as the parcels. The locators have worked great for 347,000 out of 360,000 features which is great. My frustration has arisen in trying to get the final 13,000 features geocoded. I will look into the documentation you provided. Thank you, I'll let you know how it goes. ... View more

Hello again, I'm still encountering this issue of the address locator / geocoding tool giving high scores (even 100) to addresses matched in the wrong zip code. If possible I would have these matches receive a score of zero as they are incorrect. I am running ArcGIS v10.0 (Build 3200) with SP2. All patches are installed including the "geocoding memory leak" patch. Also, when building an address locator from TeleAtlas street data, the geocoding service will use the zipcode field to some extent, but will still place very high scores (>95) for matches in the wrong postal boundary. I have to run a spatial join on a postal boundary layer and do a select by attributes to find the matches in the correct zip codes, which always eliminates over 95% of the matches. Also, the process seems to place low priority to Suffix and Prefix Type. An address of "12th St" will be matched with "12th Ave" and be given a very high score (>90). Also "N 12th St" will be matched with "S 12th St" with a high score (>90). Basically it seems the only field the address locator places any weight to is the street name and civic number. By the way I am not using composite locators of any kind. Has this issue been resolved? Is there a way to force the address locator to use these fields to validate a match? The geocoding functions worked wonderfully in 9.3.1 which makes this a real shame. *EDIT* I have imported the address locators from 9.3.1 and am experiencing the same issues. ... View more