Summary: | allow providers to provide extra metadata (e.g. satellite info) | ||
---|---|---|---|
Product: | GeoClue | Reporter: | Stefan Kost <ensonic> |
Component: | General | Assignee: | Geoclue Bugs <geoclue-bugs> |
Status: | RESOLVED WONTFIX | QA Contact: | Geoclue Bugs <geoclue-bugs> |
Severity: | enhancement | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Stefan Kost
2010-09-03 01:27:48 UTC
I wonder if we should support arbitrary metadata, or just admit that people seem to like looking at the raw satellite data and add a SatelliteInfo interface that GPS-based providers can implement. I agree this indeed is a problem. Writing one's own (GNSS based) GeoClue provider is limited to provide positioning related data only, not information about satellites. I'm currently hitting this problem whilst analyzing how to implement QtLocation positioning and satellites parts for MeeGo. As per Ross's comment, I would go for separate interface. Positioning and satellite metadata seem quite loosely coupled, although typically both are used in the same application. Closing all bugs on old geoclue. If your bug still applies to new geoclue, please do re-open, I really don't have time to go through each and every bug and evaluate separately. :( Apologies for any inconvenience caused by this change. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.