Error importing flight log

Hello,

I’m running into an error when importing a flight log “The flight log position is not valid for the given coordinate system (error 18004)”.

My coordinate system is set to wgs84, I’ve tried importing my tab delimited .txt file containing “file name, X, Y, Z” using both UTM and lat long without any success.

Does the flight log need X and Y with degrees minutes and seconds signs, decimal degrees, or meters?

Thanks in advance.

Hello,
degrees it should be when using wgs84. If you encounter the error even when having them, there is a high chance the coordinates are wrong.

Hey,

Thanks for the reply. Looks like I had an issue with selecting the project datum. I was able to import the flight log after adjusting that. After importing the flight log, I see that all of my images are georeferenced now, and when I align the images I get some components that are georeferenced and some that are not. Any idea why some of the components would not use the flight log positions?

 

Thanks.

Possibly wrong coordinates provided in these, or simply they were too off after alignment. I believe that if the biggest component is georeferenced, it should be fine. GCPs could also help big time here to put it together, but I don’t know whether you’ve used them.

GCPs won’t be possible unfortunately as it’s a vertical surface without known features. The coordinates shouldn’t be off by more than a meter, which I have chosen in the accuracy section.
When I look at the component that did use the positioning, I can see orange lines coming from each camera. I’m assuming these orange lines show how much the solves camera position varies from the flight log position. Do you know if that’s correct? The strange thing is that the orange lines appear to all come from a straight vertical line, rather than a swaying line (moving slightly in the x and y) like the flight log position should be.

Yes indeed the orange line shows the difference between gps and what the aligned position of the camera is. You may try to fix this by Control points possibly.