US20090049044A1

US20090049044A1 - Method for providing a searchable, comprehensive database of proposed rides

Info

Publication number: US20090049044A1
Application number: US11/893,085
Authority: US
Inventors: Clyde Mitchell
Original assignee: Individual
Current assignee: Individual
Priority date: 2005-02-16
Filing date: 2007-08-13
Publication date: 2009-02-19
Also published as: US9111315B2; US20130006959A9; US20150356470A1

Abstract

A method is disclosed that matches travelers for ride sharing according to personal preferences, such as smoking, music, allergies, drive sharing, expense sharing, number of riders, and gender, as well as basic trip details. In preferred embodiments the method is accessed via a website, and trips can be over any distance and/or by any land, air, or water vehicle. Embodiments require traveler verification by a payment and/or other means, and/or require travelers to supply identifying information. Matches can take into account ratings of travelers by other travelers. Confirmations, reminders, and ride sharing advice can be sent to riders before scheduled rides, and information about a shared ride can be sent to a non-rider. Fees can be charged, and credited if no match is accepted. Communications can be secure and requesting and/or accepting matches can be logged. Origin and/or destination radii can be automatically enlarged to provide more matches.

Description

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a United States filing entitled to the benefit of International Patent Application Number WO06088703A2 entitled “METHOD FOR PROVIDING A COMPREHENSIVE, SEARCHABLE DATABASE OF PROPOSED TRIPS”, filed Feb. 7, 2006, and published internationally on Aug. 24, 2006, herein incorporated by reference.
International Patent Application Number WO06088703A2 is entitled to the benefit of U.S. Provisional Patent Application No. 60/653,374, entitled “METHOD FOR PROVIDING A COMPREHENSIVE, SEARCHABLE DATABASE OF PROPOSED TRIPS”, filed Feb. 16, 2005, herein incorporated by reference.

FIELD OF THE INVENTION

The invention generally relates to ride sharing, and more specifically to methods of arranging for sharing of rides.

BACKGROUND OF THE INVENTION

Services and methods are known that match travelers who wish to make similar trips, so as to take advantage of the economic and environmental benefits of ride sharing. However, these services typically do not take into consideration the riders' personal traveling preferences. For example, they do not allow a rider to specify a gender, smoking preferences, music preferences, or to specify different departure times. This leads to unpredictable and sometimes unpleasant ride sharing experiences, especially when the methods are applied to individual trips as compared to regular, frequently repeated, short trips such as commuting to work and back.
In addition, known systems and methods for matching travelers are typically restricted to matching automotive travelers who commute within a local region. They are typically focused on “commuting areas” around cities and are therefore best suited for car pooling and local commuting. This does not benefit travelers who wish to take trips spanning a particular region, country or continent, and who may wish to share modes of transportation other than automobiles.

SUMMARY OF THE INVENTION

