![]() If not, I'll let you know and give you what I have. Tell me a bit about your computers and workflow and I think it will be a simple thing to integrate your scripts into what I have. I have to do a bit more testing and integrating of the sript with our method. Others probably have better solutions, and I'm looking forward to hear how they would do it. if the script has the image name and the accurate time it sounds straightforward to then match it with the Gps log. I could adjust it to use what you have in your KAPscript instead of the pixhawk log. I use a script in c# or python to change the exif to match the Gps. Sounds like you've already got the timing figured out. A missed picture) then it accounts for it and keeps going instead of failing. Mission Planner's tool does the same, but then if there is a discrepancy between the time of the picture and Gps log (I.e. ![]() In the meantime I take the first image and line them up with the cam messages. The signals would be better from a voltage standpoint but more difficult to hack. In reading the threads concerning the pixhawk integration there are discrepancies between the signals sent to the flash by the different kinds of cameras. Surely the must be a board that will take whatever voltage and send a signal. My thought was I could solder leads to the flash, but the voltage is crazy high (I know because it hurts, haha). I'm using a Sony A5100 for mapping and taking a picture every 0.7 seconds. KAP log file attached in case of any use/interest to anyone. The ideal would be to add the geolocation data to the images using the flight logs and the KAP script log, but any reasonably streamlined way to produce a geolocation file for the images which could then be imported to Pix4d etc. The KAP script, however, is able to log the shutter release time to ~10ms precison, which should be good enough for quite accurate geotagging.Ĭan anyone tell me how to incorporate the accurate time information into a geotagging procedure? Editing the exif data on the images doesn't work as the datetimeoriginal value can only be defined down to a second. Clock on the camera is synced via GPS time. ![]() I've been getting good results, but the accuracy of the geotagging is limited by the 1 second resolution of the timestamps for the images. I've been trying to improve the accuracy of the geotagging of images produced using a Canon S100 running CHDK and the KAP lua script, shutter triggered by Pixhawk via a CamRemote device.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |