Topics

1

Bug Reports / building tiled model with 1.5.0 7492 crashes computer hard

« on: January 14, 2019, 01:18:39 PM »

Hello,
I tried out several times building tiled models using 100 DJI-images without any problems.
Using Ultracam aerial images (17004x26460) did crash the computer really hard after ca. 50% of the GPU work (goto line 652 of the log).
There is no even a system-crash log...

The preceding image alignement worked without any errors.
Is it related to large images ? FirePro D700 ?
I assumed the tiling approach avoids the "image is too large" problem

Ruedi

2

Bug Reports / Python with PhotoScan.RasterTransformValue

« on: January 03, 2018, 03:14:53 PM »

Hi there,
I try to use raster-transforms, actually to export NDVI-Orthos.
When I run my script, a RunTimeError occurs, when exporting the ortho
Without "raster_transform = PhotoScan.RasterTransformValue", everything works fine.
Do I use the wrong syntax ?

Thanks, Ruedi


...
               self.chunk.raster_transform.formula = ["(B4-B2)/(B4+B2)"]
               self.chunk.raster_transform.calibrateRange()
               self.chunk.raster_transform.enabled = True
               self.chunk.exportOrthomosaic(saveOrtho, image_format = PhotoScan.ImageFormatTIFF, raster_transform = PhotoScan.RasterTransformValue)
...
Log:
2018-01-03 10:46:00 Agisoft PhotoScan Professional Version: 1.4.0 build 5650 (64 bit)
2018-01-03 10:46:00 Platform: Mac OS
2018-01-03 10:46:00 CPU: Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz (server)
...
2018-01-03 12:43:33     self.chunk.exportOrthomosaic(saveOrtho, image_format = PhotoScan.ImageFormatTIFF, raster_transform = PhotoScan.RasterTransformValue)
2018-01-03 12:43:33 RuntimeError: Invalid data type
2018-01-03 12:43:33 Error: Invalid data type

3

Feature Requests / Sequoia import (work around for missing channel files)

« on: September 12, 2017, 02:00:04 PM »

Hello Agisoft,
Recently I had a couple of Sequoia-datasets (using v1.4.1 Sequoia firmware...) with partially missing channel-files, e.g. a single xxxGRE.TIF or xxxRED.TIF was missing. Typically only 1 single file  from 400 is missing.
Unfortunately when Photoscan v1.3.x detects a missing channel, it treats all images as normal dataset and the multispectral-import does not appear.

I would suggest the following approach:
Please only check if the single multispectral image-tuple is complete (_GRE.TIF,_NIR.TIF,_RED.TIF,_REG.TIF (don't care about the rgb.JPG)). If one of the images in a 4-tuple is missing, skip only this tuple and continue searching.

4

Python and Java API / Null elevation

« on: March 08, 2017, 04:39:49 PM »

Hello Agisoft,

Using 113 UAV images (with X,Y,Z) and 3 GCP with proper X,Y,Z-values

Everything like build dense cloud, etc. runs fine with my Python script
With Build 3772 the scripts stops ending up in the GUI-Console with:
...
2017-03-08 14:27:50     self.chunk.exportDem(saveDEM)
2017-03-08 14:27:50 RuntimeError: Null elevation

With Build-version 2834 and older versions it runs without any complaints and generates a proper report, DEM,etc.
There is an PhotoScan.Elevation-class, but how to handle it ? in previous builds, the reference height was obviously tkane from the GCP-data  !(?)

5

Bug Reports / Orthomosaic Export Problems with v1.2.5 (2735) and Float32 image data

« on: August 10, 2016, 03:35:56 PM »

Hello,
we are using a FLIR-camera and the same set of images works fine concerning aligning,dense cloud,etc. with v116 and v125.
Each input image is a 1-channel Float32 TIFF, containing temperature values, typically 10..40.
With v116 I get a descent temperature  Orthomosaic in channel 1.
With the current v125 the scaling of the Orthomosaic is now somehow strangely normalized (I tried also with  PhotoScan.BlendingMode=DisabledBlending).
How to get the channel layout (and disabled scaling ) of v116 ?
Ruedi

Float32-images with v1.1.6
 
Band 1 Block=2647x32 Type=Float32, ColorInterp=Gray
  Minimum=-17.021, Maximum=49.017, Mean=10.409, StdDev=9.912
  Metadata:
    STATISTICS_MAXIMUM=49.017379760742
    STATISTICS_MEAN=10.409090188344
    STATISTICS_MINIMUM=-17.020740509033
    STATISTICS_STDDEV=9.9120056741228
Band 2 Block=2647x32 Type=Float32, ColorInterp=Alpha
  Minimum=0.000, Maximum=1.000, Mean=0.541, StdDev=0.498
  Metadata:
    STATISTICS_MAXIMUM=1
    STATISTICS_MEAN=0.5414550280809
    STATISTICS_MINIMUM=0
    STATISTICS_STDDEV=0.49827851714359


Float32-images with v1.2.5 (2735)

Band 1 Block=256x256 Type=Float32, ColorInterp=Gray
  Min=0.000 Max=0.000
  Minimum=0.000, Maximum=0.000, Mean=0.000, StdDev=0.000
  Overviews: 1376x836, 688x418, 344x209, 172x105
  Metadata:
    STATISTICS_MAXIMUM=0
    STATISTICS_MEAN=0
    STATISTICS_MINIMUM=0
    STATISTICS_STDDEV=0
Band 2 Block=256x256 Type=Float32, ColorInterp=Alpha
  Min=0.000 Max=1.000
  Minimum=0.000, Maximum=1.000, Mean=0.663, StdDev=0.473
  Overviews: 1376x836, 688x418, 344x209, 172x105
  Metadata:
    STATISTICS_MAXIMUM=1
    STATISTICS_MEAN=0.66312668646378
    STATISTICS_MINIMUM=0
    STATISTICS_STDDEV=0.47264117908128

6

Feature Requests / Open Project and run python script from command line

« on: June 13, 2016, 03:59:25 PM »

Hi,
Opening projects and launching Photoscan works fine, the world would be even better if as additional parameters a related python script with its argument could be added on command line:
in MacOS-unix:

open -a PhotoScanPro.app /Volumes/BigData/project09638.psx runPHScanner.py projectParameters09638.txt


preferably also for Windows/Linux...

Ruedi

7

Bug Reports / Different pixelsize in exportDem and exportOrthophoto in v1.1.0

« on: January 09, 2015, 07:20:11 PM »

Hi,
I switch recently from 1.0.4 to 1.1, after processing the same images I got strange results (manually AND with the python-interface!):
The PDF-report shows (why is no option for an ascii-export of the report...?):

Page 2: Survey Data:
Number of images: 514
Flying altitude: 260.191 m
Ground resolution: 0.0791013 m/pix
Coverage area: 2.33455 sq km
Camera stations: 514
Tie-points: 78246
Projections: 343834
Error: 2.22708 pix

Page 4: Ground Control Points:
Total (last line):
X-Error (m):   0.007136
Y-Error (m):   0.013967
Z-Error (m):   0.022269
Error (m):      0.027238
Projections:   23
Error (pix):   0.296075

Page 6: DEM:
Resolution: 4.24915 m/pix
Point density: 0.0553855 points per sq m

The ortho was export with 7cm resolution and is looking perfectly, the DEM was exported with 4.2m and was (of course...) very coarse.
Forcing the DEM-export down to 7cm revealed, that the technical pixelsize was 7cm, but the effective level-of-detail was still 4.2m.