A method is claimed for identifying ride sharing matches according to personal ride sharing preferences as well as basic ride requirements, so as to ensure a more positive ride sharing experience. Preferred embodiments of the method also allow for travel over any distance, using any desired type of vehicle.
The method includes establishing a database on a server, the database being capable of containing ride requirements and personal ride sharing preferences, providing to travelers access to the database, the access being provided in preferred embodiments through a website, and accepting from travelers ride requirements and personal ride sharing preferences. In preferred embodiments, the personal ride sharing preferences can include expense sharing preferences, gender preferences, departure time preferences, pick up location preferences, drop off location preferences, music preferences, allergy avoidance preferences, preferences for accommodating disabilities, pet related preferences, and preferences for accommodating special needs.
The method further includes identifying a ride sharing match based on the ride requirements and personal ride sharing preferences of travelers included in the ride sharing match, and providing to all travelers included in the ride sharing match access to information regarding the ride sharing match.
In preferred embodiments the method also includes verifying the identity of a traveler before accepting ride requirements and personal ride sharing preferences from the traveler and/or before identifying ride sharing matches that include the traveler. In some of these preferred embodiments, verifying the identity of the traveler includes accepting from the traveler a user ID and a password provided by the traveler using a computer, a wireless access device, or some other communication device. In other of these preferred embodiments verifying the identity of the traveler includes receiving a payment so as to establish the credibility of the traveler, or at least of someone associated with the traveler who is willing and able to make payments.
In some preferred embodiments, the method includes obtaining information from a traveler that can be used by other travelers to verify the identity of the traveler before accepting ride requirements and personal ride sharing preferences from the traveler, and/or before identifying ride sharing matches that include the traveler. And in some of these embodiments the identifying information includes at least one of: personal information, including an address, a telephone number, an email address, a date of birth, a gender, a driver's license number, a driver's license state of issue, and/or other personal information; vehicle information, including a vehicle make, a vehicle model, a vehicle year of manufacture, a vehicle license plate number, a vehicle registration, a vehicle owner name, a vehicle color, a description of vehicle condition, and/or other vehicle information; and student information, including a student ID number, a name of a college attended by the traveler, a name of a college campus attended by the traveler, and/or other student information.
In certain preferred embodiments the method includes accepting from travelers rating information pertaining to other travelers based on ride sharing experiences. In some of these preferred embodiments rating information is provided to travelers pertaining to other travelers with whom they share a ride sharing match, rating information is taken into account when identifying ride sharing matches, and/or preferences regarding acceptable rating information is considered when matching travelers for ride sharing.
in preferred embodiments, ride requirements and personal ride sharing preferences accepted from a traveler can include the capacity of a vehicle to accommodate a plurality of riders and/or preferences regarding sharing a ride with a plurality of other travelers. And in some preferred embodiments ride requirements and personal ride sharing preferences accepted from a traveler can include ride requirements and personal ride sharing preferences for a first ride from an origin to a destination and ride requirements and personal ride sharing preferences for a second ride from the destination back to the origin.
In certain preferred embodiments, when a ride sharing match is accepted by at least two travelers, confirmation is sent to all travelers who have accepted the ride sharing match, suggestions regarding practical issues of ride sharing are sent to all travelers who have accepted the ride sharing match, and information is sent regarding the ride sharing match to someone not included in the ride sharing match upon request of a traveler who has accepted the ride sharing match. And in some preferred embodiments reminders are sent to travelers who have accepted a ride sharing match a day before, a week before, and/or at other specified intervals of time before the agreed upon date and time for the shared ride.
In preferred embodiments, ride requirements and personal ride sharing preferences accepted from a traveler are compared at specified time intervals with ride requirements and personal ride sharing preferences accepted from other travelers, so as to identify ride sharing matches.
In certain preferred embodiments at least some of the communications between travelers and the database and between travelers and other travelers are secure communications. And in some preferred embodiments a record is maintained of ride requirements and personal ride sharing preferences accepted from travelers, of identified ride sharing matches including travelers, and/or of ride sharing matches accepted by travelers.
In preferred embodiments ride requirements and personal ride sharing preferences accepted from travelers can be for rides that use any type of vehicle, including a ground vehicle, an aircraft, and/or a water vessel, and for rides that cover any desired distance.
In some preferred embodiments, radii are calculated about specified departure and/or destination points, and a search is made for compatible ride sharing information with departure and destination points within those radii. And in some of these embodiments one or both of the calculated radii are automatically enlarged until a specified minimum number of ride sharing matches is identified.
In certain preferred embodiments a notifying message is sent to a traveler from whom ride requirements and personal ride sharing preferences have been accepted whenever potentially compatible information is subsequently accepted from another traveler.
In some preferred embodiments travelers are required to pay a fee so as to use the method, and in some of these embodiments at least part of the fee is credited back to the traveler if his or her use of the method does not result in acceptance of a minimum number of ride sharing matches.
And in preferred embodiments, ride requirements and personal ride sharing preferences accepted from a traveler can be changed at any time before a ride sharing match based on the ride requirements and personal ride sharing preferences is accepted by the traveler and by at least one other traveler.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional diagram that illustrates the method of the present invention;

