This is the link to the pix4d files (p4d, log and report pdf) https://we.tl/yB45ynXJH3 . Unfortunatelly pix4d fails to upload it to the cloud - we reported that already to support.
In essence we import the R_jpg pictures, what is split into rgb (jpg) and thermal (tif) by pix4d, we then disable the jpgs and only enable the “grayscale” tifs. Furthermore we only allow pictures taken above 400 m, so pictures near the ground are disabled.
We then select the thermal template and select Tau2 13mm, where we manually reset distortion parameters to be 0.
I had some success with applying alternative processing vs. standard, but I have no conclusive opinion about the step mentioned by Ina (“After changing the pixel size run step 1 and then if the difference between optimized and initial internal camera parameters is high then opt for All Prior.”).
Any of your insight would be greatly appreciated!
If you need more raw data I would be happy to share - we have a 37 km x 400 m corridor captured!
I can’t see your latest post here, strange …
It might be easier to use e-mail, for subsequent conversation, my e-mail address is reto.weiss (at) pixmap.ch.
Did you have a chance to check the other post related to cloud upload?
The R_jpeg and the RGB_jpeg should be processed individually and after step 1 has been completed merge them. See the instructions here.
Regarding the difference in optimisation; to asset it, you will have to check the quality report (see example below). If the camera optimisation is higher than 5% then apply All Prior.
Is it possible to plan a grid flight plan and take both images (RGB/thermal) at the same time and location? I noticed you are using a plane drone from the flight plan so it is possible that you’re not using pix4dcapture… how did you dealt with the flight planning? how are you managing sidelaps and front laps?
Does pix4dcapture support the communication with the two sensors at the same time?
We are planning on buying a FLIR DUO PRO Rl for solar pv inspections.
We are designing our flight plans using a custom script developed in house. But it is quite easy to plan a grid flight plan even in Mission Planner or in ugcs. I think you want to set the Flir sensor to take pictures at every 1 sec or every 5 m (let’s say) and than do the flight independent from triggering the camera.
I am going to order one as well, a FLIR duo pro r, in the next weeks.
Ok so if i understood Gabor, if I want to plan a grid flight plan with defined over/sidelaps for the thermal sensor, triggering both cameras Pix4d capture can’t help me? how would you recommend building these grid flight plans? I am planning on using it on a m600 from dji.
I am also trying to process your latest dataset (thanks) to explore the workflow, but i am having trouble doing what pix4d recommends (merging option), I was capable of merging the two datasets after processing step1 but when i try to process the 3 step it gives an error. Now i and trying to process a second time but doing the step 2 first and only than, what i am interested, in the thermal and rgb ortomosaic (step3).
I’m also trying to process Balint/Gabor’s dataset posted May 1st. However, in the zip archive referenced I only find 1738 _R.JPG images, no RGB at all.
@Pedro: You refer to two datasets processed, where did you find the RGB images?
Hey, From what i tried, the photos are converted by pix4d and it splits the two. check once you add the photos, go to project, Image properties editor.
Cheers
I am ordering one as well, for thermal and rgb ortomosaicking.
Yes, of course, you are right. It’s a little bit like magic.
Which initial processing parameters did you use, anything special or one of the templates Pix4D provides?
Hey, no problem, all i know so far is here. it sais to use a thermal template in the step1. I am lacking information what to do after merging the two, first the report from the merging operation show red sign on calibration. And I am now processing step 2 and 3 but i am only interested in the results from 3. My objective is a thermal ortomosaic and a rgb ortomosaic.
Thanks Pedro for the hint. I will try do “the same”. I’m yielding at exactly the same deliverables, a thermal and a rgb orthomosaic, both properly aligned and georeferenced. More to come.
The setup for step 1 is almost the same, the only difference I see is calibration method (Standard for RGB, Alternative for IR).
I will process the two data sets now, I guess it takes a while since the sets are pretty big.
I found a few error on the sensor width on both sensors the value is wrong. i am processing again from 0. thanks for the new data set. have you been trying to improve overlap and side lap by planning a grid flight plan?
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences,
logging in, or filling in forms. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
They help us to know which pages are the most and least popular and see how visitors move around the site.
All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partner (Google).
They may be used by Google to build a profile of your interests and show you relevant adverts on other sites.
They do not directly store personal information but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.