Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I sure agree with this request. Importing LAS directly into IW sure would shrink workflow steps a bit, we will look into getting that done as soom as possible. It is already in our development list and here are few reasons it didnt make it to top of priority yet:
1. There is a work around using ReCap. Most users happen to open the files in ReCap anyways to visualize them and hence having RCS is not a big deal.
2. Autodesk products use RCS as optimized indexed file format. Hence if user imports las directly, we will convert them to RCS internally which might take some time to convert (depending upon file size and number of files). This conversion wait might cause some inconvenience to users while they can import them by batch using ReCap and bring it in IW.
2a. If IW generates RCS internally, then user have to do this steps multiple times if they want to import the same file in Civil3D or somewhere else. But if they have RCS from Recap already, its one time conversion and hence easy for users who use multiple products for point clouds.
3. Recap offers some additional tools like clipping, cropping, registration, coordinate system conversion, etc which users use to fine tune their AOI before coming in to IW, that optimizes the workflow.
Let me know your thoughts and I will log them in for planning perspective. As always please let me know your feedback especially about point cloud processing as we strive to make that workflow as streamlined as possible.
Yes, we definitely need automatic coordinate conversion and elevation conversion from metric to imperial. We typically we get the data in UTM Metric and need to go to State Plane imperial.
We need a LAS connection routine whose primary focus and programming optimization would be for handling the LAS ground points... to efficiently and quickly create ground surfaces for engineering design and drainage analysis purposes.
We need to be able to select a rectangular boundary window so the routine will only process data inside of that user defined window boundary.
It's also taking way too long of processing time to create a TIN surface in Civil 3D using the Recap point cloud... Even when using classification filtering for ground points only to be used.
Thanks Fred for the information on las tools usage. It helps.
I do agree for large number of points C3D takes long time to process. The workflow of using key ground points from IW along with extracted breaklines (IW offers line extraction capability) help generating good terrain in faster time. But I understand this is little bit application specific.
@fcernst Thanks for the idea. With InfraWorks 2021.1, users can import LAS files directly into Infraworks and use those imported files to generate terrain, features, etc.