FIG. 2A presents the first of two preferred embodiment website screens that are used by a traveler to register with the website and to supply identifying and other personal information;

FIG. 2B presents the second of two preferred embodiment website screens that are used by a traveler to register with the website and to supply identifying and other personal information;

FIG. 3A presents the first of a series of three website screens from a preferred embodiment that are used by a traveler to provide information regarding a trip being posted by the traveler;

FIG. 3B presents the second of a series of three website screens from a preferred embodiment that are used by a traveler to provide information regarding a trip being posted by the traveler;

FIG. 3C presents the third of a series of three website screens from a preferred embodiment that are used by a traveler to provide information regarding a trip being posted by the traveler;

FIG. 4 presents a preferred embodiment website screen that is used by a traveler to provide information regarding a trip that the traveler wishes to make by riding in someone else's vehicle;

FIG. 5 presents an example of a report of possible ride sharing matches presented to a traveler by a preferred embodiment;

FIG. 6 illustrates a preferred embodiment in which ratings provided by travelers regarding other travelers with whom they have shared rides are considered when seeking ride sharing matches;

FIG. 7A presents a preferred embodiment website screen that can be used by a traveler to rate other riders who previously shared rides posted by the traveler;

FIG. 7B presents a preferred embodiment website screen that can be used by a traveler to rate other riders with whom the traveler shared rides that were not posted by the traveler;

FIG. 8 illustrates a preferred embodiment in which searches for ride sharing matches that do not immediately result in an accepted match are repeated after a specified amount of time, such as a day or an hour;

FIG. 9 illustrates a preferred embodiment in which a fee is charged for use of the method, radii are calculated about the specified origin and destination locations for a trip, and the radii are enlarged if an insufficient number of ride sharing matches are found; and

