WhoGo Maps
 

https://otsaloma.io/pub/whogo-maps.png

WhoGo Maps is a full-featured app for maps and navigation with a flexible selection of mostly OpenStreetMap-based maps and related service providers. WhoGo Maps requires the Mapbox GL Native QML component for map display, supporting both vector and raster maps with OpenGL accelerated rendering.

Download at OpenRepos.

Source code and issue tracker are available at GitHub. Translations at Transifex.

Donations appreciated: paypal.me/otsaloma

https://otsaloma.io/pub/whogo-maps-1.png

https://otsaloma.io/pub/whogo-maps-2.png

https://otsaloma.io/pub/whogo-maps-3.png

https://otsaloma.io/pub/whogo-maps-4.png

https://otsaloma.io/pub/whogo-maps-5.png

Re: WhoGo Maps
 

Might have seen that settings page in some other application before? :rolleyes:


Why a new name/app?
what are the differences?

Re: WhoGo Maps
 

New map component, Mapbox GL QML, as ported by rinigus. It brings vector maps, which works better across different size and different pixel density screens, rotates nicer, tilts for navigation and also the performance should be a lot better. It needed to be a new app as this is a big change, not yet fully proven technology, and will not work on older devices such as Jolla 1.

http://talk.maemo.org/showthread.php?t=99953

Re: WhoGo Maps
 

@otsaloma - congratulations! Great to see it released :)

As was announced from the beginning, Poor Maps GL - an intermediate step in this transition - has been removed from OpenRepos. All users are advised to move over to WhoGo Maps.

Congratulations again, great work!

Re: WhoGo Maps
 

Now I got it! :p

Re: WhoGo Maps
 

Does this have a way to launch it from command-line with a destination? Saera currently uses its internal routing engine for directions, but I'd like to give users the option to use WhoGo Maps if it's installed.

Re: WhoGo Maps
 

Why not "Rich Maps"? :D

Re: WhoGo Maps
 

... or "MeGo Maps", "WeGo Maps", "HereWeGo Maps" or simply "Go Maps"?

Seriously "WhoGo Maps" sounds strange (as if "Hugo Maps") and does not make much sense (or I just fail to see it), is somewhat cool, but primarily irritating.

But as this is @otsaloma's baby, all I / we can ask for is: Please reconsider this awkward name (for the apps sake; actually a catchy and bit flashy "Rich Maps" may suit the app best).

Re: WhoGo Maps
 

Mmm IMHO Whogo-Maps is good name, because It is not a generic name. But Hugo-Maps I like much, that Rich-Maps or whatever :)
So thanks @otsaloma for ur pretty work for it, Also to be original on name-app

Re: WhoGo Maps
 

No, unfortunately sailfish-qml doesn't support argument passing.

Re: WhoGo Maps
 

That's a shame. Ok; could I launch it and then send it a dbus message to give it a destination?

Re: WhoGo Maps
 

No, there's no dbus interface. I'm not familiar with dbus, I have no idea if it makes sense to add one.

Re: WhoGo Maps
 

So I've looked how hard it is to use DBUS from Python as I did remember there have been some long needed improvements done from the Jolla side recently - and it turns out to be really easy! :)

I've even created a tutorial to make this useful functionality as available to developers as possible:

• talk.maemo.org version of the tutorial
• together.jolla.com version of the tutorial

Re: WhoGo Maps
 

too bad i use a oneplus x with sfos 2.1.0.11 and pyotherside 1.4, but this needs pyotherside 1.5 :/
i managed to compile it, but i don't know how to tell the os to use this version

Re: WhoGo Maps
 

That may change in few days. I have build the update packages at OBS and we are testing OTA these days. If all goes well for others as for me , 2.1.3.7 will be out for onyx

Re: WhoGo Maps
 

I would have changed from Poor Maps to Pure Maps..

anyway once again thanks for the fantastic result.

Re: WhoGo Maps
 

For what it's worth, you might get WhoGo Maps working by reverting a single commit. I dropped an old work-around, figured it wasn't needed anymore...

https://github.com/otsaloma/whogo-ma...38a3a68abd8f36

Re: WhoGo Maps
 

It seems this was outdated information, so I'll likely add command line argument support at some point, and thus no dbus, despite a good guide.

Re: WhoGo Maps
 

that would be really cool. but thanks to this i learnt how to package rpms^^ i tried to install my compiled version, but who-go doesn't start, interesting thing is, that the 1.4 rpm only contains 2 files out of the src folder, but if it gets an update it's nicer :)

Re: WhoGo Maps
 

Translations now at Transifex. I copied them from Poor Maps and assigned the "poor-maps team" there, so if you have translated Poor Maps, you should have access, otherwise click some appropriate button to join.

Re: WhoGo Maps
 

Looking forward to the release with argument passing! If you want to let us know what the arguments will be, I can get a head start coding that into Saera to release when the update arrives.

Re: WhoGo Maps
 

Congrats on this release, it feels full-featured and polished.

Tested it on a OnePlus X with the 2.1.3.7 update and no connectivity. Off-line routing and real-time rerouting using OSM scout server worked very well. I am very impressed!

Voice directions with mimic also worked well. One small bug: with an English voice and American measurement units, measurements in "feet" were voiced as "miles".

Re: WhoGo Maps
 

