Messages

1

General / Re: Bad stitching with good Sequoia dataset

« on: August 16, 2017, 11:33:53 AM »

how can it be to have so much rolling shutter issue? never seen something like this

Strong wind and no gimbal

2

General / Re: Bad stitching with good Sequoia dataset

« on: August 16, 2017, 01:34:34 AM »

Hello andrey.d,

I think that you should use Height Field option for the mesh reconstruction instead of Arbitrary to avoid severe artifacts by the edges of the area of interest.

I tried this too.

I think I found the reason. There is series of deformed photos due to rollingshutter (see attachment)
Should photoscan correct this problem by optimizing alighment with rollingshutter setting?

3

General / Bad stitching with good Sequoia dataset

« on: August 15, 2017, 12:01:07 AM »

Hi!

I have the dataset of 1576 RGB images of field by Sequoia camera. It has a very good overlap - more 9 images for most points. And I use CameraAlignment with  RollingShutter options.
But result is bad. What is the problem? 

Please see Agisoft Photoscan report for details
https://share.skyglyph.com/index.php/s/vBPCTQxP0eU8BxA

4

General / Re: Bad bands interpretation in Multispectral Sequoia orthomosaic map

« on: July 10, 2017, 12:29:37 AM »

I think I find what is the problem.
Unexpected for me the Sequoia Multispectral Camera has only Green, Red, Red edge, NIR channels without Blue.
So Agisoft Photoscan couldn't make RGB result tiff map.

I suppose in this case Agisoft Photoscan should work better and set something like that as Color Interpretation:
Band 1  ColorInterp=Green
Band 2  ColorInterp=Red
Band 3  ColorInterp=Red_edge
Band 4  ColorInterp=NIR

5

General / Re: Bad bands interpretation in Multispectral Sequoia orthomosaic map

« on: July 07, 2017, 04:56:52 PM »

I mean result map was in the incorrect format: no Red, Green, Blue, NIR channel.
There is 5 band in tiff file, but the first band is Gray, 2, 3 and 4  bands are Undefined.

6

General / Bad bands interpretation in Multispectral Sequoia orthomosaic map

« on: July 05, 2017, 02:16:57 AM »

Hello,


I use this manual https://training.fws.gov/courses/references/tutorials/geospatial/CSP7304/2016documents/HandsOn_Afternoon/UAS/UAS%20II%20Post%20Processing/PhotoScan%20Processing%20Procedures%20MicaSense%20Feb%202016.pdf
 to stitch Multispectral Sequoia images into a map. The result looks without proper color information.

The resulting map has the problem with bands interpretation: the first band is Gray, 2-4 are Undefined, 5-th is Alfa.


As input, I have set of one channel images for like
IMG_xxx_GRE.TIF, 
IMG_xxx_REG.TIF
IMG_xxx_RED.TIF,
IMG_xxx_NIR.TIF.

7

Python and Java API / Howto set Mapir camera calibration setting by Python?

« on: June 14, 2017, 01:16:56 AM »

Hello

