Acute3D sample data?

You can also locate the example Acute3D data file from the Welcome to MicroStation page. If you click on this it will allow you to open and view this example file.

Hi Andrew and Keith,

thanks for your answers. They solves my question by 50%, because the data are not in original 3mx format, but imported into dgn (so I missed them when I searched for *.3mx). From data / users perspective they look like any other data created in MicroStation. But the true is the examples are great! :-)

Regards,

Jan

Unknown said:

The Acute3D data is extremely large ...

Larger than a point cloud?

Its a hard comparison to make. The Plant example is 136 MB. And that is a small one. Keep in mind the format is multi-resolution and includes imagery.

The Acute3D data is not really imported into the design -- it is attached to the design (similar to a point cloud or raster reference). The examples use attachments to URLs that simply host .3mx scene and associated data files. You can "Drop" the Acute3D data to obtain standard mesh elements with textures -- but that will be at a fixed resolution.

As Keith points out, it is a difficult to compare to point clouds directly --- But the Acute3D data at the same resolution as a point cloud will be larger -- because it contains all of the imagery (textures) as well as the mesh data which includes not just points but topology as well. Of course the Acute3D data is much more visually rich than point clouds...

Hi Jon,

I think the size is really depending upon the capture technology. If your point cloud is captured using multiple terrestrial LIDAR with sub-centimeter precision the point cloud can be very dense. A point cloud of the same scene captured using pictures and Acute3D could very likely be smaller given that :

- The mesh model could be simplified without losing too much precision (e.g. : removing triangles representing the same surface). With point cloud this is difficult to do because if you remove points even on a flat surface you will lose opacity.
- The pixel size are not sub-centimeter (which is usually the case).
- The textures are encoded with lossy compression (like JPEG, which is also usually the case).

The downside is creating a textured mesh require much more processing than just handling a bunch of points!

One thing for sure is that a scene detailed at high accuracy using point cloud or textured mesh would likely be very big.

HTH,

Mathieu

Hi Jon,

I think the size is really depending upon the capture technology. If your point cloud is captured using multiple terrestrial LIDAR with sub-centimeter precision the point cloud can be very dense. A point cloud of the same scene captured using pictures and Acute3D could very likely be smaller given that :

- The mesh model could be simplified without losing too much precision (e.g. : removing triangles representing the same surface). With point cloud this is difficult to do because if you remove points even on a flat surface you will lose opacity.
- The pixel size are not sub-centimeter (which is usually the case).
- The textures are encoded with lossy compression (like JPEG, which is also usually the case).

The downside is creating a textured mesh require much more processing than just handling a bunch of points!

One thing for sure is that a scene detailed at high accuracy using point cloud or textured mesh would likely be very big.

HTH,

Mathieu

Hi Jan,
Would be pleased to share some 3MX data and see some workflow on Microstation.
Let me know,

Yves

Hi Yves,

Unknown said:

Would be pleased to share some 3MX data

Thanks a lot, I really appreciate your offer. I did not find your contact, would you be so kind and send me an e-mail to jan.slegr@labtech.cz?

With regards,

  Jan

Yves,

If you don't mind I would also like to see more 3mx samples. Would you mind email to me: josebbpinho@gmail.com?

Thanks & regards