Forum

Recent Posts

Pages: 1 ... 8 9 [10]
91
Getting std::bad_alloc when trying to build an interpolated (not extrapolated) mesh on high from the dense cloud on some big chunks. Dense cloud is GCS (NAD83(2011)). I have successfully built interpolated and uninterpolated DEMs, and orthoimages for these chunks.

We first built an uninterpolated DEM from the dense cloud for the elevation model, then built an interpolated DEM and orthophoto (using the interpolated DEM.

I am now trying to build a mesh from the dense cloud to use for a comparison orthoimage (because in smaller experiments the mesh was much faster and smaller than the interpolated DEM).

The mesh was generated after rotating the bounding box to the DEM projected coordinate system (PCS = NAD83 UTM). Rotation was performed to minimize the height/width of the nodata collars on the DEM generated from the dense cloud, since if it stays rotated, the DEM bounds go all the way to the corners of the along-track-oriented (not PCS-oriented) bounding box. I wonder if the mesh is failing because it's doing grid interpolation over the whole empty area of the rotated bounding box. In that case, I need to switch the order or re-rotate the region to be oriented with the data, but it will probably still fail on another section that is L-shaped with a bunch of empty space.

These are the details from the node - I included a previous successful (smaller) mesh generation before too:

2021-05-07 17:45:55 BuildModel: source data = Dense cloud, surface type = Height field, face count = High, interpolation = Enabled, vertex colors = 0
2021-05-07 17:45:56 Generating mesh...
2021-05-07 17:46:20 generating 213317x132869 grid (0.00214379 resolution)
2021-05-07 17:46:20 rasterizing dem... done in 81.9141 sec
2021-05-07 17:47:42 filtering dem... done in 375.867 sec
2021-05-07 17:55:06 constructed triangulation from 21327465 vertices, 42654924 faces
2021-05-07 17:57:38 grid interpolated in 220.33 sec
2021-05-07 18:13:56 triangulating... 106374525 points 212748181 faces done in 4727.18 sec
2021-05-07 19:32:45 Peak memory used: 181.40 GB at 2021-05-07 19:32:43
2021-05-07 19:33:00 processing finished in 6425.13 sec
2021-05-07 19:33:00 BuildModel: source data = Dense cloud, surface type = Height field, face count = High, interpolation = Enabled, vertex colors = 0
2021-05-07 19:33:01 Generating mesh...
2021-05-07 19:33:37 generating 262471x233536 grid (0.00219694 resolution)
2021-05-07 19:33:37 rasterizing dem... done in 209.04 sec
2021-05-07 19:37:06 filtering dem... done in 847.863 sec
2021-05-07 19:53:17 constructed triangulation from 23493503 vertices, 46987000 faces
2021-05-07 19:57:34 grid interpolated in 380.113 sec
2021-05-07 20:20:53 Error: std::bad_alloc
2021-05-07 20:20:53 processing failed in 2872.89 sec
92
Python and Java API / Re: Reset camera alignment on list of Cameras
« Last post by Paulo on May 08, 2021, 04:21:36 AM »
Hi Alexis,

you can just create BadCameras list and populate it with your bad cameras and then just use following:

Code: [Select]
for c in BadCameras:
      c.transform = None

Hope this can help,
93
Python and Java API / Re: Custom reprojections for point clouds, DEMs, and Orthos
« Last post by Paulo on May 08, 2021, 04:16:10 AM »
Hi,

once you tansform your project into local coordinates, the point clouds will be automatically transformed.

However the DEM and Ortho have to be regenerated in the new local system....

The following example shows how I transform a project from grid crs to local crs, setting 1st camera center local coordinates to (100, 100, 100) with local crs coordinate axes set to localframe (E, N, Up) at 1st camera center.

Obviously, the dense cloud is automatically in local crs while DEM is still in original grid crs and has to be regenerated if needed in local crs.
94
Hello, I made a set of tools that allows me to scale, translate, and rotate my camera positions for localized survey projects. I want to know if I can do the same to the finalized ortho, point cloud, and DEM? sometimes projects need deliverables in both grid and ground coordinates. If possible, I would prefer to process my projects in grid coordinates and then convert the products (point clouds, DEMs, and orthos) to ground coordinates. This way I can have two sets in both projections.  I looked through the API documentation but I was unable to clearly identify methods to do these types of transformations. If you could point me in the right direction to the methods in the API documentation for each deliverable or have some examples, that would be great.
Thank you
95
Python and Java API / Reset camera alignment on list of Cameras
« Last post by Alexis on May 07, 2021, 10:39:15 PM »
Hello,

I'm working with drone data, and after aligning the cameras, I want to go back and reset the alignment on a list of 'badCameras' which are causing tie points to fly off in space.

I'm just looking to replicate right clicking an image in the GUI and running 'Reset Camera Alignment' for the list of cameras I've already identified.

Thanks!
96
Bug Reports / Re: Installation fails on linux
« Last post by andyroo on May 07, 2021, 09:28:20 PM »
Which OS distribution you are using...

CentOS 7.7.1908

and if you are working on the computer remotely (if so, then how the remote connection is established)

vncserver with Xfce desktop environment

the fix was:

yum install xcb-util-wm xcb-util-image xcb-util-keysyms xcb-util-renderutil


working now

[EDIT - adding new observations below]

I'm seeing these messages in the terminal now. I included the last debug line before the repeating sequence of console messages - with one buried error amongst the sequence. Been running for about 45 minutes now with ~8 repeats of the sequence:

Code: [Select]
loaded library "udev"
Only C and default locale supported with the posix collation implementation
Only C and default locale supported with the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Only C and default locale supported with the posix collation implementation
Only C and default locale supported with the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Only C and default locale supported with the posix collation implementation
Only C and default locale supported with the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Only C and default locale supported with the posix collation implementation
Only C and default locale supported with the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Only C and default locale supported with the posix collation implementation
Only C and default locale supported with the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 38163, resource id: 16689444, major code: 40 (TranslateCoords), minor code: 0
Only C and default locale supported with the posix collation implementation
Only C and default locale supported with the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Only C and default locale supported with the posix collation implementation
Only C and default locale supported with the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation


wondering if it's related to this post that says installing libicu-dev (before building Qt) makes the messages disappear...
97
Hello Alexey,

the latest build 12337 of 1.73 imediately breaks down and closes with a bug report window, when importing .dng files. JPEG and TIFF files work.

best regards,
Andreas
98
Thanks mks_gis,

actually in your Github, I see that most parameter changes I made (downscale for matchPhotos and buildDepthMaps, filter_mode for buildDepthMaps) are already introduced in your v7.4.

However, i do not really understand why generic_preselection is always set to False. Should it not be selectable or changeable  by user?

99
Thanks Paul, I'll look at your version and perhaps merge them.

The maintained version is on Github:
https://github.com/gisportsmouth/PhotoScan-Automation-Script

100
Feature Requests / Re: thermal images multi camera system process
« Last post by madu on May 07, 2021, 04:59:01 PM »
Hi,

in my case using a sensefly Duet-t what works for me is to leave the rgb images in the folder and create a subfolder inside with the thermals.This way agisotf understands that the one outside are the masters and the subfolder the slaves.

On the other hand, could you please share the script to convert the images to .tif with temperature values?

Best regards
Pages: 1 ... 8 9 [10]