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.
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.
BricsCAD v21 Pro version includes a growing list of Civil components in it’s foundation. MapWorks builds for previous versions of BricsCAD only used it’s CAD engine and worked with our own Civil functionality. However, beginning with this release (MapWorks 9.0 on v21 Pro Windows or higher) it will begin creating the underlying BricsCAD Civil objects (such as TinSurfaces) whenever possible and reading from them as well (when applicable). This makes MapWorks one of the first (if not the first) civil survey add-on to fully utilize the BricsCAD Civil API.
You may receive an ESRI Shapefile collection from a GIS user for a data source in generating a surface. This is typically a ShapeFile Type 1 (Point) or Type 2 (Polyline) which contains the XY values in the .SHP file, along with the elevations in a field of the associated .DBF file.
You may have noticed that when you try to copy named objects in Civil3D (or use the same name) that it will append a (1) to the name. What you might not have noticed is that if the string case of the named object varies, Civil3D will let you create what we consider to be a duplicated name !
We sure that by now everyone has heard about the deadly Corona virus. One natural response is “how close is it to me”. As it turns out, Johns Hopkins University has utilized (as of February 11, 2020) ArcGIS to produce a nearly real time map.
There are times within every project where something (or many things) can gum up the works and slow your group’s productivity. The question is how prepared you are tor them in advance and how you react when they do happen. When you hit a snag and one or more team members end up spending hours doing repetitive tasks, do you dare bill for all that time?
When gravity and moisture begins to work on steep slopes (disturbed or natural) the results are often less than optimal and slides occur. This can present the need to install anchor bolts and plates going from the loose surface to a more stable rock strata underneath. Boreholes can help determine the location of the stable strata, but from the surface it’s not readily apparent how far (on a given slope) you will need to drill to reach the stable member. Read More →
When Autodesk first introduced the Set Location tool (on the Insert tab) in 2016 we briefly experimented with it, thought it to be confusing at best and ignored it. It was a couple years later when someone sent us a drawing started this way that we determined it to be dangerous at the least.
November 4th, 2016 was a day to remember, as Autodesk had just released a 16.2 revision to Civil3D that provided what initially appeared to be some useful improvements to the Civil3D API (Application Programming Interface). A couple years before (11-29-2014) we had requested several improvements to the API to allow the creation and editing of FeatureLines on a level similar to polylines.