Topics

1

Bug Reports / Generate Ortho - Big Tiff Error

« on: April 06, 2020, 10:30:53 PM »

This problem is occurring during the "Generate Ortho" step, not the export ortho step.

I have a WorldView 3 satellite image that I am trying to generate an orthoimage for using an imported DSM. The image has 8 bands, and a pixel size of 0.3 m.

If I choose "Generate Ortho" and try to generate the ortho with the 0.3 m pixel size, I get this error (from the logs):

Code: [Select]

2020-04-06 12:16:27 Generating orthomosaic...
2020-04-06 12:16:27 initializing...
2020-04-06 12:16:27 Analyzing DEM...
2020-04-06 12:16:27 estimating tile boundaries... done in 7.39302 sec
2020-04-06 12:16:35 generating 24192x21504 orthomosaic (9 levels, 0 resolution)
2020-04-06 12:16:35 selected 1 cameras
2020-04-06 12:16:35 saved orthomosaic data in 0.006465 sec
2020-04-06 12:16:35 saved camera partition in 0.000693 sec
2020-04-06 12:16:35 scheduled 1 orthophoto groups
2020-04-06 12:16:35 loaded camera partition in 0.000307 sec
2020-04-06 12:16:35 loaded orthomosaic data in 0.000518 sec
2020-04-06 12:16:35 Orthorectifying images...
2020-04-06 12:16:35 Orthorectifying 1 images
2020-04-06 12:18:24 19jul24184818-p2as-012267371010_01_p001: 24192x21504 -> 23831x20773
2020-04-06 12:19:45 libtiff error: Maximum TIFF file size exceeded
2020-04-06 12:19:45 libtiff error: Maximum TIFF file size exceeded
2020-04-06 12:19:46 Finished processing in 198.518 sec (exit code 0)
2020-04-06 12:19:46 Error: TIFFWriteTile: unexpected error: memory stream
However, if I change the desired pixel size to 1.6 m, the orthomosaic generates properly, just at a reduced resolution.

I know I can select "BigTiff" during the export orthomosaic process, but this does not seem to be possible with the Generate Orthomosaic process. Is there a "Tweak" parameter I can add, or can this be fixed? I need the output orthomosaic to be the same pixel size as the original image (0.3 m).

2

Bug Reports / Deleted Dense Points Still Used for Mesh Generation

« on: August 31, 2018, 12:06:14 AM »

Hi,

I know this has been posted before for earlier versions, but the solutions suggested did not work. I've isolated the problem somewhat, and found a workaround, so I'm sharing it here, and hopefully it can be fixed in an upcoming version.

Version: Agisoft PhotoScan 1.4.3 (Linux and Windows both have this issue)

Problem description:

1. Delete some undesirable points from the dense point cloud.
2. I've tried both "Compact point cloud" and tried it without that option, the results are identical.
3. Choose "Workflow -> Build Mesh". Surface type Arbitrary, Reuse depth maps unchecked.
4. The resultant mesh has polygons for the entire dense point cloud, including for the deleted points.
5. To verify this, I tried deleting fully 1/2 of the dense points in the scene, and the resultant mesh still had the entire area including deleted points. I also tried deleting the sparse points, in case they were also being used for some reason, That still did not work. I tried this in linux and windows versions of photoscan and the problem exists in both. I also tried saving the project as a new file, and that did not work.

What worked:
Instead of using "Workflow -> Build Mesh" I used "Workflow -> Batch Process -> Build Mesh". I set the source type to arbitrary again, and Source Data to Dense Cloud. The resultant mesh did NOT include the deleted dense points.


This leads me to believe that "Workflow -> Build Mesh" is not using the edited Dense Cloud, but rather it is using the full dense cloud. By contrast, the batch process version does seem to use the edited dense cloud.

I hope this helps others, and I hope this gets resolved.

3

Bug Reports / Blue Screen of Death - Calculating Color Correction

« on: June 27, 2017, 07:36:31 AM »

This problem has been occurring with version 1.3.2 and the previous version (1.3.1), but I'd never had it previously.

In Windows 10 CU, all of my processing completes fine until I get to the build ortho step. At about 13% of the color correction process, my computer gives me a BSOD. This is the only application and instance in which I've seen a BSOD since Windows XP, and it only occurs during this step in photoscan. This is happening with 3 different projects I've tried.

In Linux Mint 16.04, this same project files complete the color corrections without any issues. Both the Windows and Linux installations have the most current Nvidia drivers for my 2 GTX 1080 Ti's. My CPU is a Xeon 14 core, and I have 128Gb RAM.

I didn't have logging turned on with my Windows installation, and right now I'm processing a different dataset, in Linux.

When I get a chance later this week, I'll try to rerun the color correction in windows with logging on, if that's helpful for you.

4

General / Camera Station Orientations and View Angles

« on: July 03, 2016, 02:11:42 PM »

Hi, I have a question about the camera station orientations and view angles after the alignment process.

What I am trying to do is pick a point on Image 1, and find the matching single point on Image 2, and based on the Camera Station orientations for both of these images, find the difference in the view angles between them.

In order to do this, I need to know the camera station orientations in terms of angle of view for the images' centers. Obviously PhotoScan calculates this when doing photo alignment but is it accessible to the user as a table of values or somewhere else?

Thanks in advance for your help.

5

General / Windows vs Linux for PS

« on: June 15, 2016, 11:11:56 AM »

Hello,

I just purchased a pretty high-end system specifically for two tasks. The first is and most important is creating high-res DSMs and orthos with PhotoScan across large datasets (500-5000 images) and the second is for creating and training Deep Belief Networks (machine learning neural networks, in my case specifically for image feature/object classifications).

Photoscan obviously works well with Windows (I've been using it with Windows for years) and the DBN stuff is best supported with Linux. I have tried to search for information on these forums and Google about how Photoscan's processing times/efficiency compares between Windows and Linux with no luck at all.

Does anyone have experience or actual benchmark results of processing data where the only change between systems was the OS? Does Photoscan run better under Linux than Windows?

Here's the system I'll be using:

Intel Xeon E5-2690 V4 2.6GHz Fourteen Core 35MB 135W CPU
4 x Crucial DDR4-2133 16GB ECC Reg. Ram
3 x NVIDIA GeForce GTX 970 4GB Video Card
Samsung 850 Pro 512GB SATA 6Gb/s 2.5inch SSD Hard Drive
2 x Western Digital RE 6TB SATA 6Gb/s Hard Drive