FIG. 10 illustrates a preferred embodiment in which a traveler who has requested a ride sharing match is alerted each time another traveler submits a potentially compatible ride sharing request.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIG. 1 illustrates a typical application of the method of the present invention. A database 100 is provided on a server, the database being able to contain information about travelers wishing to share rides. In the embodiment of FIG. 1, the database 100 is made available on an internet website. A first traveler 102 is planning a trip using his or her vehicle, and wants to be matched with at least one other traveler wishing to make a similar trip and interested in sharing the ride. The first traveler, who has previously registered with the website and has previously supplied identifying and other personal information, logs onto the database 102, using a computer, a web-enabled wireless device, or any other web-enabled device, and “posts” the ride 104. Together with information about the planned trip, the first traveler also provides information 106 regarding his or her personal preferences relating to the trip, such as expense sharing preferences, gender preferences, departure time preferences, pick up location preferences, drop off location preferences, music preferences, allergy avoidance preferences, preferences for accommodating disabilities, pet related preferences, and preferences for accommodating special needs.
A second traveler 108 wishes to make a similar trip, but prefers to share a ride in someone else's vehicle rather than using his or her own vehicle. The second traveler 108, who has also previously registered with the website and has also previously supplied identifying and other personal information, logs onto the database 100, and requests a ride 110. The second traveler provides information about the trip that he or she wishes to make, and also provides information 112 regarding his or her personal preferences relating to the trip.
Upon searching the database 100 for matches between travelers who have provided compatible ride sharing information, including compatible personal preferences, the server identifies a match 114 between the first traveler 102 and the second traveler 108. The first traveler 102 and the second traveler 108 are then notified 116, 118 that their ride sharing information has been matched, details are provided to each regarding the information supplied by the other, and each indicates to the website that they are willing to accept the match 120.
The website proceeds to notify 122, 124 the first traveler 102 and the second traveler 108 that the match has been accepted. In addition, if requested by either of the travelers, details regarding the trip are sent to other individuals 126, such as a friend, a parent, a spouse, and such like.
FIG. 2A presents a website screen from a preferred embodiment that is used by a traveler to register with the website and to supply identifying and other personal information. The screen includes a personal information section 200 that includes fields 202 for supplying name, address, telephone, date of birth, gender, and driver's license information. The screen also includes a section 204 that includes fields 206 where a student can supply student information, and a security section 208 where a user id and email address are entered 210. In some preferred embodiments the traveler is also required to make one or more payments. This step provides assurance that the information is legitimate and belongs to the traveler or at least someone associated with the traveler.
The registration process continues on a second screen of the same preferred embodiment, illustrated in FIG. 2B. A password section 212 includes fields 214 for supplying a password and a “secret question” and a corresponding answer to be used in the event that the traveler forgets his or her password. The screen also includes a vehicle information section 216 where the traveler can supply information 218 relating to vehicles that can be used for posted trips, such as an automobile make, model, registration number, and such like. A section for indicating types of vehicles 220 is also included. Each time a different vehicle type is selected 222, a different set of vehicle information fields 218 is presented, thereby allowing a traveler to supply information about multiple vehicles.
FIG. 3A, FIG. 3B, and FIG. 3C present website screens from a preferred embodiment that are used by a traveler to provide information regarding a trip being posted by the traveler. The screen illustrated in FIG. 3A includes a departure date and time section 300 and a section where information is provided regarding the number of riders 302 that can be accommodated and the departure and arrival regions 304. A field is also provided 306 where the traveler can indicate details regarding how the expenses of the trip should be shared, and a checkbox 308 can be selected to automatically display a similar screen with the departure and arrival regions reversed, so as to facilitate posting a return trip. The process continues on the screen shown in FIG. 3B, which includes sections regarding the posting traveler's driver's license information 310, as well as ride sharing preferences such as who will drive 312, smoking preferences 314, and the desired gender(s) 316 of the other riders. FIG. 3C includes a field 318 where other, custom ridesharing preferences and requirements can be provided, as well as a section 320 where vehicle information is supplied.
FIG. 4 presents a preferred embodiment website screen that is used by a traveler to provide information regarding a trip that the traveler wishes to make by riding in someone else's vehicle. The screen accepts information regarding when the traveler wishes to depart 400 and how flexible the traveler can be regarding the departure date, as well as the departure area 402 and arrival area 404 and ride sharing gender preferences 406. Similar screens accept information regarding other ride sharing preferences, such as smoking, music, allergies, and such like.
In preferred embodiments, once a traveler has logged into the website and supplied information regarding a desire to share a ride, including ride sharing preferences, a search is initiated and a report of possible ride sharing matches is generated. An example from a preferred embodiment is illustrated in FIG. 5. Rows in the report represent individual ride sharing matches, and columns in the report indicate the departure 500 and destination 502 cities, the date of the ride 504, the ride sharing gender preference 506, as well as hypertext links that can be activated to display more details 508 and preferences regarding a potential ridesharing partner, and to accept a ridesharing match 510. In some preferred embodiments, if the number of identified ride sharing matches is not sufficient, for example if at least 10 potential ride sharing matches are not found, the radii around the departure location and/or the arrival location are enlarged until a specified minimum number of matches is found.
In some preferred embodiments, once a ride sharing match has been accepted a set of ride sharing suggestions is supplied to each traveler included in the match. In various preferred embodiments, the ride sharing suggestions provide advice as to how to make the ride go smoothly and how to avoid any potential hazards associated with sharing a ride with strangers. An example from a preferred embodiment follows:
On the Day of the Ride:

