(19)
(11)EP 2 715 285 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
04.11.2020 Bulletin 2020/45

(21)Application number: 12730081.2

(22)Date of filing:  01.06.2012
(51)International Patent Classification (IPC): 
G01C 21/36(2006.01)
G08G 1/0969(2006.01)
G01C 21/34(2006.01)
G01C 21/20(2006.01)
G08G 1/0968(2006.01)
(86)International application number:
PCT/US2012/040550
(87)International publication number:
WO 2012/167148 (06.12.2012 Gazette  2012/49)

(54)

DEVICES AND METHODS FOR COMPARING AND SELECTING ALTERNATIVE NAVIGATION ROUTES

VORRICHTUNGEN UND VERFAHREN ZUM VERGLEICHEN UND AUSWÄHLEN VON ALTERNATIVEN NAVIGATIONSROUTEN

DISPOSITIFS ET PROCÉDÉS POUR COMPARER ET SÉLECTIONNER DES ITINÉRAIRES DE NAVIGATION ALTERNATIFS


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 03.06.2011 US 201161493086 P

(43)Date of publication of application:
09.04.2014 Bulletin 2014/15

(60)Divisional application:
20196595.1

(73)Proprietor: Apple Inc.
Cupertino, CA 95014 (US)

(72)Inventors:
  • MOORE, Bradford
    Cupertino, CA 95014 (US)
  • BLUMENBERG, Christopher
    Cupertino, CA 95014 (US)
  • VAN OS, Marcel
    Cupertino, CA 95014 (US)
  • GYATT, Graham
    Cupertino, CA 95014 (US)

(74)Representative: Barton, Russell Glen et al
Withers & Rogers LLP 4 More London Riverside
London SE1 2AU
London SE1 2AU (GB)


