Messages

1

Python and Java API / Re: Defining vertical datum when exporting point clouds

« on: September 06, 2022, 11:53:44 AM »

Hi Paulo,

Thank you for your reply. I will try once with geoid file but I'm afraid it won't be good approach for me on the long run as I was hoping for rather generic approach where I could just define EPSG code and that it's then written to the header of the LAZ file. The reason behind is that I need to have LAZ file with this vertical datum info when I pass it over to Cesium ION for tiling because otherwise Cesium assume that heights are relative to ellipsoid height and it's not fitting the globe.

I see PDAL can help with setting correctly vertical datum info but I was hoping I could do that directly in Agisoft to avoid additional steps.

Anyway, I'll look more in details there, thanks again for your answer.


Best regards,
Ivan

2

Python and Java API / Defining vertical datum when exporting point clouds

« on: September 05, 2022, 05:24:16 PM »

Hi,

When exporting the point cloud using exportPoints() function I can define only the output CRS but not the vertical datum as well. Is there any possibility to define the vertical datum (using EPSG ideally) so that it's also written to the header of the LAS/LAZ file?

3

Python and Java API / Re: Exported point clouds have coordinates moved closed to zero

« on: October 28, 2021, 10:48:04 AM »

Hi Alexey,

Yes it works when explicitly setting crs argument, I'm not sure how i missed that option before. Anyway, it's good now, thanks.

Best regards,
Ivan

4

Python and Java API / Exported point clouds have coordinates moved closed to zero

« on: October 19, 2021, 05:05:19 PM »

Hi,

I'm using Metashape Python API (v1.6) and I noticed that when exporting point clouds as LAZ the output file has coordinates in local coordinate system instead of the one defined for the chunk. Isn't it that by default, if crs is not explicitly defined it should export the points to chunk's crs?
For the other exports (DEM, Orthophoto, etc) all works fine.

I do the point cloud export like below

Code: [Select]

chunk.exportPoints(output_fpath, format=PointsFormatLAZ)


Thanks in advance.

5

Python and Java API / Re: Exported PDF report has black squares instead of text

« on: February 07, 2020, 12:01:35 PM »

Ah now it suddenly worked out fine, it might be I just had to restart my machine after updating environment variables, it probably was because of fontdir paths as you first said.
I believe it should be ok from now on, thanks a lot for help!

6

Python and Java API / Re: Exported PDF report has black squares instead of text

« on: February 07, 2020, 11:43:24 AM »

Hi Alexey,

Yes, I'm using -r key to start the python script and I'm passing also -platform offscreen as additional parameter.

7

Python and Java API / Re: Exported PDF report has black squares instead of text

« on: February 04, 2020, 11:53:39 AM »

Hi Alexey,

I've set value for QT_QPA_FONTDIR to the path you defined (it's actually same as on my machine) but it's still the same problem.
Is there any log file where I could maybe check for some warnings etc? I believe there is some missing dependency but not sure where could I look for it.

Maybe somebody else experienced problem like this?

By the way, same thing happens on another machine where we run the script (it's also running with Ubuntu 18.04).

8

Python and Java API / Exported PDF report has black squares instead of text

« on: February 03, 2020, 03:23:05 PM »

When using using Metashape Pyhon API (v 1.6) for PDF report export I get PDF where there are black squares instead of text (titles, ...). Can't figure out why is that happening. I'm running the code on Ubuntu 18.04.

Screenshot is in attachment.

9

General / Re: Agisoft PhotoScan 1.4.0 pre-release

« on: October 23, 2017, 08:48:48 AM »

Hi Agisoft team, the new features look quite interesting and useful, can you please tell me some approximate date when we can expect stable version of this release for download? Maybe you already wrote somewhere but I couldn't find.
Thanks