Uploaded image for project: 'Qt Mobility'
  1. Qt Mobility
  2. QTMOBILITY-313

QGeoPositionInfo::HorizontalAccuracy has incorrect unit/range on Maemo5

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P2: Important
    • 1.0.2
    • 1.0.0
    • Location
    • None
    • N900, Maemo5, libqtm-location 1.0.0-maemo1+0m5
    • 6e752c4f9e9a8dc7b07ab337b2b7110aac36bff8

    Description

      The values returned through QGeoPositionInfo::HorizontalAccuracy on Maemo5 have incorrect unit/range.

      In http://qt.gitorious.org/qt-mobility/qt-mobility/blobs/f0eab1572bdd2d5f0d8546d9e78f43bed3c17922/src/location/liblocationwrapper.cpp#line157, the value of device->fix->eph is copied without modification as the HorizontalAccuracy attribute.

      According to both the /usr/include/location/location-gps-device.h header, and to http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Using_Connectivity_Components/Using_Location_API, the unit of the eph field is centimeters, but the unit of HorizontalAccuracy is meters, according to http://doc.qt.nokia.com/qtmobility-1.0/qgeopositioninfo.html#Attribute-enum.

      This makes the HorizontalAccuracy field close to unusable on Maemo5, unless the user adds specific workarounds, checking for specific versions of Qt Mobility and doing the range conversion if using a buggy version.

      Attachments

        Activity

          People

            dalaing David Laing (closed Nokia identity) (Inactive)
            mstorsjo Martin Storsjö
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: