[closed] GPX Bug? - Geotagging with track recording
Posted: Mon Jun 28, 2010 1:22 pm
Hi!
Yesterday I came back from my vacation in Rhodos where I actually used AlpineQuest the first time.
I tried to tag my photos with a recorded track and had two issues:
First, my photo management tool, digiKam (Linux), had problems to process the gpx file until I changed following:
with:
Seems that digiKam is a little bit pedantic about the order in the xml prolog.
The second was, that digiKam could not find positions for some photos. I recognized that these are photos where I've not moved for a while, so I guess that AlpineQuest only makes track points when the phone is moving.
That's not so good for geotagging because the correlator tries to find a track point for the timestamp of the photo in the gpx file, and when there is no point for a longer period it can't tag the photo. I guess the most correlators would have a problem with that, not only digiKam.
So I suggest a fine tuning for the track recorder with three parameters: time (seconds), distance (meters) and course (degrees).
Every x seconds OR after y meters OR after a change of course for z degrees, the tracker should create a track point.
Apart from that I really like this app! My compliments to the programmer!
Best regards
Norbert
Yesterday I came back from my vacation in Rhodos where I actually used AlpineQuest the first time.
I tried to tag my photos with a recorded track and had two issues:
First, my photo management tool, digiKam (Linux), had problems to process the gpx file until I changed following:
Code: Select all
<?xml encoding="UTF-8" version="1.0"?>Code: Select all
<?xml version="1.0" encoding="UTF-8"?>The second was, that digiKam could not find positions for some photos. I recognized that these are photos where I've not moved for a while, so I guess that AlpineQuest only makes track points when the phone is moving.
That's not so good for geotagging because the correlator tries to find a track point for the timestamp of the photo in the gpx file, and when there is no point for a longer period it can't tag the photo. I guess the most correlators would have a problem with that, not only digiKam.
So I suggest a fine tuning for the track recorder with three parameters: time (seconds), distance (meters) and course (degrees).
Every x seconds OR after y meters OR after a change of course for z degrees, the tracker should create a track point.
Apart from that I really like this app! My compliments to the programmer!
Best regards
Norbert