Trimble Business Center

Hello. I am using the latest TBC and trying to ppk process some DJI L2 missions. I get a 100 fixed 0-5 cm solution. What I am not sure of is whether the results refer to the camera photo center or to the antenna phase center. I have significant differences in the results compared with the rtk solution's coordinates. EG, take a look at two screenshots, one from the TBC ppk solution and one from an image properties (I was rtk fix when I was captured)

These coords will always be slightly different. Also, you should be using DJI terra to perform the PPK. If a RTK mission, you still need to calculate the POS, ensure the base station coords are correct and then process. The goals is to bring in the processed las files and ortho from Terra into TBC. There is no need to rerun photogrammetry in TBC. 

Hello. I am using the latest TBC and trying to ppk process some DJI L2 missions. I get a 100 fixed 0-5 cm solution. What I am not sure of is whether the results refer to the camera photo center or to the antenna phase center. I have significant differences in the results compared with the rtk solution's coordinates. EG, take a look at two screenshots, one from the TBC ppk solution and one from an image properties (I was rtk fix when I was captured)

I am curious as to the advantages you find in using DJI Terra over TBC for processing the PPK. I can't compare the two as my experience with processing PPK is limited to TBC as I don't have Terra. I did try their 30-day demo, but it wasn't compelling enough to spend the extra $2000 per year for the subscription.

Since our survey control, our R12i base station and local ground coordinate system are already in TBC's ecosystem, the whole process flows with minimal effort using the Photogrammetry package. The results have been consistently good. Sometimes I use TBC to process the PPK, but then use those coordinates in Metashape to do the photo stitching and deliverables. Still, I'm always open to exploring other workflows.

These coords will always be slightly different. Also, you should be using DJI terra to perform the PPK. If a RTK mission, you still need to calculate the POS, ensure the base station coords are correct and then process. The goals is to bring in the processed las files and ortho from Terra into TBC. There is no need to rerun photogrammetry in TBC. 

Hello. I am using the latest TBC and trying to ppk process some DJI L2 missions. I get a 100 fixed 0-5 cm solution. What I am not sure of is whether the results refer to the camera photo center or to the antenna phase center. I have significant differences in the results compared with the rtk solution's coordinates. EG, take a look at two screenshots, one from the TBC ppk solution and one from an image properties (I was rtk fix when I was captured)

DJI Terra is free when using with L2 payload data. They quit charging for point cloud processing on the L1/L2 for nearly 2 years at this point. How are you getting the raw lidar data into TBC, as it's proprietary to DJI? If you are simply taking the images into TBC, then you are throwing away your L2 lidar sensor data completely. At that point, you might as well use a M3E for far less $$$. As I understand it, you cannot bring the .LDR, LDRT, etc. files into TBC or anything other than a DJI software. Perhaps you are using a payload with a RGB sensor only and not the L2?

I am curious as to the advantages you find in using DJI Terra over TBC for processing the PPK. I can't compare the two as my experience with processing PPK is limited to TBC as I don't have Terra. I did try their 30-day demo, but it wasn't compelling enough to spend the extra $2000 per year for the subscription.

Since our survey control, our R12i base station and local ground coordinate system are already in TBC's ecosystem, the whole process flows with minimal effort using the Photogrammetry package. The results have been consistently good. Sometimes I use TBC to process the PPK, but then use those coordinates in Metashape to do the photo stitching and deliverables. Still, I'm always open to exploring other workflows.

These coords will always be slightly different. Also, you should be using DJI terra to perform the PPK. If a RTK mission, you still need to calculate the POS, ensure the base station coords are correct and then process. The goals is to bring in the processed las files and ortho from Terra into TBC. There is no need to rerun photogrammetry in TBC. 

Hello. I am using the latest TBC and trying to ppk process some DJI L2 missions. I get a 100 fixed 0-5 cm solution. What I am not sure of is whether the results refer to the camera photo center or to the antenna phase center. I have significant differences in the results compared with the rtk solution's coordinates. EG, take a look at two screenshots, one from the TBC ppk solution and one from an image properties (I was rtk fix when I was captured)

