System for navigating drivers to passengers based on start times of events
In one embodiment a transportation request specifying a pickup location is received. The transportation request is associated with an event to be attended by a subscriber to a transportation service. A start time of the event is determined. A data source associated with the event is monitored to detect whether the start time of the event has changed. A pickup time to pick up the subscriber for the event is determined wherein the pickup time is based at least in part on the start time of the event and the pickup location.
1. A method comprising:
receiving, at one or more servers, from a passenger computing device associated with a passenger of a transportation system, a transportation request indicating a pickup location and a destination location;
determining, via the one or more servers, that the transportation request corresponds to an event comprising an event location and an event start time;
in response to determining that the transportation request corresponds to the event, determining a pickup time for the transportation request to allow the passenger to arrive at the event location by the event start time;
selecting, via the one or more servers, from among a plurality of driver computing devices associated with the transportation system, a driver computing device associated with a driver to fulfill the transportation request to transport the passenger to the event location by the event start time;
receiving, from the passenger computing device, an updated transportation request indicating a modified pickup time;
releasing the selected driver based on the modified pickup time; and
selecting a new driver computing device from among the plurality of driver computing devices to fulfill the transportation request to transport the passenger to the event location by the event start time.
2. The method of claim 1 , wherein determining that the transportation request corresponds to the event comprises identifying event information for the event within the transportation request.
3. The method of claim 1 , wherein determining that the transportation request corresponds to the event comprises:
identifying event information within a calendar file associated with the passenger; and
determining a likelihood that the passenger is going to attend the event based on the event information within the calendar file.
4. The method of claim 1 , wherein determining that the transportation request corresponds to the event comprises:
accessing previous transportation requests and historical location data associated with the passenger; and
determining a likelihood that the passenger is going to attend the event based on the previous transportation requests and the historical location data.
5. The method of claim 1 , wherein determining that the transportation request corresponds to the event comprises:
accessing event information indicating the event location and the event start time; and
comparing the event location with the destination location and the event start time with a pickup time associated with the transportation request.
6. The method of claim 1 , further comprising temporarily limiting a number of transportation requests provided to the new driver computing device to ensure that the new driver computing device can fulfill the transportation request to transport the passenger to the event location by the event start time.
7. The method of claim 1 , further comprising:
determining, via the one or more servers, that the transportation request corresponds to the event comprising an event location and the event start time based on the destination location and a transportation request time of the transportation request from the passenger computing device.
8. A non-transitory computer readable medium comprising instructions that, when executed by at least one processor, cause a computing device to:
receive, at one or more servers, from a passenger computing device associated with a passenger of a transportation system, a transportation request indicating a pickup location and a destination location;
determine, via the one or more servers, that the transportation request corresponds to an event comprising an event location and an event start time;
in response to determining that the transportation request corresponds to the event, determine a pickup time for the transportation request to allow the passenger to arrive at the event location by the event start time;
select, via the one or more servers, from among a plurality of driver computing devices associated with the transportation system, a driver computing device associated with a driver to fulfill the transportation request to transport the passenger to the event location by the event start time;
receive, from the passenger computing device, an updated transportation request indicating a modified pickup time;
release the selected driver based on the modified pickup time; and
select a new driver computing device from among the plurality of driver computing devices to fulfill the transportation request to transport the passenger to the event location by the event start time.
9. The non-transitory computer readable medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine that the transportation request corresponds to the event by identifying event information for the event within the transportation request.
10. The non-transitory computer readable medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine that the transportation request corresponds to the event by:
identifying event information within a calendar file associated with the passenger; and
determining a likelihood that the passenger is going to attend the event based on the event information within the calendar file.
11. The non-transitory computer readable medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine that the transportation request corresponds to the event by:
accessing previous transportation requests and historical location data associated with the passenger; and
determining a likelihood that the passenger is going to attend the event based on the previous transportation requests and the historical location data.
12. The non-transitory computer readable medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine that the transportation request corresponds to the event by:
accessing event information indicating the event location and the event start time; and
comparing the event location with the destination location and the event start time with a pickup time associated with the transportation request.
13. The non-transitory computer readable medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to temporarily limit a number of transportation requests provided to the new driver computing device to ensure that the new driver computing device can fulfill the transportation request to transport the passenger to the event location by the event start time.
14. The non-transitory computer readable medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to:
determine, via the one or more servers, that the transportation request corresponds to the event comprising the event location and the event start time based on the destination location and a transportation request time of the transportation request from the passenger computing device.
15. A system comprising:
at least one processor; and
a non-transitory computer readable medium comprising instructions that, when executed by the at least one processor, cause the system to:
receive, at one or more servers, from a passenger computing device associated with a passenger of a transportation system, a transportation request indicating a pickup location and a destination location;
determine, via the one or more servers, that the transportation request corresponds to an event comprising an event location and an event start time;
in response to determining that the transportation request corresponds to the event, determine a pickup time for the transportation request to allow the passenger to arrive at the event location by the event start time;
select, via the one or more servers, from among a plurality of driver computing devices associated with the transportation system, a driver computing device associated with a driver to fulfill the transportation request to transport the passenger to the event location by the event start time;
receive, from the passenger computing device, an updated transportation request indicating a modified pickup time;
release the selected driver based on the modified pickup time; and
select a new driver computing device from among the plurality of driver computing devices to fulfill the transportation request to transport the passenger to the event location by the event start time.
16. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the system to determine that the transportation request corresponds to the event by identifying event information for the event within the transportation request.
17. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the system to determine that the transportation request corresponds to the event by:
identifying event information within a calendar file associated with the passenger; and determining a likelihood that the passenger is going to attend the event based on the event information within the calendar file.
18. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the system to determine that the transportation request corresponds to the event by:
accessing previous transportation requests and historical location data associated with the passenger; and
determining a likelihood that the passenger is going to attend the event based on the previous transportation requests and the historical location data.
19. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the system to determine that the transportation request corresponds to the event by:
accessing event information indicating the event location and the event start time; and
comparing the event location with the destination location and the event start time with a pickup time associated with the transportation request.
20. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the system to temporarily limit a number of transportation requests provided to the new driver computing device to ensure that the new driver computing device can fulfill the transportation request to transport the passenger to the event location by the event start time.