@CodeDing wrote:
This will probably not be your final solution, but it is a start.
- find lowest elevation of lines (to use as base elevation)
I think its a great start! Wonderful job. And I so love the lisp working itself through the objects 🙂
Is it possible to find the heighest elevation of lines?
@CodeDing wrote:- explode entity into regions
- explode regions into lines
1) When I exploded the polyline, I noticed that there were two lines where I thought there should be one. Why is that?
2) I will use this tool in Civil3D to explort SHP files. I just checked and the MAPEXPORT tool supports Polygon which appears to be the same thing as regions. What alteration do we need to do have it stop at regions, ie not doing the whole polyline conversion?
@CodeDing wrote:- create polyline (I can't figure the best way to close the polyline, it works though)
- (optional) bring back 3DSOLID entity
PLEASE NOTE:
- This ASSUMES there are NO other Lines and NO other Regions in your model space
1) thanks for informing about non-closed polylines. I will select them all and close them that way. If anyone who reads this has a solution, please share your knowledge to the community. 🙂
2) I am curious, how could it bring back the 3D Solids? Wheren't they deleted the first place?
3) Just for the record. Out of curiosity, I tested with lines in the model space. Works without any problems with lines, ie, nothing halts or crashes.
Last but not least. I noticed a strange behaviour. Initially, I wanted to stress-test the script to see if it would mess things up if two volumes share the same edge/border.
To do so, I created two boxes and placed them next to each other. In other words, they were made in AutoCAD and not like the other volumes in the sample file. The box are also 3D Solids, but had their handles left.
So what happened was that the face/footprint was triangulated. Why did this happen?