Messages

16

Feature Requests / How to use Sequoia calibration target with Photoscan

« on: September 07, 2016, 04:41:12 PM »

Hello,
I have a Sequoia multispectral camera.

This camera is supplied with a calibration target: the pilot should take a picture either immediately before or after the flight, and it should need to calibrate the camera with the current environmental condition (sun etc...)

I know that using softwares similar to Photoscan, one should import this image to calibrate the project... for example at the project creation.

Do you know how can I do using Photoscan?

Thanks!

17

Python and Java API / Re: ValueError in buildOrthomosaic command

« on: June 23, 2016, 05:17:13 PM »

so, could it be ok the following statement?

Code: [Select]

crs = PhotoScan.CoordinateSystem("EPSG::32632")

curr_chunk.buildOrthomosaic(surface=PhotoScan.ModelData, blending=PhotoScan.MosaicBlending, projection=crs)
and please tell me also if the following are ok:

Code: [Select]

curr_chunk.exportOrthomosaic(path="C:/exportOrthomosaic.TIF", format='tif', raster_transform=PhotoScan.RasterTransformNone, projection=crs, write_kml=False, write_world=True, tiff_compression='lzw', tiff_big=False)

curr_chunk.exportModel(path="C:/exportModel.PDF", binary=True, precision=6, texture_format='pdf', texture=True, normals=True, colors=True, cameras=True, udim=False, strip_extensions=False, projection=crs)
thanks

18

Python and Java API / ValueError in buildOrthomosaic command

« on: June 23, 2016, 04:52:12 PM »

Hello,
I'm trying to build orthomosaic by the following statements:

Code: [Select]

curr_chunk = doc.chunks[0]

crs = PhotoScan.CoordinateSystem("EPSG::32632")

curr_chunk.buildOrthomosaic(surface=PhotoScan.DenseCloudData, blending=PhotoScan.MosaicBlending, color_correction=False, projection=crs)
but I get this error:

Code: [Select]

2016-06-23 15:39:25 curr_chunk.buildOrthomosaic(surface=PhotoScan.DenseCloudData, blending=PhotoScan.MosaicBlending, color_correction=False, projection=crs)

2016-06-23 15:39:25 ValueError: unsupported data source
Do you know where is my mistake?

thanks!

19

General / Re: process Point Of Interest (POI) images with Photoscan

« on: June 22, 2016, 10:16:53 PM »

fantastic Alexey!

thank you very much!!!

see picture...

20

General / Re: process Point Of Interest (POI) images with Photoscan

« on: June 22, 2016, 08:19:15 PM »

great Alexey!
thank you again!

and what about buildUV mapping parameter?
have I to use AdaptiveOrthophotoMapping value?


doc.chunk.buildUV(mapping = PhotoScan.AdaptiveOrthophotoMapping)

21

Python and Java API / "Gradual selection" utility in python

« on: June 22, 2016, 05:58:46 PM »

Hello,
do you know if there is a command in python to replicate the utility "Edit -> Gradual Selection..." provided into the GUI?

thanks!

22

General / process Point Of Interest (POI) images with Photoscan

« on: June 22, 2016, 05:13:23 PM »

Hello everybody,
I've to elaborate my images taken during the POI procedure with Photoscan.

I've never done it before...

During the fly I have taken the images and then I have processed them in the same usual way:

1. align
2. optimization
3. build dense cloud
4. mesh
5, texture

but I get the result in the attached image

I don't think it's good: where is my error? may someone help me?

My only idea is the "surface" value in the mesh elaboration: I put "HeightField" but maybe I should put "Arbitrary"...could it be?

THANKS!

23

General / Re: columns name in ascii file of export points cloud

« on: June 13, 2016, 06:00:15 PM »

Alexey, you are absolutely right, I've not explained well the example.

My drone was flying at an altitude (respect to the takeoff point) of 60 meters:

height_Drone = 60 mt

After the fly, I've loaded my photos into Photoscan and I've processed them, obtaining the mesh.

Into Photoscan, at "Ground control" tab, "Cameras" section, I see all the attributes of my photos, and the altitude reported is 95 meters:
 
height_Cameras_into_Photoscan = 95 mt

After that, I exported the points cloud (trying both "XYZ points cloud" and "ASCII pts" file type) and the altitude reported into the ascii file was 36 meters:

height_ASCII = 36 mt

The altitude reported, in the same area, by maptool2, was 105 meters:

height_MAPTOOL = 105 mt

24

General / Re: columns name in ascii file of export points cloud

« on: June 13, 2016, 11:26:32 AM »

But  the altitude  above take-off point should be:

height_Drone...

Do you know where the altitude inside the .txt (or .pts) file (output from export points cloud from Photoscan) is taken (in the example below named height_ASCII)?

25

General / Re: columns name in ascii file of export points cloud

« on: June 12, 2016, 09:59:04 AM »

Hello Alexey,
the altitude of the camera positions are automatically reported by Photoscan, I do not pass the altitude.

After having imported the photos into Photoscan I automatically see the altitude (and the values I see are the ones I reported in the examples below, named "height_Cameras_into_Photoscan").

You mean there is a way to force, into Photoscan, the altitude of the camera positions?

26

General / Re: columns name in ascii file of export points cloud

« on: June 10, 2016, 02:57:02 PM »

thanks Alexey.
I use the following coordinate system:

WGS84 UTM Zone 32N

I've some doubts, following an example:

photos into photoscan report height_Cameras_into_Photoscan=220mt

the photos was taken by a drone at a height_Drone=120mt

the ASCII file export points cloud record height_ASCII=99mt

so, everything sounds good (200 - 120 = 100 very near to 99)

but when I check the real altitude, for example via tools like "map tool" (www.zonums.com/gmaps/maptool.php), I obtain a value very far from 99mt:

height_MAPTOOL=80mt

and I don't know how to justify it...
may you have some ideas?

thanks

PS: another example:

height_Cameras_into_Photoscan=95mt

height_Drone=60mt

height_ASCII=36mt

BUT:

height_MAPTOOL=105mt (very very far from 36mt)

27

General / columns name in ascii file of export points cloud

« on: June 08, 2016, 08:02:58 PM »

Hello,
exporting the points cloud I get an ASCII file.

I use these two options:

File > Export Points... > option "XYZ Points Cloud"

File > Export Points... > option "ASCII pts"

May someone tell me the meaning/name of the columns in those files?

Thank you all!

28

General / Re: Export points cloud

« on: June 08, 2016, 07:58:26 PM »

ok Arnold, very very thanks for your precious help!

just a last question: do you know what's the meaning of the 3 textboxes named "SHIFT" I find in the export points mask?

29

General / Re: Export points cloud

« on: June 08, 2016, 07:38:03 PM »

I would use the GCP and export coordinate system as WGS 84.
Concerning the app, I use the iOS app "Map Pilot".

May you please tell me what are the meaning of the columns in the "ASCII PTS" file?

Surely it starts with longitude, latitude and altitude...

30

General / Re: Export points cloud

« on: June 08, 2016, 06:15:41 PM »

absolutely thanks HMArnold!
is it possible to choose between sparse and dense cloud?
and, just to be sure: the 3rd column, the altitude of each point of the cloud, is AGL right?