Showing content from https://github.com/nemethviktor/GeoTagNinja/issues/114 below:
Export to GPX track file aka inverse geotagging · Issue #114 · nemethviktor/GeoTagNinja · GitHub
Request summary
It would be very useful to be able to generate a GPX track file built from the gps data of existing geotagged images. In geosetter this is the Export to GPX Track File option. In exiftool it is referred to as Inverse Geotagging
Why this feature is helpful
It is not uncommon to capture geotagged photos on a phone alongside photos on a camera without GPS. For example when travelling I'll often use my phone for capturing mundane moments or for quick sharing online, but will use my camera when the situation calls for better photography. Constructing a GPS track file from the phone images is a simple way to correlate locations as often images will be captured on both devices at the same time and place. This is a reliable solution when when you haven't captured a more detailed GPS track through other means.
It is possible to create a similar GPS track using google timeline data, however this is more convoluted and less clean than using data from a selected set of images.
Example solution workflow
The workflow in geosetter works well, with a couple of possible areas for improvement.
- Navigate to and select the images that contain the location data that you want to extract
- Select the Export to GPX Track File option
- In the prompting dialog, choose some options for the file (more on these options below), and the file name and location to save to
- A track is built and saved using the locations from only the images that were selected
Options and considerations
- Field Selection: Being able to choose which metadata fields are extracted and written to the GPX file would be very useful. For example, if the GPS date/time field exists than it is the logical choice to use for the date/time stamps, however this field does not always have data. HEIC images captured on common android devices for example don't populate this field, so you would need to be able to use a different field such as the Date/Time Original or the Date Created. Choosing whether to include altitude or not is another option that could be useful.
- Time offset: Relating to the previous point, the date/time stamps may or may not be in UTC time, which is required in the GPX file. This option would allow you to correct for timezones or incorrect clocks by adding or subtracting time from the chosen field before writing to the GPX. This is essential when the image doesn't contain GPS date/time data. (it is of course also possible to account for time offsets when importing a GPS track, but having correct data in the original track file is preferable!)
- Data Sort/Order: Rather than use the order the images are shown in the file browser, it would be useful to explicitly select the order the data points are arranged in. By default, using the GPS date/time field would be the most logical option, however there are situations where you may want to select another field to sort. You may want to sort by file name, or if multiple image sources or inconsistent names exist, sorting by date taken may be a better option.
Thanks for your work in creating this amazing tool, it's really been a massive help for me. Geosetter does not support HEIC images, which unfortunately are what most of my phone images are from the last 4 years. GeoTag Ninja has been a lifesaver, I've been using exiftool instead to create GPS tracks but if the function existed in GTN it would save me so much hassle and time!
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4