- 1. Each rider, and the rider with the vehicle, should wait at least fifteen minutes at any pick-up spot. After fifteen minutes, they do not have to wait any longer.
- 2. Try your best to call the other riders if you expect to be more than five minutes late, so they know that you are still coming.
- 3. The rider with the vehicle and the other authorized riders should make sure that no other person rides with them because this can raise safety and security concerns. The rider with the vehicle, as the vehicle owner (or as the one given control over the vehicle), should not let unauthorized persons participate in the ride. Letting others participate would be unfair to the authorized riders and will result in a substantial downgrading of your rating. Any others who attempt to participate in the ride should be told that they cannot participate and should be left behind.
- 4. If any other person not covered by a Confirmation is allowed to participate in the trip, then each rider should seriously consider skipping the ride. This should not happen in most cases, but it could happen. If it does happen, we cannot give you any assurance about the identity of the other traveler, and therefore we cannot give you any assurance about your safety or security. If it does happen, and you opt to cancel, you will receive a credit. You should go to our website and then click on Contact Us, then Complaint, and then click on DOR Rider Discrepancy. You will then be prompted for more information.
- 5. If the person with the vehicle—i.e., the trip poster—does not appear, but someone else does and offers the same ride, you should not get into the vehicle. You should not take the ride. You should go to our website and then click on Contact Us, then send us an email (Please include the TripID, which you can find in the Ride Details).

FIG. 6 illustrates a preferred embodiment in which ratings provided by travelers regarding other travelers with whom they have shared rides are considered when seeking ride sharing matches. Having already shared a ride 600, the first traveler 100 rates 602 the second traveler 108 positively as a ride sharing companion. On the other hand, the second traveler 108 rates 604 the first traveler 100 negatively as a ride sharing companion. These ratings are reported to the ride sharing database 106. The second traveler 108 then posts 606 a ride, and the first traveler 100 requests 608 a similar ride. However, a search in the ride sharing database does not result in a match between the first traveler 100 and the second traveler 108, because the second traveler has included in his preferences that he (or she) does not wish to be matched with other travelers who have received negative ratings. A third traveler 610 subsequently logs onto the website and requests 612 a ride, also indicating as a preference that he or she does not wish to be matched with someone who has received a negative rating. This request 612 triggers another search of the ride sharing database 106, and this time a match is identified 614 between the second traveler 108 and the third traveler 610. As a result, the second traveler 108 and the third traveler 610 are informed 616, 618 of the match, and the match is accepted 620 by both of them. In this preferred embodiment, a search for matches is triggered each time a new ride posting or ride request is received. In other preferred embodiments, searches are carried out and matches are reported at regular intervals, such as daily or hourly.
FIG. 7A and FIG. 7B present website screens from a preferred embodiment that can be used by a traveler to rate other riders with whom the traveler has previously shared rides. The screen in FIG. 7A applies with regard to rides that were posted by the traveler, and FIG. 7B applies for rides that were shared by the traveler but not posted by the traveler. The screens present information in tables, with rows that represent shared rides and columns that include the departure city 700, the arrival city 702, and the date of the ride 704. Hypertext fields are provided in the last two columns that can be activated to display more details concerning a ride 706 and to display a separate page that can be used to supply rating information concerning riders who participated in the ride 708.
FIG. 8 illustrates a preferred embodiment in which searches for ride sharing matches that do not immediately result in an accepted match are repeated after a specified amount of time, such as a day or an hour. When a traveler requests a match 800 (or posts a ride), a search 802 is made of the ride sharing database 100 to see if any matches are found 804. If not, a specified amount of time elapses 806, and then if the time for the ride has not passed 808 the search 802 is repeated. If a match is found 804, the travelers involved in the match are notified 810, and if the match is accepted 812 then the process is complete 814. However, if the match is not accepted 812, then the cycle of waiting for a specified time 806 and repeating the search 802 continues until either a match is accepted 812 or time runs out 808.
FIG. 9 illustrates a preferred embodiment in which a fee is charged for use of the method, radii are calculated about the specified origin and destination locations for a trip, and the radii are enlarged if an insufficient number of ride sharing matches are found. The traveler begins by paying a fee 900, either on a periodic basis or on usage basis, so as to use the method. The traveler then requests a ride sharing match 902 for sharing a ride from a specific origin to a specific destination. According to standard parameters and/preferences supplied by the traveler, radii are the calculated 904 about the specified origin and destination, and a search is made 906 for matches within the radii. If a sufficient number of matches is not found 908 according to standard parameters and/or preferences supplied by the traveler, the radii surrounding the origin and/or the destination are enlarged 910, and if the radii are not too large 912 the search is repeated 906. If a sufficient number of matches is found 908 or if the radii become too large 912 then the travelers included in the matches that were found 914, if any. If a match is accepted 916, the travelers included in the match are informed 918. If no match is accepted 916, at least part of the fee is credited back to the traveler 920.
FIG. 10 illustrates a preferred embodiment in which a traveler who has requested a ride sharing match is alerted each time another traveler submits a potentially compatible ride sharing request. When a traveler first requests a ride sharing match 1000, a search is made 1002 of the ride sharing database and an initial report of matches is presented to the traveler 1004. If one of the matches is accepted by all involved travelers 1006, then the travelers are notified of the match 1008 and they proceed to make plans for the shared ride. However, if none of the initial matches is accepted 1006, then as time passes 1010 and new requests for ride share matches are received 1012, each new ride share request is checked to see if it is potentially compatible with the traveler's request 1014, and if so it is reported to the traveler 1016 and the traveler considers whether to accept it or not 1006. This process is continued until either a match is accepted or the time for the ride passes without a match being found.
Other modifications and implementations will occur to those skilled in the art without departing from the spirit and the scope of the invention as claimed. Accordingly, the above description is not intended to limit the invention except as indicated in the following claims.

