Export a "report" of the Civil 3D Toolspace contents

[Wish List System]

Summary: For project documentation purposes, would like to be able to export the contents of the Toolspace to a file (XML)

Description: Documenting a Civil 3D project would be much easier if we could dump the contents of the Tool space to a file (XML preferred) to document "everything Civil 3D" about that project. This way we could develop our own style sheet to make comprehensive "pretty" reports.

Currently, someone who inherits a Civil 3D project must take a long time to get familiar with the contents of the data model. Being able to document the project would allow better standards checking , re-familiarization with the project if time has elapsed, or communicating the project to another user, and so on.

Product and Feature: AutoCAD Civil 3D - Import/Export

Submitted By: Bruce Dana on 08/07/2014

[BlackBox]

Summary: For project documentation purposes, would like to be able to export the contents of the Toolspace to a file (XML)

Description: Documenting a Civil 3D project would be much easier if we could dump the contents of the Tool space to a file (XML preferred) to document "everything Civil 3D" about that project. This way we could develop our own style sheet to make comprehensive "pretty" reports.

Currently, someone who inherits a Civil 3D project must take a long time to get familiar with the contents of the data model. Being able to document the project would allow better standards checking , re-familiarization with the project if time has elapsed, or communicating the project to another user, and so on.

Product and Feature: AutoCAD Civil 3D - Import/Export

Submitted By: Bruce Dana on 08/07/2014

Call it what you like, the resultant code-behind the procedure will iterate the Database, and not the Toolspace tree directly, IMO.

That said, you can do this now, with only Visual LISP honestly, and even in batch process if you like... For example, consider this old post, which implements BatchFindSurface Command. As you might infer, it prompts user to select a directory, then iterates each drawing via ObjectDBX, subsequently iterating the DBX Document's database in order to determine if any Civil 3D Surfaces exist, writes found output to a temporary .CSV file, finally openning said .CSV file in user's native application for that file type.

The only real difference is that this is not built into the native context menu when you right click an element of the Toolspace.

Cheers