i also tested it on a opx with sfos 2.1.3.7 now and offline navigation worked fine. one road direction was different, but that is a backend issue.

Re: WhoGo Maps
 

when using voice navigation while playing music it pauses playback, but didn't resume after the directions. do you also experience this and is there something that could be done to resume playback automatically?

Re: WhoGo Maps
 

Feedback on voice navigation: decent, but could use some work. Points noted on a test drive:
- as mentioned by klingerware, approaching an intersection I was given an instruction to "turn left in 1000 miles"
- one instruction was "in 2.5 miles, turn right." No other voice prompt was given when I actually reached the intersection.
- My destination was on a road parallel to the main road. As I drove past, it skipped the final turns and jumped straight to "you have arrived at your destination."

Additionally, I note that you are using maneuver nodes to determine when a turn is reached. I originally used this in Saera, however by itself it can lead to missed instructions if the gps cuts out as you pass a node. I switched to nodes + checking which segment is the closest, so that new directions can be given as soon as possible when you make a turn.

Re: WhoGo Maps
 

Pity I cannot try WhoGo since, as per post #3, it does not work on my device. As a general comment, I have used a commercial satnav that gave instructions of the kind, "make <manoeuvre> in <distance>", and I found it infinitely confusing. Fortunately a software upgrade turned it into a more common, " in <distance> make <manoeuvre>", which was much better.

Re: WhoGo Maps
 

Its pity, indeed. Maybe its time to switch devices? We should have "In <distance>, <maneuver description>" in WhoGo and Poor Maps.

Re: WhoGo Maps
 

I filed an issue now. I took a quick look earlier, but didn't find where the problem originates from.

That's a known issue and hard to avoid.

Yes and no. The instructions are associated with maneuver points, but the system mainly works by comparing the GPS position with the route polyline segments, finding the closest segment and then the next maneuver node following that segment. Additionally, there are some tweaks to account for positioning inaccuracy etc.

Re: WhoGo Maps
 

I'm confused. I've WhoGo running on my JP1 just fine, using OSM Scout Server with profile "Recommended for vector tile maps". Navigation has the nice tilt option (why only when navigating?) Very smooth. It all works fully offline too. So, what am I missing here?

Re: WhoGo Maps
 

When we were testing Mapbox GL widget in summer 2017, it was a general conclusion that J1 is not able to handle OpenGL map component (crashes of test program, hanging of it and so on). Some time has passed, Mapbox GL and SFOS releases are out. Maybe something got fixed, it's hard to tell.

At that time, we also tested against Mapbox styles. So, maybe you could check whether you have any issues when using their basemaps.

If it all works, it's a great news. I think someone has been telling about positive results on J1 (maybe you). Good luck with testing !

Re: WhoGo Maps
 

In WhoGo, on my JP1, when switching to from OSM Scout to Mapbox / Mapbox Satellite and others it also works fine in a quick test. I haven't used it yet for actual navigation or other prolonged use, but it doesn't seem to instantly crash or other apparent malfunctioning. SFOS 2.1.4.

Re: WhoGo Maps
 

I was one of those that did the tests on the Jolla 1 before.
I am a bit lagging right now, but I will do the update to 2.1.4 during the weekend and redo the tests with WhoGo maps to give another feedback.
I also have a PhotonQ which was also impacted by the crashes before, and will test it too with WhoGo maps, but I don't think 2.1.4 is available for it, I'll check.

I'll get back with the results "soon" ;)

Re: WhoGo Maps
 

Fuzzillogic's good news made me test things out, and it's true, there are no crashes on the Jolla 1. Marvellous work! Map tilt makes it look so much more professional, and it's much smoother and MUCH faster than any of the 'car GPS' systems I've seen.

Re: WhoGo Maps
 

Actually, now I did notice a problem: the downloaded OSM Scout maps aren't shown. It works with Poor Maps, so I'm not sure why it isn't working with WhoGo Maps.

Re: WhoGo Maps
 

You most probably have a profile that doesn't contain Mapbox GL data in OSM Scout Server. Go to profile selection and choose a profile with vector tiles. These days I don't fetch Mapnik data anymore and use the profile with vector tiles only. You will have to download the maps after you enable vector tiles profile.

Re: WhoGo Maps
 

Great, that was indeed the problem. Are you planning to make the vector-exclusive profile the default profile in a future update?

Re: WhoGo Maps
 

I will. However, the users with profile defined (so, any current user) will have profile migrated into raster only if it was the current default. I prefer not to change the settings in invisible manner. I will also add a check on startup to warn if there are map clients in the system that are not supported by the current profile.

Re: WhoGo Maps
 

when I use OSM Scout Server, blue marks/points or route traces on the map do not display, is this a known issue?

Also returning back from minimized the map layer is empty.

Re: WhoGo Maps
 

It does display for me and I haven't heard anyone telling about it.

To ensure that there are no mixups with the versions, make sure you run the latest WhoGo Maps. Maybe uninstall, check that there is nothing left in /usr/share/harbour-whogo-maps, and install again. Report back.

Re: WhoGo Maps
 

I did reinstall, but I get the same empty layers, it might be a problem with my OSM Scout Server, I get some warnings like:
Error whtile getting mapbox GL style, and malformed mapbox GL file request styles/osmbright-en.json