Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Working location out on tunnels #562

Closed
rafacouto opened this issue Dec 30, 2013 · 9 comments
Closed

Feature: Working location out on tunnels #562

rafacouto opened this issue Dec 30, 2013 · 9 comments

Comments

@rafacouto
Copy link

It is a little bit annoying when GPS location is lost in tunnels and the current position on map becomes freezed until to the end of the tunnel. For example, Osmand does not inform when there is a speed trap in the tunnel or at its end.

I propose an improvement consisting in to calculate the estimated location based on speed before entering in the tunnel as a constant and the seconds from the lost of GPS signal.

The current location can be calculated over the main line of the route in the tunnel and navigation will be usually more comfortable. User must be informed that he or she is under a tunnel and location is calculated virtually (voice notification and a label titled something like "Under tunnel: estimated position").

@jkufner
Copy link
Contributor

jkufner commented Dec 30, 2013

Theoretically it should be possible to use accelerometers to determine current speed and then extrapolate current position from last known position, planned route and traveled distance (since speed and time is known). In addition, a compass can be used to check whether user is still heading in correct direction.

If data from sensors are good enough, short-term odometry-like navigation should be possible even without following the planned route. I believe this is very nice use-case for Kalman filter.

In all cases, the user must be informed that position is inaccurate extrapolation and last known position should be marked in map. And this feature should not be limited to navigation only.

@vshcherb
Copy link
Member

It was implemented in nightly builds already

@Tchiller
Copy link

has this been distributed already? At least in not-navigating mode, it is not working in OA+ 2.1.1

@stephan75
Copy link
Contributor

I can confirm that this feature is working for over one year now, even in the "Elbtunnel" in Hamburg, when in Navigation mode.

About the cruising mode: What is when a tunnel is forking under the earth ... where should Osmand know what direction you proceed?

So I fear: no artificial position when just in cruising mode.

@Tchiller
Copy link

Fair enough. Thank you for the update, Stephan.

@reibax-marcus
Copy link

@vshcherb , can you point out what commits resolve this problem? As of OsmAnd+ v4.2.5 the navigation halts at the entrance of tunnels and doesn't resume until gps signal comes back. This results in missed directions and warnings.

@vshcherb
Copy link
Member

vshcherb commented Jul 4, 2022

It was 2013, so I don't think it's relevant any more to comment here

@reibax-marcus
Copy link

We should either re-open this issue, or open a new one then. Which approach is better?

@vshcherb
Copy link
Member

vshcherb commented Jul 4, 2022

reopen is not possible for issues of previous release i.e. > than 1 year. Please open new one and add all details you have, is it reproducible with simulation, recorded screenshot or recorded track.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants