Messages

16

General / Quick_Layout.py

« on: March 08, 2022, 11:14:35 PM »

I have used the quick_layout python script for aligning water and forest areas where auto align doesn’t work, usually prior to building the DEM and ortho. Is it ok to use it with not aligned RTK cameras prior to building the dense cloud? Working on a large project with some forestry and would like the images included in the dense cloud.

17

General / Re: 100m Geoid Error - OSGB36 + ODN Height (EPSG::7405)

« on: March 07, 2022, 09:08:33 PM »

Perfect, thank you

18

General / Re: 100m Geoid Error - OSGB36 + ODN Height (EPSG::7405)

« on: March 01, 2022, 12:57:53 PM »

Hi Alexey,

Can you confirm that the mainstream 1.8.1 release has the offset issue fixed? I'm still on 1.7.6 but would like to upgrade due to additional features.

Thanks,

Rory

19

General / Error Opening Project - Information

« on: January 23, 2022, 02:13:27 PM »

We are currently processing a 37km corridor working in 4.5km blocks and merging the chunks for three flight segments at a time. The images are from a Zenmuse P1 at 1.1cm/px so very high resolution.

When opening one of the projects this morning I received an error about a corrupt zip archive and the project wouldn't open. The merged chunks are huge, however I opened the project yesterday without issue so not sure how it got corrupted. I tried opening the <path-to-project>\02 Segments 4-6 Files\project.zip\6\0\point_cloud\\point_cloud.zip using Windows archive utility but the file was corrupt. Not wanting to have to generate the whole project again I manually removed the merged chunk: I opened doc.xml from the project.zip folder and removed the merged chunk (6 in this case) and renumbered the active and next chunk in the header.

The project opened fine and I merged the chunks again, hopefully without corruption!

20

General / Re: 100m Geoid Error - OSGB36 + ODN Height (EPSG::7405)

« on: January 23, 2022, 01:50:56 PM »

Hello Rory,

The fix will be implemented in the next 1.8.1 update, as soon as pre-release is updated, I will let you know.

Thanks Alexey, good to know. 1.7.6 has been working fine for this project.

21

General / Re: 100m Geoid Error - OSGB36 + ODN Height (EPSG::7405)

« on: January 19, 2022, 12:43:44 PM »

Hi Alexey, I can confirm my projects are opening fine in 1.7.6 and no longer have the geoid / conversion issue.

22

General / Re: 100m Geoid Error - OSGB36 + ODN Height (EPSG::7405)

« on: January 19, 2022, 12:54:12 AM »

Hi Alexey,

Unfortunately not, the problem still exists. Will the 1.8 projects open in 1.7.6? If this can't be sorted by the time I need to export the outputs I will need to use the older version where the problem didn't exist.

Thanks,

Rory

23

General / 100m Geoid Error - OSGB36 + ODN Height (EPSG::7405)

« on: January 18, 2022, 02:27:23 PM »

Hi, since updating to Metashape 1.8 when I convert from WGS84 to OSGB36 + ODN Height using the installed OSGM15 tif geoid the heights are all exactly 100m too high. When I convert the camera positions in Metashape I get (using one image as an example):

WGS84: 57.67697 -2.735643 179.192; OSGB36: E 356224.48 N 865474.163 H: 228.992

Transforming using the OS Coordinate Converter I get:

WGS84: 57.67697 -2.735643 179.192; OSGB36: E 356224.48 N 865474.163 H: 128.991

Somehow 100m is getting added to the height. I have used the Metashape conversion without issue until I upgraded to 1.8, is this a known issue or bug?

Thanks,

Rory

24

General / Re: Filling In Sea Area

« on: May 02, 2021, 01:26:55 PM »

Hello RoryG,

If you have images taken over the water bodies and related exterior orientation information (coordinates of the camera locations with camera orientation angles), you can use the following script to apply that EO information to not aligned cameras:
https://github.com/agisoft-llc/metashape-scripts/blob/master/src/quick_layout.py

Then you should generate the DEM with extrapolated option selected and run build orthomosaic operation.

Hi Alexey,

Should I import all the images at the start, or just add in the sea images before building the DEM?

25

General / Re: Filling In Sea Area

« on: April 25, 2021, 05:02:50 PM »

Thank you Alexey, that's exactly what I was after. We're doing the surveys this week so I'll let you know how I get on.

26

General / Filling In Sea Area

« on: April 25, 2021, 01:49:08 PM »

Hi, we are surveying several coastal sites at low tide for our client, and they have requested that we "fill in" the sea in the orthos. Obviously we won't be able to process the sea areas with Metashape, however is there any way of manually positioning photos of the sea into the ortho inside Metashape, or will this need to be done in an image editor then create a world file? I've attached an image to show what's required.

27

General / Re: Defects in Dense Cloud / DSM

« on: July 17, 2020, 01:25:26 PM »

I've reprocessed the project with some GCPs grabbed from identifiable ground features and used less aggressive gradual selection and the output is now perfect. I suspect I may have removed too many points and there were areas without enough data to generate the dense cloud.

28

General / Defects in Dense Cloud / DSM

« on: July 16, 2020, 02:55:12 PM »

Hi,

I'm processing a P4RTK mission made up of four flights, PPK processed in RedToolbox. Due to the remote location of the site and difficulty to access on foot there are no checkpoints / GCPs in the project. The client requested 50cm XYZ accuracy, and according to Metashape (latest version just installed) the XY accuracy is 22cm and Y 30cm. I followed my normal workflow which has up to now worked perfectly, however in this instance I'm getting lines and trenches in the dense cloud / DSM that don't exist on the terrain. Any idea what could be causing this? Camera overlap is 75/75 and flying height of 90m (terrain following). I've attached a couple of images from QGIS, one showing the orthomosaic and the other the orthomosaic overlaid with hillshade extracted from the all classes DSM.

29

General / Re: Your opinion on USGS Agisoft Processing Workflow

« on: March 25, 2020, 12:35:21 PM »

Our workflow pretty much follows the USGS processing workflow, however we do try and not remove over 50% of the sparse cloud points. We always aim to achieve a reprojection error under 0.3px which gives us very accurate outputs - a recent test project we achieved 1.4cm RMSE XYZ on our surveyed checkpoints. You can read the article here: https://www.linkedin.com/pulse/post-processed-kinematic-gnss-mapping-rory-gillies/

Here's a couple of screen grabs from the report:

30

General / Moonlight for Nvidia Users

« on: March 24, 2020, 04:04:30 PM »

I've been having some issues with TeamViewer and was researching other solution to work on my photogrammetry PC remotely. It's connected to a monitor, however it's located away from my main office area so I access it remotely from my MacBook Pro. Microsoft RDC is no use as it doesn't leverage the GPUs, and TeamViewer is very expensive to license and get rid of the nags.

I came across Moonlight - https://moonlight-stream.org a multi-platform Nvidia Shield client. It only works if you have Nvidia GPUs, and you must have the Nvidia GeForce Experience installed, but the performance is stunning, way ahead of TeamViewer. It's designed for streaming games with full acceleration, but it can stream individual apps or the entire desktop. Setup guide can be found here: https://github.com/moonlight-stream/moonlight-docs/wiki/Setup-Guide

Well worth a look if you're looking for a remote access solution.