Traffic Violation Portal

Specification Document (WIP)

1. Vision Zero

2. The Solution

2.1 Documenting the Issues

2.2 Identifying the Violations

2.3 Identifying Infrastructure Problems

2.4 Complaining to Traffic Department

2.5 Effectiveness of the System

2.6 Gamification

3. Roles

3.1 Uploaders (Gladiators)

3.2 Analyzers (Scouts)

3.3 Moderators (Knights)

3.4 Complainants (Warlords)

3.5 Feedbacker (Sniper)

3.6 Developers and Testers (Wizards)

3.7 Traffic Police (Battle Mages)

4. Data Mining and Stat Generation

5. Credits System

5.1 Features of Credits System

5.2 Uploads

5.3 Violations

5.4 Infrastructure Issues

5.5 Other Credits Triggers

6. Moderation System

6.1 Double Moderation

6.2 Moderator Selection

6.3 Points

7. Report / Complaint Generation

7.1 Closing the Loop

8. Inclusion of authorities in the system

9. Challenges and Possible Solutions

9.1 Developing the system

9.1.1 Scalable

9.1.2 Secure

9.1.3 Finding Developers

9.2 Getting an Initial set of people

9.3 High Res Videos

9.4 Making the authorities take action on our complaints

10. Extending solution to address other Social Issues

11. Project Source

12. Version History

1. Vision Zero

Vision Zero is a road traffic safety project started in Sweden in 1997 which aims to achieve a highway system with no fatalities or serious injuries in road traffic. The project is then adopted in many developed / developing countries across the world.

Unfortunately, traffic safety is not being taken up seriously in our country and the consequence is we (India) tops the chart of fatalities related to road accidents. Few stats:

  1. India tops that List with 2,43,475 traffic related deaths / year
  2. In other terms, 1 in 4970 Indian die every year.
  3. For 10th year in a row, Tamil Nadu tops India in road accidents.

        “Lets not wait for Traffic Police, Politicians and Parties to start speaking about Vision Zero for India, since that might take a millenia. Let us take the initiative and let them follow, true to the essence of Democracy, of the people, by the people and for the people”

Please keep the Master Data Sheet opened, since various stats in the sheet will be referred from here.

2. The Solution

        Why the Government is not doing much in all this issues? Lack of funds and lack of Police Force, they would say (Is that for real is a matter of big debate). But its very true at least in Chennai, we can't afford to have a Policeman in each and every traffic signal. Also, we can't expect a single Policeman to impose fine on all the 100s of violators. This is where our solution fits in. Read on.

The prototype of the Portal shall be found @ http://grayfaceofindia.in/modules/traffic/

2.1 Documenting the Issues

The members of this system gets into the roads at critical points like signals, junctions, etc., and video record all the violations. This video recording prumocess will happen throughout the city at various times, based on our base member strength. Then all this videos are uploaded in Youtube and fed into our system with all meta data like place of recording, time of recording, etc.,

2.2 Identifying the Violations

        Then another group of members will go through the uploaded videos and note down the registration number of all vehicles of the violators. The violation type, vehicle type and they duration in which the violation occurred are also noted down and this meta-data is fed into the system.

2.3 Identifying Infrastructure Problems

        We are not just identifying the violations by the public. But also the infrastructure problems like damaged road, non working signals, missing stop lines are also identified and fed into the system.

2.4 Complaining to Traffic Department

        Every month, a complaint report is generated by System, that lists out all Traffic Infrastructure problems and all traffic violators in last one month. The complaint is then sent to Traffic Department to take action, which is then followed up with RTIs for proper action.

2.5 Effectiveness of the System

2.6 Gamification

        We gamify the whole system to encourage the members and keep them engaged. For each activity in the system, be it uploading videos, moderating a violation, sending generated complaint to Traffic Department, points are awarded.

  1. There will be leaderboards, displaying the top contributors of the week / month.
  2. There will be badges given to the members on achieving certain milestones like Uploading 100 videos, finding 100 bikers without helmet, spotting 25 Missing Spot lines, etc., The point system is completely explained in another section below.

3. Roles

3.1 Uploaders (Gladiators)

They are our front line battle hardened commandoes. They get into the roads and record the violators. As the technology and system develops, they will be gladly replaced by fixed Cameras (Autobots), which will function with more accuracy, stability and round the clock.

Anyone who has an account in the system can take up this role.

3.2 Analyzers (Scouts)

        They are our behind the scene soldiers. They just sit behind the computer and analyze all the videos uploaded by Uploaders and identify all the violations in the videos.

  1. For Traffic Violations, they extract this 4 pieces of information for each violation and feed into the system:
  1. Registration Number of Violating vehicle
  2. Type of the Vehicle
  3. Type of the Violations
  4. Duration in which the violation occurred in the whole video.
  1. For Infrastructure problems, they just post what sort of issue is found in the video.

        Extracting the Registration number from the Number plate can be automated by any algorithms (R&D)

Anyone who has an account in the system can take up this role.

3.3 Moderators (Knights)

        They start as either Uploaders / Analyzers and once they reached a certain contribution level, they are promoted as Moderators. They are the quality keepers of the system.

