Is there a way to delete layout elements through arcpy.mapping? I'm not seeing one in the 10 docs.
I presume that a workaround would be to just change the X or Y position of the element to outside the bounds of the page (although I haven't tried it), but there should really be a clean way to delete a layout element with an arcpy.mapping script.
You can not create or remove layout elements using arcpy.mapping.
You can either move elements on and off the page or like Dan suggests, in the case of text elements you can set the string to be a blank space.
NOTE - don't set the string to be completely empty (e.g., ""). This causes issues that are being addressed at SP2. The UI doesn't let you do it either. Set the string to be a single blank (e.g., " ").
Thanks for the responses everyone. I can confirm that moving an element off the page does work, as does Dan's suggestion of zeroing out the text in a text element.
Jeff, is there some kind of design reason that I'm missing for why you can't create or delete layout elements directly via arcpy.mapping? This is the exact kind of one-off map composition functionality that makes arcpy.mapping useful, but it's missing. I can't imagine that it would be that difficult to implement (especially deleting), just a few more ArcObjects routines exposed to the Python api...
It is a great question but of course the answer isn't that simple. Here is a very quick summary:
Our objective with arcpy.mapping was NOT to recreate ArcObjects capabilities but to simplify the scripting experience. If we gave you the ability to add new objects (e.g., scale bar) we would need to expose ALL of the properties associated with adding that object (aka ArcObjects).
Arcpy.mapping is intended to work with already authored mxds and layer files. The idea is that we use ArcMap and all of its 100's of buttons, menus, properties dialogs to author the content and we use arcpy.mapping to automate it.
It is difficult for us to draw a line in the sand and are always looking for good feedback on when/how we should expand the API to further enhance map automation (not map creation).
At 10.1 we are going to expand the symbology API because our users showed us some really nice use cases.
I had the same problem like Michael and would like to create resp. delete Layout elements using Python. At the same time I can completely understand that it is not a small issue for ESRI to give more power to the Python API. Still it would be great if Esri could enhance the Pyhton capabilities because it is easier to program than e.g. ArcObjects for Java. I am a big fan of the Python API esp. because of the great documentation with all the example codes! You guys at Esri do a really good job with it and should go on with it.
At 10.1 we added graphic element and text element cloning. If you have a pre-authored text element in your layout, then you can clone it an place it as many times as you need.
At 10.1 we added graphic element and text element cloning. If you have a pre-authored text element in your layout, then you can clone it an place it as many times as you need.
Jeff
Jeff -- I think I understand this now. From my other thread in the Python forum, I was under the impression that cloned elements could be added to different/new .mxd documents. From what you mention above, this sounds like it is not possible with the arcpy.mapping module and this functionality is limited to within a single .mxd and with elements that already exist.
That is, I cannot add new elements to any .mxd and I cannot add cloned elements from one .mxd to another.
