Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Damian

Pages: [1] 2 3
Bug Reports / Missing 3d lines on Cameras
« on: January 12, 2022, 06:47:42 PM »

I have a project where I created DEM. I added 3d lines describing borders of parcels (plot). The point is to update the altitudes and to show borders on pitched cameras, taken along the building site.

However, for no reason some of the lines disappear and appear on neighbouring cameras. First I though, that it was due to "hiding under dem", but as I can see it is not a rule.

How to cope with it so that all the lines appear on cameras? What is the reason for them to disappear?

Looking forward to getting any clue :)

Bug Reports / Re: Invalid shape - polygonal
« on: March 04, 2021, 11:52:35 AM »

They might have different structure, but the point is that in 1.6 Metashape I am able to set them as boundary, while in 1.7 Metashape this option is greyed out. What is more I cannot calculate the area which makes me think that they are being imported as polyline, not polygon.

I use them to export ortho and dem in parts, but now I cannot do it. KMLs are prepared and exported from QGIS.

What version of Metashape do you use? I downgraded to 1.6.6. and the problem dissapeared.  However, that is not the solution I expected to work out.

Bug Reports / Invalid shape - polygonal
« on: February 25, 2021, 10:58:13 AM »

For every project I create a kml with several polygonal shapes. Each shape has a description - map section's number. With Metashape 1.6. it was not a problem to import it and use for exporting shapes with proper file name. Now with 1.7. when I import a kml (which by the way in QGIS is imported as polygon), I cannot use it for export - just as if it was a poyline, not polygon. I cannot use it as boundary or measure the area.

In attachement two examples of KML.

I do not want to downgrade to 1.6. Is there any way you could make it work?

Best wishes

General / Markers eroors before and after selection
« on: May 28, 2020, 10:40:15 AM »
The question is about the error [m] value of markers. We have three situations:
1. All markers are selected and the cameras are optimized on them - error on control points is 0,0014 m. (1st attachement - selected_optimized)
2. I unselect all markers - the error on check points raises to 0,0037 mdespite the fact, that i have not optimised the cameras yet. (2nd attachement - unselected_before_optimization)
3. I optimize the camaeras and the error on check points is 0,187 m. (3rd attachement - unselected_optimized)

I understand the change of value between optimisation on selected and deselected markers. I don't understand why there is a value change after deselection and before the optimisation.

Loking forward to reading some explanation.

Usually it works so when orthomosaic or dem selected. Perhaps you set different coordinate systems for each chunk?

Feature Requests / Re: Orthomosaic/DEM export with watermark
« on: April 30, 2020, 11:01:06 AM »
I was wondering if request is still considered or it was fully abandoned. Any news?

Feature Requests / Re: Hierachical chunk groups
« on: April 30, 2020, 10:57:05 AM »
It has also one more advantage. We have several projects in which every month we generate trueorthomosaic, digital terrain model and differential models from same construction site. So far I group chunks by date e.g:


It would be much easier just to see it that way:

I realize that I can store several dems in one chunk, but it does not satisfy me.  @Alexey, do you plan to intoduce it to us with upcoming upgrade ;) ?

General / Mouse navigation Agisoft 1.6.2
« on: April 02, 2020, 03:56:21 PM »
I might have a silly question. I updated my Metahspae to 1.6.2. In previous version I cloud move the view by using mouse wheel/right click (with active slection). Now I notced, that both mouse wheel and right click rotate the view. If I want to move the view I need either change to "navigation" or doule-left click to center the view. 
How can I change it back to have a possibilty to move with active selection?

Bug Reports / Height difference when raster transformation
« on: October 07, 2019, 03:45:48 PM »
I have a project prepared in modern Polish Coordinate System (EPSG 2176), height Kronstad. I would like to export DEM to an old coordinate system (ESPG 2174) with the same height system. Unfortunately the height difference between rasters is around 40m.

In attachements two dems form the same project.
What could be the cause and how can I work it out?

Bug Reports / Re: Classify ground points lasts very long
« on: July 24, 2019, 02:31:32 PM »
Could I get some help with this issue? I am working with another project: Dense cloud 3 400 000 000 points, 7 500 000 tie points, dense cloud clasification after 7 hours 11%, 1 day 18 hours left.

Bug Reports / Re: Classify ground points lasts very long
« on: July 12, 2019, 01:27:15 PM »
Sorry for mistake, you are right: dense cloud has 3 200 000 000 points, tie points - 3 900 000

Parameters: 10 deg, max distance 0.3m, cell size 30m. Dense cloud points are located in the area of ~20km2. It is a road that is 35 km long and the buffer is 550 m width.

Update: it took 30 hours to perform a classification in a project with dense cloud 1 300 000 000 points, 10km2, parameters as above.

Bug Reports / Classify ground points lasts very long
« on: July 12, 2019, 08:52:54 AM »

I noticed, that ground point classification is taking now much more time than it used to. About 6 months ago classification was less time consuming than dense cloud generation. Later I noticed that both consume the same amount of time.

Now I have a project with dense cloud that contains about 3 900 000 colorized points, 8800 cameras  (42 MPix). It took 8h to generate depth maps and another 11 hours for dense cloud generation. Unfortunately, after the upgrade to version 1.5.3. the ground point classification after 10 hours shows me, that it needs 2 days 13 hours more to complete the task. I split the project into smaller parts (ca. 1 500 000 points), but there is no difference in time estimation.  Earlier it was not a problem to work with so big projects.

What could cause such situation? Before I upgraded to 1.5.3. I was not able to generate dense cloud (what has never happened before) due to "Image size mismatch error."

Looking forward to hearing from you.

General / Estimating Camera locations never ends
« on: May 24, 2019, 02:21:27 PM »

I am aligning 4000 cameras in one chunk and an issue happens: everytime when the alignment reaches "Estimating Camera locations" the process bar stops at some stage, the "time left" slowly goes down to 0 and then dissaperas. After that nothing happens [printscreen in attachement].  When I clikc "pause" or "cancel" buttons grey out and stay like that for ever.
Before that, I aligned 4500 cameras in same project in another chunk with no problem.

Alignment options are 40 000/ 4 000, earlier I tried with 30 000/3 000 - same result.

I attach a log
Thank you for quick answer.

Feature Requests / Re: Export multiple Ortho/DEM sections
« on: March 14, 2019, 12:14:20 PM »
Hello Alexey

Maybe I misunderstand what an attribute is. I checked in QGIS - the attribute is called "Name". There is also a label visible in Agisoft. I attach three pics.
No matter if I change in script "NAME" to "Name", it still exports ortho and dem as "Unknown". Does it work on your PC with provided data?

DEM is exported as RGB and tfw file appeard - thanks!

Feature Requests / Re: Export multiple Ortho/DEM sections
« on: February 25, 2019, 03:17:52 PM »
I have just cheked the script. Here what I noticed:
1. Despite the label marked as "Name" attribute, the name of the created file is still "unknown".
2. When choosing DEM as RGB export the script does not work.
3. Could you add a .tfw file creation when orthophoto export?
In the link I am to send you in a private message You can find the project I test the script on.

Looking forward to getting an answer ;)

Pages: [1] 2 3