Since the content involves real people, causing real money fines to them, there is no place for errors. Every content entry into the system, be it a video or a violation entry, have to be thoroughly checked and approved by 2 moderators.

Not anyone who has an account can moderate. Only members with certain threshold of points can moderate.

3.4 Complainants (Warlords)

        Each region will have a warlord. In Chennai, there will be 5 warlords in charge of 5 traffic regions in Chennai. Every month they generate report from the system on all violations / infrastructure problems that happen or found in their region and file a complaint with the Traffic Department.

        They follow up the complaints with the Traffic Department and see to it, no violators go unpunished and no road issues remain unfixed (at least ideally). This is going to be the toughest job in the whole system.

        Complainants will be selected out of the system (Atleast for now)

3.5 Feedbacker (Sniper)

        Once the Complainant received response from the Traffic Department that fine has been imposed or action has been taken. The Feedbacker updates the corresponding complaint with action taken data.

        Feedbackers will be selected out of the system (Atleast for now)

        Can this role be merged with moderators? (who are with the sytem for a long time and trustable)

3.6 Developers and Testers (Wizards)

        They are the blood and nerves of the System. They creates the whole system from this blueprint document. Keep it working, make sure nothing gets broke, when the system scales up and more more.

3.7 Traffic Police (Battle Mages)

        The future plan is replacing Complainant / Feedbacker combo with Traffic officials themselves. When a complaint is approved by a moderator, it goes directly to the Traffic Police in charge of that particular region. He / She imposes fine on the violators and updates the status in the system.

4. Data Mining and Stat Generation

With all the raw data that we collect, meaningful information need to be identified and possibly given to the media. Some sample data sets that can be mined and generated include:

  1. Potential revenue that could be generated in each City / Place every month, if fine is imposed on all the violators. (Initial State, if the authorities didn’t take action on our complaints)
  2. Revenue generated in each City / Place every month by fines imposed through the system.
  3. Number of `No Helmet` violations in each City.
  4. Number of Videos / Violations in each City.
  5. Number of `Hit / Accidents` happening in each City.
  6. Number of vehicles who don’t reside in their registered address in each City.

5. Credits System

Inspired by BOINC Credit System

        For each action in the system from Uploading videos, identifying violations, sharing on social networks, moderating, etc., Credits (points) are awarded. Each and every user is associated with an Organization and a Region. And so the Credits are always awarded to these three Entities:

5.1 Features of Credits System

  1. Leaderboards can be generated based on Individual users, Organizations and also the regions.
  2. The leaderboards should also be able to display credits on last week, last month and overall.
  3. Credits have 2 derived factors: Total Credits and Average Credits. (Refer `Credits - Test Data` sheet)
  1. Total Credits - sums up all the credits earned by an entity from the Date of Joining.
  2. Average Credits - just simple average of the credits earned by an entity from the Date of Joining (Formula for Average Credit is not right, have to modify it)
  1. Credits are awarded to the members only when the moderator approves the video / violation.

5.2 Uploads

For each video upload, the uploader is awarded points that is equal to the duration of the video in seconds. Then for each violation identified in that video, 20% of the violation points goes to the Uploader, while 100% of the violation points goes to the Analyzer.

Uploaders points for a video = [Duration of Video] + 0.2 * [sum of violation points]

5.3 Violations

        For each violation, the points are awarded as per the following table:

No

Violation Type

Fine

Points

1

Jumping Signal [driving at red light]

100

10

2

Crossing Stopline / Pedestrian Crossing

100

10

3

Driving without Helmet

100

10

4

Using Mobile Phones while driving

100

10

5

Driving-on Footpath

100

10

6

Number Plate Offences

100

10

7

Parking violations

100

10

8

Overloadîng a vehicle beyond extent limit

2000

200

9

Lack of proper maintenance and structure of vehicle

1000

100

10

Charging Excess Fare

100

10

11

Refusal to ply for Hire

100

10

12

Moving against One-Way

100

10

13

Improper use of Headlights

100

10

14

Hom offences

100

10

15

Misbehavior with Passenger

100

10

16

Overtaking dangerously

100

10

17

Driving at a speed exceeding as mentioned in MVA:12

400

40

18

Dangerous Lane cutting

100

10

19

Dangerous DI" Reckless Driving

1000

100

20

Accidental Offences

500

50

21

Illegal racing on road

500

50

5.4 Infrastructure Issues

No

Issue

Points

1

Signal Not Working

500

2

No Stop Line

250

3

Damaged road - Severe

500

4

Damaged road - Light

250

5

Encroachment - Small

100

6

Encroachment - Medium

200

7

Encroachment - Large

400

8

No Median

50

5.5 Other Credits Triggers

No

Event

Points

Frequency

1

Signup

100

Once

2

Share Portal in FB

50

once in a week

3

Share Portal in Twitter

50

once in a week

4

Share Portal in LinkedIn

50

once in a week

5

Share Portal in Google Plus

50

once in a week

6

Share Video in FB

violationPoints * 0.01

once in a week

7

Share Video in Twitter

violationPoints * 0.01

once in a week

8

Share Video in LinkedIn

violationPoints * 0.01

