Hi I was really disappointed with reverse geocoding of qtmobility.
I had done a application with qtmobility 1.0.1 at that time reverse geocoding was not available. So I used google web API and QNetworkAccessManager to do the job. Now when its available I tried it and results were not so good. First all I need is an address from a coordinate, and I get a list of places. Now I have to see how many places it returned? how close are they to the lat/lon that I provided for reverse coding. Even after doing that level of detail was very poor. Best address I got was: south bangalore, karnataka, india. while with google I was getting the sub-street also. and it was conveniently available as a string in returned json. It also has lot of other details nearby things. But at the top of the json there was the best possible resolved it could get (provide a similar api). And in general I have seen a lot of qtmobility like this: "if backend does this.... then this.... Backend may do that. Now where is this documentation what does a backend actually do, say symbian or maemo backend. And if you start coding keeping in mind all these "backend may do this and that", code will turn out to be a mess. Thanks, Kahola _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback
