View Single Post
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#246
Originally Posted by otsaloma View Post
SFOS still has QtLocation 5.2. That "osm.mapping.host" parameter was added in 5.6. Documentation for QtLocation 5.2 is not officially available, but maybe Ubuntu 15.04 might be close. But note that Jolla has backported individual commits and updated individual things like the HERE plugin, so it's understandably quite difficult to figure out.

What you're trying to do is (to my knowledge) simply not possible with the SFOS version of QtLocation. My advice would be to wait for QtLocation 5.6 (maybe we need a new community IRC pressure meeting?) or if you can't wait, ask Martin about his pure QML component. Poor Maps uses QtLocation's Map component, but has custom tile loading to work around stuff like this, but that's not designed to be reusable.
I must say that situation with QtLocation on SFOS is frustrating. Its probably a naive question but I am going to ask it anyway: now, when we have Qt5.6, is it possible to compile missing QtLocation 5.6 and add it ourself via OpenRepos or other distribution mechanism? @otsaloma, you have been following for a while, do you know whether it is possible?


To keep you in the loop and give an overview of the server development:

On the server side, I have been working on making it simple to use it with multiple maps. Rendering of the maps has been resolved already with Mapnik. Now I have added support for search using the data from all available maps. This is done for geocoder-nlp backend.

Finally, I think I know how to get routing through multiple maps supported as well. Namely, I am planning to incorporate Valhalla (routing engine behind Mapzen routing solution). After few days of porting, I managed to run the first routing tests using valhalla's program on SFOS device. Calculation of a route from Stockholm (Sweden) to Aarhus (Denmark) took just 2 seconds on Nexus 4. That's compared to ~45 seconds on the same device on the same route when using libosmscout. Not sure whether valhalla is always faster, but the start is promising. In addition to speed, valhalla routing engine allows us to "glue" the countries/territories together solving the long-standing issue of routing between countries.

There are several technical issues to be resolved with the adaptation of Valhalla, but it should be possible. Also we would have to discuss with @otsaloma and @MartinK few technical choices on how to do that when I know a bit more about Valhalla requirements.

I might make one more release before adding Valhalla to push out support for search in all maps and catch up with the advances in libosmscout.
 

The Following 5 Users Say Thank You to rinigus For This Useful Post: