Topics

1

Python and Java API / Export DEM using chunk.exportRaster(): Vertical Datum mising

« on: February 16, 2024, 02:48:47 PM »

Hi all,

I'm trying to export a DEM using chunk.exportRaster(), using python module.

Code: [Select]

                # Set projections
                set_projection = Metashape.OrthoProjection()
                set_projection.crs = Metashape.CoordinateSystem("EPSG::"+str(epsg))

                # Set image compression
                set_img_compression = Metashape.ImageCompression()
                set_img_compression.tiff_compression = Metashape.ImageCompression.TiffCompressionLZW

                # DEM export settings
                output_path = outputs_folder + os.path.basename(os.path.splitext(project_path)[0] + '-DSM-'+str(res_cm)+'cm-epsg'+str(epsg)+'.tif')
                print(output_path)
                chunk.exportRaster(
                    output_path,
                    image_format=Metashape.ImageFormatTIFF,
                    source_data=Metashape.ElevationData,
                    image_compression=set_img_compression,
                    projection = set_projection,             
                    resolution_x = res_cm/100, resolution_y = res_cm/100     
                    )
                   
                print(f"DSM exported from {project_path} to {output_path}")

If DEM was build using WGS84 (EPSG::4326), the export runs ok.
The problem occurs with DEM's build using WGS84 + EGM96 height (EPSG::9707): RuntimeError: Vertical datum missing: WGS 84 (EPSG::4326) to EGM96 height (EPSG::5773)

Any ideia to solve this issue?

2

General / Get orthomosaic estimated resolution previous to build - via Python

« on: August 19, 2022, 02:18:45 PM »

Hi,

How/when does Metashape estimates the best orthomosaic resolution (shown on "Build Orthomosaic" window)?
How to get this value via python?

I'll need to know this value previously the orthomosaic build, so I can choose the right resolution for a specific project.
The idea is to accelerate the processing and save disc space (building orthomosaics with worst resolutions).

Thanks.

3

General / Micasense Reflectance Panels - Calibration via python misses .CSV file

« on: July 29, 2021, 02:17:18 PM »

Hi,

I'm calibrating Micasense Rededge-MX imagery using panels, via python:

Code: [Select]

chunk.locateReflectancePanels()
print("»» Panels located.")
print("»» Calibrating reflectance, using panels and sun sensor...")
chunk.calibrateReflectance(use_reflectance_panels=True, use_sun_sensor=True)
print("»» Reflectance calibrated.")

With the .csv file (reflectance values) already loaded, this python code won't consider the .csv file values. Please see images attached.
On other hand, doing the procedure via GUI, after "locate panels", the .csv file values are automatically filled.
In this situation - and if the .csv file exists - I guess it would be better if the .csv file is loaded via python. Or maybe adding an additional flag to do that.

And another thing: the values detected from the QRCode are not the same as written on the panel. I've tried this on different panels, with the same mismatching results.
If no .csv loaded, do we need to input the panel values manually or that is expected to be done on QRCode reading? Since values mismatch, I'm confused.

Panel original images 5 bands: https://we.tl/t-fUtd5vYhFX

Any help?
Thanks.

4

General / Micasense RP06 Panel - Wrong mask detection

« on: July 22, 2021, 03:27:49 PM »

Hi,

I'm using a Micasense calibration panel - version RP06 - but Metashape can't detect it correctly.
I need to mask the calibration area manually for every band.

Anyone with this kind of problem?
Metashape update is needed or I'm missing something?

Thanks.

5

General / FLIR Duo R - Thermal - Processing as a Rigid Camera Rig - Multi-Camera System

« on: February 03, 2021, 07:15:06 PM »

Hello Metashape Fellows,

I'm bringing again to the discussion the processing of images captured with the FLIR Duo R.
There have been a number of reports from other users who were able to obtain thermal orthomosaics, and from others who were not so lucky. However, as far as I know, there is no generalized procedure for doing this.
Presently is possible to obtain a separate RGB and Thermal ortomosaics. The main problem is to get both co-registered.