(56)References cited: : 
EP-A1- 2 031 352
DE-A1- 19 531 766
JP-A- 2002 243 480
JP-A- 2011 038 815
US-A- 4 914 605
US-A1- 2006 184 317
US-A1- 2008 040 683
US-A1- 2010 161 160
US-A1- 2010 268 448
US-A1- 2010 324 817
WO-A2-2010/081538
DE-A1-102009 023 610
JP-A- 2005 283 168
JP-A- 2011 038 815
US-A1- 2004 243 307
US-A1- 2006 287 818
US-A1- 2008 062 141
US-A1- 2010 241 975
US-A1- 2010 312 466
US-B1- 6 321 161
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    Background



    [0001] Many portable electronic devices are capable of displaying maps and providing navigational assistance to a user. Such navigational assistance often requires the device to calculate one or more possible routes from a starting point to a destination. What are needed are devices, methods, and machine-readable media to facilitate intuitive comparison and selection of calculated navigation routes on a portable electronic device.

    [0002] JP 2002 243480 describes a navigation system by which a bypass route for avoiding a congestion or the like can be selected by a user. In the system disclosed, a processing control unit acquires a designated return point P by converting a prescribed place (P) into a position (a latitude, a longitude) on a map when the prescribed place (P) is pressed by the user on a guidance route R1 connecting a stating place S to a destination G as shown in Fig. (a). A section up to the return point P from an own-vehicle position V (a first crossing) is set as an avoidance section L. The processing control unit searches a plurality of bypass routes to bypass the set avoidance section L, and it displays, e.g. three bypass routes R2 to R4 as shown in Fig. (b). After that, when any of the bypass routes is selected by the user, a new guidance route containing the selected bypass route is prescribed, and the user is guided up to the destination G according to the new guidance route.

    Summary



    [0003] Devices, methods, and machine-readable media to facilitate intuitive comparison and selection of calculated navigation routes are disclosed.

    [0004] According to some embodiments, a number of calculated navigation routes can be displayed on a map. Each route may be highlighted in a manner that allows each route to be easily differentiated. For example, each route may be identified with different color or highlighting schemes and/or may be identified by an unobtrusive callout. As disclosed herein, a callout.

    [0005] US2010312466 discloses a device and a method for navigating a vehicle along a route from a starting position or an instantaneous position to a destination. To this end, a route calculation device of a navigation device calculates a route course which is composed of a sequence of several coherent roads stored on a digital map of a memory device as a first route, and additionally calculates at least one alternative route by allocating a penalty attribute, especially increased average traveling time, road distance or the like, to at least one road of the first route.

    Summary



    [0006] The invention is defined in the appended claims, to which reference should now be made.

    Brief Description of the Drawings



    [0007] The above and other aspects and advantages of the invention will become more apparent upon consideration of the following detailed description, taken in conjunction with accompanying drawings, in which like reference characters refer to like parts throughout, and in which:

    FIG. 1 shows an illustrative screen shot of a map with several alternative routes displayed simultaneously in accordance with various embodiments;

    FIG. 2 shows an illustrative screen shot of a zoomed- in map with several alternative routes displayed simultaneously in accordance with various embodiments;

    FIG. 3 shows an illustrative screen shot of a list of navigation tiles in accordance with various embodiments;

    FIG. 4 shows an illustrative screen shot of navigation tiles in accordance with various embodiments;

    FIG. 5 shows an illustrative screen shot of a navigation tile in accordance with various embodiments;

    FIG. 6 shows an illustrative screen shot map with several alternative routes displayed simultaneously in accordance with various embodiments;

    FIG. 7 shows an illustrative screen shot of an electronic device in accordance with various embodiments;

    FIG. 8 shows a flowchart of a method for comparing and selecting alternative navigation routes in accordance with various embodiments;

    FIG. 9 shows a flowchart of a method for comparing and selecting alternative navigation routes in accordance with various embodiments;

    FIG. 10 shows a flowchart of a method for comparing and selecting alternative navigation routes in accordance with various embodiments;

    FIG. 11 is a schematic view of an illustrative touch I/O device that can receive touch input for interacting with a computing system via wired or wireless communication channel in accordance with some embodiments of the invention;

    FIG. 12 is a block diagram of an illustrative system for providing alternative navigation routes in accordance with some embodiments of the invention;

    FIG. 13 is a block diagram illustrating an exemplary API architecture in accordance with some embodiments of the invention; and

    FIG. 14 is a block diagram of an illustrative software stack by which applications can make calls to Services A or B using APIs in accordance with some embodiments of the invention.


    Detailed Description of the Disclosure



    [0008] FIG. 1 shows an illustrative screen shot of map 100 with several alternative routes displayed simultaneously in accordance with various embodiments. Map 100 is displayed in landscape mode (i.e., the display is wider than it is tall); however, map 100 may also be displayed in portrait mode (i.e., with the display taller than it is wide). The display mode can be based on the current orientation of the device (e.g., using an accelerometer contained in the device) or the user can choose to lock the display into one preferred mode or the other.

    [0009] Map 100 includes a number of relevant navigational elements including: highways H1, H2, H3, H4, and H6; secondary roads R111, R113, R115, and R117; route callouts 101, 102, 103, 104, and 105; starting point 107 and destination point 109; ocean 120, river 121, bridge 122, and tunnel 123; context-appropriate menu 142 and compass 144; sidebar 140; and topbar 130, including preferences button 132, navigation-mode button 134, and start button 136. Map 100 may be displayed upon the user indicating that he or she desires to travel by car from starting point 107 in Clarksville to destination point 109 in Bennington.

    [0010] Route callouts 101, 102, 103, 104, and 105 corresponding to Route 1, Route 2, Route 3, Route 4, and Route 5, respectively, identify the available alternate routes generated by the device. The roads along each route can be highlighted such that each route is easily identifiable and distinguishable from the other routes. For example, each route may be highlighted in a different color. Roads displayed on map 100 that are not along any of the calculated routes may be displayed in a more discrete color and/or in thinner lines than roads that are along one or more routes.

    [0011] The route callouts in map 100 only display the names given to each route, but can, according to some embodiments, display more information, including distance and estimated travel time for the corresponding route. The amount of information displayed in a callout may be adjusted by the user. For example, the user can indicate a preference to display only the route name in the callout, force the callout to display an additional information field (e.g., the route distance), or display as much information as space permits. According to some embodiments, a user can tap and hold a callout on the touch-sensitive screen to display additional information associated with the route. For example, if a callout normally only displays the route name, tapping and holding the callout or its associated route can result in additional information being displayed, including travel distance and time. In order to display the additional information, the callout may be made larger temporarily, or a pop-up type box may appear on the screen. Route callouts may generally be displayed on map 100 in a manner that does not obscure any important map elements (e.g., major roads and intersections, cities, towns, etc.).

    [0012] According to some embodiments, a user can choose a particular route from among the routes displayed on map 100 by tapping the touch-sensitive screen anywhere along the route or by tapping the callout associated with the desired route. Other embodiments may allow a user to use other means of selecting a route, including but not limited to, using a mouse or keyboard, speaking the route name, or using any other suitable method. Once a user has selected a particular route, the route can be distinguished from the other unselected routes in any suitable manner. For example, the selected route may be highlighted even more prominently than it was prior to selection by using a brighter color, thicker lines, and/or increasing the size of the associated callout. Route 3 on map 100 has been highlighted using double lines to indicate that the user has selected that route to travel from starting point 107 to destination point 109. Alternatively or additionally, unselected routes can be faded or otherwise de-emphasized. For example, unselected routes like Route 1 and Route 2 on map 100 may be faded, displayed in a more subdued color, or displayed with thinner lines. Similarly, the callouts associated with unselected routes can be faded, made smaller, or otherwise de-emphasized.

    [0013] Calculated routes can be prioritized based on a set of user preferences. For example, the user preferences may indicate that a user would like to avoid toll roads, avoid traffic, minimize travel distance, minimize travel time, take a scenic route, travel on a particular road, or stop at a POI en route. The device can calculate which routes best match the user's preferences and rank each route accordingly. Data about the five calculated routes on map 100 is displayed in sidebar 140. Routes 1-5 are prioritized by travel distance (i.e., Route 1 has the shortest distance and Route 5 has the longest).

    [0014] Sidebar 140 can provide the user with relevant, context-appropriate information in a manner that does not affect the readability of map 100. Sidebar 140 is located discretely on the side of the display and shows key information regarding five calculated routes that may allow a user to determine which route is best; however, according to some embodiments, sidebar 140 may be placed in any appropriate section of the screen or omitted completely. Sidebar 140 also need not be displayed simultaneously with the routes. For example, the information displayed in sidebar 140 may be accessed via a context-specific menu and displayed in a separate window. In other contexts, a sidebar may provide other relevant information. For example, during navigation the sidebar may present the user with details about travel speed, distance to the destination, estimated arrival time, nearby POIs, etc. As with callouts, the amount and type of information displayed in the sidebar may be customized by the user.

    [0015] Context-appropriate menu 142 can be accessed to perform various functions that are relevant to the currently displayed screen. While the device is in route-selection mode (i.e., as displayed on map 100) menu 142 may provide options to enter a list mode (discussed in detail below with respect to FIG. 3), hide the sidebar, show traffic, show POIs, and show terrain. If a user decides to show terrain, the roads and highlighted routes may be altered such that they remain easily visible and distinguishable. Menu 142 may be accessed in any suitable manner, including but not limited to tapping and holding the touch-screen display.

    [0016] Map 100 can also include topbar 130. Topbar 130 can be disposed at the top of the display and contain high-level options that are always relevant. For example, topbar 130 can include several virtual buttons, such as preferences button 132, navigation-mode button 134, and start button 136, which can be activated by tapping the buttons on the touch-screen display. Activating preferences button 132 can provide the user with a set of customizable options (discussed in detail below with respect to FIG. 7). Navigation mode button 134 provides the user with an easy way to switch between available navigation modes (i.e., driving, transit, and walking modes). Activating Start button 136 may begin navigation along the selected route (e.g., Route 3).

    [0017] Compass 144 can be displayed in a portion of map 100 to provide directional context for the map without obscuring any important map elements.

    [0018] FIG. 2 shows an illustrative screen shot of a zoomed-in map 200 with several alternative routes displayed simultaneously in accordance with various embodiments. Map 200 displays a subsection of the area displayed in map 100 of FIG. 1 while in navigation mode. In particular, map 200 is zoomed in around the current location of the device while the user is traveling on highway H4 en route from the starting point to the destination. Because the device is in navigation mode, start button 136 of FIG. 1 can change to end button 236 of FIG. 2. Starting point 107 and destination point 109 (see FIG. 1) are not visible on map 200; however, callouts 210 and 212 indicate the direction to each of those points, respectively. Callouts 101, 102, 104, and 105 indicate the direction to each alternate unselected Routes 1, 2, 4, and 5, respectively.

    [0019] The level of zoom for map 200 can be automatically determined based on a number of factors including, but not limited to the user's current speed, the current speed limit, the distance to the next turn, and/or the distance to POIs. For example, if the user is moving relatively quickly along a route and the distance to the next turn is relatively far, the map can be zoomed to a level that displays a large portion, if not all, of the map. Such a zoomed-out view can provide the user with context, including how far they are along the route. However, as the user approaches a turn or other location where more detail would be useful (e.g., as the user approaches a POI or the destination) the map can be automatically zoomed in to a level that provides a useful amount of detail.

    [0020] Zooming in and out can be accomplished seamlessly by gradually zooming in or out based on at least the factors listed above. For example, a user traveling down a highway at a relatively high speed may be presented with a map view that is zoomed out very far. However, as the user approaches a POI (e.g., a rest area along the highway), the map may gradually zoom in to show the user precisely where the POI is located. In the event that a user is driving relatively slowly through a neighborhood, the map view may remain zoomed in to a very detailed level the entire time. Map 200 is uses a top-down view with the map oriented such that north is up and south is down even though the user is traveling north to south along highway H4. According to some embodiments, the angle and orientation of the map view can be altered to coincide with the point of view of the user. For example, a user driving south along highway H4 may be presented with a map view displaying a view of the highway facing south from a low-elevation point of view.

    [0021] Sidebar 240 can display a number of fields with information relevant to the user's trip, including the user's current speed, the current speed limit, the estimated time of arrival ("ETA"), distance traveled, distance remaining, and options to show various POIs. Each of the fields in sidebar 240 may be collapsed, for example by tapping the field, in order to provide more space to display additional information.

    [0022] The POI section of sidebar 240 indicates that the user has chosen to display gas stations along the route. Icons 220 and 222 represent two gas stations that are currently visible on map 200. Icon 220 is highlighted, indicating that the user selected it (e.g., by tapping it). Selecting icon 220 can, according to some embodiments, result in the display of context-appropriate menu 242. Menu 242 can allow the user to set the location of icon 220 as either the new destination or add the location as a waypoint on the way to the original destination point (i.e., destination point 109 of FIG. 1).

    [0023] Tapping one of the callouts 101, 102, 103, 104, 105, 210, or 212 can result in altering the map view and the information displayed in callout 240. For example, tapping callout 212 may result the map changing to a zoomed-in view of the area around the destination. Similarly, the information in sidebar 240 may change to display a wider range of POIs near the destination. For instance, the list of POIs may expand to include hotels and/or specific well-known tourist attractions (e.g., stadiums and museums). Tapping a callout for an alternate route (e.g., callout 101 for Route 1) may provide the user with information regarding navigation to or by that route. For example, the user may decide, while travelling on Route 3, to switch to Route 4. The device may provide the user with information regarding the distance to Route 4 and an estimation of how much time the route change is expected to add or subtract from the trip.

    [0024] After a user has navigated along one route for a period of time, the originally calculated alternate routes may become irrelevant to the user. Therefore, according to some embodiments, the device can recalculate alternate routes while a user is navigating from one point to another. Alternate routes may be generated continuously or at predetermined intervals. For example, a user may choose to deviate from the selected navigation route for any number of reasons (wrong turns, detours, rest stops, etc.) and could benefit from having the ability to choose from a set of routes calculated from their current location. Alternate routes may also be calculated upon the occurrence of an event (e.g., upon the device receiving information regarding a traffic accident along the route). So, if the device receives notification that there is a traffic jam along the selected route, alternative routes can be calculated based on the user's current location. The user can select one of the new routes by tapping the route or tapping the new callout associated with the desired route. Newly calculated alternate routes may also be manually requested by the user.

    [0025] FIG. 3 shows an illustrative screen shot of a list 300 of navigation tiles in accordance with various embodiments. List 300 shows navigation tiles 301, 302, and 303, which correspond to Route 1, Route 2, and Route 3 (e.g., of FIG. 1). Navigation tiles 301, 302, and 303 include a relatively simple pictorial view of each route on the right-hand side and relatively detailed text information about the routes on the lefthand side. If more calculated routes exist, the user can scroll down (e.g., by dragging a finger upward on the touch-sensitive screen) to view the additional routes. The position of the screen relative to the entire list of navigation tiles may be indicated by the location of scrollbar 350. A user may select a particular route by tapping the desired navigation tile. Once the desired route is selected, the user can tap start button 136 to begin navigation.

    [0026] Navigation tiles 301, 302, and 303 may provide more detailed text information than can be displayed in a full map view (e.g., map 100 of FIG. 1). For example, in addition to the distance and estimated travel time, a navigation tile may also include information regarding the cost of tolls along the route and traffic status with traffic pictorials 360, 361, and 362. Navigation tile 302 includes red-light traffic pictorial 361, which indicates a traffic problem along the route. The location of the traffic issue is shown on the route pictorial by icon 363. According to some embodiments, the user can tap icon 363 to get detailed description 364 of the traffic issue.

    [0027] The route pictorials may also include route-change indicators 370, 371, 372, 373, and 374. Route-change indicators can provide a user with a clear understanding of the number and locations of route changes (e.g., turns, on-ramps, and off-ramps) along the route, which may otherwise be difficult to determine without the benefit of a fully detailed map.

    [0028] FIG. 4 shows an illustrative screen shot of navigation tile selector 400 in accordance with various embodiments. As an alternative to list 300, navigation tiles may be slid back and forth. Status bar 410 may indicate how many calculated routes are available and which route is currently being displayed. Screen shot 400 shows navigation tile 403 situated between navigation tiles 402 and 403. Status bar 410 indicates that navigation tile 403 is the third of five available navigation tiles.

    [0029] FIG. 5 shows an illustrative screen shot of navigation tile selector 500 in accordance with various embodiments. Navigation tile selector is very similar to selector 400, except that it employs buttons 510 and 511 to choose between available navigation tiles. Title 512 indicates which navigation tile is actively being displayed and how many navigation tiles are available to choose from.

    [0030] FIG. 6 shows an illustrative screen shot of a map 600 with several alternative transit routes displayed simultaneously in accordance with various embodiments. A user can enter transit mode by tapping the transit section, represented by a pictorial of a bus, of navigation mode button 134. The transit section of navigation mode button 134 is shaded to indicate that it is the active navigation mode. When the device enters transit mode, several public transportation routes can be calculated from starting point 107 to destination point 109. Map 600 shows three different transit options (train, bus, and ferry); however, any other transit options, such as subways, trolleys, and taxis, may be included in other embodiments. Legend 642 may be displayed to show a user the pictorial representations of the available transit options. As with the driving routes, each transit route can be highlighted simultaneously and in different colors so that they are easily distinguishable from one another. A user can choose a particular transit route by tapping the touch-sensitive screen anywhere along the route, or by tapping the callout associated with the desired, route.

    [0031] Sidebar 640 can include collapsible fields 643, 644, 645, and 646, representing train schedules, bus schedules, ferry schedules, and route information, respectively. Tapping any one of the schedule fields 643, 644, or 645 may display scheduling information for that mode of transit. For example, tapping train schedule field 643 can give the user information about train schedules for the different calculated routes. According to some embodiments, schedules accessed by tapping fields 643, 644, and 645 may reside on a third party server (e.g., a website) and require the user to view the schedules in another application (i.e., a web browser). In other embodiments, the device can automatically download transit schedules and provide the scheduling information directly in the navigation application. If the user chooses one particular route, schedule information may only be provided for the transit options relevant to that route. For example, if Route 2 is chosen from map 600, tapping bus schedule field 644 may only display the schedule for bus routes along Route 2.

    [0032] Route information field 646 in sidebar 640 can display key information regarding each calculated route. For example, the travel time and total price can be displayed for each calculated route. The estimated travel time and total price can be calculated from time and fee schedules downloaded to, or otherwise accessed by, the device. Time estimations can be dynamic and take into account the current time and the scheduled arrival time of each transit option. For example, if the train departing from Clarksville at starting point 107 departs every hour, the estimated travel time may include the amount of time between the current time and the next departure as well as the lag time between connecting from the train to the ferry at route change indicator 672 and the ferry to the bus at route change indicator 674, thereby giving an estimation of the total door-to-door time and not simply an aggregate of the time spent on each transit option.

    [0033] Route change indicators 671, 672, 673, and 674 may be displayed in order to show the user where they will be required to change transit options. For example, the user will have to change from a train to a bus at the point indicated by route change indicator 671 along Route 1. In the event that it is not clear which route a particular route change indicator is associated with, the indicator may be highlighted in the color matching the route, or otherwise identified. For example, route change indicator 673 is along both Route 2 and Route 4; however, it only applies to Route 4 (a user traveling along Route 2 will remain on the bus, while a user traveling along Route 4 will change from a bus to a ferry at the point indicated at route change indicator 673). On map 600, the Route(s) associated with particular route change indicators are listed in parentheses after the 'Δ' symbol. If a particular route change indicator applies to more than one route, each associated route can be identified (e.g., route change indicator 674 is associated with Route 3 and Route 4).

    [0034] FIG. 7 shows an illustrative screen shot of an electronic device 700 in accordance with various embodiments. Device 700 includes screen 780, route priority menu 781, callout display menu 782, and input mechanism 783. Screen 780 shows a display of a preferences menu (e.g., the menu that would be displayed by tapping preferences button 132 of FIG. 1). Route priority menu 781 contains options that can allow device 700 to calculate navigational routes according to a user's preferences. A user can rank options in the route priority list according to their relative importance to the user. For example, menu 781 shows Min. Distance as the number one ranked option and Min. Time as the second. However, a user may choose to reorder the list. To reorder the list, a user may, for instance, tap and hold an option and drag it to the desired position in menu 781. A user may also choose to uncheck any of the options in order to remove that option from route calculations.

    [0035] Callout display menu 782 controls the information that is provided to a user in callouts (e.g., callout 101 of FIG. 1). The options in menu 782 are not exhaustive and additional options may be added by the user or via software updates. Because callouts are designed to be unobtrusive, the user can rank the options in the order of personal preference. If all fields cannot be displayed in a callout, the fields may be displayed in the order they are ranked in menu 782. For example, if the options are set as in menu 782 and there is only enough space to display two fields in a callout, only the Route Name and Total Distance may be displayed. Additional fields may be displayed if a user desires, for example, by tapping and holding the callout.

    [0036] FIG. 8 shows a flowchart of a method 800 for comparing and selecting alternative navigation routes in accordance with various embodiments. Method 800 begins at step 801 and proceeds to step 803, in which a number of navigation routes are calculated and navigation tiles are prepared. Navigation routes may be calculated in order to satisfy a set of user preferences. For example, a number of navigation routes may be calculated to coincide with the user preferences set in route priority menu 781 of FIG. 7. Navigation tiles may then be prepared for each route by generating a pictorial representation of each navigation route along with text information associated with the route.

    [0037] In step 805, navigation tiles can be displayed on a screen with the pictorial representation of a navigation route and details about the route. For example, as described above with respect to FIG. 3, each navigation tile may include a simple pictorial depiction of the route associated with that tile, where the pictorial may include textual information regarding major roads and turns along the route. The detailed information may include helpful data associated with the route such as distance, travel time, tolls, and traffic. In some embodiments, the navigation tiles may be displayed in a list, like navigation tiles 301, 302, and 303 of FIG. 3. In further embodiments, a user may browse through the displayed navigation tiles by sliding the navigation tiles back and forth as described with respect to FIG. 4, using buttons as described with respect to FIG. 5, or using any other suitable method.

    [0038] In step 807, the device can receive a selection of a navigation tile. A particular tile may be selected, for instance, by tapping the tile on a touch-sensitive screen. Once a navigation tile has been selected, a more detailed map, such as the maps depicted in FIG. 1, FIG. 2, and FIG. 6, which corresponds to the navigation tile selected at step 807 may be displayed.

    [0039] FIG. 9 shows a flowchart of a method 900 for comparing and selecting alternative navigation routes in accordance with various embodiments. Method 900 begins at step 901 and proceeds to step 903 in which a map including geographical identifying information is displayed at a first one of several zoom factors. For example, the zoom factor may result in the entire route (e.g., from the start point to the destination) being displayed. Alternatively, the zoom factor may result in only a portion of the route being displayed (e.g., the area immediately surrounding the user's current position).

    [0040] At step 905, navigation routes superimposed over the map may be displayed. Each navigation route can have the same starting and destination points, and each navigation route may be identified by an associated callout. For example, various routes between the starting and destination points and their associated callouts may be superimposed on the map, which is displayed at the first zoom factor. As described with respect to FIG. 1, the zoom factor may allow for each navigation route to be displayed in its entirety. However, as described with respect to FIG. 2, at other zoom factors only portions of some routes may be displayed.

    [0041] At step 907, where to place each of the callouts on the map so that each callout identifies its associated navigation route for the first zoom factor may be determined. For example, if each navigation route is displayed in its entirety at the first zoom factor, the callouts may be displayed such that they clearly and unobtrusively identify their associated navigation routes. Alternatively, if only portions of some routes are displayed at the first zoom factor, callouts may indicate various information about routes that are not displayed, including the distance and direction to those routes from a user's current position. At step 909, the callouts for each displayed navigation route can be displayed in the place determined for the first zoom factor.

    [0042] FIG. 10 shows a flowchart of a method 1000 for comparing and selecting alternative navigation routes in accordance with various embodiments. Method 1000 begins at step 1001 and proceeds to step 1003 in which a map including a plurality of routes is displayed. At step 1005, a navigational route may be overlaid on top of two or more routes. The navigational roué may include start and destination points. The map may be, for example, map 600 of FIG. 6 with routes associated with route callouts 601, 602, 603, and 604.

    [0043] At step 1007, a route change indicator may be displayed at a transition point between the two routes. For example, in transit mode, a route change indicator may indicate where a user will be required to change transit options (e.g., from ferry to bus or from train to ferry. In other embodiments, route-change indicators may indicate where a user will be required to turn (or take other appropriate action).

    [0044] It is to be understood that the steps shown in methods 800, 900, and 1000 are merely illustrative and that existing steps may be modified or omitted, additional steps may be added, and the order of certain steps may be altered.

    [0045] Moreover, the methods described with respect to FIGS. 8-10, as well as any other aspects of the invention, may each be implemented by software, but may also be implemented in hardware, firmware, or any combination of software, hardware, and firmware. They each may also be embodied as machine-readable code recorded on a machine-readable medium. The machine-readable medium may be any data storage device that can store data that can thereafter be read by a computer system. Examples of the machine-readable medium may include, but are not limited to, read-only memory, random-access memory, flash memory, CD-ROMs, DVDs, magnetic tape, and optical data storage devices. The machine-readable medium can also be distributed over network-coupled computer systems so that the machine-readable code is stored and executed in distributed fashion.

    [0046] Described embodiments may include touch I/O device 1101 that can receive touch input for interacting with computing system 1103 (FIG. 9) via wired or wireless communication channel 1102. Touch I/O device 1101 may be used to provide user input to computing system 1103 in lieu of or in combination with other input devices such as a keyboard, mouse, etc. One or more touch I/O devices 1101 may be used for providing user input to computing system 1103. Touch I/O device 1101 may be an integral part of computing system 1103 (e.g., touch screen on a laptop) or may be separate from computing system 1103.

    [0047] Touch I/O device 1101 may include a touch sensitive panel which is wholly or partially transparent, semitransparent, non-transparent, opaque or any combination thereof. Touch I/O device 1101 may be embodied as a touch screen, touch pad, a touch screen functioning as a touch pad (e.g., a touch screen replacing the touchpad of a laptop), a touch screen or touchpad combined or incorporated with any other input device (e.g., a touch screen or touchpad disposed on a keyboard) or any multi-dimensional object having a touch sensitive surface for receiving touch input.

    [0048] In one example, touch I/O device 1101 embodied as a touch screen may include a transparent and/or semitransparent touch sensitive panel partially or wholly positioned over at least a portion of a display. According to this embodiment, touch I/O device 1101 functions to display graphical data transmitted from computing system 1103 (and/or another source) and also functions to receive user input. In other embodiments, touch I/O device 1101 may be embodied as an integrated touch screen where touch sensitive components/devices are integral with display components/devices. In still other embodiments a touch screen may be used as a supplemental or additional display screen for displaying supplemental or the same graphical data as a primary display and to receive touch input.

    [0049] Touch I/O device 1101 may be configured to detect the location of one or more touches or near touches on touch I/O device 1101 based on capacitive, resistive, optical, acoustic, inductive, mechanical, chemical measurements, or any phenomena that can be measured with respect to the occurrences of the one or more touches or near touches in proximity to touch I/O device 1101. Software, hardware, firmware or any combination thereof may be used to process the measurements of the detected touches to identify and track one or more gestures. A gesture may correspond to stationary or non-stationary, single or multiple, touches or near touches on touch I/O device 1101. A gesture may be performed by moving one or more fingers or other objects in a particular manner on touch I/O device 1101 such as tapping, pressing, rocking, scrubbing, twisting, changing orientation, pressing with varying pressure and the like at essentially the same time, contiguously, or consecutively. A gesture may be characterized by, but is not limited to a pinching, sliding, swiping, rotating, flexing, dragging, or tapping motion between or with any other finger or fingers. A single gesture may be performed with one or more hands, by one or more users, or any combination thereof.

    [0050] Computing system 1103 may drive a display with graphical data to display a graphical user interface (GUI). The GUI may be configured to receive touch input via touch I/O device 1101. Embodied as a touch screen, touch I/O device 1101 may display the GUI. Alternatively, the GUI may be displayed on a display separate from touch I/O device 1101. The GUI may include graphical elements displayed at particular locations within the interface. Graphical elements may include but are not limited to a variety of displayed virtual input devices including virtual scroll wheels, a virtual keyboard, virtual knobs, virtual buttons, any virtual UI, and the like. A user may perform gestures at one or more particular locations on touch I/O device 1101 which may be associated with the graphical elements of the GUI. In other embodiments, the user may perform gestures at one or more locations that are independent of the locations of graphical elements of the GUI. Gestures performed on touch I/O device 1101 may directly or indirectly manipulate, control, modify, move, actuate, initiate or generally affect graphical elements such as cursors, icons, media files, lists, text, all or portions of images, or the like within the GUI. For instance, in the case of a touch screen, a user may directly interact with a graphical element by performing a gesture over the graphical element on the touch screen. Alternatively, a touch pad generally provides indirect interaction. Gestures may also affect non-displayed GUI elements (e.g., causing user interfaces to appear) or may affect other actions within computing system 1103 (e.g., affect a state or mode of a GUI, application, or operating system). Gestures may or may not be performed on touch I/O device 1101 in conjunction with a displayed cursor. For instance, in the case in which gestures are performed on a touchpad, a cursor (or pointer) may be displayed on a display screen or touch screen and the cursor may be controlled via touch input on the touchpad to interact with graphical objects on the display screen. In other embodiments in which gestures are performed directly on a touch screen, a user may interact directly with objects on the touch screen, with or without a cursor or pointer being displayed on the touch screen.

    [0051] Feedback may be provided to the user via communication channel 1102 in response to or based on the touch or near touches on touch I/O device 1101. Feedback may be transmitted optically, mechanically, electrically, olfactory, acoustically, or the like or any combination thereof and in a variable or non-variable manner.

    [0052] Attention is now directed towards embodiments of a system architecture that may be embodied within any portable or non-portable device including but not limited to a communication device (e.g. mobile phone, smart phone), a multi-media device (e.g., MP3 player, TV, radio), a portable or handheld computer (e.g., tablet, netbook, laptop), a desktop computer, an All-In-One desktop, a peripheral device, or any other system or device adaptable to the inclusion of system architecture 1200, including combinations of two or more of these types of devices. FIG. 12 is a block diagram of one embodiment of system 1200 that generally includes one or more computer-readable mediums 1201, processing system 1204, Input/Output (I/O) subsystem 1206, radio frequency (RF) circuitry 1208 and audio circuitry 1210. These components may be coupled by one or more communication buses or signal lines 1203.

    [0053] It should be apparent that the architecture shown in FIG. 12 is only one example architecture of system 1200, and that system 1200 could have more or fewer components than shown, or a different configuration of components. The various components shown in FIG. 12 can be implemented in hardware, software, firmware or any combination thereof, including one or more signal processing and/or application specific integrated circuits.

    [0054] RF circuitry 1208 is used to send and receive information over a wireless link or network to one or more other devices and includes well-known circuitry for performing this function. RF circuitry 1208 and audio circuitry 1210 are coupled to processing system 1204 via peripherals interface 1216. Peripherals interface 1216 includes various known components for establishing and maintaining communication between peripherals and processing system 1204. Audio circuitry 1210 is coupled to audio speaker 1250 and microphone 1252 and includes known circuitry for processing voice signals received from peripherals interface 1216 to enable a user to communicate in real-time with other users. In some embodiments, audio circuitry 1210 includes a headphone jack (not shown).

    [0055] Peripherals interface 1216 couples the input and output peripherals of the system to processor 1218 and computer-readable medium 1201. One or more processors 1218 communicate with one or more computer-readable mediums 1201 via controller 1220. Computer-readable medium 1201 can be any device or medium that can store code and/or data for use by one or more processors 1218. Medium 1201 can include a memory hierarchy, including but not limited to cache, main memory and secondary memory. The memory hierarchy can be implemented using any combination of RAM (e.g., SRAM, DRAM, DDRAM), ROM, FLASH, magnetic and/or optical storage devices, such as disk drives, magnetic tape, CDs (compact disks) and DVDs (digital video discs). Medium 1201 may also include a transmission medium for carrying information-bearing signals indicative of computer instructions or data (with or without a carrier wave upon which the signals are modulated). For example, the transmission medium may include a communications network, including but not limited to the Internet (also referred to as the World Wide Web), intranet(s), Local Area Networks (LANs), Wide Local Area Networks (WLANs), Storage Area Networks (SANs), Metropolitan Area Networks (MANs) and the like.

    [0056] One or more processors 1218 run various software components stored in medium 1201 to perform various functions for system 1200. In some embodiments, the software components include operating system 1222, communication module (or set of instructions) 1224, touch processing module (or set of instructions) 1226, graphics module (or set of instructions) 1228, one or more applications (or set of instructions) 1230, and navigation module [or set of instructions] 1238. Each of these modules and above noted applications correspond to a set of instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, medium 1201 may store a subset of the modules and data structures identified above. Furthermore, medium 1201 may store additional modules and data structures not described above.

    [0057] Operating system 1222 includes various procedures, sets of instructions, software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

    [0058] Communication module 1224 facilitates communication with other devices over one or more external ports 1236 or via RF circuitry 1208 and includes various software components for handling data received from RF circuitry 1208 and/or external port 1236.

    [0059] Graphics module 1228 includes various known software components for rendering, animating and displaying graphical objects on a display surface. In embodiments in which touch I/O device 1212 is a touch sensitive display (e.g., touch screen), graphics module 1228 includes components for rendering, displaying, and animating objects on the touch sensitive display.

    [0060] One or more applications 1230 can include any applications installed on system 1200, including without limitation, navigation, a browser, address book, contact list, email, instant messaging, word processing, keyboard emulation, widgets, JAVA-enabled applications, encryption, digital rights management, voice recognition, voice replication, location determination capability (such as that provided by the global positioning system (GPS)), a music player, etc.

    [0061] Touch processing module 1226 includes various software components for performing various tasks associated with touch I/O device 1212 including but not limited to receiving and processing touch input received from touch I/O device 1212 via touch I/O device controller 1232.

    [0062] System 1200 may further include navigation module 1238 for performing the method/functions as described herein in connection with Figures 1-8. Navigation module 1238 may at least function to calculate navigation routes based on at least a starting point and destination point (e.g., starting point 107 and destination point 109 of FIG. 1). Navigation module 1238 may also incorporate route priority preferences (e.g., route priority preferences 781 of FIG. 7). A location determination capability (such as that provided by the global positioning system (GPS)) can be included as part of navigation module 1238 or as a separate module that can interact with navigation module 1238. Navigation module 1238 may also interact with touch processing module 1226 to receive user input and one or more applications 1230 (e.g., a navigation application). Navigation module 1238 may be embodied as hardware, software, firmware, or any combination thereof. Although navigation module 1238 is shown to reside within medium 1201, all or portions of navigation module 1238 may be embodied within other components within system 1200 or may be wholly embodied as a separate component within system 1200.

    [0063] I/O subsystem 1206 is coupled to touch I/O device 1212 and one or more other I/O devices 1214 for controlling or performing various functions. Touch I/O device 1212 communicates with processing system 1204 via touch I/O device controller 1232, which includes various components for processing user touch input (e.g., scanning hardware). One or more other input controllers 1234 receives/sends electrical signals from/to other I/O devices 1214. Other I/O devices 1214 may include physical buttons, dials, slider switches, sticks, keyboards, touch pads, additional display screens, or any combination thereof.

    [0064] If embodied as a touch screen, touch I/O device 1212 displays visual output to the user in a GUI. The visual output may include text, graphics, video, and any combination thereof. Some or all of the visual output may correspond to user-interface objects. Touch I/O device 1212 forms a touch-sensitive surface that accepts touch input from the user. Touch I/O device 1212 and touch I/O device controller 1232 (along with any associated modules and/or sets of instructions in medium 1201) detects and tracks touches or near touches (and any movement or release of the touch) on touch I/O device 1212 and converts the detected touch input into interaction with graphical objects, such as one or more user-interface objects. In the case in which touch I/O device 1212 is embodied as a touch screen, the user can directly interact with graphical objects that are displayed on the touch screen. Alternatively, in the case in which touch I/O device 1212 is embodied as a touch device other than a touch screen (e.g., a touch pad), the user may indirectly interact with graphical objects that are displayed on a separate display screen embodied as I/O device 1214.

    [0065] Touch I/O device 1212 may be analogous to the multi-touch sensitive surface described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Patent Publication 1002/0015024A1, each of which is hereby incorporated by reference.

    [0066] Embodiments in which touch I/O device 1212 is a touch screen, the touch screen may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, OLED (organic LED), or OEL (organic electro luminescence), although other display technologies may be used in other embodiments.

    [0067] Feedback may be provided by touch I/O device 1212 based on the user's touch input as well as a state or states of what is being displayed and/or of the computing system. Feedback may be transmitted optically (e.g., light signal or displayed image), mechanically (e.g., haptic feedback, touch feedback, force feedback, or the like), electrically (e.g., electrical stimulation), olfactory, acoustically (e.g., beep or the like), or the like or any combination thereof and in a variable or non-variable manner.

    [0068] System 1200 also includes power system 1244 for powering the various hardware components and may include a power management system, one or more power sources, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator and any other components typically associated with the generation, management and distribution of power in portable devices.

    [0069] In some embodiments, peripherals interface 1216, one or more processors 1218, and controller 1220 may be implemented on a single chip, such as processing system 1204. In some other embodiments, they may be implemented on separate chips.

    [0070] One or more Application Programming Interfaces (APIs) may be used in some embodiments. An API is an interface implemented by a program code component or hardware component (hereinafter "API-implementing component") that allows a different program code component or hardware component (hereinafter "API-calling component") to access and use one or more functions, methods, procedures, data structures, classes, and/or other services provided by the API-implementing component. An API can define one or more parameters that are passed between the API-calling component and the API-implementing component.

    [0071] An API allows a developer of an API-calling component (which may be a third party developer) to leverage specified features provided by an API-implementing component. There may be one API-calling component or there may be more than one such component. An API can be a source code interface that a computer system or program library provides in order to support requests for services from an application. An operating system (OS) can have multiple APIs to allow applications running on the OS to call one or more of those APIs, and a service (such as a program library) can have multiple APIs to allow an application that uses the service to call one or more of those APIs. An API can be specified in terms of a programming language that can be interpreted or compiled when an application is built.

    [0072] In some embodiments the API-implementing component may provide more than one API, each providing a different view of or with different aspects that access different aspects of the functionality implemented by the API-implementing component. For example, one API of an API-implementing component can provide a first set of functions and can be exposed to third party developers, and another API of the API-implementing component can be hidden (not exposed) and provide a subset of the first set of functions and also provide another set of functions, such as testing or debugging functions, which are not in the first set of functions. In other embodiments, the API-implementing component may itself call one or more other components via an underlying API and thus be both an API-calling component and an API-implementing component.

    [0073] An API defines the language and parameters that API-calling components use when accessing and using specified features of the API-implementing component. For example, an API-calling component accesses the specified features of the API-implementing component through one or more API calls or invocations (embodied, for example, by function or method calls) exposed by the API and passes data and control information using parameters via the API calls or invocations. The API-implementing component may return a value through the API in response to an API call from an API-calling component. While the API defines the syntax and result of an API call (e.g., how to invoke the API call and what the API call does), the API may not reveal how the API call accomplishes the function specified by the API call. Various API calls are transferred via the one or more application programming interfaces between the calling (API-calling component) and an API-implementing component. Transferring the API calls may include issuing, initiating, invoking, calling, receiving, returning, or responding to the function calls or messages; in other words, transferring can describe actions by either of the API-calling component or the API-implementing component. The function calls or other invocations of the API may send or receive one or more parameters through a parameter list or other structure. A parameter can be a constant, key, data structure, object, object class, variable, data type, pointer, array, list or a pointer to a function or method or another way to reference a data or other item to be passed via the API.

    [0074] Furthermore, data types or classes may be provided by the API and implemented by the API-implementing component. Thus, the API-calling component may declare variables, use pointers, use or instantiate constant values of such types or classes by using definitions provided in the API.

    [0075] Generally, an API can be used to access a service or data provided by the API-implementing component or to initiate performance of an operation or computation provided by the API-implementing component. By way of example, the API-implementing component and the API-calling component may each be any one of an operating system, a library, a device driver, an API, an application program, or other module (it should be understood that the API-implementing component and the API-calling component may be the same or different type of module from each other). API-implementing components may in some cases be embodied at least in part in firmware, microcode, or other hardware logic. In some embodiments, an API may allow a client program to use the services provided by a Software Development Kit (SDK) library. In other embodiments an application or other client program may use an API provided by an Application Framework. In these embodiments, the application or client program may incorporate calls to functions or methods provided by the SDK and provided by the API, or use data types or objects defined in the SDK and provided by the API. An Application Framework may, in these embodiments, provide a main event loop for a program that responds to various events defined by the Framework. The API allows the application to specify the events and the responses to the events using the Application Framework. In some implementations, an API call can report to an application the capabilities or state of a hardware device, including those related to aspects such as input capabilities and state, output capabilities and state, processing capability, power state, storage capacity and state, communications capability, etc., and the API may be implemented in part by firmware, microcode, or other low level logic that executes in part on the hardware component.

    [0076] The API-calling component may be a local component (i.e., on the same data processing system as the API-implementing component) or a remote component (i.e., on a different data processing system from the API-implementing component) that communicates with the API-implementing component through the API over a network. It should be understood that an API-implementing component may also act as an API-calling component (i.e., it may make API calls to an API exposed by a different API-implementing component) and an API-calling component may also act as an API-implementing component by implementing an API that is exposed to a different API-calling component.

    [0077] The API may allow multiple API-calling components written in different programming languages to communicate with the API-implementing component (thus the API may include features for translating calls and returns between the API-implementing component and the API-calling component); however the API may be implemented in terms of a specific programming language. An API-calling component can, in one embodiment, call APIs from different providers such as a set of APIs from an OS provider and another set of APIs from a plug-in provider and another set of APIs from another provider (e.g. the provider of a software library) or creator of the another set of APIs.

    [0078] Figure 13 is a block diagram illustrating an exemplary API architecture, which may be used in some embodiments of the invention. As shown in Figure 13, the API architecture 1300 includes the API-implementing component 1310 (e.g., an operating system, a library, a device driver, an API, an application program, software or other module) that implements the API 1320. The API 1320 specifies one or more functions, methods, classes, objects, protocols, data structures, formats and/or other features of the API-implementing component that may be used by the API-calling component 1330. The API 1320 can specify at least one calling convention that specifies how a function in the API-implementing component receives parameters from the API-calling component and how the function returns a result to the API-calling component. The API-calling component 1330 (e.g., an operating system, a library, a device driver, an API, an application program, software or other module), makes API calls through the API 1320 to access and use the features of the API-implementing component 1310 that are specified by the API 1320. The API-implementing component 1310 may return a value through the API 1320 to the API-calling component 1330 in response to an API call.

    [0079] It will be appreciated that the API-implementing component 1310 may include additional functions, methods, classes, data structures, and/or other features that are not specified through the API 1320 and are not available to the API-calling component 1330. It should be understood that the API-calling component 1330 may be on the same system as the API-implementing component 1310 or may be located remotely and accesses the API-implementing component 1310 using the API 1320 over a network. While Figure 13 illustrates a single API-calling component 1330 interacting with the API 1320, it should be understood that other API-calling components, which may be written in different languages (or the same language) than the API-calling component 1330, may use the API 1320.

    [0080] The API-implementing component 1310, the API 1320, and the API-calling component 1330 may be stored in a machine-readable medium, which includes any mechanism for storing information in a form readable by a machine (e.g., a computer or other data processing system). Examples of machine-readable media include magnetic disks, optical disks, random access memory, read only memory, flash memory devices, etc.

    [0081] In FIG. 14 ("Software Stack"), an exemplary embodiment, applications can make calls to Services 1 or 2 using several Service APIs and to Operating System (OS) using several OS APIs. Services 1 and 2 can make calls to the OS using several OS APIs.

    [0082] Note that the Service 2 has two APIs, one of which (Service 2 API 1) receives calls from and returns values to Application 1 and the other (Service 2 API 2) receives calls from and returns values to Application 2. Service 1 (which can be, for example, a software library) makes calls to and receives returned values from OS API 1, and Service 2 (which can be, for example, a software library) makes calls to and receives returned values from both OS API 1 and OS API 2. Application 2 makes calls to and receives returned values from OS API 2.


    Claims

    1. A method comprising:

    displaying a map on a touch-sensitive display screen of an electronic device (1200) at a first zoom level (100);

    calculating, by the electronic device (1200), a plurality of routes extending from a starting point to a destination point;

    displaying the plurality of calculated routes from the starting point to the destination point simultaneously overlaid on the map on the touch-sensitive display screen at the first zoom level;

    for each calculated route of the plurality of calculated routes, displaying an associated callout (101', 102', 103', 104', 105') that displays a corresponding time to travel to the destination point; and

    receiving a selection of a route from the plurality of calculated routes via the touch-sensitive display screen; characterised in that the method further comprises the steps of:

    zooming in to display the map at a second zoom level (200), wherein a set of off-screen routes of the plurality of calculated routes is not displayed on the map at the second zoom level; and

    displaying a subset of the plurality of callouts on the map associated with each route of the set of off-screen calculated routes (102, 104, 105), each callout of the subset of the plurality of callouts indicating a direction to a respective off-screen calculated route .


     
    2. The method of claim 1, wherein each route of the plurality of calculated routes is highlighted and differentiable from all other displayed routes.
     
    3. The method of claim 2, wherein each route of the plurality of calculated routes is highlighted in a different color.
     
    4. The method of claim 1 further comprising displaying the selected route more prominently than the other displayed routes.
     
    5. The method of claim 1 further comprising displaying a start point indicator and a destination point indicator.
     
    6. The method of claim 5, wherein the plurality of routes further comprises at least one route-change indicator, the route-change indicator representing a location for a route change for the associated route.
     
    7. The method of claim 1 further comprising:

    providing navigation assistance along the selected route; and

    recalculating periodically a second plurality of navigational routes based at least on a current location of the electronic device.


     
    8. The method of claim 7 further comprising recalculating the second plurality of navigational routes at one of predetermined intervals, on an input from a user, and upon the occurrence of a predetermined event.
     
    9. The method of claim 7 further comprising continuously recalculating the second plurality of navigational routes.
     
    10. The method of claim 1, wherein the associated callout further displays at least one of a route name, a total distance, an estimated time of arrival, and a total price.
     
    11. The method of claim 1, wherein displaying the map comprises displaying the map at a zoom factor based on at least one of the following navigation factors:

    speed limit;

    distance to a next turn; and

    distance to a Point of Interest.


     
    12. The method of claim 1, wherein at least two of the plurality of calculated routes share a portion of a common route.
     
    13. The method of claim 1, wherein the callouts do not overlap any geographical identifying information.
     
    14. The method of claim 1 further comprising displaying a context-appropriate menu based upon an input from a user.
     
    15. The method of claim 1, wherein at least one navigation route of the plurality of navigation routes has a transit portion that requires use of a transit vehicle to traverse, the method further comprising:

    accessing a set of transit data related to the transit vehicle's traversal of the transit portion; and

    displaying a set of transit schedules from the set of transit data on the touch-sensitive display screen of the electronic device.


     
    16. The method of claim 1, wherein receiving a selection of a route comprises receiving selection of an associated callout for the route.
     
    17. A machine readable medium storing a program for executing by at least one processing unit of an electronic device, the electronic device comprising a touch-sensitive display, the program comprising sets of instructions for implementing the method according to any of the claims 1-16.
     
    18. An electronic device comprising:

    a touch-sensitive display screen;

    a set of processing units; and

    a machine readable medium storing a program for execution by at least one of the processing units, the program comprising sets of instructions for implementing the method according to any of claims 1-16.


     


    Ansprüche

    1. Verfahren umfassend:

    Anzeigen einer Karte auf einem berührungsempfindlichen Anzeigebildschirm eines elektronischen Geräts (1200) in einer ersten Zoomstufe (100);

    Berechnen, durch das elektronische Gerät (1200), einer Vielzahl von Routen, die sich von einem Startpunkt zu einem Zielpunkt erstrecken;

    Anzeigen der Vielzahl von berechneten Routen von dem Startpunkt zu dem Zielpunkt gleichzeitig überlagert auf der Karte auf dem berührungsempfindlichen Anzeigebildschirm in der ersten Zoomstufe;

    für jede berechnete Route der Vielzahl von berechneten Routen, Anzeigen eines zugeordneten Ausrufs (101', 102', 103', 104', 105'), der eine entsprechende Reisezeit zu dem Zielpunkt anzeigt; und

    Empfangen einer Auswahl einer Route aus der Vielzahl von berechneten Routen über den berührungsempfindlichen Anzeigebildschirm; dadurch gekennzeichnet, dass das Verfahren ferner die folgenden Schritte umfasst:

    Heranzoomen, um die Karte in einer zweiten Zoomstufe (200) anzuzeigen, wobei ein Satz von Routen außerhalb des Bildschirms der Vielzahl von berechneten Routen in der zweiten Zoomstufe nicht auf der Karte angezeigt wird; und

    Anzeigen einer Teilmenge der Vielzahl von Ausrufen auf der Karte, die jeder Route des Satzes von außerhalb des Bildschirms berechneten Routen (102, 104, 105) zugeordnet ist, wobei jeder Ausruf der Teilmenge der Vielzahl von Ausrufen eine Richtung zu einer jeweiligen außerhalb des Bildschirms berechneten Route anzeigt.


     
    2. Verfahren nach Anspruch 1, wobei jede Route der Vielzahl von berechneten Routen hervorgehoben und von allen anderen angezeigten Routen unterscheidbar ist.
     
    3. Verfahren nach Anspruch 2, wobei jede Route der Vielzahl von berechneten Routen in einer anderen Farbe hervorgehoben ist.
     
    4. Verfahren nach Anspruch 1, wobei die ausgewählte Route prominenter als die anderen angezeigten Routen angezeigt wird.
     
    5. Verfahren nach Anspruch 1 ferner umfassend Anzeigen eines Startpunktindikators und eines Zielpunktindikators.
     
    6. Verfahren nach Anspruch 5, wobei die Vielzahl von Routen ferner mindestens einen Routenänderungsindikator umfasst, wobei der Routenänderungsindikator einen Standort für eine Routenänderung für die zugeordnete Route darstellt.
     
    7. Verfahren nach Anspruch 1, ferner umfassend:

    Bereitstellen von Navigationshilfe entlang der ausgewählten Route; und

    periodische Neuberechnung einer zweiten Vielzahl von Navigationsrouten auf der Grundlage mindestens eines aktuellen Standorts des elektronischen Geräts.


     
    8. Verfahren nach Anspruch 7 ferner umfassend Neuberechnen der zweiten Vielzahl von Navigationsrouten in einem von vorbestimmten Intervallen, nach einer Eingabe eines Benutzers und bei dem Auftreten eines vorbestimmten Ereignisses.
     
    9. Verfahren nach Anspruch 7, ferner umfassend kontinuierliches Neuberechnen der zweiten Vielzahl von Navigationsrouten.
     
    10. Verfahren nach Anspruch 1, wobei der zugeordnete Ausruf ferner mindestens einen von einem Routennamen, einer Gesamtdistanz, einer geschätzten Ankunftszeit und einem Gesamtpreis anzeigt.
     
    11. Verfahren nach Anspruch 1, wobei Anzeigen der Karte Anzeigen der Karte mit einem Zoomfaktor umfasst, der auf mindestens einem der folgenden Navigationsfaktoren basiert:

    Geschwindigkeitsbegrenzung;

    Entfernung zu einer nächsten Abbiegung; und

    Entfernung zu einem Point of Interest.


     
    12. Verfahren nach Anspruch 1, wobei mindestens zwei aus der Vielzahl der berechneten Routen einen Teil einer gemeinsamen Route teilen.
     
    13. Verfahren nach Anspruch 1, wobei die Ausrufe keine geographischen Identifizierungsinformationen überlappen.
     
    14. Verfahren nach Anspruch 1 ferner umfassend Anzeigen eines kontextgerechten Menüs auf der Grundlage einer Eingabe eines Benutzers.
     
    15. Verfahren nach Anspruch 1, wobei mindestens eine Navigationsroute der Vielzahl von Navigationsrouten einen Transitabschnitt aufweist, der Verwendung eines Transitfahrzeugs erfordert, wobei das Verfahren ferner umfasst:

    Zugreifen auf einen Satz von Transitdaten, die sich auf die Transitfahrzeug-Durchquerung des Transitabschnitts beziehen; und

    Anzeigen eines Satzes von Transitplänen aus dem Satz von Transitdaten auf dem berührungsempfindlichen Anzeigebildschirm des elektronischen Geräts.


     
    16. Verfahren nach Anspruch 1, wobei Empfangen einer Auswahl einer Route Empfangen von Auswahl eines zugeordneten Ausrufs für die Route umfasst.
     
    17. Maschinenlesbares Medium, das ein Programm speichert, das von mindestens einer Verarbeitungseinheit eines elektronischen Geräts ausgeführt werden soll, wobei das elektronische Gerät eine berührungsempfindliche Anzeige umfasst, wobei das Programm Sätze von Anweisungen zum Implementieren des Verfahrens nach einem der Ansprüche 1-16 umfasst.
     
    18. Elektronisches Gerät umfassend:

    einen berührungsempfindlichen Anzeigebildschirm;

    einen Satz von Verarbeitungseinheiten; und

    ein maschinenlesbares Medium, das ein Programm zur Ausführung durch mindestens eine der Verarbeitungseinheiten speichert, wobei das Programm Sätze von Anweisungen zum Implementieren des Verfahrens nach einem der Ansprüche 1-16 umfasst.


     


    Revendications

    1. Un procédé comprenant :

    l'affichage d'une carte à un premier niveau de zoom (100) sur un écran d'affichage sensible au toucher d'un dispositif électronique (1200) ;

    le calcul, par le dispositif électronique (1200), d'une pluralité d'itinéraires s'étendant d'un point de départ à un point de destination ;

    l'affichage de la pluralité d'itinéraires calculés du point de départ au point de destination, simultanément surajoutés à la carte sur l'écran d'affichage sensible au toucher au premier niveau de zoom ;

    pour chaque itinéraire calculé de la pluralité d'itinéraires calculés, l'affichage d'une légende associée (101', 102', 103', 104', 105') qui affiche un temps correspondant pour atteindre le point de destination ; et

    la réception d'une sélection d'un itinéraire parmi la pluralité d'itinéraires calculés, via l'écran d'affichage sensible au toucher ; caractérisé en ce que le procédé comprend en outre les étapes de :

    zoom pour afficher la carte à un second niveau de zoom (200), un ensemble d'itinéraires hors écran de la pluralité d'itinéraires calculés n'étant pas affichés sur la carte au second niveau de zoom ; et

    l'affichage d'un sous-ensemble de la pluralité de légendes sur la carte associées à chaque itinéraire de l'ensemble d'itinéraires calculés hors écran (100, 200, 105), chaque légende du sous-ensemble de la pluralité de légendes indiquant une direction vers un itinéraire calculé hors écran respectif.


     
    2. Le procédé de la revendication 1, dans lequel chaque itinéraire de la pluralité d'itinéraires calculés est accentué et différentiable de tous les autres itinéraires affichés.
     
    3. Le procédé de la revendication 2, dans lequel chaque itinéraire de la pluralité d'itinéraires calculés est accentué en une couleur différente.
     
    4. Le procédé de la revendication 1, comprenant en outre l'affichage de l'itinéraire sélectionné de façon plus marquée que les autres itinéraires affichés.
     
    5. Le procédé de la revendication 1, comprenant en outre l'affichage d'un indicateur de point de départ et d'un indicateur de point de destination.
     
    6. Le procédé de la revendication 5, dans lequel la pluralité d'itinéraires comprend en outre au moins un indicateur de changement d'itinéraire, l'indicateur de changement d'itinéraire représentant un emplacement correspondant à un changement d'itinéraire de l'itinéraire associé.
     
    7. Le procédé de la revendication 1, comprenant en outre :

    la production d'une assistance à la navigation le long de l'itinéraire sélectionné ; et

    le recalcul périodique d'une seconde pluralité d'itinéraires de navigation au moins en partie sur la base d'un emplacement courant du dispositif électronique.


     
    8. Le procédé de la revendication 7, comprenant en outre le recalcul de la seconde pluralité d'itinéraires de navigation à l'un parmi : des intervalles prédéterminés, sur une entrée provenant d'un utilisateur, et à la survenue d'un événement prédéterminé.
     
    9. Le procédé de la revendication 7, comprenant en outre le recalcul continu de la seconde pluralité d'itinéraires de navigation.
     
    10. Le procédé de la revendication 1, dans lequel la légende associée affiche en outre au moins l'un parmi : un nom d'itinéraire, une distance totale, un temps d'arrivé estimé, et un prix total.
     
    11. Le procédé de la revendication 1, dans lequel l'affichage de la carte comprend l'affichage de la carte à un facteur de zoom au moins en partie basé sur l'un des facteurs de navigation suivants :

    limitation de vitesse ;

    distance à un prochain changement de direction ; et

    distance à un point d'intérêt.


     
    12. Le procédé de la revendication 1, dans lequel au moins deux de la pluralité d'itinéraires calculés partagent une section commune d'un itinéraire commun.
     
    13. Le procédé de la revendication 1, dans lequel les légendes ne se chevauchent avec aucune information d'identification géographique.
     
    14. Le procédé de la revendication 1, comprenant en outre l'affichage d'un menu approprié au contexte, sur la base d'une entrée provenant d'un utilisateur.
     
    15. Le procédé de la revendication 1, dans lequel au moins un itinéraire de navigation de la pluralité d'itinéraires de navigation comporte une section de transit qui nécessite pour sa traversée l'utilisation d'un véhicule de transit, le procédé comprenant en outre :

    l'accès à un ensemble de données de transit relatives à la traversée de la section de transit par le véhicule en transit ; et

    l'affichage, sur l'écran d'affichage sensible au toucher du dispositif électronique, d'un ensemble d'horaires de transit issu de l'ensemble de données de transit.


     
    16. Le procédé de la revendication 1, dans lequel la réception d'une sélection d'un itinéraire comprend la réception de la sélection d'une légende associée de l'itinéraire.
     
    17. Un support lisible par machine stockant un programme destiné à être exécuté par au moins une unité de traitement d'un dispositif électronique, le dispositif électronique comprenant un afficheur sensible au toucher, le programme comprenant des jeux d'instructions pour l'implémentation du procédé selon l'une des revendications 1 à 16.
     
    18. Un dispositif électronique comprenant :

    un écran d'affichage sensible au toucher ;

    un ensemble d'unités de traitement ; et

    un support lisible par machine stockant un programme destiné à être exécuté par au moins l'une des unités de traitement, le programme comprenant des jeux d'instructions pour implémenter le procédé selon l'une des revendications 1 à 16.


     




    Drawing












































    Cited references

    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description