Details
-
Epic
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
Location & Positioning Backlog
Description
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):
- Qt 5.3
- Update documentation to bring in line with other Qt5 libs (
QTBUG-24877) - Android port for QtPositioning (
QTBUG-34102) - iOS port for QtPositoning (position engine done, satellite information not available)
- QtLocation QML API frozen from Qt 5.3 onwards
- Update documentation to bring in line with other Qt5 libs (
- Qt 5.4
- Re-enable automated CI runs and fix related auto test in during the process (
QTBUG-31797) - Removal of Qt3D dependency from QtLocation (done)
- Example polishing (QTBUG-24845)
- New platform ports for QtPositioning
- WinRT Port (
QTBUG-37778)
- WinRT Port (
- Re-enable automated CI runs and fix related auto test in during the process (
- Qt 5.5
- Technology Preview for Qt Location
- Place backend for OSM plug-in (done)
- Qt 5.6
- First committed API release & plenty of bug fixes
- Qt 5.7
- Mostly just bug fixes
- Qt 5.8
- Add support for custom tile sources (
QTBUG-46650) - Offline map tiles support in QtLocation (
QTBUG-45732)
- Add support for custom tile sources (
- Qt 5.9
- Tile layers (
QTBUG-49475) - External map renderer (
QTBUG-53851) - External map item rendering (
QTBUG-53852) - Improved Tile caching API to support customizations (
QTBUG-46970) - Map Tilt/Rotation support (
QTBUG-56473,QTBUG-40774) - Add overzoom support (aka tile blending) to the stock renderer (
QTBUG-23659) - Cache mercator projection of qgeocoordinates
- Vector-based map rendering (via 3rdparty mapbox-gl-native library)
- Add fitViewportToVisibleMapItems to only consider visible items when fitting the viewport (
QTBUG-57912) - Add MapItemGroup, to combine multiple map items in a separate qml file (
QTBUG-55211) - Add MapParameter, to expose and control plugin-specific functionalities at runtime
- Tile layers (
- Qt 5.10
- Add QGeoPolygon, and use it also in Map.visibleRegion, to return the correct polygon also on rotated/tilted maps
- Use clipper to implement ::contains()
- Change the current tile-based providers to always support the full range of zoom levels by enabling overzoom
- Add QGeoPolygon, and use it also in Map.visibleRegion, to return the correct polygon also on rotated/tilted maps
- Mid to long term
- Improve performance of map item rendering (QTBUG-25728)
- Possibly offload the rest to glsl on those platforms supporting double precision fp
- With this, also skip the clipping, as opengl knows how to deal with stuff behind the camera
- Possibly offload the rest to glsl on those platforms supporting double precision fp
- Add better 3D map items support
- Add 3D content rendering support
- Support first fragment translucency (possibly in 2 passes)
- Including MouseArea support
- Perform data provisioning in a separate thread
- Including mipmap generation
- Possibly also texture uploading
- Add support to burn map items into tiles
- Support additional cylindrical projections
- Support non-cylindrical projections
- Support globe rendering
- Support terrain rendering
- Content provider reviews
- Evaluate adding a geoservice provider plugin, based on OSM data, for offline places, geocoding and routing, using the one or the other 3rd party library.
- Evaluate using a 3rd party library to allow usage of offline vector data (not just raster) and rasterize it to tile on demand (e.g., libosmscout, or others)
- 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/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) (
QTBUG-45284)
- New platform ports for QtPositioning
- Win Desktop positioning plugin (
QTBUG-48082)
- Win Desktop positioning plugin (
- Improve performance of map item rendering (QTBUG-25728)
- Qt6 (breaking changes)
- MapType rework
- Plugin should be split, to separate the discovery functionalities from an API for the actual attached instance
- All public c++ classes should have at least a virtual destructor
Attachments
Issue Links
- relates to
-
QTBUG-72239 Qt Location changes in Qt6
- Open
-
QTBUG-20865 Map types and modes of map plugin
- Open
-
QTBUG-19937 Cannot pass address into RouteQuery element
- Open
-
QTBUG-34102 Android port for QtPositioning
- Closed
-
QTBUG-31797 tst_declarative_ui fails in CI
- Closed
-
QTBUG-31798 tst_declarative_core fails in CI
- Closed
-
QTBUG-23659 Smooth transition between zoom levels and panning by approximating previously cached textures at other levels
- Closed
-
QTBUG-24414 Profile the memory consumption of the Places API and identify possible optimisations.
- Open
-
QTBUG-24415 Profile the memory consumption of the Maps/Navigation API and identify possible optimisations.
- Open
-
QTBUG-24614 Error dialogs for places qml example (possible error handling API tweaking)
- Open
-
QTBUG-37778 Implement Qt Geopositioning for WinRT
- Closed
-
QTBUG-31741 Remove all JsonDB dependencies from QtLocation
- Closed
-
QTBUG-48082 Positioning backend for Windows
- Closed
-
QTBUG-25728 Map item geometry should be approximated during zoom
- Reported
-
QTBUG-24888 No QML API to query for the set of supported routing features
- Open
-
QTBUG-24998 Add ability to search multiple categories (in Places app)
- Open
-
QTBUG-25080 Performance system test application
- Open
-
QTBUG-19975 QLocale set set measurement system
- Open
-
QTBUG-20545 QML: MapRoute element doesn't have property for node's images
- Open
-
QTBUG-23415 Map datelines and wrapping
- Open
-
QTBUG-23420 Plugin properties on Map etc should be writeable more than once
- Open
-
QTBUG-24069 Make QPlaceContent extendable by third parties
- Open
-
QTBUG-24845 Example polishing
- Open
-
QTBUG-25971 Batch saving of places
- Open
-
QTBUG-26778 Import Places functionality
- Open
-
QTBUG-23492 Unit tests for Places QML elements
- Open
-
QTBUG-23535 Category Model to return model index for a given category (id)
- Open
-
QTBUG-23859 Optimize coordinateToScreenPosition and similar transforms
- Open
-
QTBUG-25779 Create sequencer application to replay user input into maps
- Open
-
QTBUG-26779 Make QPlaceAttribute Extendable
- Open
-
QTBUG-23171 The map item coordinates should be able to be animated.
- Closed
-
QTBUG-24874 Places search results can include another search query (explore mode)
- Closed
-
QTBUG-24877 Documentation polishing
- Closed
-
QTBUG-32937 Consider adding tile server url(s) as parameter for OSM mapping plugin
- Closed
-
QTBUG-45284 OSM offline plugin
- Closed
-
QTBUG-23744 The QML Position type should expose the equivalent QGeoPositionInfo in the C++ API
- Closed
-
QTBUG-23746 Port all examples to use Qt Quick Controls
- Closed
-
QTBUG-27015 Geoservices plugins should be responsible for rendering the map and map objects
- Closed
-
QTBUG-31590 Nokia backend related backlog
- Withdrawn
-
QTBUG-26771 Complete JsonDb Plugin
- Withdrawn
-
QTBUG-26776 Support User Authentication
- Withdrawn