Notices

Thanks, working fine now.

I have just published a new release of the server. This version introduces the support for route calculations. Thus, together with a client, you could use it for offline navigation by car, bicycle, or while walking. The changelog will be added to the first post when it will be updated.

As a reference, route calculation for shorter distances takes few seconds on a device (I use it on Nexus 4). For example, Stockholm -> Malmö (600 km) is about 15 seconds. Route calculation from Stockholm to Aarhus (950 km) would take about 45 seconds.

Since it can take significant amount of time, the client program has to be a bit more patient with timeouts. See https://github.com/otsaloma/poor-maps/issues/23 for a reference and how to patch Poor Maps to work around it.

There are also changes that allow you to tweak label rendering (thanks to @Karry!). These are under advanced settings. Use caution while experimenting with them.

With the latest release of Poor Maps, there is no need anymore to add plugins from the thirdparty folder into your .local/shared/harbour-poor-maps folder. To avoid confusion, its probably better to use official Poor Maps plugins to interact with the server.

After exposing routing functionality of the libosmscout library, there are more issues with the stability of the server. For example, @otsaloma has submitted the cases where either the server crashed https://github.com/rinigus/osmscout-server/issues/31 or was not able to find the route https://github.com/rinigus/osmscout-server/issues/32 .

It seems to me that there were not that many users of routing functionality of the library so far and we are one of the first ones. This is, in general, not a problem as long as we help to fix the bugs and make the library better. The principal developer of the library - Tim Teulings (@Framstag) - is very active and is resolving the issues rather quickly. For example, during a week he was able to: [1] fix the issue related to suggesting illegal turns and the routes were only public transport can go; [2] propose a fix to an issue leading to segfault of the server in a case reported by @otsaloma. These fixes would be released with the next version of the server.

So, I would like to ask you to file the issues that you have. Please try to get an URL that leads to a problem. I will try to react in timely manner and either fix them myself or report upstream in a way that would allow Tim to reproduce and fix it.

In addition, please keep the library installed on your PCs. Some fixes, such as the ones related to taking illegal turns, would require regeneration of the maps. So, you would have to get a newer version of the library (git pull), compile and install it again, and then reimport the maps. One of the tasks that I am planning to resolve is related to simplifying this cycle by providing an Import tool, but such cycle is needed until its done.

We are not yet in the stage where everything is working as it should. But, with all of our help, the library and the server could be improved significantly.

The current issues and my todo list are shown under https://github.com/rinigus/osmscout-server/issues

I am getting following error when trying to install from Warehouse.
Any ideas/help what I am doing wrong?

Jolla-C and 2.0.4.14

You are the second user who has this problem - I have received earlier report via OpenRepos.

I have just tested it on my Nexus 4 and I can install the server without a problem. This was tested on an SFOS image that I built earlier today for 2.0.4.13 (for ported devices we have a scratchbox that corresponds to .13 version). I have libgomp-4.8.3-1.2.5 installed as a dependency. [I don't own any official device and I cannot test it on jolla].

I suspect that your repos need to be refreshed (maybe Jolla refreshed gomp recently?). Try to run from command line:

pkcon refresh
pkcon search name libgomp

and see if the library is available.

I installed without problems from Warehouse. It's not easy to import maps for this moment :-)

JollaC(exAquaFish), v.2.0.4.14.

I had the same problem. I believe you need to refresh all repos first ('pkcon ref' should do) - at least I think that solved it for me.

Thanks!

Refresh helped and after that i could see libgomp and able to install OSM Scout Server from Warehouse!

Just to add to this, if you're using Poor Maps, the way to get the URL, is to run Poor Maps via the terminal with command

Among the output will be something like

and similar for search and nearby venues. That's the URL to look for. You can also save the output to file by using command

I have just published a new release: 0.3.0.

0.3.0 release is built against libosmscout release https://github.com/rinigus/libosmsco...0.git.20161110 . I am going to tag libosmscout versions, so you could always build corresponding Import tool.

For end users, the main change is in fixing multiple bugs related to routing in the libosmscout library by its authors: segfault at certain conditions reported by @otsaloma (thank you!), taking the wrong turns, and few others.

There are several important changes "under the hood". I am using now GNU Libmicrohttpd to provide HTTP backend. As a result, the clients can use up to 100 connections served using as many threads as there are CPUs on your device. The limit of connections is hard-coded, but if there is a huge interest in specifying it as an option, I will add it. This change should simplify the client's side of communication since it would not have to worry about exceeding the limit.

The server is now built using static linking to libosmscout, marisa, and libmicrohttpd. Its mainly done for two reasons: libosmscout API is changing as it is developed leading to incompatibilities between the versions; there is no need for other RPMs as you install the server. After an upgrade, I suggest to remove libosmscout-qt and libmarisa from your devices. I am planning to drop these packages from OpenRepos a bit later when users would move to 0.3.0 or later release.

NB! When you start using a new version, please update the maps! Few bugs were fixed in libosmscout library by fixing an importer. So, to get these fixes, you would have to update the maps with the latest version.

I have added a session log (see Settings to enable it). You could use it when reporting bugs to get the corresponding URL.

If your favorite client does not support routing yet, but supports GPX, you could now calculate the route and save the result in GPX format (see URL parameters in server GitHub project page).