21
« on: December 28, 2012, 08:56:55 PM »
Hello George
Sorry for replying so late, yes I get results in the order of xy= 1 * GSD & z = 2 * GSD
In the example attached the area was flown at 2.5cm GSD and the results are shown.
Points were tested with conventional survey and heights where within 40mm.
Regarding smooth vs sharp , I think is has got to do with what algorithms are use in
the processing , sharp being more suited to to built up areas.
Hello Piste
In Photoscan I obtain a total error of 0.014 m and 0.284 pixels using 14 GCP with known coordinates...
very good I say...(pixel size was of about 3cm)
When I have compared the point cloud exported with that one obtained in the same area
with a terrestrial laserscanner I have found an error in height till 50 cm...
Why this?
Can be you be assured that both surveys are based on the same height control?
I have done a 1000ha survey and the previous baseline survey was done by lidar,
Comparable results where good , I can forward some images, they are to large to attach,
if you are interested email me at - herman@sasurv.com
Hello Santiago
The report said my error was 0.497 pix and my ground resolution was 0.077 m/pix. I asked the support team to explain the results to me but their explanation didn't clarify my doubts. They told me an error <0.5 was considered to be good, but I want to know what's the error in meters for my project. Or compared to a total station or a RTK GNSS how did I do. Do you know based on what do they say <0.5 is good.
The 0.497 pix basically indicate that in generating the point cloud and in aligning the photographs
image to image the GCP marked in photo 1 agrees to photo 2 at an average of 1/2 a pixel.
The 0.077m is the average combined xyz error , this can be split in the actual x,y & z error per
point "View errors" tab in "Ground control" view
You can accept this accuracy but results are still based on the number and also position of GCP.
To few GCP and to far apart would have the obvious results.
Hello Eduardo
What in your opinion would be the right strategies for corridor mapping
I dont really know , I have just done a 65km pipeline survey. The results were very bad.
I have noticed that a slim rectangular shape does not process well. As soon as the ratio of
the long side related to the short side get to approx. 0,2 the results are poor.
This can firstly be spotted if the plane of the photo/camera's are not parallel to the bounding
box.
In a slim corridor the area rotates very easily along the length of the corridor.
In the 65 km pipeline the area was shaped in a "C" form and I thought this should give it
strong geometry , but no luck.
We had 380 GCP spaced at a 250m interval, and we opted to cut the corridor into 65 lenghts
of approx. 1.5km in length (with some overlap) and this worked ok.
I don't know really what approach to take, maybe tie strips flown perpendicular to the corridor
might help, this would result in a lot of extra work but might be essential , will experiment with
this in the next project.