Dear Experts,
I have experience importing LIDAR into my Civil3D (v2020) workspace, to create surfaces. Is there any benefit of using ArcGIS Pro (via the Connector) to import my LIDAR, instead? Does it handle better than ReCap? Which method do you recommend, as the best practice?
What would be the benefit of gathering GIS into ArcGIS Pro first and then using Connector to access it?
Is it better to import the data directly through ReCap?
I have done a little bit of research, trying to find out the benefits of using ArcGIS Pro, and trying to determine whether we need to keep and maintain subscription to ArcGIS every year. The main (and currently) only reason I see as a benefit of owning ArcGIS Pro, is that I would have the ability to publish maps, so that someone else is able to view the map in 'Realtime', but is that the only reason?
But, is that the only reason? Is it also better to download LIDAR into ArcGIS first, and then import the data into Civil3D, or is that a "pointless" - pun intended 😉 - step that needs not be taken? Lol
Also, does it help with data size, in anyway? Does it help Civil3D keep the file size smaller? I have had trouble with file sizes getting too big, so if it helps make the file size smaller, then I suppose it is worth the extra step...
Just mulling over some workflow issues, and trying to determine how to smooth things out...
Thanks for reading my post, and as always, I appreciate any comments and suggestions!
Linette
DotSoft Software has LAS Tools. This will allow you to connect and use (quickly) large .las, .laz, etc. @TerryDotson is a regular contributor here.
So, just to inquire, while I have you on the line. What then, are the benefits of having an ArcGIS Pro account/subscription, if you already own Civil 3D? Just trying to gather "points" to support the cause... oh too many puns, lol.
So you are using LiDAR to create a surface and that's good because LiDAR can capture the detail that other surface 'definitions' can't. As you already know, other types of surface definitions don't take as long as LiDAR to build a surface so there's an apprent trade-off between a detailed surface and the speed at which that surface is created.
I find the most benefit derived from LiDAR is having it 'trimmed down' to only the area of interest. Bringing in 7 square miles of LiDAR data is unnecessary when you only need 1 acre, or less. This is especially true when you're receiving data, e.g. surveyed field data or drone capture, and not downloading the point cloud from open source--you can request the sender to trim down or thin out the point cloud on his end. This way you don't have to wrestle with the periphery points you'll never use or decrease the ultra high density which slows you down.
Chicagolooper
@ChicagoLooper @Anonymous
Couldn't agree more.
If it's still being a pain, then take the trimmed and stripped LIDAR and thin it some, then triangulate to surface.
I also like to render a nice set of high res DEM tiles.
Data optimization ahead of hitting your software package incredibly underrated, and overlooked.
I find Autodesk's Software generally does a great job once the data is well optimized.
As mentioned above LASTools has a stack of utilities for doing some of these things, and is **** fast, multicore optimized.
Honorary mentions to QGIS, ESRI Suite, and if you really need a sledgehammer - Safe's FME.
While searching came across this, which I think might be of some help: Process LiDAR
Unfortunately all Civil 3D third party apps have trouble creating/handling large Raster datasets that we need to deal with on a daily basis now.. only due to the limitations of the Civil 3D API.. no fault of their own..
This will remain the case until Civil 3D project managers get up to date on the industry trend.. and adapt…
Can't find what you're looking for? Ask the community or share your knowledge.