Thursday, October 8, 2015

Uber AirPort Virtual Taxi Queue



The New System Uber Is Implementing at Airports Has Some Drivers Worried
Initially, the queue system went by proximity, matching the customer to the nearest driver when they request a ride. But Uber has been slowly updating the system to a first in first out policy, so as soon as a driver enters a specified area near the airport they are placed in a virtual queue.

In an email to drivers, Uber explained “your location within the shaded area does not affect your position in queue. If a rider cancels, you'll remain at the front of the queue, and if you leave the shaded area, reject or cancel a trip, or turn off your phone you will go to the back of the queue.” Drivers were warned not to park on any private property while waiting for a ride request.

http://taxi-news.co.uk/uber-go-londons-airports/
Cars are booked in automatically as the enter the parameters of the system.
The driver is then given 15 seconds to accept. After acceptance, they are allocated a queue position number.
The company boasts that because of the amount of PR, publicity and advertising planned, drivers won’t have to wait long, unlike the Feeder Park where drivers often do four hours.

How Uber is Getting Around DC Airport Restrictions [Updated]
The driver has to call the user to specify exactly where they will meet and what the destination is, but it does at least make it possible to get an Uber ride, if with more than average difficulty. Uber drivers aren't going to want to wander around looking for a passenger, especially if it involves the toll road to Dulles. 

https://www.reddit.com/r/uberdrivers/comments/3biuj8/virtual_airport_queue/
http://uberpeople.net/threads/airport-virtual-queues.22182/

Labels

Review (572) System Design (334) System Design - Review (198) Java (189) Coding (75) Interview-System Design (65) Interview (63) Book Notes (59) Coding - Review (59) to-do (45) Linux (43) Knowledge (39) Interview-Java (35) Knowledge - Review (32) Database (31) Design Patterns (31) Big Data (29) Product Architecture (28) MultiThread (27) Soft Skills (27) Concurrency (26) Cracking Code Interview (26) Miscs (25) Distributed (24) OOD Design (24) Google (23) Career (22) Interview - Review (21) Java - Code (21) Operating System (21) Interview Q&A (20) System Design - Practice (20) Tips (19) Algorithm (17) Company - Facebook (17) Security (17) How to Ace Interview (16) Brain Teaser (14) Linux - Shell (14) Redis (14) Testing (14) Tools (14) Code Quality (13) Search (13) Spark (13) Spring (13) Company - LinkedIn (12) How to (12) Interview-Database (12) Interview-Operating System (12) Solr (12) Architecture Principles (11) Resource (10) Amazon (9) Cache (9) Git (9) Interview - MultiThread (9) Scalability (9) Trouble Shooting (9) Web Dev (9) Architecture Model (8) Better Programmer (8) Cassandra (8) Company - Uber (8) Java67 (8) Math (8) OO Design principles (8) SOLID (8) Design (7) Interview Corner (7) JVM (7) Java Basics (7) Kafka (7) Mac (7) Machine Learning (7) NoSQL (7) C++ (6) Chrome (6) File System (6) Highscalability (6) How to Better (6) Network (6) Restful (6) CareerCup (5) Code Review (5) Hash (5) How to Interview (5) JDK Source Code (5) JavaScript (5) Leetcode (5) Must Known (5) Python (5)

Popular Posts