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

UI - Show max speed sign next to speed camera icon #3721

Open
ignaciolep opened this issue Apr 28, 2017 · 7 comments
Open

UI - Show max speed sign next to speed camera icon #3721

ignaciolep opened this issue Apr 28, 2017 · 7 comments
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning

Comments

@ignaciolep
Copy link
Contributor

Hello,

It would be great if OsmAnd could show the max speed sign next to the speed camera icon, reading the speed limit value from the maxspeed tag in the enforcement=maxspeed relation or from the highway=speed_camera node (device).

It could also show a traffic light sign for the enforcement=traffic_signals relation.

I made two mockups:

max speed sign - camera
traffic light sign - camera

Thanks!
Ignacio

@pebogufi
Copy link

Great Idea !
Peter

@pl71
Copy link
Contributor

pl71 commented May 7, 2017

👍

@polarbearing
Copy link

I see several problems here:

  • the allowed speed is already shown in a widget. Arguably it is a bit too small to be observed while driving. However, effectively the speed with the camera symbol is redundant.
  • the first mockup uses the same speed symbol in a red circle that OsmAnd uses when I exceed the speed, which is confusing if I am driving below the limit
  • we have cameras here in areas with variable speed limit, thus the app would indicate a higher limit than it is allowed when the variable speed is posted lower on the street.
  • I am absolutely against warning of traffic light cameras. Exceeding the speed can happen gradually when the driver has more attention to the road than to his instruments. But driving over a red traffic light is a concious decision in full view of the traffic situation, which poses an immediate and deadly hazard on crossing traffic. Such a warning would encourage to drive on red over junctions without a camera.

@ignaciolep
Copy link
Contributor Author

Perhaps the max allowed speed widget could increase its size during the camera alert. The idea is to quickly identify the speed limit of the camera.

I didn't understand the problem with variable speed limit areas. Shouldn't the speed_camera have the lowest maxspeed limit?

About the traffic light camera alert, of course that nobody wants to encourage illegal driving. Sometimes the camera is a just a trap to collect fines, for example when the yellow light duration time is too short or the light changes and the car stops a few centimeters over the pedestrian crossing.

Think of this alert as if it were a sign in the street announcing the camera:

image image

@polarbearing
Copy link

variable speed limit

We have a motorway tunnel which normally is 80 km/h and has cameras. The limit can be reduced to 60 or 40 depending on traffic condition or hazards in the tunnel. When the signs are changed, the camera will flash also when you exceed the temporary lower limit. There is some grace time so only vehicles who have seen the lower limit when entering the tunnel are flashed.

As for trapping with yellow being to short, that should be illegal and you should complain to your court if that happens. Here, there are prescribed yellow phases depending on the allowed speed (i.e. a 70 road has longer yellow than 50) that allows to react humanly.

@vshcherb vshcherb added the Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning label Sep 20, 2017
@littlehelper
Copy link

+1 for the proposal to show a max speed sign and a traffic light sign on the screen.
For me the max speed shown in the widget is too small and therefore difficult to see while driving.

@532910
Copy link
Contributor

532910 commented Oct 23, 2020

Speedcam limit is also should be announced.

AlexNcUa added a commit to AlexNcUa/OsmAnd that referenced this issue Oct 4, 2021
- RouteCalculationResult attachAlarmInfo method extended to add max speed to speed camera AlarmInfo taken either from speed camera point (preferred) or from RouteSegmentResult.
- WaypointHelper getMostImportantAlarm and announceVisibleLocations updated to attach actual distance to speed camera AlarmInfo.
- AlarmWidget extended with ability to show max speed for speed camera when available.
- VoiceRouter.announceAlarm extended with special handling for speed camera announcement to announce distance and max speed when available.
- CommandBuilder / JsCommandBuilder extended with new speedCameraAlarm method, which allows announce speed camera with distance and max speed.
- TestVoiceActivity extended to test speed camera with distance and max speed announcement.
AlexNcUa added a commit to AlexNcUa/OsmAnd that referenced this issue Oct 29, 2021
- Rework icons to be more consistent with american signs (separated icons added for american region) and less confusing with regular speed limit.
- Distance to camera visualization added.
- Additionally fix alarm icon re-sizing on large screens (related not only to speed cameras, icon re-sizing was missed, as result bottom text was out of icon area)
AlexNcUa added a commit to AlexNcUa/OsmAnd that referenced this issue Dec 21, 2021
- Add fallback for C_SPEED_CAMERA_ALARM in JsCommandBuilder
- Combine checks for text change / bottom text change in the AlarmWidget.updateInfo into one conditional statement and extract updateTextWidget / updateBottomTextWidget methods.
AlexNcUa added a commit to AlexNcUa/OsmAnd that referenced this issue Dec 21, 2021
- Refactor AlarmInfo to always accept maxSpeed in meters per second, and provide it either in meters per second or in accordance with requested speed constants settings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning
Projects
None yet
Development

No branches or pull requests

7 participants