Qt Mobility Tech Preview - Maps and Navigation API
Welcome to the Maps and Navigation API forum on DevNet.
The Maps and Navigation API is among the most recent being developed under the Qt Mobility program. It allows developers access to mapping, routing and geocoding services via a cross-platform API, and comes with a plugin which can be used to access the corresponding Nokia services. Our intent is to share our work in progress with you and listen to your comments on this forum in order that we strive to build the best possible solution.
Today’s release shares our “Technology Preview” package of the new APIs planned for the Qt Mobility 1.1.0 release, including the Maps and Navigation API. Qt Labs will still be used to communicate the availability of new packages, but DevNet is where you will have the opportunity to review and comment on the API, and share information with other developers about the API.
The Maps and Navigation API is still under active revision and development so feel free to provide any feedback or comments you feel will help improve the API or to ask about the directions we’ll be taking the API between now and the final release.
Welcome to the forum, we look forward to your comments and contributions in the development of the new Qt Mobility Maps and Navigation API.
Qt Development Team.
Is there a type with the QGeoSearchManager on this page [doc.qt.nokia.com]. In particular, it says “The geocode(QGeoAddress), geocode(QGeoCoordinate) and placeSearch() functions return QGeoSearchReply objects, which …”
Shouldn’t one be geocoding and the other reverse geocoding?
That’s correct. The current plugin is for online maps – if you’re viewing the map you’re probably downloading map data (unless it’s already been cached).
Do you have a use case for when someone might want to control the downloading for an online map viewer? Up until now I’ve been assuming that anyone using a map viewer with an online maps data plugin would be fine with handing control of when the downloading occurs to the viewer and/or the plugin.
There are some cache control hints you can give via parameters for the plugin – we’ll document those properly once we sort out the naming and a few other issues.