Hi,
Hatch area property is not visible in Civil 3D 2024 Geometry properties. Only after manual edit of boundary vertex for example. I used Hath.ByGeometry node from Civil3DToolkit.
Do you have any experience with this or any trick or tip how to solve this to solve the visibility of area after creation of hatch?
Try forcing a document refresh.
Thank you @jacob.small. I tried this without expected result:
Might be that the transaction has to complete first… I think you’ll need to move into some custom code to force this to happen, as Civil 3D toolkit isn’t maintained anymore. Is there a different node in new builds which you can use as a basis for an alternative?
Our customer is looking for solution in Civil 3D 2024 at this moment.
Yeah - but if we know a solution in 2025 or 2026 it can help narrow in on a work-around in 2024. Rather than inventing the wheel from scratch, look at how other wheels work and do that. 
1 Like
This is an issue with AutoCAD that I’ve seen for many releases.
Sometimes the area just isn’t available for a hatch object, and I’ve had to generate new boundaries to calculate them in the past (it’s the main reason I teach my users to keep a closed polyline for all hatches).
While true that AutoCAD has a problem with intersecting boundaries and hatches. This isn’t the issue here.
Even the simplest hatches will fail to give an area when Dynamo creates them.
Here’s an example in Civil 3D 2026. I think @zachri.jensen was made aware of this in another thread as well. Otherwise, here’s a bug! 
The node to create a Hatch in The Civil Nodes also creates a Hatch without the area property to be accessed. If I find some time, I will examine this and see if there is a solution.
1 Like