** Some time ago I've shared here a procedure where RGB images (cut to size 1440x1080) were processed first, and then replaced in the project with the thermal images (resized to 1440x1080). It was not perfect, it had clear misalignments, but it already gave an idea of ​​the thermal panorama of the covered area. Presently I don't recommend this option..

** A more consistent procedure is to merge the RGB images with the thermal images (both 1440x1080), creating a single multi-spectral RGBT image. This article explains and demonstrates this procedure: https://www.mdpi.com/2072-4292/11/11/1365.
I made several attempts in this way, the procedure surely becomes more seamless but still misses co-registration between bands. The RGB orthomosaic appears correctly but the Thermal shows evident stretching misalignments. So, improvements must be done.

** Currently, as I've mentioned, processing only thermal images produces good results. This is already a big step forward.

** Lately, using the multi-camera system processing approach, my expectation would be that this process could work with the FLIR Duo R. Unfortunately, the results are still not satisfactory: the thermal orthomosaic always presents stretching misalignments.
In comparison, I did several processing with sample images captured with Micasense Altum (https://micasense.com/sample-data-altum) - 5 bands + Thermal - always with good results. To try to match the processing conditions to the FLIR Duo R, I removed all the orientation information and characteristics of the sensors that are registered in the EXIF ​​of the Altum images. Even so, the results were good. The thermal orthomosaic stitching is good and and the co-registration between the multi-spectral bands and the thermal band (orthomosaics) loses very little quality.

I'm attaching some results from my processing with the FLIR Duo R and I'm providing the image dataset in use, asking for collaboration of the interested users and Metashape moderators, for a proper solution.

Image dataset RGB + Thermal: https://meocloud.pt/link/453b2b19-5475-443f-9106-96745c93b105/FLIR-Duo-R/

6

General / Remove null instances

« on: August 20, 2020, 10:48:04 AM »

I'm trying to remove an orthomosaic that is not appearing on the chunk items but no luck so far (it was wrongly created after cancelling a duplication of an orthomosaic).
I'm using v1.6.3

Code: [Select]

chunk.orthomosaics
2020-08-20 08:39:26 [<Orthomosaic 'Orthomosaic: Mosaic Blending, 17915x13107'>, <Orthomosaic 'Copy of Orthomosaic: Mosaic Blending, '>, <Orthomosaic 'Orthomosaic: Average Blending, 17915x13107'>]

chunk.orthomosaics[1]
2020-08-20 08:42:37 <Orthomosaic 'Copy of Orthomosaic: Mosaic Blending, '>

chunk.orthomosaics[0].clear()
# <Orthomosaic 'Orthomosaic: Mosaic Blending, 17915x13107'> is deleted from chunk items, but stills in chunk.orthomosaics

chunk.orthomosaics
2020-08-20 08:45:53 [<Orthomosaic 'Orthomosaic: Mosaic Blending, '>, <Orthomosaic 'Copy of Orthomosaic: Mosaic Blending, '>, <Orthomosaic 'Orthomosaic: Average Blending, 17915x13107'>]

chunk.orthomosaics[1].clear()
Stills in chunk.orthomosaics

Any ideias?

7

General / Enable/Set as Default Orthomosaics - Python API

« on: March 24, 2020, 05:35:55 PM »

Hi,

I have two orthomosaics in my project/chunk, and I have to enable/disable (Set as Default) them separately inside a script.
I need to activate 'ortho 1' to use with chunk.exportRaster(condition_1), and 'ortho 2' to use with chunk.exportRaster(condition_2).
I can retrieve the orthomosaics available using chunk.orthomosaic, but can't activate the one I need.
Also trying to use chunk.orthomosaic.key but I'm not getting there.

Any suggestions?

8

General / Export Tiled Model - Cesium

« on: February 26, 2020, 07:58:29 PM »

When exporting a tiled model to Cesium 3D Tile format, the options from the export window appears greyed out.
I'm unable to change the reference system.
Is this standard - and if it is, why? Or I'm missing something?

9

General / Decoding for RAW/.CR2 images

« on: January 31, 2020, 12:35:06 PM »

When opening a set of photos in RAW format (Canon file type .CR2) using Photoscan 1.2.6, the color decoding is quite good and if the photo was taken with the right settings and in good light conditions there's no need to tune anything before start to process.

With Metashape 1.5 - using the same photos - they are overexposed and I can't find a way to tune them right inside Metashape. Convert them using another software will make the workflow longer.

Anyone with the same problem? Suggested solutions?

Agisoft, can the RAW decoding be reverted to the previous condition? Certainly more people are dealing with the same issue.

10

General / MicaSense RedEdge-MX - Calibration Panels

« on: July 30, 2019, 01:52:49 PM »

Hi,

About the Micasense Rededge-MX workflow, I'm trying to understand how Metashape handles multiple calibration panels/multiple flights in the same chunk.

Considering this topic from Micasense:
https://support.micasense.com/hc/en-us/articles/115000765514-Use-of-Calibrated-Reflectance-Panels-For-RedEdge-Data ;

does Metashape consider the time stamp of the cameras to interpolate the calibration effect?

11

General / DEM generation takes too long (build dem)

« on: January 29, 2019, 12:53:40 PM »

Hi PS folks,

In the last month I've been processing some corridor mapping projects and the DEM generation is very time consuming and takes to long to conclude.
Let's say 1000 photos might take 20-25h to generate the DEM. Sometimes more.
This is very unpractical if some minor adjusts are needed until the final product, I believe there's something wrong on my approach.
Comparatively,  a 1000 photos project  covering a squared area takes only 25min to produce the DEM.
In either cases I'm using reference data to all the photos.

After reaching 45% of the DEM generation process, it becomes very slow and the computer is working very far from full processing capacity.
The project covers a corridor extension of about 30km.

I've attached some info about the project.

Found this thread but not sure about the relation between both situations: https://www.agisoft.com/forum/index.php?topic=9071.0

Any suggestion why this might be happening?

UPDATES:
1. Followed the suggestion on the thread above (resetting transformation and using local coordinates) and the result is the same: it is stuck at 45%, and rising very slowly.
2. Reducing the region to 1/5 of the original size, the process is much faster as expected, but at 45% turns to become unpredictable slower.

12

General / RasterTransform RasterTransform.palette RasterTransform.range

« on: March 08, 2018, 03:29:28 PM »

Hi,

I've been trying to use the class RasterTransform but I'm struggling to understand the RasterTransform.palette and RasterTransform.range objects.
These are not documented anywhere (as far as I can tell). Could you please provide an example of using this RasterTransform on exporting an Orthomosaic with PhotoScan.RasterTransformType.RasterTransformPalette ?

How should I build my RasterTransform.palette and RasterTransform.range objects? What information should they contain?

13

General / FLIR DUO R - Thermal orthomoscaic

« on: November 28, 2017, 07:42:44 PM »

Hi All,

Anyone one with experience with FLIR DUO R?
Just bought one and I'm getting involved with the file formats and processing workflows.
My objective is to process thermal images with Photoscan, to output thermal orthomosaics.
This camera can capture radiometric JPG images (RGB+Thermal), or an RGB JPG + TIFF Thermal.
I guess Photoscan can't handle radiometric JPG's, if anyone have any experience  I would appreciate some advise.

Any suggestions?

14

General / PRJ - unsupported datum transformation

« on: November 07, 2017, 05:30:09 PM »

Hi all,

I'm trying to combine a reference system with a vertical datum into a PRJ file.
Already have a working PRJ with both reference and vertical datum (kindly sent from Agisoft).
I've tried to do the same, but using a different reference system, the PRJ was accepted by photoscan, but when I'm exporting the DSM, I get the unsupported datum transformation.

I'm sending the working PRJ and the reference system + geoid which I would like to combine. Geoid file from the Agisoft database.
Anyone can give me a hand?
Thanks.

15

General / Export markers - ticked coordinates

« on: February 15, 2016, 08:43:04 PM »

Hi All,

Does anyone know a way to export the marker coordinates (projected! not over the photos)?
I need the coordinates of the ticked point over the dense cloud or the orthophoto. (LLA or XYZ, in the same reference system as the model).

Is it possible?