DJI Terra is free when using with L2 payload data. They quit charging for point cloud processing on the L1/L2 for nearly 2 years at this point. How are you getting the raw lidar data into TBC, as it's proprietary to DJI? If you are simply taking the images into TBC, then you are throwing away your L2 lidar sensor data completely. At that point, you might as well use a M3E for far less $$$. As I understand it, you cannot bring the .LDR, LDRT, etc. files into TBC or anything other than a DJI software. Perhaps you are using a payload with a RGB sensor only and not the L2?

I am curious as to the advantages you find in using DJI Terra over TBC for processing the PPK. I can't compare the two as my experience with processing PPK is limited to TBC as I don't have Terra. I did try their 30-day demo, but it wasn't compelling enough to spend the extra $2000 per year for the subscription.

Since our survey control, our R12i base station and local ground coordinate system are already in TBC's ecosystem, the whole process flows with minimal effort using the Photogrammetry package. The results have been consistently good. Sometimes I use TBC to process the PPK, but then use those coordinates in Metashape to do the photo stitching and deliverables. Still, I'm always open to exploring other workflows.

These coords will always be slightly different. Also, you should be using DJI terra to perform the PPK. If a RTK mission, you still need to calculate the POS, ensure the base station coords are correct and then process. The goals is to bring in the processed las files and ortho from Terra into TBC. There is no need to rerun photogrammetry in TBC. 

Hello. I am using the latest TBC and trying to ppk process some DJI L2 missions. I get a 100 fixed 0-5 cm solution. What I am not sure of is whether the results refer to the camera photo center or to the antenna phase center. I have significant differences in the results compared with the rtk solution's coordinates. EG, take a look at two screenshots, one from the TBC ppk solution and one from an image properties (I was rtk fix when I was captured)

Maybe I wasn't clear, but I didn't want to process lidar data in TBC. I am done with DJI Terra. What I want is to process the ppk and get photo coordinates so I can process them in AgiSoft Metashape. DJI Terra photogrammetry is not free. Only lidar. And yes, you can also export an Ortho from there, but without any control. TBC supports the L2 Sensor for photogrammetry PPK. Like it does with Mavic. It reads all the files. What I am not sure of is whether it applies corrections from the DJI antenna to the DJI camera center.

DJI Terra is free when using with L2 payload data. They quit charging for point cloud processing on the L1/L2 for nearly 2 years at this point. How are you getting the raw lidar data into TBC, as it's proprietary to DJI? If you are simply taking the images into TBC, then you are throwing away your L2 lidar sensor data completely. At that point, you might as well use a M3E for far less $$$. As I understand it, you cannot bring the .LDR, LDRT, etc. files into TBC or anything other than a DJI software. Perhaps you are using a payload with a RGB sensor only and not the L2?

I am curious as to the advantages you find in using DJI Terra over TBC for processing the PPK. I can't compare the two as my experience with processing PPK is limited to TBC as I don't have Terra. I did try their 30-day demo, but it wasn't compelling enough to spend the extra $2000 per year for the subscription.

Since our survey control, our R12i base station and local ground coordinate system are already in TBC's ecosystem, the whole process flows with minimal effort using the Photogrammetry package. The results have been consistently good. Sometimes I use TBC to process the PPK, but then use those coordinates in Metashape to do the photo stitching and deliverables. Still, I'm always open to exploring other workflows.

These coords will always be slightly different. Also, you should be using DJI terra to perform the PPK. If a RTK mission, you still need to calculate the POS, ensure the base station coords are correct and then process. The goals is to bring in the processed las files and ortho from Terra into TBC. There is no need to rerun photogrammetry in TBC. 

Hello. I am using the latest TBC and trying to ppk process some DJI L2 missions. I get a 100 fixed 0-5 cm solution. What I am not sure of is whether the results refer to the camera photo center or to the antenna phase center. I have significant differences in the results compared with the rtk solution's coordinates. EG, take a look at two screenshots, one from the TBC ppk solution and one from an image properties (I was rtk fix when I was captured)