GNOME Bugzilla – Bug 548652
[Inconsistency] GST_TAG_LOCATION is used for different meanings.
Last modified: 2008-09-02 06:38:20 UTC
We have GST_TAG_LOCATION, which according to the docs that is: "original location of file as a URI (string)" First we should probably fix plugins that are not using it as such or redefine it. /home/ensonic/projects/gstreamer/gst-plugins-base/gst-libs/gst/tag/gstvorbistag.c LOCATION : Location where track was recorded /home/ensonic/projects/gstreamer/gst-plugins-base/tests/check/libs/tag.c ASSERT_TAG_LIST_HAS_STRING (list, GST_TAG_LOCATION, "Bristol, UK"); I'd like to support location information from EXIF and MP4/3GP tags: In MP4/3GP we have 'loci' udta atom which among other things defines Name String Text of place name Longitude Unsigned int(32) Fixed-point value of the longitude Latitude Unsigned int(32) Fixed-point value of the latitude Altitude Unsigned int(32) Fixed-point value of the altitude AstronomicalBody String Text of astronomical body we could map name to GST_TAG_LOCATION and define GST_TAG_LOCATION_{LONGITUDE,LATITUDE,ALTITUDE} for the GSP location. I think we can live for a while without AstronomicalBody. EXIF has a lot more http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/GPS.html
This definitely needs clarification. Maybe add GST_TAG_GEOLOCATION for strings and GST_TAG_GPS_LOCATION_* for long/lat/alt.
There's also bug #481169 for the geo/gps tags.
2008-09-02 Stefan Kost <ensonic@users.sf.net> * gst-libs/gst/tag/gstvorbistag.c: * tests/check/libs/tag.c: Use new geo location tags from core. Fixes #481169