Upload Wizard currently inserts the altitude information from the EXIF metadata, incorrectly, as the third parameter into the {{Location dec}} template. It looks like the template doesn't support altitude information at all.
We're inclined to remove it altogether unless there are good reasons to keep it and a proper way to include it. Thoughts? There's no reference to altitude info on https://commons.wikimedia.org/wiki/Commons:Geocoding
Erik
-- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
Er, why don't we fix the template or just "park" the altitude as an advisory string within the template?
Introducing elements of 3D to maps are not science fiction, and one can imagine over the next couple of years far more cameras will have accurate altitude data that would be quite handy for detailed mapping. Particularly where the height of the camera would benefit automatic creation of stitched models from multiple photographs.
Fae
The GPS-attitude from cameras has such an high noise level and is in some cases completely wrong so that it's IMO not useful. This is also the reason why the openstreetmap project collect these data.
For me more important is the heading parameter, we have an usage of that on para's map and some cameras/smartphones has an compass, for all other cameras it would be nice if an user can add this parameter on the map with upload-wizzard.
Greetings Kolossos
Am 03.06.2012 11:19, schrieb Fae:
Er, why don't we fix the template or just "park" the altitude as an advisory string within the template?
Introducing elements of 3D to maps are not science fiction, and one can imagine over the next couple of years far more cameras will have accurate altitude data that would be quite handy for detailed mapping. Particularly where the height of the camera would benefit automatic creation of stitched models from multiple photographs.
Fae
On 3 June 2012 12:45, Kolossos tim.alder@s2002.tu-chemnitz.de wrote:
The GPS-attitude from cameras has such an high noise level and is in some cases completely wrong so that it's IMO not useful. This is also the reason why the openstreetmap project collect these data.
For me more important is the heading parameter, we have an usage of that on para's map and some cameras/smartphones has an compass, for all other cameras it would be nice if an user can add this parameter on the map with upload-wizzard.
Greetings Kolossos
I agree, noise and also lag are a big issue (my camera often adds old GPS data to new photos before the GPS has had time to update itself, which can take several minutes from switching on). However we should consider design and metadata coping for future cameras with better accuracy. Perhaps on batch upload a user can have some options to ignore parts of the EXIF data that may be inaccurate or might be felt to be invading their privacy.
As an example of the heading data, my photo here http://commons.wikimedia.org/wiki/File:Shop_window_with_mini_couture_mannequin.jpg has compass data unused in the EXIF (from a Sony HXV5). I always find the altitude data fails to be correctly interpreted (I have to delete what I think is the direction in degrees from the altitude string). It may be that the system might benefit from partially parsing with a bit more intelligence based on knowing the camera model rather than assuming standardization that may not be pragmatic. This may be especially useful in adding some estimate of camera accuracy for EXIF GPS information.
Fae
Is this focusing on the wrong data sources, I know the phones do provide the information but the better quality DLSRs dont would this then cause end users focus away from the quality images. or encourage a dumbing down of quality to provide the details
On 3 June 2012 20:13, Fae faenwp@gmail.com wrote:
On 3 June 2012 12:45, Kolossos tim.alder@s2002.tu-chemnitz.de wrote:
The GPS-attitude from cameras has such an high noise level and is in some cases completely wrong so that it's IMO not useful. This is also the
reason
why the openstreetmap project collect these data.
For me more important is the heading parameter, we have an usage of that
on
para's map and some cameras/smartphones has an compass, for all other cameras it would be nice if an user can add this parameter on the map
with
upload-wizzard.
Greetings Kolossos
I agree, noise and also lag are a big issue (my camera often adds old GPS data to new photos before the GPS has had time to update itself, which can take several minutes from switching on). However we should consider design and metadata coping for future cameras with better accuracy. Perhaps on batch upload a user can have some options to ignore parts of the EXIF data that may be inaccurate or might be felt to be invading their privacy.
As an example of the heading data, my photo here < http://commons.wikimedia.org/wiki/File:Shop_window_with_mini_couture_mannequ...
has compass data unused in the EXIF (from a Sony HXV5). I always find the altitude data fails to be correctly interpreted (I have to delete what I think is the direction in degrees from the altitude string). It may be that the system might benefit from partially parsing with a bit more intelligence based on knowing the camera model rather than assuming standardization that may not be pragmatic. This may be especially useful in adding some estimate of camera accuracy for EXIF GPS information.
Fae
Commons-l mailing list Commons-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/commons-l
There is a parameter for altitude, just like for heading. The format is alt:xxxx
Example: {{Location|42|15.75|0|N|42|39.56|0|E|alt:153_source:exif_heading:122.141343}}
The GPS-attitude from cameras has such an high noise level and is in some cases completely wrong so that it's IMO not useful. This is also the
If we completely ignore altitude data then we just discourage users that do provide the data. It might be worthwhile to compile a statistics of altitude values (which percentage does provide them, histogram of values etc.)
I have been running a bot that extracts GPS EXIF data from files and adds the Location templates, so I would have access to such data. Looks like that bot can be retired once everybody uses the new upload wizzard.
For me more important is the heading parameter, we have an usage of that on para's map
and the Wikiminiatlas of course
On Sun, Jun 3, 2012 at 3:35 PM, Daniel Schwen lists@schwen.de wrote:
Example: {{Location|42|15.75|0|N|42|39.56|0|E|alt:153_source:exif_heading:122.141343}}
OK, we can easily fix the current format if that's preferred over throwing away the altitude data.
Am 03.06.2012 16:04, schrieb Erik Moeller:
On Sun, Jun 3, 2012 at 3:35 PM, Daniel Schwen lists-SYvMc73jUx+zQB+pC5nmwQ@public.gmane.org wrote:
Example: {{Location|42|15.75|0|N|42|39.56|0|E|alt:153_source:exif_heading:122.141343}}
OK, we can easily fix the current format if that's preferred over throwing away the altitude data.
If alitude will be kept it would be good to fix https://bugzilla.wikimedia.org/show_bug.cgi?id=32410 (MediaWiki api doesn't serve EXIF GPSAltitude (and other tags) as decimals)
It's annoying to get errors in the UW for altitudes like "57/1" Thanks :-)
Raimond.