The Mapir camera needs manual setting for custom pixel size and focal length.
(There is link to instruction
https://www.mapir.camera/blogs/guide/processing-survey2-camera-images-in-agisoft-photoscan)

How can I set it by Python script?
Can I just use this code

Code: [Select]

...
chunk = PhotoScan.app.document.addChunk()
camera = chunk.addCamera();
camera.sensor = chunk.addSensor();
camera.sensor.label  = 'Mapir Survey2'
camera.sensor.type = PhotoScan.Sensor.Type.Frame
camera.sensor.width = int("0.00134")
camera.sensor.height = int("0.00134")
camera.sensor.focal_length = int("3.97")
camera.sensor.fixed = True
... ?

8

Python and Java API / Re: exportReport error

« on: March 07, 2017, 05:55:26 PM »

Thanks

9

Python and Java API / Re: exportReport error

« on: March 07, 2017, 02:03:27 AM »

I'm running script from command line

10

Python and Java API / exportReport error

« on: March 07, 2017, 01:02:30 AM »

Hello,

I have the problem with report exporting:

Code: [Select]

chunk.exportReport("report.pdf") It works well before. And it works well in a GUI mode now.

Current ver. 1.3 build 3772 linux 64bit
Error:

ExportReport
Segmentation fault (core dumped)

Thanks

11

Python and Java API / Bed result after changing Coordinate System for export

« on: March 03, 2017, 05:39:28 AM »

Hello,

Could you help me to understand how I have to set Coordinate System?
I have csv with image coordinates file with in EPSG::4326.
I need export map in  EPSG::3857
A did it but stitching quality was terrible.
I use this code to load images and reference (csv) file

Link th the report https://drive.google.com/open?id=0B5NgaXpGOtOUNzhBempTd2lMUXVUaUhLZEpxZElSZ096dkhJ
The csv file in attachment

My code:

Code: [Select]

chunk.addPhotos(images_list)
camera = chunk.cameras[0]
chunk.loadReference(out_csv, format=PhotoScan.ReferenceFormatCSV, columns="nxyzabc", delimiter=",", group_delimiters=False, skip_rows=1)
chunk.crs = PhotoScan.CoordinateSystem("EPSG::4326")....
And before export orthomap I change CoordinateSystem to EPSG::3857

Code: [Select]

crs = PhotoScan.CoordinateSystem("EPSG::3857")
doc = PhotoScan.app.document

doc.open(project_path)
chunk = doc.chunk
chunk.crs = crs

chunk.buildOrthomosaic(surface=PhotoScan.ModelData, blending=PhotoScan.MosaicBlending, color_correction=False)
chunk.exportOrthomosaic(args.ortho_path, image_format=PhotoScan.ImageFormatTIFF, raster_transform=PhotoScan.RasterTransformNone, write_kml=False, write_world=False, write_alpha=True, tiff_compression=PhotoScan.TiffCompressionDeflate)


12

General / Re: Agisoft PhotoScan 1.3.0 pre-release

« on: February 05, 2017, 03:06:43 PM »

Hello andrey.d,

Actually, it doesn't seem to be related to the version 1.3 - you have set the projected coordinate system, so by default PhotoScan will be building the orthomosaic in geographic coordinates, but since you have no reference information that model is arbitrary oriented causing incorrect scene estimation.

Thank you, Aleksey.

The answer was in using Local CRS as you write here:
http://www.agisoft.com/forum/index.php?topic=2718.0

13

General / Re: Agisoft PhotoScan 1.3.0 pre-release

« on: February 04, 2017, 01:21:11 PM »

Hello Aleksey,

I have some problems with using dataset without reference with python script.
I need result in EPSG::3857 (it placed in virtual place near (0, 0) point and one pixel equal to one point in EPSG::3857 crs- but it okey for me.

In GUI mode all work fine. BUT when I do it in a script I receive huge map (about 1M x 1M pixels)

The question is how I can get from agisoft optimal size or resolution for export.


This is part of my code:

Code: [Select]

crs = PhotoScan.CoordinateSystem("EPSG::3857")
doc = PhotoScan.app.document
doc.open(project_path)
chunk = doc.chunk

chunk.addPhotos(images_list)
chunk.matchPhotos(accuracy=PhotoScan.MediumAccuracy, preselection=PhotoScan.NoPreselection)
chunk.alignCameras()
chunk.buildModel(surface=PhotoScan.HeightField, interpolation=PhotoScan.EnabledInterpolation)

chunk.crs = crs
chunk.buildOrthomosaic(surface=PhotoScan.ModelData, blending=PhotoScan.MosaicBlending, color_correction=False)
chunk.exportOrthomosaic(args.ortho_path, image_format=PhotoScan.ImageFormatTIFF, raster_transform=PhotoScan.RasterTransformNone, write_kml=False, write_world=False, write_alpha=True, tiff_compression=PhotoScan.TiffCompressionJPEG, jpeg_quality=90, tiff_big=True)

 

14

General / Re: Agisoft PhotoScan 1.3.0 pre-release

« on: January 30, 2017, 02:14:12 PM »

Dear Aleksey,

Could I manage mem,  virtual mem and cpu cores by script.
I see examples for cpu cores setting,  but it don't work in last build of 1.3.

Thanks.

15

General / Re: Agisoft PhotoScan 1.3.0 pre-release

« on: January 20, 2017, 12:22:55 PM »

Hello andrey.d,

For me it looks like the camera orientation angles loaded to the Reference pane is incorrect - so the model orientation in space in also incorrect. I've input very large number as "camera accuracy (deg)" to the Reference pane settings and then Updated the Reference pane - the orientation of the model after that looked valid.

I have image_name, longitude, latitude, altitude, yaw, pitch, roll
Could you give right format of csv file in my case?