Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 2 days, 19 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 3 days, 14 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 5 days, 23 hrs ago - more...
 |
Feathers McGraw |
2016-11-12
, 20:36
|
|
Posts: 654 |
Thanked: 2,368 times |
Joined on Jul 2014
@ UK
|
#21
|
Guys, I just wanted to say thank you for working on this. Looking forward to testing it when there are prebuilt maps or an import tool!
|
|
2016-11-13
, 11:16
|
|
Posts: 105 |
Thanked: 205 times |
Joined on Dec 2015
@ Spain
|
#22
|
Hi guys!
Thank you very much for this piece of gold for our Sailfish OS!
I'm trying to making OSM Scout Server working on a Jolla 1, but after installing correctly OSM Scout Server, import and convert maps correctly with libosmscout and copying it to
After opening OSM Scout Server I only can see this error on main screen:
I have to say that with same imported maps, and in same folder, OSM Scout aplicattion from Warehouse https://openrepos.net/content/karry/osm-scout everything is working as spectated:
What is what I'm doing wrong?
For importing maps from http://www.geofabrik.de/ I'm doing:
./build.sh nordrhein-westfalen.osm.pbf for import with libscout
And copying the resulted files (which are a lot) into /home/nemo/Documents/Maps
Can you help me please?
Have you got any converted-working map with OSM Scout Server to compare the results and seeing what I'm doing wrong?
Thank you very much for this piece of gold for our Sailfish OS!
I'm trying to making OSM Scout Server working on a Jolla 1, but after installing correctly OSM Scout Server, import and convert maps correctly with libosmscout and copying it to
Code:
/home/nemo/Domcuments/Maps
I have to say that with same imported maps, and in same folder, OSM Scout aplicattion from Warehouse https://openrepos.net/content/karry/osm-scout everything is working as spectated:
What is what I'm doing wrong?
For importing maps from http://www.geofabrik.de/ I'm doing:
./build.sh nordrhein-westfalen.osm.pbf for import with libscout
And copying the resulted files (which are a lot) into /home/nemo/Documents/Maps
Can you help me please?
Have you got any converted-working map with OSM Scout Server to compare the results and seeing what I'm doing wrong?
|
|
2016-11-13
, 12:26
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#23
|
Originally Posted by ferlanero
You are very-very close. Just few touches and you should be fine.
What is what I'm doing wrong?
For importing maps from http://www.geofabrik.de/ I'm doing:
./build.sh nordrhein-westfalen.osm.pbf for import with libscout
And copying the resulted files (which are a lot) into /home/nemo/Documents/Maps
Can you help me please?
Have you got any converted-working map with OSM Scout Server to compare the results and seeing what I'm doing wrong?
I suspect that your problems are just due to version mismatch. The libosmscout is developing very fast these days. In particular, the server together with Poor Maps exposed routing component and there are quite a few bugs fixed over the last weeks. As a result, the database format is changing as well. So:
1. Import the maps using the libosmscout version against which the server has been built: https://github.com/rinigus/libosmsco...0.git.20161110
2. When importing, I suggest to use the command line as in https://github.com/rinigus/osmscout-server#maps . This would delete the temporary and debug files from the maps folder. To my knowledge, the build script does not do that and you could end up with 2x larger import. Just adjust the path of the typefile and your map folder/pbf. Expect to get the similar size for imported map as you had PBF.
3. Keep the maps that you use for the server and OSM Scout separate. This is to avoid the version mismatch. We will converge eventually, but just do it for now while the development is rapid. Since you can specify the path for your maps in the server easily, I suggest to put the maps used by server into some other folder. On my phone, I use /home/nemo/Maps and subfolders with countries. So, to get Estonian maps, I use /home/nemo/Maps/estonia in my settings.
As you noticed, the maps are converted into multiple smaller files. That is correct and you would need them.
Please let me know if that helped. If not, we'll look further into it.
| The Following 3 Users Say Thank You to rinigus For This Useful Post: | ||
|
|
2016-11-14
, 12:56
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#24
|
Here is my first take on simplified import. I have compiled Import statically for Linux x86_64 and wrote a small script to assist while importing. This version supports ONLY PBF-formatted OpenStreetMap maps. You can get maps from
http://download.geofabrik.de/
download the importer from
/link removed, see the next post/
uncompress the import tool and see included README.
This is a first try and I hope it works well. Please report back on how did it work and if there are any errors. I plan to drop it from dropbox in future and add the importer binaries to the releases at github. That way you will be able to get the importer corresponding to the release that you use.
Import tool was built using https://github.com/rinigus/libosmsco...uild_import.sh and "import" branch of libosmscout.
At present, only Linux on x86_64 architecture is provided. I don't know how to make similar build for Windows or Mac. If someone could chip in that would be of great help. Alternatively, Windows and Mac users could setup a virtual machine (VirtualBox, for example) with Linux and use it to import maps.
Last edited by rinigus; 2016-11-25 at 12:39.
http://download.geofabrik.de/
download the importer from
/link removed, see the next post/
uncompress the import tool and see included README.
This is a first try and I hope it works well. Please report back on how did it work and if there are any errors. I plan to drop it from dropbox in future and add the importer binaries to the releases at github. That way you will be able to get the importer corresponding to the release that you use.
Import tool was built using https://github.com/rinigus/libosmsco...uild_import.sh and "import" branch of libosmscout.
At present, only Linux on x86_64 architecture is provided. I don't know how to make similar build for Windows or Mac. If someone could chip in that would be of great help. Alternatively, Windows and Mac users could setup a virtual machine (VirtualBox, for example) with Linux and use it to import maps.
Last edited by rinigus; 2016-11-25 at 12:39.
| The Following 6 Users Say Thank You to rinigus For This Useful Post: | ||
|
|
2016-11-25
, 10:20
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#25
|
I have been working on making import of the maps simpler. The state is a bit work in progress, but it should be close to full release.
Right now, on each release in GitHub, the Import tool is built automatically using Travis and AppVeyor. As a result, we can get compiled import tools for Linux and Windows. While Linux version includes a small script that simplifies import to command "import mapfilename_in_pbf" , Windows build requires a bit more sophisticated input.
So, I would like to ask users interested in offline maps:
1. Linux users: Please test whether import works for you. Please report even if its just OK and include your distro. Would like to get conformation that it works in general, not just on PCs available to me.
2. Windows users: Please test whether you could run Import.exe by double clicking on it. No import will run, just command line help should be shown. Again please give a feedback, even a short one. If you wish to use it for map import as it is then I strongly suggest to use the similar options as in https://github.com/rinigus/libosmsco...inux/import.sh . Otherwise, you will end up with lots of debug info and get very large map directories that you have to store on device.
3. (quick note - I am getting help with this script via libosmscout developers mailing list) Someone with Windows scripting skills (minimal should already be better than mine), please write a script that would confirm to the spec below. If you don't know how to make it in full, please start discussion and write some parts that you can. Maybe then Windows users could finalize this small script to make map import easy.
The compiled packages are available at
https://github.com/rinigus/libosmsco...0.git.20161118
Let's use this for current testing. As soon as we get Windows scripts ready, we could make a new server release with the corresponding Import tools.
What I expect the Windows script should do:
Aim: finalize a compiled Windows package for simple importing maps into libosmscout
* The compiled binary of Import can be grabbed at https://github.com/rinigus/libosmsco...0.git.20161118 . The new script will be a part of this package and would allow us to distribute importers to the users.
* The script could be similar to https://github.com/rinigus/libosmsco...inux/import.sh
* While in Linux, we are used to start commands from terminal, in Windows its more common to drag-and-drop. So, on dragging downloaded OSM or OSM.PBF file, the new script should:
Since I am not familiar with Windows scripting, I am just afraid that it would take too long time for me to make it. So, please help even if its really trivial for you.
Last edited by rinigus; 2016-11-28 at 17:19.
Right now, on each release in GitHub, the Import tool is built automatically using Travis and AppVeyor. As a result, we can get compiled import tools for Linux and Windows. While Linux version includes a small script that simplifies import to command "import mapfilename_in_pbf" , Windows build requires a bit more sophisticated input.
So, I would like to ask users interested in offline maps:
1. Linux users: Please test whether import works for you. Please report even if its just OK and include your distro. Would like to get conformation that it works in general, not just on PCs available to me.
2. Windows users: Please test whether you could run Import.exe by double clicking on it. No import will run, just command line help should be shown. Again please give a feedback, even a short one. If you wish to use it for map import as it is then I strongly suggest to use the similar options as in https://github.com/rinigus/libosmsco...inux/import.sh . Otherwise, you will end up with lots of debug info and get very large map directories that you have to store on device.
3. (quick note - I am getting help with this script via libosmscout developers mailing list) Someone with Windows scripting skills (minimal should already be better than mine), please write a script that would confirm to the spec below. If you don't know how to make it in full, please start discussion and write some parts that you can. Maybe then Windows users could finalize this small script to make map import easy.
The compiled packages are available at
https://github.com/rinigus/libosmsco...0.git.20161118
Let's use this for current testing. As soon as we get Windows scripts ready, we could make a new server release with the corresponding Import tools.
What I expect the Windows script should do:
Aim: finalize a compiled Windows package for simple importing maps into libosmscout
* The compiled binary of Import can be grabbed at https://github.com/rinigus/libosmsco...0.git.20161118 . The new script will be a part of this package and would allow us to distribute importers to the users.
* The script could be similar to https://github.com/rinigus/libosmsco...inux/import.sh
* While in Linux, we are used to start commands from terminal, in Windows its more common to drag-and-drop. So, on dragging downloaded OSM or OSM.PBF file, the new script should:
- open a terminal (or PowerShell). I suspect its done automatically in Windows, but I don't know for sure
- make a directory with the simplified name based on the dragged map file name. I used to remove -latest.osm.pbf from the map fine name and make directory just on the basis of remaining name. See Linux script for details
- start Import.exe from relative bin\Import.exe . The style map.ost is under stylesheets directory. See compiled binary for package structure. Its expected that users just unpack it and can use importer straight away (no install is needed).
- keep terminal open after Import.exe is finished, so the user could examine output for errors
- on any error (cannot make export directory), stop the script (set -e in bash).
Since I am not familiar with Windows scripting, I am just afraid that it would take too long time for me to make it. So, please help even if its really trivial for you.
Last edited by rinigus; 2016-11-28 at 17:19.
| The Following 5 Users Say Thank You to rinigus For This Useful Post: | ||
|
|
2016-11-25
, 11:09
|
|
Posts: 105 |
Thanked: 205 times |
Joined on Dec 2015
@ Spain
|
#26
|
Originally Posted by rinigus
Wow! In Linux (Ubuntu 16.04) works really great!!
I have been working on making import of the maps simpler. The state is a bit work in progress, but it should be close to full release.
Right now, on each release in GitHub, the Import tool is built automatically using Travis and AppVeyor. As a result, we can get compiled import tools for Linux and Windows. While Linux version includes a small script that simplifies import to command "import mapfilename_in_pbf" , Windows build requires a bit more sophisticated input.
So, I would like to ask users interested in offline maps:
1. Linux users: Please test whether import works for you. Please report even if its just OK and include your distro. Would like to get conformation that it works in general, not just on PCs available to me.
2. Windows users: Please test whether you could run Import.exe by double clicking on it. No import will run, just command line help should be shown. Again please give a feedback, even a short one. If you wish to use it for map import as it is then I strongly suggest to use the similar options as in https://github.com/rinigus/libosmsco...inux/import.sh . Otherwise, you will end up with lots of debug info and get very large map directories that you have to store on device.
3. Someone with Windows scripting skills (minimal should already be better than mine), please write a script that would confirm to the spec below. If you don't know how to make it in full, please start discussion and write some parts that you can. Maybe then Windows users could finalize this small script to make map import easy.
The compiled packages are available at
https://github.com/rinigus/libosmsco...0.git.20161118
Let's use this for current testing. As soon as we get Windows scripts ready, we could make a new server release with the corresponding Import tools.
What I expect the Windows script should do:
Aim: finalize a compiled Windows package for simple importing maps into libosmscout
* The compiled binary of Import can be grabbed at https://github.com/rinigus/libosmsco...0.git.20161118 . The new script will be a part of this package and would allow us to distribute importers to the users.
* The script could be similar to https://github.com/rinigus/libosmsco...inux/import.sh
* While in Linux, we are used to start commands from terminal, in Windows its more common to drag-and-drop. So, on dragging downloaded OSM or OSM.PBF file, the new script should:
* open a terminal (or PowerShell). I suspect its done automatically in Windows, but I don't know for sure
* make a directory with the simplified name based on the dragged map file name. I used to remove -latest.osm.pbf from the map fine name and make directory just on the basis of remaining name. See Linux script for details
* start Import.exe from relative bin\Import.exe . The style map.ost is under stylesheets directory. See compiled binary for package structure. Its expected that users just unpack it and can use importer straight away (no install is needed).
* keep terminal open after Import.exe is finished, so the user could examine output for errors
* on any error (cannot make export directory), stop the script (set -e in bash).
Since I am not familiar with Windows scripting, I am just afraid that it would take too long time for me to make it. So, please help even if its really trivial for you.
It's a really improvement to handle offline maps. Thank you very much!!Now I have a question: OSMScout will be handle offline maps from sdcard? I love this app and how it works! So I love to see its evolution.
Thank ypou very much for all your efforts!!
| The Following 4 Users Say Thank You to ferlanero For This Useful Post: | ||
|
|
2016-11-25
, 11:26
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#27
|
OSM Scout Server should handle maps from SD. You just have to specify the map folder which is on SD card (use Linux path). Its under Settings, in OSM Scout Server GUI.
| The Following 3 Users Say Thank You to rinigus For This Useful Post: | ||
|
|
2016-11-25
, 13:28
|
|
Posts: 105 |
Thanked: 205 times |
Joined on Dec 2015
@ Spain
|
#28
|
Originally Posted by rinigus
You are right. Everything is working great!
OSM Scout Server should handle maps from SD. You just have to specify the map folder which is on SD card (use Linux path). Its under Settings, in OSM Scout Server GUI.
Thanks
| The Following 3 Users Say Thank You to ferlanero For This Useful Post: | ||
|
|
2016-11-28
, 21:12
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#29
|
The new release is out: 0.4.0, followed by 0.4.1
A highlight of this release is introduction of pre-compiled map importer that can be used to convert OSM maps to the libosmscout format using Linux or Windows PC. See https://github.com/rinigus/osmscout-server#maps for instructions. While in Linux all should be rather simple, in Windows, an additional script simplifying the import is needed. I've got some help on libosmscout mailing list and, hopefully, we could make such a script soon.
I have removed OpenMP requirement of the server which should reduce the problems with installing it. Please let me know if the resulting performance of the server is degraded. I have not noticed any slowdown.
I would like to thank Carmen F. B. @carmenfdezb for Spanish translation of GUI interface. Its a great initiative!
Several bugfixes were incorporated in this release. In particular, a problematic routing case found by @otsaloma has been fixed in the upstream library.
0.4.1: Updated Spanish translation allowing you to get routing instructions in Spanish. Work of Carmen F. B. @carmenfdezb, thank you!
Last edited by rinigus; 2016-11-29 at 07:17.
A highlight of this release is introduction of pre-compiled map importer that can be used to convert OSM maps to the libosmscout format using Linux or Windows PC. See https://github.com/rinigus/osmscout-server#maps for instructions. While in Linux all should be rather simple, in Windows, an additional script simplifying the import is needed. I've got some help on libosmscout mailing list and, hopefully, we could make such a script soon.
I have removed OpenMP requirement of the server which should reduce the problems with installing it. Please let me know if the resulting performance of the server is degraded. I have not noticed any slowdown.
I would like to thank Carmen F. B. @carmenfdezb for Spanish translation of GUI interface. Its a great initiative!
Several bugfixes were incorporated in this release. In particular, a problematic routing case found by @otsaloma has been fixed in the upstream library.
0.4.1: Updated Spanish translation allowing you to get routing instructions in Spanish. Work of Carmen F. B. @carmenfdezb, thank you!
Last edited by rinigus; 2016-11-29 at 07:17.
| The Following 11 Users Say Thank You to rinigus For This Useful Post: | ||
|
|
2016-11-29
, 10:04
|
|
Posts: 654 |
Thanked: 2,368 times |
Joined on Jul 2014
@ UK
|
#30
|
I've been reading the documentation in preparation for giving this a go, it's all really clear and well presented! Thank you to whoever wrote it.
Documentation often gets overlooked in projects like this where development is fast, I believe having decent docs will really help build up a userbase quickly. Well done
Documentation often gets overlooked in projects like this where development is fast, I believe having decent docs will really help build up a userbase quickly. Well done
| The Following 6 Users Say Thank You to Feathers McGraw For This Useful Post: | ||
 |
| Tags |
| geocoder, linux, offline maps, router, sailfish os, tiles |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 20:01.