Notices

Originally Posted by ferlanero

Thank you very much for this piece of gold for Sailfish offline navigation. I have no words to be grateful for your work! Thank you very much @rinigus !

Originally Posted by Sthocs

+1, the work you (including every people involved - server/clients) are doing is unbelievable, you are basically almost bringing to Sailfish a native solution for the most voted TJC feature! (almost because no voice, but I personally don't need it). It can really help promoting Sailfish.

Originally Posted by Sthocs

One thing I've noticed while trying it is that the search results are totally not relevant when libpostal is not enabled. Wouldn't it make sense to enable it by default and invite the users to chose their search language(s) on first start?

Originally Posted by jdrescher

Hello guys,

I am currently developing a sport tracker app for SFOS.
I would like to use OSM Scout Server for providing map informations but unfortunately it does not work.

This is what I tried:

Code:

Map {
        id: map       
        plugin: Plugin 
        {
            name: "osm"
            PluginParameter
            {
                name: "useragent"
                value: "Laufhelden/0.0.1 (Sailfish)"                
            }
            PluginParameter { name: "osm.mapping.host"; value: "http://localhost:8553/v1/tile/" }
        }
        }
...

The map from the server seems not to be found and instead is trying to use WIFI connection to download the map.

The server is running nicely and works with modRana and Poor Maps.

Originally Posted by jdrescher

I would like to use OSM Scout Server for providing map informations but unfortunately it does not work.

Originally Posted by otsaloma

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.

Originally Posted by rinigus

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?

Originally Posted by otsaloma

I don't actually know if it's possible, but looking the commit activity, there's a lot of fixes related to e.g. geoclue positioning, and just using upstream 5.6 might not work well on all devices and trying to port those patches to 5.6 might be difficult. Additionally, there are API changes between 5.2 and 5.6, which means upgrading would break many apps written for 5.2. The API changes are small and it's easy to adapt to them, but it might be difficult for app authors to support both versions.

Also note, that this problem of using using a custom tile source, e.g. OSM Scout Server, is only partially served by the OSM plugin in QtLocation 5.6. It allows you to set the host, e.g. "http://tile.openstreetmap.org/" in "http://tile.openstreetmap.org/{z}/{x}/{y}.png", but the requested URL will always end in "{z}/{x}/{y}.png". What we'd really need is a plugin that supports a template URL string, so that you can have X, Y and Z as URL parameters instead of path components or additional parameters like day/night or API keys etc. And also, a plugin parameter for tile size so that the requested tiles can be shown correctly. A custom QtLocation plugin would be easy to distribute separately, e.g. at OpenRepos, but probably difficult to use in Harbour apps.

Originally Posted by rinigus

What's telling is that there has been no activity visible with QtLocation 5.6. From this maybe we can conclude that we should not expect situation change in a short term.