Error with geotagging (fixed position defined as geotag)

Bug #1510510 reported by Nicolas DERIVE
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Medium
Bill Filler
Ubuntu UX
Triaged
High
Jouni Helminen
camera-app (Ubuntu)
Fix Released
Medium
Ugo Riboni

Bug Description

When tacking photographs using camera-app, I experience various problems with geotagging. Sometimes I don't get any geotag (picture 1.jpg) and most of the time I got a wrong geocoding, that is always the same, and some place I never went to (2.jpg, 3.jpg are examples of photos with known places to demonstrate that, Versailles castle orangeraie and Eiffel tower in France).

If more info/tests are needed, don't hesitate to ask.

Related branches

Revision history for this message
Nicolas DERIVE (kalon33) wrote :
Revision history for this message
Nicolas DERIVE (kalon33) wrote :
Revision history for this message
Nicolas DERIVE (kalon33) wrote :
Revision history for this message
Nicolas DERIVE (kalon33) wrote :

I experience these problems on a Nexus 4 (mako), configured on ubuntu-touch/stable/bq-aquaris.en. Both OTA-6 and OTA-7 are affected.

Revision history for this message
Bill Filler (bfiller) wrote :

possibly this could be caused by error with location-service returning the incorrect location.
@uriboni
please investigate and assign to location-service if that is the case

Changed in camera-app (Ubuntu):
assignee: nobody → Ugo Riboni (uriboni)
importance: Undecided → High
status: New → Triaged
Changed in canonical-devices-system-image:
milestone: none → ww02-2016
assignee: nobody → Bill Filler (bfiller)
importance: Undecided → High
status: New → Triaged
Changed in camera-app:
status: New → Triaged
importance: Undecided → High
Ugo Riboni (uriboni)
Changed in camera-app (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Ugo Riboni (uriboni) wrote :

I am going to assume that GPS was active in the location settings when the pictures were taken.

One interesting thing about images 2 and 3 is that both seem to have location 48.0000, 2.0000 and the two real locations where the pictures were taken also share the same degrees value (central Paris is 48.8548, 2.3471)

It is possible that in case the sensor has a bad location fix, it returns the best estimate it can get, even if the reading is only good to a hunded kilometers accuracy.

The sensor seems to return the estimated accuracy of the data, but the camera application currently does not check this information and just stores the coordinate reading.

Maybe we should only geotag images if the accuracy of the reading is relatively good (50m-100m perhaps ?)

Bill Filler (bfiller)
no longer affects: camera-app
Changed in canonical-devices-system-image:
status: Triaged → In Progress
Revision history for this message
Ugo Riboni (uriboni) wrote :

@Ubuntu-UX: ideally we want to have on screen an UI element (visible only when geotagging has been requested) which informs the user if the picture is going to be actually geotagged if they shoot right now, or not (due to missing location fix or location fix being too inaccurate).
This way the user can still choose to shoot (and the picture will not be geotagged), or wait until a better fix is available.
Can you please advice if you think this is a good idea, and if you agree how this UI element is going to look like ?

Changed in ubuntu-ux:
status: New → Confirmed
Changed in ubuntu-ux:
status: Confirmed → Triaged
importance: Undecided → High
assignee: nobody → Jouni Helminen (jounihelminen)
Revision history for this message
Jouni Helminen (jounihelminen) wrote :

To me it sounds like issues with location in general, I wouldn't do special casing for camera. If the GPS is enabled from system settings, and geotagging is enabled for the camera, it should Just Work (at least outdoors) .

There have been several complaints on the phone mailing list about the GPS in general, and looks like some issues were fixed in OTA-8, so perhaps try with that again.

 In normal circumstances to get a first time (cold start) GPS-only fix outdoors might take 10 minutes, but getting location after that is much faster. Assisted GPS (A-GPS) is much faster and also works indoors, but I am not sure if we are using that?

I would get location-service people to look at this.

If we wanted to add any UI for displaying whether there is a GPS fix in the camera, I think it shouldn't get in the way of taking pictures - maybe changing the GPS icon to a broken/red GPS icon if GPS is enabled but there is no fix? and then updating the icon to normal GPS enabled icon once a fix has been acquired.

Bill Filler (bfiller)
Changed in canonical-devices-system-image:
milestone: ww02-2016 → backlog
importance: High → Medium
Changed in camera-app (Ubuntu):
importance: High → Medium
Changed in canonical-devices-system-image:
status: In Progress → Confirmed
Changed in camera-app (Ubuntu):
status: In Progress → Confirmed
Changed in camera-app (Ubuntu):
status: Confirmed → Fix Committed
Changed in camera-app (Ubuntu):
status: Fix Committed → Fix Released
Changed in canonical-devices-system-image:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.