![]() In fact the offset I need is the opposite: -1 hour and +12 minutes! But if I enter this camera time into the PSU offset dialogue, it gives me an offset of +1hour and -12 minutes. So at 14:00 local time, my camera reads 13:12. On top of which my camera clock is 12 minutes fast. Right now my camera clock is set to GMT, but we are in British Summer Time, i.e. ![]() ![]() The geotag functions in PSU have had many bugs in the past - see my entries in Mantis for some of them - and I think there are still bugs. Not to mention that the clock drift on my cameras is something awful, and I can only guess at how far it was out for a picture I took two months ago! All horribly confusing This can be confusing if you are processing in a DST period but the pictures were taken outside a DST period or vice versa. And then when you process them with PSU some time later, you may or may not be in a DST period and notwithstanding what Mke says about PSU working in UTC the offset dialogue shows the computer time including any DST offset (being in the UK I can't tell if it includes time zone offsets too). For example: your camera time may have included DST offset when some images were taken but not when others were taken to complicate this further the former may include shots taken when DST was not in force - if you forgot to set the camera back - and the latter may include ones taken when DST was in force. This gives 4 different possibilities for the camera setting alone, then multiply this by the offset to where and when you are when processing the images with PSU. correct local time for the time zone) and daylight saving times. including or not including either or both of local time (i.e. I doubt your results are random per se, but perhaps the images have a mixture of different camera time settings. Having said that I wouldn't put it past some apps to disregard the spec but if in doubt simply open the file with a text editor like notepad and check (GPX being a human-readable format, it's basically XML). (NB There is a bug with reverse geotagging which is discussed on another thread and has an easy workround.)Īs Mke says the GPX file should contain UTC, it's explicit in the GPX format specification. Mke's excellent advice should set you on your way. Once you have figured out the correct time offset - which I agree can be challenging - it works fine. When you say "in batch" I assume you mean using batch processing or using the Geotag panel and selecting >1 image. I have not encountered any issues, so I'm pretty confident it works (but see later). So for your photos from Indonesia, you'll need to make a manual adjustment of between 6 and 9 hours, depending on the time zone you were in. If you click on the track's date-time in PSU, a dialog box is displayed allowing you to adjust the time - however having read this post you'll see that the explanation it gives for its necessity is misleading (I guess I should file an enhancement request in Mantis). PSU doesn't make any automatic adjustment - it just uses the raw UTC value, so it's up to you to make a manual adjustment.Google Earth adjusts my last trip to shows the time as UTC + 1 hour (I guess they're choosing to omit the Daylight Saving Time adjustment - strange). ![]() On my Android device, I use GPX Viewer to view my tracks, and that automatically displays the correct local time, with a note showing the adjustment made (UTC +2 hours on my last trip). ![]() It's then up to the software you use to calculate the local time (or not). I imagine that it uses the latitude, longitude and GPS signal to calculate the UTC, rather than calculating back from the potentially inaccurate time on your smartphone/GPX recording device. That's always the case, irrespective of your location or the time settings on your camera. Well I don't have problems tagging in batches myself, however I have just (again) got tangled up with the time offset myself, so I can provide some information on that part.Īll GPX files record times in 'Coordinated Universal Time' (UTC) - equivalent for most purposes to Greenwich Mean Time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |