Like a lot of things in Civil3D, it is possible but not easy to do. This post is an attempt to provide a step-by-step procedure on how to add additional properties to AeccCogoPoints.
Because of the way IntelliCAD creates a copy of a partial menus content and resource DLL (the icons), then locks that DLL at the operating system level, users of our add-ons that change have to do a special procedure in order to see the new menu items and icons. For example our MapWorks product receives additions on pretty much a weekly basis and while we can update the files in our install folder, that’s not enough as it is on other platforms. Follow this procedure to see the new menu items and icons.
The process of importing contours from shapefiles is actually a two step process, since the results from Autodesk’s MAPIMPORT command does not elevate the resulting polylines. This is a step-by-step procedure on how to take a shapefile of contours to elevated polylines in AutoCAD (Map/Civil3D).
We’ve often said “we don’t mind hard work, it’s unnecessary work that bothers us“. Such is the case in obtaining lidar data for surface generation. From our previous experience the process involved:
- Use a browser to go to a certain government website.
- Zoom and pan around till we found the area of interest.
- Click to select our area and place our order.
- Wait for an email to arrive telling us our data is ready.
- Download to find it’s a massive file.
Most users won’t hit this limit and shouldn’t worry about it until they do. However a handful of our users processing extremely massive surfaces have reported an error message like “System.OutOfMemoryException” and/or “Array dimensions exceeded supported range”.
AutoCAD has a long history, and we go back all the way. Our primary developer started using AutoCAD with version 1.0 on the original IBM PC with a 10mb hard drive and CGA graphics (now we have mp3 files larger than that). Here is a detailed history, including corresponding drawing versions, .NET framework used, etc.
In the early days of AutoCAD, users could safely use a NODe osnap to snap to a point block while zoomed out because they knew it would only return the actual intended point of the insert. Then along came an
improvement that had AutoCAD return the insertion point of the attributes. With that improvement meant you had constantly zoom in to make sure you were getting the right point.
For those that aren’t aware, the OSNAPNODELEGACY set to 1 causes the CAD engine restore the logical NODe osnap of the point object only. Now in the highly unlikely case you want to snap to attributes, you can use the INSert osnap.
Deleting parcels (by name) in Civil3D can sometimes be difficult. Right clicking the parcel name doesn’t work, erase on the parcel label does nothing. Here is a step-by-step procedure to quickly delete multiple parcels by name, without picking a single segment.
Read More →
When we worked up our procedure for importing Lidar into Civil3D a couple months ago, we realized there were way too many steps and way too many hoops to jump through. Hoops preparing the data, through Recap to prepare a RCP/RCS, through Civil3D creating a point cloud, and finally creating the surface. Highly trained professionals have more important things to do with their time than spend it like a well trained circus animal jumping through hoops, so we did something about it.