DJI Terra and PVsyst

[Nikoloz]

Hello

Does anybody know how to export terran as 3d object From DJI Terra to PVsyst??  Dji terra is an app to use with dji matrice drone

[Muhammed Sarikaya]

Dear Nikoloz,

You have to find a way to extract the three coordinate points (X, Y, and Z) of your 3D object and save them as a CSV file. This way, PVsyst will accept the CSV file as topography.

Regards,

[Nikoloz]

No..... CSV file is not a solution it took an ugly terran. I have converted obj file to 3ds fil , which was 7 MB in size , imported it to 3d shading scene as a groung data but there is another big problem PVsyst is not situable to work with high quality objects (the 3d terran what PVsyst imports by default those maps are too old) and it stucked , frezzed and didnot respond.we are working with huge landskape about 1.4 square kilometers . This is a serious problem when your customers are working on big farms like 150-200 MW and if PVsyst freezes all the time

Edited Tuesday at 12:29 PM by Nikoloz

[Eric Poirrier]

Dear Nikoloz,

We recommend using a maximum of 50k polygons for the ground data. Exceeding this number will make PVsyst slower without significantly improving the accuracy of the simulation results.

The import ground as CSV provided by PVsyst has an option to simply the geometry to meet with the 50K limit, you can either use this tool or find a way to reduce the number of polygons in your 3DS file.

Regards

[MicheleANE]

10 hours ago, Eric Poirrier said:

Dear Nikoloz,

We recommend using a maximum of 50k polygons for the ground data. Exceeding this number will make PVsyst slower without significantly improving the accuracy of the simulation results.

The import ground as CSV provided by PVsyst has an option to simply the geometry to meet with the 50K limit, you can either use this tool or find a way to reduce the number of polygons in your 3DS file.

Regards

Dear Eric, 50k polygons are really too few for large power plants on complex terrain. 

We also often work on 100MW+ projects and it would be a life-saver if the terrain polygon number would not influence the speed of the software as a whole. 

Is there really nothing that can be done for this? We have software that can do real-time rendering of millions of polygons...

Please consider this, best regards