Has anyone played with creating a camera settings parameters file for use in react captured with an H20 / H20T (wide angle)?
One of the issues that I know you will encounter is that when taking a picture with the H20 series the files that are created in the DCIM folder on the SD card will produce [file name]_W.jpg (where the “_W” signifying wide angle) [file name]_Z.jpg (zoom), and [file name]_T (thermal). So you will have to manually pull out just the picture set that you want to stich together (a tip for this would be to use the “" placeholder and then the _W to show JUST the files that where created by the wide angle zoom - so in the search bar inside of the folder containing the sets of images type "_W” select all the shown files, copy, and paste them into a new folder and you’ve got your data set to import easily!)
We are tasked with creating orthos often and not having a fully supported fleet that works with React just caused us some issues, so I would love to get a parameters file to allow auto importing and support with the H20 series of cameras (wide, zoom, or thermal - any and all would be great).
We would like to add as many cameras as possible to our database; this is not yet there. We need some good datasets to test and calibrate before adding them. If you would like to share some datasets with us, please contact us to support.
Thermal would not work at the moment; if you need to process thermal images, please contact us and share how thermal imagery would help you in your projects. It is very important for us to understand your needs.
So your file was working perfectly until the most recent update. Now we are only able to get 3 or 4 pictures to properly show after completing the processing. I have tried on at least 4 data sets now using the same technique we were before with no luck.
Were there some behind the scenes updates that took place? Is there a new camera file that we should be using instead of the linked one?
On a separate computer (new desktop image) I reinstalled React as well as downloaded and installed the xml parameters file again. Using an old data set which had previously worked, I attempted to recreate the ortho using the same settings and was unable to properly recreate it.
3 maybe 4 images are placed on the overlay, the processing script appears to run through… something… and then the final ortho and overlay is shown with just the 3 or 4 images properly(?) placed ontop of the ortho.
Thank you in advance for looking into this, I recently attended a UAS Symposium in Florida and in showcasing your ortho solution sold several copies of your software to LEO partners across the state.
Hi Fernanda!
the file works great!. Now, the H20T generates a Radiometric Thermal imagery that Pix4D fields and react dont understand radiometrically, just as a jpg pic. Do you have a way to process them?!
I am adding 3 examples
Thanks a lot!!
Unfortunately PIX4Dfields will only deliver jpg orhomosaic.
There is a workaround for H20T camera that is mentioned on this video, using our product PIX4Dmapper, with a conversion first… DJI H20T in Pix4Dmapper - ATygeo Thermal integration - YouTube
Can someone share a tutorial on how to process the ZH20 DJI thermal data in Pix4D? I am unable to process the acquired data (ZH20). I have files with name_T.jpg, name_W.jpg, name_Z.jpg. I shall be grateful for your support.
Hello @mudassar_bzu, The Zenmuse H20T has multiple sensors such as an Infrared thermal camera, Zoom camera, wide camera and Laser Rangefinder. So, if you want to process the thermal images, you have to first open it and figure out which is thermal images(it should be simple because you can easily identify the difference in RGB and thermal images by looking at them) and then copy those images to a new folder and process it on the Pix4Dmapper. For more information on creating a new project in Pix4Dmapper, follow the below steps,
I do know the _T.JPG is thermal and all the other stuff. But when i process the _T.Jpg in pix4D it give me error fail in writing tie point matching? and process fail to complete. Please see below figure
Hello, The reason it might be failing at step 1 would be, either bad images, a wrong processing option, or the wrong camera parameter detected by the software. So, I would suggest you to follow the below support article step by step and you should be able to process it. Please make sure to follow every step under Guidelines for Troubleshooting and see if that helps to solve your issue.
Hello, has this compatibility issue been resolved?
I am a firefighter and we regularly use Pix4React with the M30T for operational night mapping. We are equipped with M300 and H20N and we would like to be able to use this lens for the same type of use. Going through a pix4mapper is of little interest to us given the orthophoto generation times. Likewise, investing in a pix4mapper license just to make conversions seems quite expensive and counterproductive to me. Do you have other solutions compatible with the operational timing of our missions that would allow us to process our thermal images before integrating them into pix4react?
The observation of this lack of compatibility seems to date back to 2021. Have you worked and made progress on this problem? Is this a priority and will pix4react remain incompatible with the H20N or M3T?
Hello,
Indeed, the H20N sensor is not listed among the compatible sensors. The H20T, M30 and M3 are compatible, which we have already tested in the field.
However, for the H20N, this is not the case. Using the configuration file dedicated to the unlisted camera leaves me with the message:
Your camera is not supported at the moment.
I found this solution on your site:
To process these images correctly using Pix4D’s software, a workaround is to use third-party software to convert the rjpeg images into TIFF files with temperature information before processing them with PIX4D’s software. For more information: Thermal images convertion.
Do you have a specific configuration file for the H20N? Can we create this kind of file?
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.