Claims

1-20. (canceled)

21. A method for identifying ride sharing matches for travelers, each ride sharing match matching at least two travelers, the method comprising:

establishing a database on a server, the database being capable of containing ride requirements and personal ride sharing preferences;

providing to travelers access to the database;

accepting from the travelers ride requirements and personal ride sharing preferences;

Identifying a ride sharing match based on the ride requirements and personal ride sharing preferences; and

providing to all travelers matched by the ride sharing match access to information regarding the ride sharing match.

22. The method of claim 21, further comprising:

verifying the identity of a traveler before at least one of:

accepting from the traveler ride requirements and personal ride sharing preferences; and

identifying a ride sharing match for the traveler.

23. The method of claim 22, wherein verifying the identity of the traveler includes at least one of:

accepting from the traveler a user ID and a password, at least one of the user ID and the password being provided by the traveler using one of a computer, a wireless access device, and other communication devices; and

receiving a payment, so as to establish the identity of at least someone associated with the traveler who is at least able to make payments.

24. The method of claim 21, further comprising obtaining identifying information from a traveler before at least one of:

identifying a ride sharing match for the traveler,

at least some of the identifying information being usable by other travelers to verify the identity of the traveler.

25. The method of claim 24, wherein the identifying information includes at least one of:

personal information, including at least one of an address, a telephone number, an email address, a date of birth, a gender, a driver's license number, a driver's license state of issue, and other personal information;

vehicle information, including at least one of a vehicle make, a vehicle model, a vehicle year of manufacture, a vehicle license plate number, a vehicle registration, a vehicle owner name, a vehicle color, a description of vehicle condition, and other vehicle information; and

student information, including at least one of a student ID number, a name of a college attended by the traveler, a name of a college campus attended by the traveler, and other student information.

26. The method of claim 21, further comprising:

accepting from travelers rating information pertaining to other travelers based on ride sharing experiences.

27. The method of claim 26, further comprising at least one of:

providing to a first traveler rating information pertaining to a second traveler who is matched by a ride sharing match with the first traveler;

identifying ride sharing matches taking into account rating information that pertains to travelers; and

accepting from a first traveler a personal ride sharing preference regarding rating information, so as to avoid matching the first traveler with a second traveler if rating information pertaining to the second traveler does not satisfy the personal ride sharing preference of the first traveler.

