Topics

1

Python and Java API / Feature request - return data for publishData

« on: July 06, 2023, 01:12:17 PM »

The current publishData class in python does not return any information or data, neither does it alert users to exceptions/errors that occur during uploading.
At the very least, it would be great if the class could return the request information, so that users do not have to query e.g. Sketchfab externally for the UID of the uploaded models.
Or have I simply overlooked this feature?

2

Python and Java API / How to? Access object file size

« on: July 06, 2023, 01:10:09 PM »

Hi,

What is the easiest way of accessing file size information through the Python API? I have tried accessing the file size for a mesh+textures, but do not seem to be able to find this information in the objects "meta" properties. This would be great information to have for certain processes (e.g., to decide whether or not to decimate models).

If not currently possible, it would make for a straightforward addition to the API, seeing as the information is already present in the information panel itself besides Creation Date and Software version; which do both show up in the "meta" property.

3

Feature Requests / Generate footprint/outline of point cloud/mesh/DEM/orthomosaic

« on: March 22, 2023, 01:41:00 PM »

Hi,

I originally raised this as a comment in the Agisoft Metashape-script github repo to an existing issue (https://github.com/agisoft-llc/metashape-scripts/issues/48).
Me, the OP and others would all be keen to have a function that calculates the footprint/outline of point cloud/mesh/DEM/orthomosaic from within Agisoft Metashape.
In that, we mean a polygon that follows the shape, like so:


Internally, Agisoft Metashape is able to calculate the footprint/area outline of mesh and DEM.
This is e.g. evidenced by the "Coverage" area parameter in the processing report and is used internally by the Area() commands.
It would be great if there were a way to access this process directly, and export it to a shape from within the GUI and through the Java/Python APIs.
Based on the github issue, more users would benefit from a feature like this.

4

General / Export shapes with same coordinate system as custom-view orthomosaic

« on: February 15, 2022, 12:55:43 AM »

Hi!

I have been struggling with an otherwise very simple task: exporting annotations and shapes in the same coordinate system as used for the orthomosaic.
The export works as expected when the orthomosaic is top-view and has a "normal" crs. However, I have not been able to export "projected" shapes from a custom-view or side-view orthomosaic.

In this case, my custom-view orthomosaic uses epsg:4978, but with negative X and huge Y coordinates, e.g.:
WGS 84 (EPSG::4978) -1931.398 X 6357705.971 Y

Obviously, there is a working transform - as the shapes are successfully printed on this side-view. Would anyone be able to help me out and point me to the obvious; any idea on how to access this transform and use it for the export of the shapes in the same coordinate system as the orthomosaic?

Any help is greatly appreciated!

5

Python and Java API / Get shape/marker coordinates in current-view orthomosaic reference frame

« on: December 17, 2021, 07:30:21 PM »

Hi,

Is there anyone who has succeeded in accessing/exporting shape coordinates within the coordinate system used by a non-crs (i.e., "current view") orthomosaic? Thus-far all created polygons drawn on the orthomosaic come out with completely different coordinates... Would be great to not only be able to export the shapes with model references, but also for them to go with the orthomosaic (from different view points).

Description of problem:
1. create "view-point" orthomosaic
2. draw a shape on the "view-point" orthomosaic
3. export shape (need to select a CRS) and orthomosaic (unable to select a CRS/undefined)
4. plot in e.g. Arcgis - shape and orthomosaic will be far apart. <- Help needed

Cheers!

6

Python and Java API / select&remove through gradual selection of connected components / resolution Q

« on: September 13, 2020, 05:40:35 PM »

Hi,

Just wondering whether the current Python API support the selection and removal of connected component sizes based on their relative size. Alternative, I am aware there is a function for removing connected mesh components based on an absolute value - anyone has any idea on how to get mesh sizes for individual components within the models so that I can use the former to get the desired results?

Secondly, which functions are used to generate metadata listed on the second page of the processing report? I.e., Flying altitude, ground resolution, coverage area, etc? Would be amazing if these could be accessed through the Python API.

Cheers