Due to this bug:
https://bugreports.qt.nokia.com/browse/QTSDK-419
you'll probably need to check out Qt Mobility from git and build it from source.

The Lightmap example was added to show off the positioning part of the Location API - some time after that we added a Maps API (with support for map markers etc...).

The default plugin uses the...

Not a problem - although I'd be happier if the search for "London" worked on it's own :)

I'll bring this example up the next time I'm talking to the people behind the servers - at the very least...

It would be highly preferrable that you open a new bug report rather than adding data to that closed bug.

That bug report does contain a hint though - "No data available for the specified...

A change request has been created to track this: http://bugreports.qt.nokia.com/browse/QTMOBILITY-1644

It's probably worth reading the terms of service attached to the Nokia plugin which provides the routing, since it might have an impact on what you can or can't do in a commercial context:...

If you're using the 1.2 beta on Symbian you might have some troubles, since there seems to have been a packaging problem (which should be fixed by the final release). If that's not the case I'm not...

I was actually referring to some different bugs which were spotted by other people that have since been closed. I think that QTMOBILITY-841 just needs retesting and closing since those other bug...

We just checked and it seems like the declarative plugin for Location wasn't in the sis file for the 1.2 beta. Sorry about that.

We checked some more and it appears that it should be in sis file...

There were a few bugs in that area that have since been fixed.

You might have better luck with mapObjectsInScreenRect with a 3 by 3 rectangle centered on the position. If that still doesn't help...

From the 1.1 release onwards, there's the Qt Mobility Landmarks API:
http://doc.qt.nokia.com/qtmobility-1.1.0/location-overview.html#landmarks

Does it work if you change

to
?

From:
http://discussion.forum.nokia.com/forum/showthread.php?220075-QGeoPositionInfoSource-initialization-problem

The main problem I see is with positionUpdated, which needs to be a slot, which also means it needs to be a member function of MainWindow.

So you need something like this in the header file:
...

You might want to try waiting for a while. Generally it's best to be outside, away from buildings and trees, and even then it can take quite a while depending on various factors. On phones that...

From what I can gather it looks for a few folders that may or may not exist, in an attempt to cover the directory layours a variey of possible SDK versions. So not finding the path isn't necessarily...

Are you using QTM_USE_NAMESPACE in your code (as per http://doc.qt.nokia.com/qtmobility-1.1.0/quickstart.html)?

I think might have put that last reply in the wrong tab :) Now I just need to track down the right thread (and possibly the right site) where that tip was relevant...

QGeoCoordinate is already present in Qt Mobility 1.0.x

I don't know enough about the legalities of using Qt Mobility 1.1.0 sources in a Qt Mobility 1.0.0 app to comment on that. The biggest...

Do you have

QTM_USE_NAMESPACE

somewhere near the top of your source file?

(From http://doc.qt.nokia.com/qtmobility-1.1.0/quickstart.html)

Qt Mobility 1.1.0 comes with the Maps and Navigation functionality, and was released a little while back. Officially it's out of beta, although improvements will be coming in future versions.

What version of Qt Mobility are you using? We had some problems with the positioning methods for the 1.0.x releases which might be releated that were fixed in 1.1.0. Might be worth giving it a try.

That's your problem then - there is no valid ground speed attached to your position. What are using as arguments to setPositioningMethods(...)?

The bug is being tracked by http://bugreports.qt.nokia.com/browse/QTMOBILITY-876

What does hasAttribute(QGeoPositionInfo::GroundSpeed) give you?

I think there's a bug with the bounding box returned by the route object. I'll have a poke around and file something in the bug tracker shortly.

We'll fix it eventually, but if you want a work...