I would like to add map matching support to WhoGo Maps. So, I would like to verify the general approach with you:

• add more modes to the route to distinguish from car and transit modes
• set the direction of the map in following preference: map matched direction, app.navigationStatus.direction, calculated direction from gps points
• allow user to specify whether (s)he wants map matching on NavigationPage, after rerouting settings. If selected, the route mode will be taken into account while calculating map matching
• allow users to specify globally the map matching mode in Preferences. The selected mode will be used when not navigating.

When added that way, it should be rather non-intrusive and simple to use.

it would be nice to have an indicator showing us how is the signal and/or it's hooked or not

just to give you some example on what i mean, jolla maps has a circle surrounding the pointer, that becomes smaller and smaller as the signal is stronger, or herewego as a flashing circle surrounding the pointer and when the signal is good it stop flashing and the pointer becomes green

it would be nice to have something like this...

See otsaloma/poor-maps#62

Hi,
the old Pictures on Openrepos show the remaining time in the above right see here:

Why is this gone? Or is it not gone and I#M to blind to see it? i never ever saw it while using the App for navigation. It would be very useful :)

well the title pretty much explain everything, it would be nice to have a way to calculate routes with tolls or not...since opencage have it maybe even osmscout can have it...

0.5–2?

At least geo URIs.

https://talk.maemo.org/showthread.php?p=1542851#post1542851

I said earlier that the animations are smooth and so they are, but the little symbol that shows your position keeps jumping forward and back. It looks like it is moving along the map and when too far, then the whole map including the symbol is jerked back. It is not too distracting but noticeable.

https://talk.maemo.org/showpost.php?p=1543039&postcount=66

Limit to user's locale language and English.

https://developer.foursquare.com/docs/api/venues/tips#response-fields

I am filing it early since it may influence your design.

When driving, its good to have support for changing between day and night styles. Already now, Mapbox provides day/night traffic style, I am working on making the similar pair of styles for the server. Ideally, basemaps could be put in pairs for automatic switch in accordance with the local sunrise as well as colors used to render POIs, roads, menu button and texts with speed/scale. The latter could be done also with the assumption of light (day) and dark (night) backgrounds.

At least from a GPX file.

Only for vector sources? Configurable in the preferences page?

"you can search for venues by name."

Dear maintainers,

Thanks for your awesome work.
I've added pt-br translation in transiflex, would you mind adding it to whogo maps? During last translation update you did not add it, so please let me know if something is missing.

Regards

It would be nice to have these maps included by default, like in Poor Maps.

Clear button in the main menu should also call endNavigating, or at least set app.navigationActive = false.

WhoGo Maps currently lacks (technically) overlay maps, respectively (by functionality) nautical maps ("sea marks"). Poor Maps provides them (both).
Although it may be not trivial to correctly overlay a vector base map with a raster overlay map, OSMand~ (under Android) does that nicely.

P.S.: Personally, WhoGo Maps' current inability to display nautical markings constitutes a regression compared to Poor Maps.

Looks like search and navigation providers are not stored in config or not loaded. Result is that these providers are reset to default on start.

Hey,
is it possible to make the actual speed:

Better visible?
Maybe put it in the head and make it white like the remaining kilometers or something.
While driving it's very hard to see, at least for me ;)

By the way: What does the thing under it display? I didn't found out what it is used for..

Writing it up to be sure that I'll remember it:

When driving, current position icon is blinking on each update. I wonder whether this fix has been applied : http://talk.maemo.org/showpost.php?p=1540591&postcount=69

It doesn't look so when checking position marker QML.

One less likely needed.

I was not able to see the translation in action before the release and it contained some strings that were too long to fit the screen. These have been shortened and 2 new strings translated (see Transifex). Please, update

Misc issues:

• km / m should be translatable
• Types of venues (ATM, Cafe...) are not available for translation. They are cryptic in English.
• Whogo Maps has a translatable word in it but is not in transifex.

While testing map matching, I was getting several times zero division error in the return statement

return seg_dist_deg * (med_dist_m / med_dist_deg)

of calculate_segment_distance in poor/util.py file. I presume that it was due to the fact that the map matched position was exactly on a segment and in a middle of it.

Not sure what's the best way to fix it though.

Feature request: the user should be able to import (and display) personal POIs from a local .kml file

many thanks

Previous discussion: otsaloma/poor-maps#5

will nice to enable this option in whogo-maps, valhalla is supporting auto_shorter. I will contribute with beers and coffees to my request.
thanks.

Previous dicussion: otsaloma/poor-maps#3

With the rewrite, getDestination is not available at https://github.com/otsaloma/whogo-maps/blob/master/qml/whogo-maps.qml#L145 . Just saw this bug and I am writing it up not to forget

Maybe add a diameter symbol "⌀"? (Accuracy is likely radius though, but there's no radius symbol.)

Do we need proper objects for POIs, maneuvers and route? Currently it's a half-butchered mess due to previosly being built around MapQuickItems and Canvas, which are no longer used.

Hey,

When driving through a (longer) tunnel while navigating the GPS signal is obviously lost and QtLocation delivers some "old" basic location, resulting in a jumping map.
Would it be possible to disable updating the location via QTLocation when driving through a tunnel (cheap solution), and maybe as a second step following the current road with the last known velocity until the end of the tunnel plus some buffer until a GPS fix (complex solution). The second step would also be very useful when in tunnels with branches or departures.

Cheers.

i.e. get rid of the enabled below.

I just don't quite remember why this needed to locked – @rinigus: your code, do you remember? Given the pregeneration, turning it on might have a slight delay, but that should be no big deal, and turning it off would still serve previously generated audio, but we can add a simple check on the QML side to ignore those. Anything else?