I provided a DWG to an architect who's using (I think) C3D.?ÿ In the DWG are a bunch of POINT entities (not survey points, but simple 3D nodes).?ÿ The architect isn't able to use these to generate a surface.?ÿ I don't use C3D, so I'm at a loss for suggestions.?ÿ Any ideas?
Thanks!
Send me the DWG I'll add a surface, but what about breaklines?
If those point entities have an elevation aasociaass with them, he can add them to the surface as a block.?ÿ
Civil3D can create a surface from drawing objects.
I'm not sure if your point objects count as points (as in the dropdown).
Right-click on "Drawing Objects" in the prospector (as below) and choose "Add..."
If those point entities have an elevation aasociaass with them, he can add them to the surface as a block.?ÿ
This is most likely the correct answer, but it will be dependent on the entity type of the points you supplied as seen by the architect. The points that are referred to by Dave Karoly are regular Autocad points. The points you supplied are most likely blocks. The architect will have to list one of your points. If it is called a block, Trundle is right. If it is called a point (I've never seen a point from another software show as an Autocad point, but I can't say that it's impossible), then Mr. Karoly is correct.
An architect using C3D? I'm not sure if I'm more amused or frightened!
When sharing I export my final surface as an xml. That breaks all dependencies and just about guarantees it will come across well.
When sharing I export my final surface as an xml. That breaks all dependencies and just about guarantees it will come across well.
This was my first thought as well. If you created a surface, just share as an XML file.
When sharing I export my final surface as an xml. That breaks all dependencies and just about guarantees it will come across well.
Unless they are using Microstation...
?ÿ
?ÿ
The points that are referred to by Dave Karoly are regular Autocad points.
That's what I provided, POINT entities, not point blocks.?ÿ I'll send the architect the instructions Dave shows above.
I'll also try the XML export.?ÿ I'm assuming I can do that in TBC, but I've never done it.
When sharing I export my final surface as an XML. That breaks all dependencies and just about guarantees it will come across well.
Unless they are using Microstation...
What is that suppose to mean? BENTLEY InRoads, which runs on MicroStation can import a surface from XML.
When sharing I export my final surface as an XML. That breaks all dependencies and just about guarantees it will come across well.
Unless they are using Microstation...
What is that suppose to mean? BENTLEY InRoads, which runs on MicroStation can import a surface from XML.
Perhaps so - but Microstation itself apparently cannot. We provided a C3D XML surface to another firm using Microstation and the contours blew up completely. They spent days screwing around with it and wound up completing the job in C3D and converting it to Microstation for submittal to DOT. This was a nation firm with very experienced Microstation users.
True, but that is like saying AutoCAD can't open an XML file. Civil3d is to AutoCAD as InRoads is to Microstation. Microstation and AutoCAD are the media while Civil3d and InRoads is the design aid in which they run on top of.
?ÿ
My initial effort at exporting an XML from TBC was unsuccessful.?ÿ It looks like it's ready to export, but clicking the Export button doesn't do anything.?ÿ I have the surface selected, and the export file folder isn't write-protected, so I'm not sure what I'm doing wrong.?ÿ Can any of you TBC users shed some insight?
Thanks!
Did you hit the export button at the bottom (TBC can be a little cryptic sometimes...yes but did you hit all the buttons you are supposed to hit LOL).
Also push the ... button to be sure it is putting it in an expected location.?ÿ TBC saves the file but doesn't close the dialog which could be confusing.
It saved a LandXML for me.
True, but that is like saying AutoCAD can't open an XML file. Civil3d is to AutoCAD as InRoads is to Microstation. Microstation and AutoCAD are the media while Civil3d and InRoads is the design aid in which they run on top of.
?ÿ
I have no idea exactly what software they were using - we were on the sending end. They were supposedly "experts" who design DOT highways on a regular basis and had done this many times before. They could not import a surface?ÿ from their own AutoCAD files to Microstation. That's all I know...
Assuming that you have an edited surface - if you don't/can't use xml then 3D Faces is another good option (in a dwg or dxf) - tell the end user to select the maintain vertices option (or whatever it's called in their software) when creating the new surface - Send the border too. This will result in an exact duplicate of the surface you create.
?ÿ
?ÿ
The points that are referred to by Dave Karoly are regular Autocad points.
That's what I provided, POINT entities, not point blocks.?ÿ I'll send the architect the instructions Dave shows above.
I'll also try the XML export.?ÿ I'm assuming I can do that in TBC, but I've never done it.
I know you use Bricscad, but I'm not sure what you run on top of that. Carlson users and Land Desktop users may think they are providing point entities also, but I can tell you for a fact that these are only recognized as blocks. The main reason being that an Autocad point has no attributes, it is strictly a point. So if you have a point with a point number, description, and elevation, it's pretty safe to say that Autocad/C3D is listing it as an attributed block.
Feel free to send them Mr. Karoly's instructions. The block entities are listed right there also. I'm just 99.99% sure that they need to pick a block as the entity. I tested this in a drawing with Carlson points, and points did not work, but blocks did. They should know this already anyway.
Oh, C3D, how did we ever survey without it... (the sarcasm is thick aith this one)