Forum

Recent Posts

Pages: [1] 2 3 ... 10
1
Python and Java API / Compute Total Marker Error in m
« Last post by mschul on Today at 03:02:44 PM »
Dear community,

I am trying to write a script to calculate the total projection error of the markers in m.

I found the following example that computes the individual marker errors in pix: https://www.agisoft.com/forum/index.php?topic=14595.0


However, the conversion from pix to m is not clear to me.  I would be very happy if someone can help me. I am using Metashape 2.0.0.

Thanks in advance !
2
Bug Reports / Re: Details view sort by column
« Last post by James on Today at 11:40:40 AM »
Sorry, I should have been a bit more rigorous before reporting it as a bug.

Hopefully I'll soon get a chance to pin it down, and try to reproduce it on a smaller project that I can share.
3
General / Re: HELP! suddenly camera errors, has something changed in settings?
« Last post by Mr.Vain on March 29, 2023, 08:18:10 PM »
Hi Mr. Vain,

what is strange on your bad project is that camera accuracy is all set to default which is 10m. If the data was correctly RTK corrected then accuracy should be at cm level and this accuracy should be read from XMP meta `data (as long as you have set this option in preferences > Advanced tab). By having such loose accuracy, your camera positions are not so constrained and the 1 m error shows some inconsistency between camera positions and GCPs.... Maybe you can show the reference errorrs window (View errors button) to see how this error is distributed between X,Y and Z ....

For your good project what was the final f adjusted value (from camear calibrarion window)? and what was the f adjusted value for bad project?

Thank you so much!!!!! I replaced the computer 1.5 months ago and reinstalled metashape and after that i have not made that setting. I have totally missed that one, dont ask me how.....I checked other project computed with the same settings and they are ok but not perfect. As long as i have used GCP:s around the area of intrerest the result have been ok there but with the project now i was looking a bit from the gcp.s and the result was no good at all wich the usually are. Again, thank you so much :).
4
General / Re: HELP! suddenly camera errors, has something changed in settings?
« Last post by Paulo on March 29, 2023, 07:24:41 PM »
Hi Mr. Vain,

what is strange on your bad project is that camera accuracy is all set to default which is 10m. If the data was correctly RTK corrected then accuracy should be at cm level and this accuracy should be read from XMP meta `data (as long as you have set this option in preferences > Advanced tab). By having such loose accuracy, your camera positions are not so constrained and the 1 m error shows some inconsistency between camera positions and GCPs.... Maybe you can show the reference errorrs window (View errors button) to see how this error is distributed between X,Y and Z ....

For your good project what was the final f adjusted value (from camear calibrarion window)? and what was the f adjusted value for bad project?
5
Helo photo,

it should work in Ascii where each record is in the form of lat,long,Geoid height or long,lat,geoid height.... Also Trimble ggf format file....

If your geoid is the BKG Quasigeoid of the Federal Republic of Germany GCG2016. Then you can use ascii format as:
Code: [Select]
5.1 ASCII format
The ASCII file contains one dataset per raster point consisting of the point position coordinates (in degrees) and the pertaining quasigeoid height (in m). The columns are separated by a blank space. As file extension “.txt“ is used.
As pseudovalue outside the territory of the FRG for the quasigeoid height the value “999999.“ has been entered.
Example:
53.64583333 13.86875 36.4582
53.64583333 13.88125 36.4363
...
Then use Table lat/lon/alt (*.txt) when adding your geoid file as in following screen shot...
6
General / HELP! suddenly camera errors, has something changed in settings?
« Last post by Mr.Vain on March 29, 2023, 07:06:44 PM »
Hi forum!

This is really strange, i seem to have a big issue with camera errors. I dont really know what all numbers means but if i compare them to earlier projects from late 2022 its a big difference. Today i saw that i had quit big differences in height when comparing to earlier flights, 25cm as the biggest. I am using a DJI Matrice 300RTK with a P1 camera so i get really good pictures and the gcp:s are measured with trimble R12i gps with really good accuracy and still i get a really poor result. When looking at older flights with the same drone i have perfect result and the estimated error in the reference cameras is as highest 10cm for only 1 pic and then its from 3cm down to millimeters for the rest. Looking at my latest flights its now from 2m error for the worst pics and 70cm for the best! After the alignment of the pictures i import the GCP:s and the are not spot on my ground markings, the are 5-10cm of and they used to be spot in since the RTK on the drone always is good. What am i missing here? I really hope someone can help med because this is a BIG problem for me right now. I will attach 2 screendumps also, one with a project wich is good from december 2022 and one from a flight a couple of days ago so you can see the difference.

Have a good day! :)
7
Hello Paulo,

I just received the data, but unfortunately, it's available in the following formats:
ASCII, binary, Javad, for Leica, Survey, Topcon, and Trimble.

I've tried multiple times to import it as shown here: https://agisoft.freshdesk.com/support/solutions/articles/31000148332-how-to-use-height-above-geoid-for-the-coordinate-system
However, it doesn't work or sometimes displays an "out of range" error. I've tried numerous times, but with no success.

Is there any way to convert these formats? Or do I absolutely require the geoid in TIF format? I greatly appreciate your support.

Best regards
Photo
8
Bug Reports / Re: Shortcut key to next image zoom off
« Last post by Alexey Pasumansky on March 29, 2023, 06:23:05 PM »
Hello Joel,

Is it correct, that the problematic behavior can be only reproduced, if custom key is assigned to Next/Previous Photo command, whereas default PgUp/PgDn shortcuts work as expected?

9
photo,

great to hear! Now if your ordered geoid is referenced to ETRS89 datum (i.e. geoid height refers to geocentric ETRS89 datum) and want to use a geoid file referenced to non-geocentric DBREF datum, you must follow following to create relevant geoid for DBREF.....https://agisoft.freshdesk.com/support/solutions/articles/31000161533-what-to-do-if-you-need-to-use-an-existing-geoid-on-another-datum
10
Hello Alexey,

unfortunately we need more like 100-300 images. It would be helpful to have a pyhton function for rotating the object at axis XYZ for a certain degree like 5° or 10°.

So in final you could rotate the object and save the view automatically in a loop.

Pages: [1] 2 3 ... 10