General backlog for possible tasks/features in QtLocation – things not necessarily ever committed to but under consideration.
Please add new suggestions via new user stories to Jira and link them against this epic as already done below. Hopefully over time this epic can be transformed into somewhat of a roadmap for QtLcation development. The aim is to have an official release of QtLocation as part of Qt 5.2.
Current considerations which need further discussions and separate Jira details (no particular order of priority yet):
- Short term (up to Qt 5.3)
- Re-enable automated CI runs and fix related auto test in during the process (QTBUG-31797)
- Potential release of Qt Location as part of 5.3 (or possibly a technical preview)
- Update documentation to bring in line with other Qt5 libs (QTBUG-24877)
- Example polishing (QTBUG-24845)
- Android (
- iOS (position engine done, satellite information not available)
- Removal of Qt3D dependency
- Mid to long term
- New platform ports
- Content provider reviews
- There are Nokia and OSM Maps backends which have to be reviewed from a quality and applicability perspective. Does a Nokia plug-in make sense going forward (whats the maintainer situation, Nokia has monetary interest in its REST API users)
- The JsonDB place plug-in provides offline place facilities and as such is not actually providing new information. While JsonDB is unlikely to be a valid storage it could be possible to port it to some other form of storage such as SQL.
- The Nokia Places backend does provides online retrieval and search of place information but has the same issues as the above Nokia Maps backend.
- The OSM plug-in does not implement a place backend. It needs to be investigated whether OSM can provide place information. If it can provide the relevant information new implementation is required.
- The OSM/Mapnik plug-in could potentially utilize offline OSM data. The data is rather large on storage but when split into individual location (e.g. split by country) it is feasible to store map data on the local device (more details http://wiki.openstreetmap.org/wiki/Downloading_data)
- A potential Android port may open up possibilities to provide Google based Map/Place services. This requires further study of Google's T&Cs.