once in a week

9

Share Video in Google Plus

violationPoints * 0.01

once in a week

10

On becoming a Moderator

1000

Once

11

On 10 Uploads

600

Once

12

On 100 Uploads

8000

Once

13

On 1000 Uploads

100000

Once

14

On 10 Violation findings

200

Once

15

On 100 Violation findings

3000

Once

16

On 1000 Violation findings

40000

Once

17

On 10000 Violation findings

500000

Once

18

On 100000 Violation findings

6000000

Once

Moderator actions and their Credits are explained in the corresponding section.

6. Moderation System

The accuracy of the content should be 100%. Our long term vision is to enable Traffic Department automate the process of identifying violators / traffic issues and imposing fine on them. By then, no one should sue Traffic Department because of some misinterpretation / mis information in our system.

6.1 Double Moderation

        Every content should be moderated twice. And only when 2 of the moderators agree with either acceptance or rejection of the content, the decision is finalized. When a conflict arise between the first two moderators, it is again passed to next 2 moderators, until they agree upon their choice of either accepting or rejecting.

        Moderators will have additional controls visible in the portal to facilitate moderation.

6.2 Moderator Selection

        Any Uploader / Analyzer when they reach an average Credit of 200 (value subjected to change), gets into the role of Moderator. The points awarded for approving / rejecting content should be such that, without much effort, the moderator should be able to retain the minimum Average Credit. Because whenever the minimum Average Credit, goes below the threshold 200, the moderator loses his / her role.

6.3 Points

[Will be updated later, once the basic system without Moderation is up and running]

7. Report / Complaint Generation

The Complainants when logged in get provisions to generate reports based on the violations. They can apply filters and specify specific time frames and regions and generate reports based on those filters. The Point system doesn’t apply to them.

The generated complaints are then sent to Traffic Department for action. Its the complete responsibility of the complainant to make the officials take action on the complaint, be it through regular visits to Police Stations, or through RTI followup, etc.,

7.1 Closing the Loop

        Once action has been taken by the Department, the action taken report is obtained, probably through RTI and Feedbacker updates the violation entries with status updates like Fine Imposed, Can’t Find Vehicle Owner, Can’t Impose fine for so and so reason, etc.,

        Thus this step completes the full loop from identification of violation to imposing fine.

        Point to Brainstorm: How do we select Feedbacker? or Is it fine to merge the roles of feedbacker with the moderators?

8. Inclusion of authorities in the system

In the long run, the idea is to equip the traffic officials with the right system to automate and ease their work. We will strive to take the system into the governance. The design of the system will evolve to accommodate this requirement.

The basic idea is to create accounts for the Department official themselves, let them login and see the reported problems in their Jurisdiction. They can take action on the complaint and also close the complaint in our system with proper feedback like Fine Imposed, Can’t with Vehicle Owner because of outdated data in RTO, etc.,

If possible, we will link RTO database and let Police search for vehicle owner’s details just by typing in their Vehicle Registration Number. We will create a completely new requirement specification document, once we evolve to this phase. But this is one of our end goals, to automate the traffic department.

9. Challenges and Possible Solutions

9.1 Developing the system

        Yes, developing this whole idea itself is one of the biggest challenges, mainly because of 9.1.3

9.1.1 Scalable

The system should be scalable. It starts with a City and it should scale up, to cover the whole country. It might not end there. The system could be used by those from any part of the world, where this traffic problem happens.

9.1.2 Secure

        We are saving real people’s real data, be it the members details or violators details. Nothing should be tampered with or go out.

9.1.3 Finding Developers

        I would say we are IT Hub of the whole world, providing IT support to all banks / Corporates around the world. So the best minds are already here. But finding the right persons, who share similar intent regarding Traffic Problems might be a challenge.

9.2 Getting an Initial set of people

        We might have a starting problem in finding people who could get into roads and take videos and also people who could put their valuable time in analyzing the videos. Once the system is setup, we will visit all NGOs in Chennai and take a seminar on the whole idea. By this way, we could be able to gather initial supporters. But I believe, once the activity in the system crosses certain threshold, people would join in automatically thanks to our excellent Leaderboard idea (I believe).

9.3 High Res Videos

        The videos taken in mobile till now are of maximum 1080p, that is supported by youtube. But when we go with superior cameras, with even better resolutions, Youtube won’t help much. Ideal solution is to buy separate server space, which would be costly.

9.4 Making the authorities take action on our complaints

        Yes, This is not an easy task, based on our past experience. But in the past, we just sent all our complaint only through Registered Post. Didn’t have direct face to face conversations with the officials, which we have plan to do here after.

10. Extending solution to address other Social Issues

        The system can also be tweaked to address other social issues which can be documented by a video / photo. Let it be garbage on road, broken street lights, overflowing sewage or anything. It can be documented and registered in the system. All similar issues can then be aggregated into a report and sent to the respective department to take action.

11. Project Source

        The complete project will be put in Public Domain under GNU GPL v3 and the related media under CC 3.0. More Technical details will be documented in a separate Technical Requirement document.

12. Version History

Version

Date

Title

1.0

June 26, 2014

First Draft of the Complete System