If you love the out of the box reporting capabilities of Civil 3D you can stop reading this post and move on to the next one (may I suggest Brian Hailey’s recent post?), if not then read on.
If you find that you are exporting information from Civil 3D to Excel or Word and then modifying the look of the reports, then you probably should look into report customization. If you used a competing product that had a certain look to them and it isn’t available in Civil 3D and you want the same look, then you may want to create a custom report to produce the same look as the previous software package. If you want to extract information (maybe calculating the number of rings required for all of the manholes in a sewer network) from the Civil 3D model and present it in a specific format you may want to look into report customization.
Autodesk has been nice enough to provide the source code for the report so you (or someone for you) can create new reports.
To modify the XML reports you can edit the various xsl and xml files located in this folder:
You can edit the files using Notepad or a one of the xsl editor programs that are available. At this point I’ve only used Notepad so I can’t recommend an xsl editor (although I do know the full version of Microsoft Visual Studio doesn’t let you work with them).
Once you understand the structure and how the files are linked together it isn’t that hard to modify them. But unless I’m doing something quick and easy I’ll create the report using .NET.
Autodesk has also provided all of the source code for the .NET reports. They are located in this folder:
To modify the .NET reports you can use the Microsoft Visual Studio (or another IDE program). The structure of the reports is pretty straight forward and provide a good foundation for creating your own reports.
The other alternative is to have someone else do the customization for you, someone like me. If you are interested you can email me to find out more information.