View Issue Details

IDProjectCategoryView StatusLast Update
0000699GeoSetterUser Interfacepublic2011-01-08 16:22
Reporterevert Assigned ToFriedemann  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Product Version3.3.60 Release 
Target VersionFixed in Version3.3.101 beta 
Summary0000699: Feature request: Option to only use positions in the past
DescriptionThis follows on from issue 698 and is a feature request.

As I described in Issue 698, using points in the past is 100% accurate, because my GPS only records new points when I move, but using points in the future is uncertain. I want my geotagging to be as accurate as possible and thus don't want to use points in the future.

My feature request is this:

On the "Synchronize with GPS Data Files" screen, there are currently two options for "Assignment of Found Positions". I would like a third option: "Assign only to a track point before the shoot time".

What it must do is the same as option "Assign Exactly to Found Position", but it must only consider track points earlier than the shoot time that fall within the Maximum Time Difference.

Additional InformationI've looked at quite a few geotagging programs and Geosetter is so far the best one that I found - the built in map and image preview is great. This feature would make it even better for me.

I'm working on a website that is likely to have a large number of users who'll all need geotagging software and I want to add a link to Geosetter.
TagsNo tags attached.


related to 0000698 resolvedFriedemann Time Difference always shown as positive number 


2011-01-08 16:21


Issue History

Date Modified Username Field Change
2010-12-21 14:17 evert New Issue
2010-12-24 00:10 Friedemann Status new => assigned
2010-12-24 00:10 Friedemann Assigned To => Friedemann
2011-01-08 16:21 Friedemann File Added: do_no_use_future_trackpoints.jpg
2011-01-08 16:21 Friedemann Status assigned => resolved
2011-01-08 16:21 Friedemann Fixed in Version => 3.4.51 beta
2011-01-08 16:21 Friedemann Resolution open => fixed
2011-01-08 16:22 Friedemann Relationship added duplicate of 0000698
2011-01-08 16:22 Friedemann Relationship deleted 0000698
2011-01-08 16:22 Friedemann Relationship added related to 0000698