Loading Profile...
PhotoLocatr shouldn't suck
mattb
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hey mattb,
Sorry about the issue you report--the app assumes the photo-taking session happens in one day and all at one time. The traveling use case certainly isn't handled as well as it could be. I'll see what I can do to alter the logic to better handle this.
-Jeff -
Inappropriate?Sorry to be so harsh in my twitter, I know what it's like to work on a service and have people forget you're a real person behind the (free) code. Thanks very much for responding.
So, I had a really extreme example of how bad this can be. I used your app in Geneva, Switzerland, and then two days later in London UK. When I ran photolocatr to geolocate just a couple of pics that I'd taken in the last few hours, it re-wrote the geo data of the most recent 20 or more pictures (including overwriting data for pictures that already had geodata that I placed by hand). Apparently extrapolating linearly according to time, it spread them in a line over the hundreds of miles between London and Geneva.
The three things that would have helped would be:
a) sanity checks on how far picture timestamps are from GPS datapoint timestamps
b) the chance to choose which pictures get geocoded
c) never overwriting the geodata on a picture that already has it.
oh, and a pony of course.
1 person says
this answers the question
-
Inappropriate?No, don't worry about it--I agree. I'll make those fixes--I think those are totally reasonable.
Thanks for your input!
-Jeff
I’m going back to the code
1 person says
this answers the question
-
-
