Messages

1

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

« on: February 16, 2024, 06:37:44 PM »

Hi Alexey,

It worked. Thanks!
If any other geoid files to be added, maybe a path to the folder would be nice.

Export DEM with Metashape GUI works fine too, using the same compound coordinate system.

Regards

2

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?

3

General / Re: generating a multispectral orthophoto with Mavic 3 multispectral

« on: May 18, 2023, 04:52:16 PM »

This is not supported with Metashape as you are trying it, you need to build custom pipeline in front of metashape for this to work.

Hi olihar, what kind of custom pipeline? RGB Band split, co-registration with multispectral data, to be able to process all together?

My expectation is that Metashape will have a proper worflow for Mavic 3M images processing.

4

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

« on: April 13, 2023, 06:11:43 PM »

Hello Alexey,

I've missed the chunk.loadReflectancePanelCalibration() function... this solved the problem.
Meanwhile, the reflectance values shown after the chunk.locateReflectancePanels() and prior to .csv. load,  are they calculated? Shouldn't they be the same as the .csv file?

Thanks.

5

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

« on: April 13, 2023, 12:43:57 PM »

Hi Alexey,

Here they are: https://sendgb.com/phOr1Wy4ktd

I guess there might be something wrong on the reflectance calculation: the calculated values from MS does not match the ones from the .csv
Ideally, the .csv would not be necessary at all.

6

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

« on: April 11, 2023, 07:10:15 PM »

Hi, I'm reviving this topic because I've got stuck again with this issue.

Tried MS v2.0 and it still occurs: the chunk.locateReflectancePanels() won't load/search for the .csv file with the radiometric values; and worst, it loads some values that not even match with the values shown on the panel.

Any thoughts about this?
Anyone as been through this issue?

I'll appreciate your comments.

7

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

« on: August 19, 2022, 08:07:07 PM »

Would you like to share?

8

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

« on: August 19, 2022, 07:10:34 PM »

Thanks Paulo.

The value is actually the one you've mentioned, but I really need to get it via python API.

9

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.

10

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

« on: August 21, 2021, 10:48:07 AM »

Hi Alexey,

Two different panels and .csv radiometric files

https://we.tl/t-2OjeEDi8oj

11

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

« on: August 19, 2021, 06:25:15 PM »

Any news on this issue?
Have you been able to reproduce?

12

General / Re: Micasense RP06 Panel - Wrong mask detection

« on: August 19, 2021, 06:23:48 PM »

Sorry the delay, here they are.

https://we.tl/t-rMhj90udba

I'm sending you a large number of panels, while the ones on folder 05 seems to be the problematic ones.

13

General / Re: Micasense RP06 Panel - Wrong mask detection

« on: August 02, 2021, 09:15:36 PM »

Hi Alexey,

Please note that the panel detection and masking is not perfect as when we use the older RP05 or RP04 versions.
This might need a fine tune to avoid non calibration pixels to be inside the mask.

Regards.

14

General / Re: Micasense RP06 Panel - Wrong mask detection

« on: July 29, 2021, 02:34:06 PM »

RP06 panels are detected and masked correctly with this 1.7.4 version.

Nice work.

15

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.