Messages

1

Bug Reports / Re: Metashape EPSG:3857 not recognized by gdal2tiles

« on: February 18, 2022, 11:17:21 AM »

Dear Alexey,

I noticed the issue when exporting from a script, but I also tried it through the GUI and it gives the same problem.
I also tried adding the EPSG:3857 WKT as prj file and adding it to Metashape, same result.

Thank you for your answer

Evert

2

Bug Reports / Metashape EPSG:3857 not recognized by gdal2tiles

« on: February 17, 2022, 04:01:19 PM »

Dear,

When trying to tile a raster exported by Metashape in EPSG::3857 (WGS 84 / Pseudo-Mercator), gdal2tiles (https://gdal.org/programs/gdal2tiles.html) errors because of the included CRS information is unexpected.

ERROR 6: Cannot find coordinate operations from `ENGCRS["WGS 84 / Pseudo-Mercator",EDATUM[""],CS[Cartesian,2],AXIS["easting",east,ORDER[1],LENGTHUNIT["metre",1]],AXIS["northing",north,ORDER[2],LENGTHUNIT["metre",1]],ID["EPSG",3857]]' to `EPSG:3857'

Do you have any idea why the CRS info in the metashape tif is not read as EPSG:3857 (https://epsg.io/3857) but as a ENGCRS which seems weird?

Thank you in advance
Feel free to let me know if this is a gdal issue

3

General / Re: How to turn on all gpus?

« on: January 18, 2022, 10:20:47 PM »

I am indeed building a script for headless Python scripts execution so I was wondering if anything special needed to be set up.

4

General / Re: How to turn on all gpus?

« on: January 18, 2022, 10:09:28 PM »

Thank you for your quick response. If I were to not use this code snippet, all GPUs would still be used as gpu_mask is the max value, correct?

So then this code would only be needed when we need to disable a specific GPU like you said for the special cases.

5

General / Re: How to turn on all gpus?

« on: January 18, 2022, 09:54:33 PM »

Is this snippet still relevant or are the defaults for both gou_mask and cpu_enable good by themselves for the most efficient setup?

6

Bug Reports / Re: Regression in Pointcloud 3DTiles tileset data

« on: October 11, 2021, 08:23:46 PM »

That does indeed seem to change the behaviour.
The values look similar (not exactly, few meters shift)

Code: [Select]

{'Height': {'maximum': 588.2065221817237, 'minimum': 411.24811327206055},
 'Latitude': {'maximum': 0.7694814403213569, 'minimum': 0.769259291829557},
 'Longitude': {'maximum': -2.08724332318532, 'minimum': -2.087468395182987}}

I thought Cesium was in ECEF and not 4326?

7

Bug Reports / Re: ExportRaster wkt is different to the projection CRS

« on: October 11, 2021, 05:52:32 PM »

Sorry for the bump, I was wondering if this behaviour has changed in recent versions or if it is still the same?
Thank you!

8

Bug Reports / Re: Regression in Pointcloud 3DTiles tileset data

« on: October 11, 2021, 05:44:04 PM »

Using the Python API, this is the code we use:

Code: [Select]

            doc = Metashape.Document()
    doc.addChunk()
    doc.chunk.crs = Metashape.CoordinateSystem("EPSG::3857")
    doc.save("PSP.psx")
    doc.chunk.importPoints(
            projected_file,
            crs=Metashape.CoordinateSystem("EPSG::3857"),
        )
        doc.chunk.exportPoints(
            os.path.abspath(output_path),
            format=Metashape.PointsFormat.PointsFormatCesium,
        )

Is there anything that should be changed between 1.6 and 1.7?

I am not sure how to check the boundary shapes

9

Bug Reports / Re: RuntimeError: Can't decompress depth

« on: October 11, 2021, 05:42:16 PM »

Yes both start a project from scratch.

10

Bug Reports / Re: RuntimeError: Can't decompress depth

« on: October 11, 2021, 04:28:56 PM »

Hey Alexey,

We observe the same failure on 2 different laptops so the chance it's related to RAM is quite low.
Not overclocked btw.

Greetings

Evert

11

Bug Reports / Regression in Pointcloud 3DTiles tileset data

« on: October 11, 2021, 03:39:01 PM »

When updating from 1.6.3 to 1.7.5 we noticed the following regression, especially the height is weird.
Expected

Code: [Select]

{'Height': {'maximum': 586.442 ± 5.9e-04, 'minimum': 406.613 ± 4.1e-04},
 'Latitude': {'maximum': 0.7694819644872486 ± 7.7e-07,
              'minimum': 0.7692585288653095 ± 7.7e-07},
 'Longitude': {'maximum': -2.0872437834475623 ± 2.1e-06,
               'minimum': -2.0874694308012236 ± 2.1e-06}}
Actualy

Code: [Select]

{'Height': {'maximum': -6356138.153753753, 'minimum': -6356339.057442965},
 'Latitude': {'maximum': 1.5611652318912046, 'minimum': 1.5359569979858492},
 'Longitude': {'maximum': 1.8649031691950797, 'minimum': -3.046626475879601}}

Our flow is: importPoints, exportPoints(PointsFormatCesium)

Is there a relevant changelog available for what could affect this?

12

Bug Reports / RuntimeError: Can't decompress depth

« on: October 08, 2021, 04:30:48 PM »

We're processing 2 completely different projects using the python API. In 1.6.3 this worked, but in 1.7.4 and 1.7.5 these seem to fail with the following code and logs:

Code: [Select]

openexr error: Error reading pixel data from image file "openexr". Unexpected tile x coordinate.
openexr error: Error reading pixel data from image file "openexr". Unexpected tile x coordinate.
openexr error: Error reading pixel data from image file "openexr". Unexpected tile x coordinate.
openexr error: Error reading pixel data from image file "openexr". Unexpected tile x coordinate.
Traceback (most recent call last):
chunk.buildDenseCloud(point_colors=True,progress=XXX)
RuntimeError: Can't decompress depth


13

Bug Reports / exportPoints crashing with local path

« on: October 08, 2021, 02:14:26 PM »

The following code snippet displays the error which seems to be a regression somewhere between 1.6.3 and 1.7.4.

Code: [Select]

    doc = Metashape.Document()
    doc.addChunk()
    doc.chunk.crs = Metashape.CoordinateSystem("EPSG::3857")
    doc.save("PSP.psx")

    doc.chunk.importPoints(las_path, crs=Metashape.CoordinateSystem("EPSG::3857"))

    doc.chunk.exportPoints(os.path.abspath("test1.zip"), format=Metashape.PointsFormat.PointsFormatCesium)
    print('ok1')
    doc.chunk.exportPoints("test2.zip", format=Metashape.PointsFormat.PointsFormatCesium)
    print('ok2')

Which errors with the following logs

Code: [Select]

ExportPoints: path = /ABS/test1.zip, format = PointsFormatCesium
point cloud size: 1065 points
ok1
ExportPoints: path = test2.zip, format = PointsFormatCesium
Traceback (most recent call last):
  File "XXX.py", line 19, in <module>
    doc.chunk.exportPoints("test2.zip", format=Metashape.PointsFormat.PointsFormatCesium)
OSError: Can't create directory: No such file or directory (2):

Thanks for any support

14

Bug Reports / Re: Standalone version needs libGL.so

« on: January 25, 2021, 02:45:47 PM »

The environment is `Linux d24600ff409b 4.19.121-linuxkit #1 SMP Tue Dec 1 17:50:32 UTC 2020 x86_64 GNU/Linux`

That does indeed solve it. Is this requirement specified somewhere?

Is `libglu1` also fine? What is the difference with `libgl1`?

15

Bug Reports / Standalone version needs libGL.so

« on: January 04, 2021, 03:06:26 PM »

Code: [Select]

FROM python:3

RUN wget https://s3-eu-west-1.amazonaws.com/download.agisoft.com/Metashape-1.7.0-cp35.cp36.cp37.cp38-abi3-linux_x86_64.whl

RUN python3 -m pip install Metashape-1.7.0-cp35.cp36.cp37.cp38-abi3-linux_x86_64.whl

SHELL ["/bin/bash", "-c"]

CMD 'python3'

Running `import Metashape` in the previously specified docker container results in

Code: [Select]

>>> import Metashape
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.9/site-packages/Metashape/__init__.py", line 3, in <module>
    from .Metashape import *
ImportError: libGL.so.1: cannot open shared object file: No such file or directory