Upsampling mesh...?

haven't tested it on point cloud directly, but there is an option to create mesh from points - available in both CE and SS4

as for your second question, there is a tool to decimate mesh (reduce number of vertices / edges) and another one to subdivide it (add additional vertices/edges to smooth it) - available in MS CE

Hi Peter, 

Managed to get the mesh from the cloud, also function to decimate works fine.. but can't find anything.. to add more :/ Any Tips would be meeega welcomed. 

Thank you

J

Hi Peter, and everyone

I must say, this forum, u guys are very few ppl who did not bombarded me with questions why would I like this to be done etc etc, makes no sense etc etc, without giving any advice.

Thanks to your hints I have managed to do what according to many other forums wasn't possible and had NO sense... but it did had a sense to me simply because I am working on some sort of cloud modeling, can't give away to many details, but all I wanted to check is that my results are NOT similar or same as subdividing a mesh in a regular way like the one below, but in order to check it I first had to see how it would look like..

This is a very heavy task and my computer was only able to do small areas, but enough for my RD. So once again thanks everyone.

P.S Out of the curiosity? Is there a size limit for DGN? 

hi Julian, in V8 DGN there is no limit of filesize, resp. the only limit is your OS filesystem. more about limits and capabilities of V8 DGN here - http://www.mdlapps.com/microstation/ustnhelp47.html

yes, I thought about similar purpose. btw, when it comes to meshes, have you tied the Meshlab? free app with lots of tools dedicated to Mesh manipulation

Peter Tegza said:

have you tied the Meshlab?

Can one exchange data between Meshlab and MicroStation?

yep, STL and OBJ file formats are available, but I haven't tested it in MS yet

Hi Julian,

Julian Olszewski said:

who did not bombarded me with questions why would I like this to be done etc etc,

Well, but sometimes such information (what is behind a question) can be crucial. In last 20 years I remember plenty of discussions when somebody wanted to know how to do something technically without providing any context. And after long time spent it was found out that the whole discussion was useless because there was e.g. better way or wrong tool was discussed ;-)

Julian Olszewski said:

Out of the curiosity? Is there a size limit for DGN? 

Peter's answer is "nearly right", so I'd like to provide more details: Usually the definition is that DGN V8 maximum size are 4 GBs. It's based on fact that DGN V8 format is implemented as Microsoft Compound File. Whereas this format is very flexible, nothing in IT is "unlimited", but limits are very high in this case. On the other hand the format is tight closely to underlying OS and file system. In time when V8 was release 32bit OS and FAT file system were used and these facts defined possible address space inside the file as well as its maximum size.

To ensure created DGN will be readable on any PC and any V8 version, to think about 4 GB as about max size makes sense (despite of it probably can be larger on modern 64bit OS and new generations of NTFS).

But it mostly technical theory, because even much smaller file contains so many elements, that it will become slow and unusable. And it's even more complicated, because it's not about the amount of data only, but about type of elements: e.g. when you will create DTM from let's say 1 million of points and will store the terrain as triangles, it will probably kill MicroStation efficiently. On the other, when you will store the same data as Terrain element (cannot be created by MicroStation, but can be imported using LandXML), MicroStation will have not any problem with it.

Regards,

  Jan

Hi Julian,

Julian Olszewski said:

who did not bombarded me with questions why would I like this to be done etc etc,

Well, but sometimes such information (what is behind a question) can be crucial. In last 20 years I remember plenty of discussions when somebody wanted to know how to do something technically without providing any context. And after long time spent it was found out that the whole discussion was useless because there was e.g. better way or wrong tool was discussed ;-)

Julian Olszewski said:

Out of the curiosity? Is there a size limit for DGN? 

Peter's answer is "nearly right", so I'd like to provide more details: Usually the definition is that DGN V8 maximum size are 4 GBs. It's based on fact that DGN V8 format is implemented as Microsoft Compound File. Whereas this format is very flexible, nothing in IT is "unlimited", but limits are very high in this case. On the other hand the format is tight closely to underlying OS and file system. In time when V8 was release 32bit OS and FAT file system were used and these facts defined possible address space inside the file as well as its maximum size.

To ensure created DGN will be readable on any PC and any V8 version, to think about 4 GB as about max size makes sense (despite of it probably can be larger on modern 64bit OS and new generations of NTFS).

But it mostly technical theory, because even much smaller file contains so many elements, that it will become slow and unusable. And it's even more complicated, because it's not about the amount of data only, but about type of elements: e.g. when you will create DTM from let's say 1 million of points and will store the terrain as triangles, it will probably kill MicroStation efficiently. On the other, when you will store the same data as Terrain element (cannot be created by MicroStation, but can be imported using LandXML), MicroStation will have not any problem with it.

Regards,

  Jan