Forum

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 - radar_boy

Pages: [1] 2
1
General / Re: Using Leica DMC III images
« on: August 10, 2021, 05:49:28 PM »
I woud fix all parameters.....

I'm returning to this processing again and just want to triple check that the focal length, pixel sizes and principal point coordinates are fixed to those from the [synthetic] camera calibration, and all other values are also fixed, presumably at zero?

If so, once erroneous sparse points are removed and Cameras Optimised (i.e. final bundle adjustment) only the exterior orientation (i.e. camera stations/poses) are adjusted? If this is correct, I'm curious to know what kind of Accuracy you used for the camera locations (m) and orientations (degrees) please? Did you import values from a table of ephemeris data for the flight (I have SD for locations, via dGNSS, and orientations, via IMU), or did you set Accuracy values the same for all photos? If the latter is the case, did you use small/tight values (e.g. fractions of a metre and fractions of a degree) or larger/looser values (e.g. a metre or more and a degree or more)?

Many thanks again!  :)

2
General / Re: Using Leica DMC III images
« on: August 03, 2021, 12:48:42 PM »
Here is my Camera Calibration GUI. I believe the only difference with yours is I have fixed f


3
General / Re: Using Leica DMC III images
« on: August 03, 2021, 11:58:44 AM »
Many thanks for your reply Paul  :)

I have a PDF which contains the info in the same format as you presented. For anonymity I've removed the Serial Number, but everything else is just a copy & paste:

Code: [Select]
Geometric Calibration
The output image geometry is based on the Pan Camera head (reference head =
master camera). All other camera heads are registered and aligned to this head.
Aerial triangulation checks overall system performance based on.
Output image
Reference Camera PAN
Serial Number NNNNNNNN
Number of rows/columns [pixels] 25728 x 14592
Pixel Size [um] 3.900 x 3.900
Image Size [mm] 100.3392 x 56.9088
Focal Length [mm] 92.0000 mm + /- 0.002 mm
Principal Point [mm] X= 0.0000 mm, Y= 0.0000 mm + /- 0.002 mm
The “SYNTHETIC” geometric calibration is based on a simulated mathematical lens distortion calculation based on the detailed optical design data of the lens.

4
General / Using Leica DMC III images
« on: August 02, 2021, 06:23:26 PM »
I would like to use some stereo, vertical Leica DMC I and DMC III aerial imagery, provided as RGB in TIFF format. I have exterior orientation metadata as text, together with some interior orientation metadata (e.g. calibrated focal length, pixel size etc). I can import said data and metadata.

I have started by working with a block of >70 DMC III images and Align Photos to create a sparse cloud.

Unless I deliberately fix the focal length it ends up changing dramatically (>34000 mm vs. the calibrated 92mm). When I then use Model > Gradual Selection and progressively select points in the sparse cloud according to Reconstruction Uncertainty I get distinct structures forming:





When I fix the focal length the sparse point cloud appears thus:



These structures suggest systematic errors. I sense there is something wrong with the camera model? Is there something extra I should be doing to import Leica DMC images? Might the systematic errors be related to the fact DMC use multiple 2D arrays?

5
First, which country, agency/company and camera? I have some archive camera calibration reports and you never know, they might match...!

Second, the variations you report (0.2 and 0.5 mm)... are these with reference to the [assumed] principal point?

Andy

6
Camera Calibration / Clarification regarding Calibrate Fiducials
« on: March 20, 2020, 01:08:12 AM »
Am I correct in guessing that Calibrate Fiducials assumes the fiducial marks are symmetrical (equidistant from the principle point) and uses the given scan resolution to calculate their approximate coordinates? Is this done on a per-image basis, or use means (or some other statistic) if multiple images are selected together (therefore more representative coordinates)? I'm just seeking some clarification please.  ;)

If this is correct it'd be great to add such to the manual for future reference.

Many thanks

Andy

7
Feature Requests / Calibrate Fiducials: um & dpi options
« on: March 20, 2020, 12:56:23 AM »
When using Calibrate Fiducials it would be wonderful to have the options to input the scan resolution in um (microns) and dpi please.

Many thanks

Andy

8
There may be a way of doing this which I haven't yet discovered (please provide instructions if there is) but we really need a means creating 2D (i.e. horizontal) markers... i.e where only x,y coordinates were able to be measured. Also, where 3D markers are used (i.e. the only kind of marker I'm aware of in the current version) it would be very useful indeed to differentiate between 2D/horizontal (x,y) and 1D/vertical (z) marker accuracy, as the two are often very different indeed (e.g. when using GNSS to survey marker locations). Using just one overall Accuracy for each marker is very limiting when it comes to bundle adjustment with markers surveyed by different means or in different conditions.

9
General / Re: Patches of high/low areas in point cloud of terrain
« on: March 02, 2018, 07:36:21 PM »
I can't export as XML, when when I import the same XML nothing appears (there are no error messages either)...

11
General / Re: Patches of high/low areas in point cloud of terrain
« on: March 02, 2018, 01:54:33 PM »
I'm revisiting this thread because, unfortunately, I was never able to get rid of these artifacts. I'd hoped that new versions might provide a fix (I'm now running 1.4.1) but to no avail. I followed the instructions in the previous post to the letter, but with no improvement.

12
The *.geom and *.vrt formats are becoming ever more popular for photo station ephemeris, camera models and RPC, not least in the airphoto sector. With 1000s of images having to be processed it is impractical to add this data manually. Can PhotoScan be updated to automatically recognise and import this data please?

Many thanks

Andy

13
General / Using *.geom for ephemeris and camera model for images?
« on: November 08, 2017, 01:25:08 PM »
I have a bunch of vertical and oblique airphotos I wish to use in SfM (*.jpg as it happens). Each one has a *.geom file, which appears to contain the photo station ephemeris data and the camera model for each. My question is, how can I automatically add all this metadata into PhotoScan. I have 1000s of images and doing it manually is not practical!

Many thanks in advance.

Andy

14
General / Re: Using *.vrt for ephemeris/RPC of oblique airphotos?
« on: November 08, 2017, 01:21:43 PM »
No thoughts on this from anyone, including the AgiSoft ream???  :'(

15
General / Using *.vrt for ephemeris/RPC of oblique airphotos?
« on: October 27, 2017, 07:37:17 PM »
I'm using oblique airphotos acquired by NOAA and made freely available as TIFF here:

https://geodesy.noaa.gov/storm_archive/coastal/viewer/index.html

Each TIFF comes with an associated *.vrt file... a format I'm not familiar with. To me it appears to contain ephemeris/RPC.

I want to generate geo-referenced point clouds, as well orthophotos from multiple TIFFs. Is there a way for importing the information from the VRT files into PhotoScan for this purpose (therefore with no GCP required)?

Pages: [1] 2