We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2018-03-30 14:25:49 +0200

Native Offline Maps: OSM Scout Server

This is a thread dedicated to a native offline maps solution provided by OSM Scout Server. While I prefer to keep general discussion at TMO and get bug reports via GitHub, there are general announcements that could be of interest to SFOS users not following TMO.

Native offline maps have been requested by many, with the corresponding request being #1 most voted for. OSM Scout Server provides maps for rendering, calculates routes, and searches for locations. This is done in offline mode.

For users, in rather unusual manner for mobile map applications, there are two applications needed:

  • OSM Scout Server to provide data;
  • Map client accessing OSM Scout Server.

Usually, on mobile, all-in-one solutions are provided. By using such split design, users can select their own preferred client. Among clients providing offline maps access we have Poor Maps, modRana, and the new wave of OpenGL-accelerated map clients WhoGo Maps and sports application Laufhelden. All these clients, through accessing OSM Scout Server, share the storage data, benefit from improvements of the server and underlying libraries. In short, such split allows each of the parts to focus on one particular task and do it well, in line with Unix philosophy.

Fortunately, after integration with systemd, users don't have to be concerned about running the map client and server. The user is expected to fire up the map client with the server started automatically by systemd when needed. So, users are just using a favorite map client and need to access the GUI of OSM Scout Server only to download, update, or remove maps.

How does it compare to the best offline solutions on other mobile platforms? That's, in the end, to the users to test. When using with OpenGL accelerated maps, you are getting combination of state-of-the-art libraries, some of them not available or usually limited to online mode only on other platforms. Already more than a year ago, SFOS was the first mobile OS that had libpostal and its datasets available allowing OSM Scout Server to parse addresses in natural manner in many languages. Probably the main drawback, when compared to offline solutions on other platforms, is the larger data footprint required by OSM Scout Server. This is since the server combines multiple backend libraries and the data formats used by each of them are unique to the each of them. Fortunately, many of SFOS devices have access to SDCard which can be used to provide cheap storage for maps.

In addition to the software itself, we have extensive Users Guide in several languages providing tutorials on how to setup and run the server. Enjoy!

Native Offline Maps: OSM Scout Server

This is a thread dedicated to a native offline maps solution provided by OSM Scout Server. While I prefer to keep general discussion at TMO and get bug reports via GitHub, there are general announcements that could be of interest to SFOS users not following TMO.

Native offline maps have been requested by many, with the corresponding request being #1 most voted for. OSM Scout Server provides maps for rendering, calculates routes, and searches for locations. This is done in offline mode.

For users, in rather unusual manner for mobile map applications, there are two applications needed:

  • OSM Scout Server to provide data;
  • Map client accessing OSM Scout Server.

Usually, on mobile, all-in-one solutions are provided. By using such split design, users can select their own preferred client. Among clients providing offline maps access we have Poor Maps, modRana, and the new wave of OpenGL-accelerated map clients WhoGo Maps and sports application Laufhelden. All these clients, through accessing OSM Scout Server, share the storage data, benefit from improvements of the server and underlying libraries. In short, such split allows each of the parts to focus on one particular task and do it well, in line with Unix philosophy.

Fortunately, after integration with systemd, users don't have to be concerned about running the map client and server. The user is expected to fire up the map client with the server started automatically by systemd when needed. So, users are just using a favorite map client and need to access the GUI of OSM Scout Server only to download, update, or remove maps.

How does it compare to the best offline solutions on other mobile platforms? That's, in the end, to the users to test. When using with OpenGL accelerated maps, you are getting combination of state-of-the-art libraries, some of them not available or usually limited to online mode only on other platforms. Already more than a year ago, SFOS was the first mobile OS that had libpostal and its datasets available allowing OSM Scout Server to parse addresses in natural manner in many languages. Probably the main drawback, when compared to offline solutions on other platforms, is the larger data footprint required by OSM Scout Server. This is since the server combines multiple backend libraries and the data formats used by each of them are unique to the each of them. Fortunately, many of SFOS devices have access to SDCard which can be used to provide cheap storage for maps.

In addition to the software itself, we have extensive Users Guide in several languages providing tutorials on how to setup and run the server. Enjoy!