Use enforcement tolerance for better speed limit UX #5640

New issue

Open

opened 2023-08-03 01:16:16 +00:00 by euf · 0 comments

euf commented

2023-08-03 01:16:16 +00:00

(Migrated from github.com)

Feature request rationale
Some countries have well-documented tolerance levels for speed limit enforcement. For example, in Russia it is 20 km/h, so most of the drivers would be going 100 km/h on a highway with a 90 km/h limit. In Organic Maps, these drivers would be notified of an exceeded speed limit. This could be seen as an unwanted distraction by those who keep up with the traffic but still wish to know whether this may lead to legal consequences.

Describe the solution you would like
I propose to compile a database for speed limit enforcement tolerance levels by country and region. Using this data, I suggest moving from two-state speedometer UI towards three-state, so that users can clearly see if they are below speed limit / below enforcement tolerance / above those.

The main challenge would be implementing region-specific logic. Consider the following enforcement tolerances gatherd from https://en.wikipedia.org/wiki/Speed_limits_by_country and other sources:

Russia has the simplest "20 km/h"
Croatia has "10 km/h up to 100 km/h; 10% over"
Indonesia has "10% within towns; 20% of speed limit in toll roads"
Australia has "3 km/h in Victoria; 10% in other states"
China has "20% in highways; 50% within towns and outside built up area"
Cyprus has "10% + 2 km/h up to 100 km/h; 20% over"
USA has "5 MPH in Colorado, Florida, Michigan, Missouri, Pennsylvania, New Mexico, North Dakota, and Wyoming; 10 MPH in Kansas, Kentucky, Oklahoma, Montana, and West Virginia; and 15 MPH in Georgia"

This leaves us with many parameters such as country/state/province, urban/rural area, motorway/trunk/primary/etc, regular/toll road, and other conditionals. It's also worth noting that ideally tolerances should be double-checked with up-to-date local sources, since Wikipedia and other websites may be outdated.

Describe alternatives you have considered
Several apps such as Waze and Yandex allow users to specify speeding threshold manually. While being a good starting point, its main use case is to help staying below enforcement tolerance. If we wish to keep settings as simple as possible, determining the threshold automatically would be a better UX.

Additional context
While working on some mockups regarding #2968, I came up with a possible visual representation for an "above limit, below tolerance" state (the one in the middle):

As you can see, it works really well with both Vienna-convention and MUTCD-style signs. That would be nice for displaying proper shapes of the speed limit backgrounds (as Google and Apple do).

**Feature request rationale** Some countries have well-documented tolerance levels for speed limit enforcement. For example, in Russia it is 20 km/h, so most of the drivers would be going 100 km/h on a highway with a 90 km/h limit. In Organic Maps, these drivers would be notified of an exceeded speed limit. This could be seen as an unwanted distraction by those who keep up with the traffic but still wish to know whether this may lead to legal consequences. **Describe the solution you would like** I propose to compile a database for speed limit enforcement tolerance levels by country and region. Using this data, I suggest moving from two-state speedometer UI towards three-state, so that users can clearly see if they are below speed limit / below enforcement tolerance / above those. The main challenge would be implementing region-specific logic. Consider the following enforcement tolerances gatherd from https://en.wikipedia.org/wiki/Speed_limits_by_country and other sources: - Russia has the simplest "20 km/h" - Croatia has "10 km/h up to 100 km/h; 10% over" - Indonesia has "10% within towns; 20% of speed limit in toll roads" - Australia has "3 km/h in Victoria; 10% in other states" - China has "20% in highways; 50% within towns and outside built up area" - Cyprus has "10% + 2 km/h up to 100 km/h; 20% over" - USA has "5 MPH in Colorado, Florida, Michigan, Missouri, Pennsylvania, New Mexico, North Dakota, and Wyoming; 10 MPH in Kansas, Kentucky, Oklahoma, Montana, and West Virginia; and 15 MPH in Georgia" This leaves us with many parameters such as country/state/province, urban/rural area, motorway/trunk/primary/etc, regular/toll road, and other conditionals. It's also worth noting that ideally tolerances should be double-checked with up-to-date local sources, since Wikipedia and other websites may be outdated. **Describe alternatives you have considered** Several apps such as Waze and Yandex allow users to specify speeding threshold manually. While being a good starting point, its main use case is to help staying below enforcement tolerance. If we wish to keep settings as simple as possible, determining the threshold automatically would be a better UX. **Additional context** While working on some mockups regarding #2968, I came up with a possible visual representation for an "above limit, below tolerance" state (the one in the middle): <img src="https://github.com/organicmaps/organicmaps/assets/11754264/279f5dc7-f316-4574-a4e2-466b96567978" width=30%> <img src="https://github.com/organicmaps/organicmaps/assets/11754264/eaba7f88-a6e3-4d30-ad88-c0fb76993eb2" width=30%> <img src="https://github.com/organicmaps/organicmaps/assets/11754264/5c2b4538-c0e4-4be6-a68b-d517b7fa79fd" width=30%> <img src="https://github.com/organicmaps/organicmaps/assets/11754264/5fb45af5-f853-4d91-adec-cba14a835a8d" width=30%> <img src="https://github.com/organicmaps/organicmaps/assets/11754264/c15265f0-e6ee-4810-9fd9-58b603c32261" width=30%> <img src="https://github.com/organicmaps/organicmaps/assets/11754264/6bf3c917-bb1e-4329-ba53-2ae7c834f870" width=30%> As you can see, it works really well with both Vienna-convention and MUTCD-style signs. That would be nice for displaying proper shapes of the speed limit backgrounds (as Google and Apple do).

👍 1

This repo is archived. You cannot comment on issues.