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

Pages: 1 ... 7 8 [9] 10 11 ... 31
General / Re: Footprints script
« on: October 19, 2019, 09:00:25 PM »
it is a nonsense to set higher the tie points limit than the key points limit

Bug Reports / Re: Cylindrical orthomosaic fails
« on: October 19, 2019, 08:53:15 PM »
Here you are.

Bug Reports / Cylindrical orthomosaic fails
« on: October 15, 2019, 08:05:47 PM »
Cylindrical ortho fails even if cylindrical DEM has been built correctly.


General / Re: Correction terminology Spanish version
« on: August 22, 2019, 12:58:06 PM »
Thanks, Paulo. I guess some typos might be my fault.

General / Re: Agisoft filling in bolt and rivet holes I need to see.
« on: July 13, 2019, 03:49:24 PM »
No, your are not. No more build dense cloud stage. Just skip it and build mesh on depth maps as Alexey suggests.

General / Re: Draw rectangle polygon
« on: June 26, 2019, 04:21:24 PM »
draw it on cad and import to your project

Alignmen problems, I second that. Scroll right the ref pane table and check pixel errors for your photos. I you find images with errors greater than 1 pix, then you should check their alignment carefully. sometimes reset alignment of those poorly aligned photos and redoing alignment of the same, fixes problems. By the way, what camera/lens combo has been used? Could lens zoom have changed between shots?

General / Re: Combining imported scan data with photogrammetry
« on: June 26, 2019, 04:08:21 PM »
create markers in laser dense cloud and place them on photos, then update. Make sure source view in ref pane shows cooedinates in the tls reference system for the created markers.

General / Re: Adjust camera coordinates
« on: June 18, 2019, 06:34:31 PM »
To amend camera altitudes, a simple trick it is to export cameras in ref pane, then copy camera lines paste file to an excel sheet, modify altitudes by adding whatever, and then import back in the same fashion. However, if this constant "error" comes truely from an offset between the gnss antenna and camera nodal point, then you can set it more properly in the camera calibration dialog.


General / Re: Move marker(s) re-do the workflow again ?
« on: June 17, 2019, 08:04:38 PM »
A marker is a projection (2D) of a ground (3D) point on the image plane (the film or the image sensor). If you drag a marker in one or several photos from a to b and then you update, the entire project will chane a bit because the new projection forces the whole bundle block to shift, rotate and re-scale to best fit the new constraints in the solution.
So moving markers to line up an orto made of old photos with something (I guess with current ortho) is a bit of a weird approach. I would rather move or choose another ground point to pin the old photos to currently existing features... i mean it looks like you are trying to warp the orthomosaic rather than to do a seven parameters geometric transform (scale, rotation, translation).

General / Re: Move marker(s) re-do the workflow again ?
« on: June 17, 2019, 11:56:34 AM »
No, PRobert, a projection is a marker instance in a photo. If you move one, and the optimize, everything in your project will change this any product of the previous status becomes obsolete and requires to be rebuilt. If you just update, then what changes is only the external orientation, thus all products also become obsolete but only in scale and position. Mesh and dense cloud can be updated to the new external orientation of the chunk, but DEM and ORTHO need to be rebuilt as 3D rotation and shift in the source data, changes it all inside those products and they cannot be just updated.
by the way, what't the use of building mesh and texture in your case? just curious

General / Re: What is the best way to align photos with GCP?
« on: May 27, 2019, 07:31:52 PM »
Although 2 is strictly right, 3 works perfecly well in the very most of cases, unless your GCPs are very badly distributed and/or they are in a coordinates system that is incompatible with that of the cameras (that is the case when GCP are in a local system with totally diferent numbers than camera centers).
Normally, enabling/disabling cameras does not make any diference in EO but after the third decimal place (sub mm). Well that is assuming that accuracy settings are left as default by 0.005m for GCP and  10m for cameras.
Best regards

PD. re-align is pointless in my opinion.

check-points (unchecked ground control points) will play some role in the optimization as they are tie points placed by user, thus it is normal that project adjustment statistics change a bit if you opimize after having added check points. If you do not trust your hability to pick a point well, simply do not re-optimize.

General / Re: ultra high settings alignement
« on: May 07, 2019, 12:34:52 PM »
RTF  ;) page 23
Since tie point positions are estimated on the
basis of feature spots found on the source images, it may be meaningful to upscale a source photo
to accurately localize a tie point. However, Highest accuracy setting is recommended only for very
sharp image data and mostly for research purposes due to the corresponding processing being quite
time consuming.


General / Re: GCPs with no elevation value?
« on: May 06, 2019, 04:02:06 PM »
You can add GCP with XYZ using precise XY and guessed Z taking it from google earth, for example, then set accuracy accordingly, for example an accuracy of 0.005/10 would mean 5mm in horizontal positioning and 10 meters in vertical.
Also, if you are using a drone geo-tagged images, you can use 10/10/0.2 for camera accuacy. So the drone altitude measuered by the baro altimeter (which is often quite accurate in relative) will make your model to be properly leveled while GCP will put it into right XY


Pages: 1 ... 7 8 [9] 10 11 ... 31