Multiple complex surface hide boundary doesn't work

[wang890]

so we have this lidar which some buildings elevations are included and when built contours will go through buildings. I tried to clean up all the building footprint lines generated from this lidar and made sure they are all closed. tried 3d and 2d poly and when the polyline gets a bit complex. (no overlap of course). and civil 3d will fail to use it as hide boundary. I was originally hoping I can just select hundreds of buildings and then it hides all the triangulations under it.

later I converted them to wipeout, downloaded a lisp to convert multiple polyline to wipeout. works great but later realized when reference ortho in and it also gets wiped out. because it has to be under the contour, mask on top of contour and ortho on top of mask. they are contradictory to each other.

so the only way is to use hide boundary. or of course manually delete triangles which will take forever.

see screenshots. maybe someone have some recommendations.

[Mike.M.Carlson]

Hi-

is it possible to upload your surface dwg and the building boundaries?  I have an idea, but want to try before sharing idea.

thanks!

[wang890]

here is the file

[wang890]

pretty cool I can attach 12mb file.

so take the v-site-bldg. layer which is the boundaries I want to use to hide the surface.

Thank you let me know what you can find.

I even tried to create another surface with these boundaries and then delete triangles outside of them and use hide boundary and pick surface and that didn't work either. I think the only way is manually delete triangles on the inside of each building. that is a lot of work lol.

[Mike.M.Carlson]

Thanks!  sorry can you also upload the source lidar point file?

Mike

[wang890]

Yeah my bad. should have this or else surface maybe set to rebuild auto so will be empty.

I renamed it a bit just in case and rename back to .xyz

[Mike.M.Carlson]

Hey there-

Well I was able to verify the issues you were having on your end.  I suspected initially that it was the overall size of your TIN and/or the fact that the surface was built from a very large number of points via the .xyz file.  Therefore, I tried to use the Create Cropped Surface command to break the overall surface into more manageable pieces, while maintaining a dynamic link to the overall surface file.

I was able to get the command to work to create 6 separate cropped surfaces in a 2nd dwg file.  I tried to add multiple hide boundaries for the building footprints to no avail. 

However, I was able to extract TIN lines from each of the cropped surfaces and subsequently built 6 new surfaces from these extracted 3D faces.  I added the applicable building outlines to these segregated surfaces as non-destructive breaklines after I added the Drawing Objects (3D faces) to the Surface Definition.  Then I actually was able to add multiple hide boundaries (40 at a time) to these surfaces built from the 3D faces.  I'm not sure why adding multiple hide boundaries worked in this case, but I have a theory that it is related to having simpler/smaller surface with no link to the .xyz file.

I concede that this last approach defeats the purpose of what you were after though.  I recommend figuring out a way to break up the .xyz file into smaller pieces and build 6-8 smaller surfaces...then add your hide boundaries.  Then you can try to paste all of these into an overall surface or keep them separate, as I assume your formal production drawings will have scales that will require more zoomed-in perspectives anyway. 

Anyway, I've given it all I can tonight.  I hope it helps / good luck!

Mike

[wang890]

Hi Mike

thank you so much for your help

that is very creative what you came up with. it's perfectly fine for my purpose. we need to make some drawings showing contours of this lidar and just don't want contours to go through buildings.

so you are saying once you crop the surfaces to 6 roughly equal pieces and add multiple building boundary as hide works. oh and you had to rebuild surface from tin. I will try rebuild all from tin or even xml first see if that works. I think you are right maybe it's the xyz type of definition causing problems.

the building envelops are not really that complicated and I know back then I make holes in surface from another surface boundary and that works fine.