Offline Maps PureOS

Software PureOS
, ,
1

Hello,
I have to travel fairly frequently without cellular services. Can I utilize maps on PureOS offline?

If not, are there any good offline map/directional software for GNU/Linux that support the Librem 5?

Thank you so much!

8 Likes
2

I’m interested in this also, I think there should be ways to do it but I don’t know how at the moment. Here is a link about such things: Using OpenStreetMap offline - OpenStreetMap Wiki

Related GNOME Maps issues:

2 Likes
3

If you are motivated enough you can try osmin, but you’ll have to download the source code and compile it

I tried it on one of my L5 with PostmarketOS, it’s available by default, The map scrolling is very fast, very smooth, and it’s very easy to download maps (many Gb per country)
But I didn’t tried to make it work with the GPS, so I can’t tell if it will works with your L5’s GPS

3 Likes
4

You could give the Organic Maps flatpak from flathub a try. Currently, it crashes when accessing the location for me, but you can download maps.

2 Likes
5

Puremaps with the osm server works well from flathub Search for 'puremaps' | Flathub. Osmin works fine with gps on postmarketOS

5 Likes
6

Have you tried filling an issue request?

1 Like
7

I was tinkering a bit with a little with PureMaps and OSM Scout Server its a bit convoluted/difficult to set up (I haven’t succeeded yet).

There is an older maps app I saw that some people recommended, I may post it here if I remember it might be Navit but I haven’t tried it myself

A couple I just found looking things up:

2 Likes
8

It looks like an issue exists but was closed. Perhaps it was closed by mistake or the actual fix wasn’t implemented? Enabling location access causes Organic Map to crash (PureOS 10.3) · Issue #61 · flathub/app.organicmaps.desktop · GitHub

1 Like
9

I used Puremaps and OSM Scout Server with offline maps last night to find my way to my son’s baseball game yesterday. Worked great.

6 Likes
10

When you go on the pureos store and look at the puremaps app, it says that the app is unsafe because it uses a “legacy windowing system,” to clarify in what way is it unsafe? It looks really good to me.

2 Likes
11

It probably means the application still uses Qt5.

1 Like
12

Pure Maps flatpak should be of use to you I think

2 Likes
13

The GUI system? So it won’t be supported too much longer and if someone manages to find a way to exploit it there won’t be any new software patches kind of thing?

1 Like
14

My speculative statement is based on this quote:

1 Like
15

I read everything in that forum you sent and I understood around 10% of it, nheko, sounds like a Japanese cat, the matrix, agent Smith, flatpak, I half know that word from getting my phone to work last week with your help, some guy called amarok and Irvinewade.

Still working on sending mms messages with the default texting app.

1 Like
16

I believe that this message means the application is an X11 application or, at least, has those ports open in the flatpak manifest. [Edit: Specifically if the flatpak manifest includes socket=x11 instead of socket=wayland (? or socket=fallback-x11) , flathub will label this as “Unsafe” and say “Uses a legacy windowing system”. I’m not 100% sure if that is duplicated in the PureOS store or not. Probably.]

2 Likes
17

What does socket = x11 mean exactly?

1 Like
18

It’s a possible line in a flatpak manifest. Manifests - Flatpak documentation

The idea of flatpaks is to package applications (including all of their dependencies; mediated through ostree) and run them in a container that is isolated from your base system (using bubble-wrap and usernamespace features). But that is too naive. It turns out that applications often need to have some interaction with the rest of the system (e.g. access to some parts of the filesystem (e.g. ~/Downloads) , access to the network (e.g. a browser), access to d-bus, access to various IPC sockets, pulseaudio, …).

For example, if an application is X11 based, it will need to have access to your X11 server. To allow that, the manifest must include the line “socket=x11”. Similarly, if the application is Wayland based, it will need to have access to your Wayland compositor. To allow that the manifest must include the line “socket=wayland”

1 Like