This is the bug tracker for Photo Organizer.
FS#101 - Support GPS tags
Attached to Project:
Photo Organizer
Opened by Solomon Peachy (pizza) - Wednesday, 20 September 2006, 22:14 GMT
Last edited by Solomon Peachy (pizza) - Saturday, 09 June 2007, 15:59 GMT
Opened by Solomon Peachy (pizza) - Wednesday, 20 September 2006, 22:14 GMT
Last edited by Solomon Peachy (pizza) - Saturday, 09 June 2007, 15:59 GMT
|
Details* Tag each image with basic GPS data (latitude, longitude, altitude, speed, and heading) (add to photo_tech; investigate best format?)
* EXIF GPS import code * Photo add, bulk update, photo editing UI & Backend support * XML support for GPS information. (both import and export) As for formats, I'd rather the database use metric units for altitude and speed, heading in degrees (float), and latiude/long as three floating-point numbers (D:M:S). This complicates the database a tad. |
This task depends upon
Closed by Solomon Peachy (pizza)
Saturday, 09 June 2007, 15:59 GMT
Reason for closing: Implemented
Additional comments about closing: r1317
Saturday, 09 June 2007, 15:59 GMT
Reason for closing: Implemented
Additional comments about closing: r1317
On the other hand, knowing which direction we're facing is useful.
The GPS Timestamp is highly useful; should we use it instead of the camera's timestamp?
As for latitude/longitude, a single floating-point number will suffice.
latitude, longitude, altitude, img_direction. FiN.
Todo -- input/output format cooking (eg 90 34' 33" E <==> -90.553112)
XML schema extensions (and import/exprt code)
EXIF code.
Next up -- EXIF and format cooking.
[+-]DDD.ffff (eg -90.331, or 22.999121)
DDD MM.ffff[NSEW] (eg 129 21.3451 E, or 23 00.211 S)
DDD MM'SS"[NSEW] (eg 129 21'22" E, or 23 00'12" S)
We'll be storing all datapoints in terms of the first (eg -19.22112) but I'd prefer we display them using both that and the user-friendly (19 12'21" W) format.
That, and we still need to properly parse the EXIF data to import this stuff.