28. The method of claim 21, wherein ride requirements and personal ride sharing preferences accepted from a traveler can include at least one of:

a ride requirement that the number of travelers matched by a ride sharing match must not exceed a maximum capacity of a vehicle; and

a ride sharing preference regarding the number of riders that share a ride.

29. The method of claim 21, wherein ride requirements and ride sharing preferences accepted from a traveler can include:

ride requirements and ride sharing preferences for a first ride from an origin to a destination; and

ride requirements and ride sharing preferences for a second ride from the destination back to the origin.

30. The method of claim 21, further comprising, upon acceptance of a ride sharing match by at least two matched travelers, at least one of:

providing notice of acceptance of the ride sharing match to all travelers who have accepted the ride sharing match;

providing suggestions regarding practical issues of ride sharing to all travelers who have accepted the ride sharing match; and

providing information regarding the ride sharing match to someone not matched by the ride sharing match upon request of a traveler who has accepted the ride sharing match.

31. The method of claim 21, further comprising sending reminders to travelers who have accepted a ride sharing match, the reminders being sent at specified intervals of time in advance of an agreed upon date and time for a shared ride.

32. The method of claim 31, wherein the specified intervals of time include at least one of a day and a week.

33. The method of claim 21, wherein ride requirements and personal ride sharing preferences accepted from a traveler are considered at specified time intervals together with ride requirements and personal ride sharing preferences accepted from other travelers, so as to identify ride sharing matches at the specified time intervals.

34. The method of claim 21, wherein at least one of a communication between a traveler and the database and between a first traveler and a second traveler includes a communication that is a secure communication.

35. The method of claim 21, further comprising maintaining a record of at least one of:

ride requirements and personal ride sharing preferences accepted from a traveler;

identified ride sharing matches; and

acceptances by a traveler of ride sharing matches.

36. The method of claim 21, wherein ride requirements and personal ride sharing preferences accepted from travelers can include at least one of:

a ride requirement regarding the use of at least one of a ground vehicle, an aircraft, a water vessel and other vehicles; and

a personal ride sharing preference regarding the use of at least one of a ground vehicle, an aircraft, a water vessel and other vehicles.

37. The method of claim 21, wherein ride requirements and personal ride sharing preferences accepted from travelers can include at least one of:

a ride requirement for a ride over any desired distance; and

a personal ride sharing preference for a ride over any desired distance.

38. The method of claim 21, wherein identifying a ride sharing match includes calculating a radius about at least one of a departure point and a destination point.

39. The method of claim 38, wherein at least one of the calculated radii is automatically enlarged until a specified minimum number of ride sharing matches is identified.

40. The method of claim 21, further comprising providing information to a first traveler regarding ride requirements and personal ride sharing preferences accepted from a second traveler when a possible ride sharing match has been identified based on ride requirements and personal ride sharing preferences accepted from the first traveler and the ride requirements and personal ride sharing preferences accepted from the second traveler.

41. The method of claim 21, further comprising requiring payment by a traveler of at least one fee so as to use the method.

42. The method of claim 21, further comprising crediting to a traveler at least part of a fee paid by the traveler if use of the method by the traveler does not result in acceptance of a minimum number of ride sharing matches.

43. The method of claim 21, wherein ride requirements and personal ride sharing preferences accepted from a traveler can be changed at any time before a ride sharing match based on the ride requirements and personal ride sharing preferences is accepted by the traveler and by at least one other traveler.

44. The method of claim 21, wherein personal ride sharing preferences of a traveler can include at least one of an expense sharing preference, a gender preference, a departure time preference, a pick up location preference, a drop off location preference, a music preference, an allergy avoidance preference, a preference for accommodating disabilities, a pet related preference, and a preference for accommodating special needs.

45. The method of claim 21, wherein access to the database is provided to travelers through a website.