TWI533264B - Route display and review - Google Patents

Description

Route display and review

The present invention is generally directed to a mapping application.

With the proliferation of mobile devices such as smart phones, users are enjoying a wide variety of applications that can be executed on their devices. One popular type of application is a mapping and navigation application that allows users to view maps and get route directions. Although such mapping and navigation applications are popular, such applications have disadvantages in terms of their user interface and features, which is inconvenient for the user.

Some embodiments of the present invention provide an integrated mapping application that includes a number of useful modalities, including orientation browsing, map searching, route recognition, and route navigation operations. These operations are complex tasks that, although complementary, each have very different user interface (UI) requirements. In some embodiments, the mapping application has a novel UI design that addresses the integration of the required controls for each of its different modalities into a smooth and coherent application user interface. Difficult challenges. The novel UI design and the application are defined to be performed by a device having a touch sensitive screen that displays the output of the application. In some embodiments, the device has a multi-touch interface for interacting with the application by allowing a user to provide touch and gesture input via the screen.

In some embodiments, one of the mapping application UI targets is to enable screen control The items are kept to a minimum to display as many interactive maps as possible. One element in this design is a button cluster that floats over the content itself rather than (as typical of a phone UI element) occupying the full width of the screen. In addition, this cluster is adapted to the current task of animating the content of the cluster as it moves between different modalities (eg, between browsing, searching, routing, and navigation). This general element of an adaptive nature enables the mapping application to optimize for its tasks while maintaining consistent appearance and interaction models as they transition between tasks.

In some embodiments, an example of an adaptive floating control item is a list control item. Some embodiments of the mapping application display when there is a chance to display a list of items (the list is a list of instructions in a route, or a list of search results when multiple results are found for a given query) A list button is used as one of the floating controls. In some embodiments, touching the list button brings up a modal list view. Having a modal list view keeps the mapping application simple and keeps the map in front and centered. In some embodiments, the manifest view itself is adapted and optimized for the type of manifest displayed, as the search results will be displayed along with star ratings (when available) and the routing steps will include instruction arrows.

Another floating control item is a control item for viewing a map in three dimensions (3D) or checking a route. The mapping application provides 3D controls as a fast mechanism for entering and exiting 3D. This control also serves as an indicator that (1) the current view is a 3D view, and (2) a 3D perspective can be used for a given map view (eg, a reduced map view may not have a 3D view available) ).

In addition to the 3D control, the mapping application of some embodiments also allows a user to transition a map view from a two-dimensional (2D) presentation to a 3D via a gesture input to the multi-touch interface of the device. Presented. For example, the two user input functions enable the user to "push down" a 2D map view into a 3D map view or "pull up" a 3D map view into a 2D map view. This can also be considered as two fingers A virtual camera is pulled down from a 2D (from the top) view to a 3D (side angle) view. As further described below, in some embodiments, a 3D view of the map is generated by presenting the map view at a particular location that is conceptually considered to capture the location of one of the virtual views of the map view.

In some embodiments, the mapping application allows a user to also rotate a 2D or 3D map via a gesture input. In some embodiments, the mapping application is a vector mapping application that allows direct manipulation of the map (such as rotation and 2D/3D manipulation) while browsing the map. However, some of the effects on the map can be confusing. In the absence of an easy way to return to the north-up orientation (i.e., the orientation of the north aligned with the top of the device), some users may have difficulty interacting with the map view. To address this issue, the mapping application of some embodiments provides an unobtrusive floating compass control on the map that acts both as an indicator pointing north and as a button to resume northward orientation. In order to further minimize clutter on the map, the mapping application only displays the button in a limited number of situations, such as when the local map is rotated.

In order to minimize the number of screen controls, the specific infrequently used actions are placed in the primary UI screen located after the "page curl", and the page curl is displayed on the map provided by the application. On the view. In some embodiments, the page curl is permanently displayed on at least some of the views provided by the application. For example, in some embodiments, the application displays the page curl permanently on the initial map view, and the application provides an initial map view to allow a user to browse or search for an orientation or identify a route. In some embodiments, the page is curled into a controllable UI item that has a different appearance in different embodiments, such as buttons, page roll-up angles, eye-catching hint angles for maps, and the like. Page curl (1) indicates the orientation of another set of controls that are conceptually "behind" the current view, and (2) after selection, directs the application to "peel" the current view to display the display control An animation of another view of another collection. The map painted The application allows the user to control page curl using a number of different gestures (eg, select, drag, touch, swipe, rotate, etc.). In some embodiments, when the user provides different gesture input, the mapping application displays an animation that the page is folded, lifted, and/or curled in a different combination of angle and rotation, as if the user was grasping Hold a corner of the paper to manipulate a piece of paper.

The use of page curling allows the application to display more of the map, while providing an unobtrusive way to access additional functionality provided by another set of controls. Additionally, in some embodiments, the application does not use page curling in map views where additional functionality is considered inappropriate for current tasks. For example, in some embodiments, the application does not display this page curl while presenting the map view used during navigation.

In some embodiments, the application displays page curl for each map view provided by the application. In other embodiments, the application does not display page curl with every map view provided by the application. For example, the application of these embodiments does not display page curl when a map view is used during navigation. However, in some embodiments, the page curls back when the application is displaying an overview of the route while navigating.

In some embodiments, the search field of the mapping application is another UI tool that the application uses to smooth transitions between different modalities. In some embodiments, a user can initiate a search by tapping in the search field. The touch guides the application to present an animation that (1) presents a screen keypad and (2) opens a search table filled with valuable completions. This table has some important subtleties. When the search field is touched and before the word is edited, or when the search field is empty, the table contains a list of "recently used", in some embodiments, "recently used" is requested by the user. Recent search and route guidance. This makes it very easy to quickly bring out the results of recent accesses.

After any edits in the search field, the table is populated by a search completion from both the local source (eg, bookmarks, contacts, recent searches, recent route directions, etc.) and the remote server. However, some embodiments include only recent route guidance when the user has not typed any text into the search field. Once the text is typed, the mapping application removes the recent route guidance from the search completion table. Incorporating the user's contact card into the search interface adds additional flexibility to the design. When the display is recently used, in some embodiments, one of the directions from the current orientation to the user's home is always provided, while in other embodiments, the route is provided in the context of the content deemed "appropriate". Also, when the search term matches at least a portion of an address tag (eg, "ork" of "work"), in some embodiments, the application presents the tagged user as one of the search tables. address. Together, these behaviors make searching the UI a powerful way to get results on a map from multiple sources. In addition to allowing a user to initiate a search, in some embodiments, the presence of a text field in the main map view also allows the user to see the query corresponding to the search results on the map and remove the query by clearing the query. Wait for the search results.

Another way in which the mapping application closely integrates the search and route identification experience is by providing a number of different ways to get guidance. As mentioned above, the lookup table provides quick access to the most recently used route. For any orientation selected on the map view, in some embodiments, the mapping application also presents an information display banner (eg, a window) that displays a route extracted from the current orientation to one of the pins (eg, A driving route) without leaving the map view one of the quick route navigation UI controls (eg, buttons). In addition, the mapping application also provides a selectable navigation UI control (eg, a button) on the main map view (eg, in the upper left corner) that presents a modal guide when selected (modal Directions) The editing interface that enables the user to request more customized routes, such as routes that are not starting from the current orientation or instead of one of the driving routes. In some embodiments, the mapping application provides a number of different selectable routes based on which one of the route queries is received via the guidance UI control. Implemented here In the example, the user can then select one of the routes. In some embodiments, one of the routes is presented as a preset selected route, and the user can change the selected route to one of the other presented routes. It should be noted that although neither the route history entry nor the fast route navigation control in the search field performs an action that cannot be achieved with the guidance item, the two serve as important accelerators that make it easier to obtain the most general desired route.

Once the route guidance has been obtained, the route guidance will remain in existence until the route guidance is clearly cleared. This enables the mapping application to enter one of the modes for navigation optimization. This navigation mode has many novel features. A novel feature is that at any time during navigation, the user can present a full screen mode for a display view optimized for turn-by-turn direction and a display for the remaining route more suitable for browsing. Move between the overview modes of the view. Some embodiments also allow the search to be performed while navigating in the overview mode. For example, some embodiments provide a pull-down handle that allows the search field to be pulled into the overview display. Alternatively or in combination, some embodiments allow for a search to be performed via voice recognition input of the devices of some embodiments during navigation.

The continuity between the overview mode and the full screen mode is achieved by a local set of transitions and a constant set of controls in the map. In order to enter the full screen mode, in some embodiments, the application (1) automatically hides the floating control items and along the top column (with UI controls) and (2) fully expands the map. The app limits interaction with the map during full screen mode. In some embodiments, a touch is required to access the automatically hidden controls, and despite that, the controls are still adapted to have a full screen navigation appearance while highlighting the ETA along the top column.

The mapping application of some embodiments allows the user to stop navigating in both the overview mode and the full screen mode at any time during navigation by selecting one of the controls to end navigation. The mapping application of some embodiments allows the user to navigate Modify the turn-by-turn navigation view at any time to see an alternative three-dimensional (3D) view or a two-dimensional (2D) view. In some embodiments, the 3D steering cue navigation is an animated visualization of the navigational route emerging from the vantage point of the virtual camera traveling in the direction of the route based on the direction of travel of the user and, in some embodiments, the direction of travel and Speed is captured by direction data associated with the device (eg, GPS data, triangulation cell tower data, etc.).

While navigating, the mapping application of some embodiments allows a user to change the position of the virtual camera (i.e., the position at which the rendered navigation route begins) via a gesture input on the screen of the device. The movement of the virtual camera (i.e., the movement of the appearing route from its location) allows the mapping application to present an alternative 3D view. Some embodiments even use a virtual camera to visualize a top-down 2D view for turn-tip navigation, while other embodiments visualize a top-down 2D view by zooming in and out of a 2D map. In some embodiments, the mapping application presents a 3D button that acts as both a 3D indicator and a 3D initiator/two state switch.

Different embodiments provide different illustrative action inputs to adjust the 3D/2D view during turn alert navigation. In some embodiments, the gesture input is a two-finger pinch/expansion operation to adjust the zoom level. This adjustment of the zoom level inherently adjusts the position and rotation of the camera relative to the route guidance, and thereby changes the 3D perspective of the route guidance. Alternatively, in addition to or in addition to the zooming operation, other embodiments provide other illustrative motion inputs (e.g., finger drag operations) that change the position of the camera. In still other embodiments, a gesture input (eg, a finger drag operation) briefly changes the view direction of the camera to allow a user to briefly scan one side of the navigation route. In these embodiments, the application returns the camera to its previous view along the route after a short period of time.

The mapping application of some embodiments provides a realistic road traffic sign that is used during navigation and during browsing of the identified route. In some embodiments, the markers are textured images that are very similar to the actual road sign, and the markers include Let arrows, text, shields, and distances. The mapping application of some embodiments presents a number of variations in a large number of different contexts. For the driving control that is closely followed, the sub-marks that just hang under the main sign are presented. In some embodiments, the logo is presented in different colors according to regional criteria. Also, when a driving is passed during navigation, the mapping application uses the simulated sign to move over the road to animate the sign to leave. When approaching a driver, the mapping application draws attention to the logo by subtle animations (eg, flashing across the entire logo).

As noted above, the mapping application of some embodiments uses a seemingly realistic road traffic sign to provide a novel way of browsing a route that the application has identified. For example, in some embodiments, the mapping application allows a user to select and scroll through a sign along a junction of the identified route as the application presents the identified route to the user. A presentation or eye-catching prompt when the user scrolls through each of the markers (eg, via a color eye-catching prompt or via another geometry (eg, a circle or other token) that marks the portion) with the current focus Part of the associated route. Alternatively or in combination, the user may scroll through each of the markers by selecting different joints of the route to view the markers associated with the joints. Some of these embodiments provide this interaction only for routes that are not defined between the user's current location and the destination. In other words, such embodiments do not provide this browsing experience when presenting a route that connects the user's current location to the destination. However, other embodiments provide a route browsing experience via road traffic signs in other or all other contexts that display the route.

The above features of the mapping application of some embodiments, as well as some other features, are further described below. In the above and following description, many of these features are described as part of an integrated mapping application that provides one of novel orientation browsing, location search, route recognition, and route navigation operations. However, those skilled in the art will recognize that in other embodiments, such novel operations are performed by an application that does not perform all such operations or perform other operations in addition to such operations.

The foregoing summary is intended to serve as a brief description of some embodiments of the invention. It is not intended to be an introduction or overview of all the subject matter disclosed in this document. The embodiments described in the [Summary of the Invention] and other embodiments will be further described in the following [Embodiment] and [Embodiment]. Thus, in order to understand all of the embodiments described in this document, a comprehensive review of the "invention", "embodiment" and "schematic description" is required. In addition, the claimed subject matter is not limited by the illustrative details in the "invention", "embodiment" and "schematic description", but is defined by the scope of the appended patent application, because the claimed subject matter can be in other specific forms. To reflect the spirit of the target.

100‧‧‧ devices

105‧‧‧First stage

110‧‧‧ second stage

115‧‧‧ third stage

120‧‧‧User Interface (UI)

125‧‧‧Parking area

130‧‧‧Map drawing application

140‧‧‧top column

145‧‧‧Location Control Item/List View Control

150‧‧‧3D control

155‧‧‧Page Curl Control

160‧‧‧Guidelines

165‧‧‧Search field

170‧‧‧Bookmark Controls

205‧‧‧ first stage

210‧‧‧ second stage

215‧‧‧ third stage

220‧‧‧ fourth stage

225‧‧‧ fifth stage

230‧‧‧ sixth stage

235‧‧‧List view control

240‧‧‧ route generation control

245‧‧‧Start control

250‧‧‧End control

255‧‧‧Clear control

260‧‧‧ route

261‧‧‧ route

300‧‧‧ compass

305‧‧‧ first stage

310‧‧‧ second stage

315‧‧‧ third stage

320‧‧‧ fourth stage

325‧‧‧ fifth stage

326‧‧‧ current position indicator

345‧‧‧simulated light projection

405‧‧‧ first stage

410‧‧‧ second stage

415‧‧‧ third stage

420‧‧‧ fourth stage

425‧‧‧User's current location

505‧‧‧Virtual Camera

510‧‧‧ first stage

515‧‧‧ second stage

520‧‧‧ third stage

525‧‧‧3D map view

530‧‧‧3D map view

535‧‧‧3D map scene

540‧‧‧2D map view

545‧‧‧2D map

550‧‧‧ track

555‧‧‧Track

600‧‧‧Virtual Camera

605‧‧‧ first stage

610‧‧‧ second stage

615‧‧‧ third stage

625‧‧‧3D map view

630‧‧‧3D map view

635‧‧‧3D map

640‧‧‧3D map view

705‧‧‧ first stage

710‧‧‧ second stage

715‧‧‧ third stage

720‧‧‧ fourth stage

725‧‧‧ Current orientation of the device

740‧‧‧2D view/2D map

745‧‧‧3D map

805‧‧‧ first stage

810‧‧‧ second stage

815‧‧‧ third stage

905‧‧‧ first stage

910‧‧‧ second stage

915‧‧‧ third stage

920‧‧‧ fourth stage

925‧‧‧ fifth stage

930‧‧‧6th stage

1005‧‧‧ first stage

1010‧‧‧ second stage

1015‧‧‧ third stage

1020‧‧‧ fourth stage

1025‧‧‧2D map view

1030‧‧‧Rotated map view

1105‧‧‧First stage

1110‧‧‧ second stage

1115‧‧‧ third stage

1120‧‧‧ fourth stage

1125‧‧‧Map view

1130‧‧‧Rotated map view

1205‧‧‧First stage

1210‧‧‧ second stage

1215‧‧‧ third stage

1220‧‧‧2D map view

1225‧‧‧2D map view

1230‧‧‧2D map view

1300‧‧‧Program

1405‧‧‧First stage

1410‧‧‧ second stage

1415‧‧‧ third stage

1420‧‧‧ fourth stage

1505‧‧‧First stage

1510‧‧‧ second stage

1515‧‧‧ third stage

1520‧‧‧ fourth stage

1605‧‧‧ first stage

1610‧‧‧ second stage

1615‧‧‧ third stage

1620‧‧‧ fourth stage

The first phase of 1701‧‧

1702‧‧‧ second stage

1703‧‧‧ third stage

1710‧‧‧3D map

1712‧‧‧Virtual Camera

1714‧‧‧3D map view

1724‧‧‧3D map view

1734‧‧‧3D map view

Line 1750‧‧

1755‧‧‧ line

1800‧‧‧Virtual Camera

1805‧‧‧First stage

1810‧‧‧ second stage

1815‧‧‧ third stage

1825‧‧‧3D map view

1830‧‧‧3D map view

1835‧‧‧3D map

1840‧‧‧3D map

1850‧‧‧ arc

1855‧‧‧Location

1860‧‧‧ position

1865‧‧‧ position

1900‧‧‧Processing (or map display) pipeline

1905‧‧‧ base map extractor

1910‧‧‧Grid build processor

1915‧‧‧Grid Builder

1920‧‧‧ basemap provider

1925‧‧‧Map Display Engine

1930‧‧‧Virtual camera

1975‧‧‧ Controller

2005‧‧‧First Stage

The second phase of 2010‧‧

The third phase of 2015‧‧

2020‧‧‧ fourth stage

2040‧‧‧Search Form

2045‧‧‧ icon

2050‧‧‧ Bookmark icon

2055‧‧‧Cancel control

2060‧‧‧Start control

2105‧‧‧ first stage

2110‧‧‧ second stage

2115‧‧‧ third stage

2120‧‧‧ fourth stage

2155‧‧‧Search Form

2190‧‧ pin

2205‧‧‧ first stage

2210‧‧‧ second stage

2215‧‧‧ third stage

2220‧‧‧ fourth stage

2250‧‧‧Screen keypad

2255‧‧‧Search Form

2290‧‧‧ banner

2295‧‧‧ route extraction control

2305‧‧‧First stage

2310‧‧‧ second stage

2315‧‧‧ third stage

2390‧‧‧Pushpin

2395‧‧‧Pushpin

2405‧‧‧First stage

2410‧‧‧ second stage

2415‧‧‧ third stage

2420‧‧‧ fourth stage

2455‧‧‧Search Form

2505‧‧‧ first stage

2510‧‧‧ second stage

2515‧‧‧ third stage

2520‧‧‧ fourth stage

2555‧‧‧Search Form

2605‧‧‧First stage

2610‧‧‧ second stage

2615‧‧‧ third stage

2620‧‧‧ fourth stage

2630‧‧‧ Bookmark icon

2700‧‧‧Program

2805‧‧‧First stage

2806‧‧‧top column

2810‧‧‧ second stage

2815‧‧‧ third stage

2820‧‧‧ fourth stage

2830‧‧‧Search field

2835‧‧‧List view control

2840‧‧·Pushpin

2845‧‧‧Pushpin

2846‧‧‧Information Banner

2850‧‧‧ points of interest

2855‧‧ pin

2890‧‧‧3D illustration

2900‧‧‧Map drawing application

2905‧‧‧Device

2910‧‧‧Search Completion Manager

2915‧‧‧Local Source Manager

2920‧‧‧Remote Source Manager

2925‧‧‧List Manager

2930‧‧‧Search Query Profiler

2935‧‧‧New search completed repository

2940‧‧‧New Route Guidance Repository

2950‧‧‧Contacts Repository

2955‧‧‧Bookmark repository

2960‧‧‧Search and Map Server

2965‧‧‧Search completed repository

2970‧‧‧ Route Guidance Repository

Map of 3000‧‧‧

3005‧‧‧ first stage

3010‧‧‧ second stage

3015‧‧‧ third stage

3025‧‧‧Pushpin

3030‧‧‧"X" button

3105‧‧‧ first stage

3110‧‧‧ second stage

3115‧‧‧ third stage

3120‧‧‧ fourth stage

3140‧‧‧Search Form

3200‧‧‧ Procedure

3300‧‧‧Program

3400‧‧‧Program

3505‧‧‧ first stage

3510‧‧‧ second stage

3515‧‧‧ third stage

3520‧‧‧ fourth stage

3555‧‧‧Search Form

3605‧‧‧ first stage

3610‧‧‧ second stage

3615‧‧‧ third stage

3620‧‧‧ fourth stage

Map of 3630‧‧

3705‧‧‧ first stage

The second phase of 3710‧‧

3715‧‧‧ third stage

3720‧‧‧ fourth stage

3755‧‧‧Search Form

3760‧‧ Search Search

3800‧‧‧Graphical User Interface (GUI)

The first phase of 3805‧‧

The second phase of 3810‧‧

3815‧‧‧ third stage

3820‧‧‧ fourth stage

3825‧‧‧The fifth stage

3830‧‧‧6th stage

3835‧‧‧Media display area

3840‧‧‧ index label

3845‧‧‧Information display area

3850‧‧‧top column

3860‧‧·Pushpin

3865‧‧‧ banner

3875‧‧‧ arrow

3895‧‧‧"Previous" button

3905‧‧‧First stage

3910‧‧‧ second stage

3915‧‧‧ third stage

3920‧‧‧ fourth stage

3925‧‧‧ fifth stage

3940‧‧‧Search Form

4005‧‧‧First stage

4010‧‧‧ second stage

4015‧‧‧ third stage

4020‧‧‧ fourth stage

4025‧‧‧ fifth stage

4030‧‧‧Sixth stage

4035‧‧‧ seventh stage

4040‧‧‧8th stage

4060‧‧‧Pushpin

4065‧‧‧ banner

4070‧‧‧"List" button

4075‧‧‧ Inputs

4105‧‧‧ first stage

4110‧‧‧ second stage

4115‧‧‧ third stage

4120‧‧‧ fourth stage

4125‧‧‧ fifth stage

4130‧‧‧6th stage

4200‧‧‧ Procedure

4305‧‧‧First stage

The fourth phase of 4310‧‧

4315‧‧‧ third stage

4320‧‧‧Fourth stage

4360‧‧‧User Interface (UI) Project

4365‧‧‧User Interface (UI) Project

4370‧‧‧User Interface (UI) Project

4375‧‧‧User Interface (UI) Project

4380‧‧‧User Interface (UI) Project

4405‧‧‧First stage

4410‧‧‧ second stage

4415‧‧‧ third stage

4420‧‧‧ fourth stage

4450‧‧‧ index label

4455‧‧‧Comment

4460‧‧‧top column

4505‧‧‧First Stage

4510‧‧‧ second stage

4515‧‧‧ third stage

4520‧‧‧ fourth stage

4545‧‧‧ Expanded information display area

4550‧‧‧Comment Index Label

4555‧‧‧Information Index Label

4560‧‧‧User Interface (UI) Project

4565‧‧‧User Interface (UI) Project

4575‧‧‧User Interface (UI) Project

4601‧‧‧Users

4602‧‧‧Users

4603‧‧‧ User's finger

4604‧‧‧ User's finger

4605‧‧‧First stage

4610‧‧‧ second stage

4615‧‧‧ third stage

4705‧‧‧First Stage

4710‧‧‧ second stage

4715‧‧‧ third stage

4750‧‧‧ mark

4805‧‧‧ first stage

4810‧‧‧ second stage

4815‧‧‧ third stage

4820‧‧‧Device

4825‧‧‧large screen display area

4830‧‧‧Pushpin

4835‧‧‧ banner

4905‧‧‧First stage

4910‧‧‧ second stage

4915‧‧‧ third stage

4920‧‧‧ fourth stage

4930‧‧‧ instruction mark

4950‧‧‧Start control

5005‧‧‧ first stage

5010‧‧‧ second stage

5015‧‧‧ third stage

5020‧‧‧ fourth stage

5035‧‧‧ Directional icon

5055‧‧‧Search Form

5105‧‧‧First stage

5110‧‧‧ second stage

5115‧‧‧ third stage

5120‧‧‧Table device

5205‧‧‧First stage

5210‧‧‧ second stage

5215‧‧‧ third stage

5220‧‧‧ fourth stage

5225‧‧‧First scrollable sign

5235‧‧‧New sign

5250‧‧‧New section

5290‧‧‧ current joint indicator

5305‧‧‧First stage

The fifth phase of 5310‧‧

5315‧‧‧ third stage

5400‧‧‧Device

5405‧‧‧First stage

5410‧‧‧ second stage

5415‧‧‧ sign

5420‧‧‧ mark

5425‧‧‧ mark

5430‧‧‧ mark

5435‧‧‧top column

5505‧‧‧First stage

5510‧‧‧ second stage

5515‧‧‧ third stage

5520‧‧‧Last instruction mark

5525‧‧‧Overview control

5530‧‧‧top column

5540‧‧‧Continue control

5570‧‧‧End control

5600‧‧‧Program

5700‧‧‧ devices

5705‧‧‧First Stage

5710‧‧‧ second stage

5715‧‧‧ third stage

5717‧‧‧ fourth stage

5719‧‧‧The fifth stage

5720‧‧‧User interface

5721‧‧‧6th stage

5725‧‧‧Parking area

5730‧‧‧Map drawing application

5740‧‧‧top column

5750‧‧‧ Floating 3D Controls

5760‧‧‧Guidelines

5765‧‧‧Search field

5780‧‧‧Guide type page

5782‧‧‧Table

5784‧‧‧ mark

5805‧‧‧First Stage

5810‧‧‧ second stage

5815‧‧‧ third stage

5901‧‧‧First stage

5902‧‧‧ second stage

5903‧‧‧ third stage

5910‧‧‧3D navigation map scene

5912‧‧‧Virtual Camera

5916‧‧‧Device orientation indicator

5918‧‧‧3D map view

5928‧‧‧Three-dimensional navigation map view

5938‧‧‧2D map view

5950‧‧‧Track

5955‧‧‧Track

5960‧‧‧3D button

6005‧‧‧ first stage

6010‧‧‧ second stage

6015‧‧‧ third stage

6030‧‧‧Car icon

6040‧‧‧ banner

6050‧‧‧ banner

6060‧‧‧ instruction mark

6075‧‧‧ Overview Controls

6100‧‧‧Device

6105‧‧‧First stage

6110‧‧‧ second stage

6115‧‧‧ third stage

6120‧‧‧ fourth stage

6125‧‧‧ fifth stage

6130‧‧‧6th stage

Route 6135‧‧

6140‧‧‧ "Start" user interface control

6200‧‧‧ State diagram

6205‧‧‧Map browsing status

6210‧‧‧ Indicates the action input identification status

6215‧‧‧ State (rotation state)

6220‧‧‧ Status (mobile browsing status)

6225‧‧‧ Status

6230‧‧‧Inertial calculation status

6235‧‧‧Perspective change state

6240‧‧‧Inertial calculation status

6245‧‧‧Rebound calculation status

6250‧‧‧The status of the banner used to display the selected orientation

6255‧‧‧Used to display the status of the prepared area of the selected position

6260‧‧‧Search type suggestion status

6265‧‧‧Used to display the status of search results

6270‧‧‧ route entry status

6275‧‧‧Route display status

6280‧‧‧Navigation Status/Navigation Mode

6285‧‧‧Step mode status

6290‧‧‧Automatic stepping state

6300‧‧‧Activity Computing Device Architecture/Action Computing Device

6305‧‧‧Processing unit

6310‧‧‧ memory interface

6315‧‧‧ peripheral device interface

6320‧‧‧ camera subsystem

6325‧‧‧Wireless communication subsystem

6330‧‧‧ Audio subsystem

6335‧‧‧I/O subsystem

6340‧‧‧Optical sensor

6345‧‧‧ Directional Sensor

6350‧‧‧Acceleration sensor

6355‧‧‧Touch Screen Controller

6360‧‧‧Other input controllers

6365‧‧‧ touch screen

6370‧‧‧ memory

6372‧‧‧Operating System (OS)

6374‧‧‧Communication Directive

6376‧‧‧Image User Interface Instructions

6378‧‧‧Image Processing Instructions

6380‧‧‧Input processing instructions

6382‧‧‧Operation Processing Instructions

6384‧‧‧ camera instructions

6400‧‧‧Electronic system

6405‧‧‧ Busbar

6410‧‧‧Processing unit

6415‧‧‧Graphical Processing Unit (GPU)

6420‧‧‧System Memory

6425‧‧‧Network

6430‧‧‧Reading Memory (ROM)

6435‧‧‧Permanent storage device

6440‧‧‧Input device

6445‧‧‧ Output device

6500‧‧‧Working environment

6502a‧‧‧Customer Devices

6502b‧‧‧Customer device

6502c‧‧‧Customer device

6510‧‧‧Wired or wireless network

6512‧‧‧Access device

6514‧‧‧ gateway

6520‧‧‧ Wide Area Network (WAN)

6530‧‧‧Map service

6550‧‧‧Other services

6560‧‧‧GPS satellite

The novel features of the invention are set forth in the appended claims. However, for purposes of explanation, several embodiments of the invention are set forth in the following figures.

Figure 1 illustrates an example of a device that performs an integrated mapping application of some embodiments.

Figure 2 illustrates an example of an integrated application that adaptively modifies a cluster of floating control items.

Figure 3 illustrates an example of an integrated application that adaptively modifies a cluster of floating control items.

4 illustrates a manner in which a mapping application of some embodiments provides a 3D control as a fast mechanism for entering a 3D mode for three-dimensional viewing of a map orientation.

Figure 5 presents a simplified example to illustrate the concept of a virtual camera.

Figure 6 conceptually illustrates perspective adjustment features provided by the mapping application of some embodiments.

Figure 7 illustrates an example of two indicative actions for downsampling a 2D map into a 3D map.

Figure 8 illustrates the transition from a 2D map view to a 3D map view.

Figure 9 illustrates that the mapping application of some embodiments changes the appearance of the 3D control to indicate different 2D and 3D states of the map view.

Figure 10 illustrates an example of rotating a 2D map and using a compass to straighten a rotated map.

Figure 11 illustrates another example of a rotating map in some embodiments of the invention.

Figure 12 illustrates the rotational operation along with the inertial effect.

Figure 13 illustrates the rotational operation along with the inertial effect.

14 illustrates that the mapping application of some embodiments uses novel techniques to adjust the text and/or symbols appearing in the map view or to keep the text and/or symbols unadjusted as the map view is rotated.

Figure 15 illustrates an example of directed text and/or symbols.

Figure 16 illustrates an example of a user transitioning from a 3D map view to a 2D map view via two indicative action actions.

Figure 17 illustrates zoom adjustment features provided by the mapping application of some embodiments.

Figure 18 conceptually illustrates features provided by the mapping application of some embodiments for maintaining the position of the virtual camera within a defined range along an arc of a circle.

Figure 19 conceptually illustrates a process or map rendering pipeline executed by a mapping application of some embodiments to visualize a map for display at a client device.

Figure 20 illustrates the interaction of a user who has a search list with a list of recent searches and recent directions for the user with an application executing on the user's device.

Figure 21 illustrates an example of typing a search query and performing a search in a search field.

Figure 22 illustrates an example of an instant display of a search list that initiates a search query and a list of recommended search completions.

Figure 23 illustrates an example of an instant display of a search list that initiates a search query and a list of recommended search completions.

Figure 24 illustrates the typing of a partial address and obtaining a home address from a contact card. An example of a guideline.

Figure 25 illustrates an example of a guide for a user to type a partial search term and obtain a work address from a contact card.

Figure 26 illustrates an example of typing a partial search query and a list selection bookmark for the search completion in the self-search table.

Figure 27 conceptually illustrates a procedure performed by some embodiments for determining the order in which suggested search completions from different sources are displayed in a search table.

Figure 28 illustrates an example of performing a mapping application on a device having a relatively large display area compared to a display area of a smaller device.

Figure 29 illustrates an example architecture of a mapping application that provides a list of suggested search completions based on a search query.

Figure 30 illustrates an example of clearing search results from a map.

Figure 31 illustrates an example of interaction between a user executing a selected search result displayed on a map and an application executing on a user's device.

32 illustrates a procedure performed by some embodiments for determining a particular type of transition to be displayed between a current map view of a user and a target map view containing search results for a user performing a search query.

Figure 33 illustrates a procedure performed by some embodiments to determine whether to modify a target zone when the target zone at least partially overlaps the original zone originally defined by the mapping application.

Figure 34 illustrates a procedure performed by some embodiments to determine whether to display from the original region when (1) the target region at least partially overlaps with the original region originally defined by the mapping application and when considering the target region to be modified Animation to the target area.

Figure 35 illustrates a situation in which an application displays a transition to a target map area containing a corresponding search result without providing any animation between the current map view and the target map view.

Figure 36 illustrates the application detecting the search results in the original current map view and therefore There is no need to scale or transition to any new target map area with animation.

FIG. 37 illustrates a case where the search result in the target map view is not in the original area, so that the application expands the target area and displays an animation between the original area and the target area.

Figure 38 conceptually illustrates a UI page for displaying detailed information about the selected orientation.

Figure 39 illustrates an example of a mapping application that uses a 3D rendering operation to display a particular search result.

Figure 40 conceptually illustrates an animation showing a satellite image of one orientation.

Figure 41 illustrates an image showing the orientation.

Figure 42 conceptually illustrates a procedure performed by some embodiments for displaying different types of images when launching a "details screen" for displaying detailed information about the orientation.

Figure 43 illustrates scrolling off the index tab.

Figure 44 illustrates the launching of a third party application when the user selects an entry displayed in the information display area.

Figure 45 illustrates launching a third party application when a user selects a UI project for a third party application.

Figure 46 illustrates two mapping application execution individuals executing on two different devices of two different users while presenting two different sets of information in the same orientation.

Figure 47 illustrates the display of indicia on an index tab in the detailed information screen for the selected orientation.

Figure 48 illustrates the interaction of a user for displaying a "Detailed Information Screen" for a particular orientation with a mapping application of some embodiments.

Figure 49 illustrates an example of interaction between a user using a route selection guide and a mapping application.

Figure 50 illustrates the user and mapping application used to obtain route selection guidelines An example of the interaction.

Figure 51 conceptually illustrates one example of displaying route selection guidelines in a relatively large display area of the device.

Figure 52 illustrates a set of scrollable command flags scrolling through a particular route selected by the user.

Figure 53 illustrates scrolling through different scrollable markers.

Figure 54 illustrates an example of one of a set of scrollable instruction flags showing a particular route selected by a user.

Figure 55 illustrates an example of interaction between a user and an application for switching to the overview mode while reviewing the selected route.

Figure 56 conceptually illustrates a procedure performed by some embodiments to allow a user to view a flag for a set of instructions for a joint in a route between a starting orientation and an ending orientation.

Figure 57 illustrates an example of a device that performs a mapping application of some embodiments.

Figure 58 illustrates a manner in which the navigation application of some embodiments provides 3D control items as a fast mechanism for entering a 3D navigation mode.

Figure 59 illustrates the concept of a virtual camera.

Figure 60 illustrates an example of interaction between a user using a route selection guide and a mapping application.

Figure 61 illustrates a device for displaying a mapping application when the local mapping application changes from a non-immersive map view for map browsing to an immersive map view for navigation.

62A-62B conceptually illustrate state diagrams depicting different states of the integrated mapping, search, and navigation applications of some embodiments and transitions between such states.

Figure 63 is an example of the architecture of a mobile computing device.

Figure 64 conceptually illustrates an example of an electronic system to which some embodiments of the present invention are implemented.

Figure 65 illustrates a map service job environment in accordance with some embodiments.

Numerous details, examples, and embodiments of the invention are set forth and described in the following detailed description. However, it will be apparent to those skilled in the art that the present invention is not limited to the illustrated embodiments and the invention may be practiced without the specific details and examples discussed.

Some embodiments of the present invention provide an integrated mapping application that includes a number of useful modalities, including orientation browsing, map searching, route recognition, and route navigation operations. In some embodiments, the application is defined to be executed by a device having one of the touch-sensitive screens that displays the output of the application. In some embodiments, the device has a multi-touch interface for allowing a user to interact with the application by providing touch and gesture input via the screen. Examples of such devices are smart phones (eg, iPhone® sold by Apple Inc., mobile phones operating Android® operating systems, mobile phones operating Windows 8® operating systems, etc.).

Several detailed embodiments of the invention are described below. Section I describes the UI controls and map browsing experience provided by the mapping application of some embodiments. Section II then describes the characteristics of the novel search field of the mapping application. Section III then describes a novel UI for presenting different types of detail information about the orientation. Next, Section IV describes several different ways for the user to get directions from the mapping application. Section V then describes the different modes of operation of the integrated mapping application of some embodiments. Section VI describes an example electronic system to which some embodiments of the present invention are implemented. Finally, Section VII describes a map service operating environment.

I. Map browsing

A. General control items

1 illustrates an example of a device 100 for performing an integrated mapping application of some embodiments of the present invention. The application has a novel user interface (UI) design that smoothly and consistently integrates different models for applications by using a minimal set of screen controls that float above the content to display as much content as possible. The control of each of the states. In addition, this cluster is adapted to the current task of animating the content of the cluster as it moves between different modalities (eg, between browsing, searching, routing, and navigation). This common element of adaptive nature enables the mapping application to be optimized for different tasks while maintaining a consistent look and interaction model as it moves between tasks.

Figure 1 shows three phases 105, 110, and 115 of interaction with a mapping application. The first stage 105 shows the UI 120 of the device, which includes several icons of several applications on the docking area 125 and on the page of the UI. One of the illustrations on this page is an illustration of the mapping application 130. The first stage shows that the user selects the mapping application by touching the screen with the orientation of the application on the screen of the device.

The second stage 110 shows the device after the mapping application has been launched. As shown in this stage, the UI of the mapping application has a start page, in some embodiments, the start page (1) displays a map of the current orientation of the device, and (2) is configured in the top column 140 and acts as a float. Several UI controls for the control. As shown in FIG. 1, the floating control items include a position control item 145, a 3D control item 150, and a page curl control item 155, and the top column 140 includes a guidance control item 160, a search field 165, and a bookmark control item 170.

The guidance control 160 opens a page via which the user can request to identify a route between a starting orientation and an ending orientation. As further described below, this control item is one of three mechanisms through which the mapping application can be directed to identify and display a route between two orientations, the other two being (1) for the map The selected item in the display shows one of the control items in the information banner, and (2) is displayed by the device identification Search for a recent route in field 165. Therefore, the information banner control and the search field 165 are two UI tools that the application uses to make the transition between different modalities smooth.

In some embodiments, a user can initiate a search by tapping in the search field 165. The touch guides the application to present an animation that (1) presents a screen keypad and (2) opens a search table filled with valuable completions. This table has some important subtleties. When the search field is touched and before the word is edited, or when the search field is empty, the table contains a list of "recently used", in some embodiments, "recently used" is requested by the user. Recent search and route guidance. This makes it very easy to quickly bring out the results of recent accesses.

After any edits in the search field, the table is populated by a search completion from both the local source (eg, bookmarks, contacts, recent searches, recent route directions, etc.) and the remote server. However, some embodiments include only recent route guidance when the user has not typed any text into the search field. Once the text is typed, the mapping application removes the recent route guidance from the search completion table. Incorporating the user's contact card into the search interface adds additional flexibility to the design. When the display is recently used, in some embodiments, the route from the current orientation to the user's home is always provided, while in other embodiments, the route is provided in the context of the content deemed "appropriate". Also, when the search term matches at least a portion of an address tag (eg, "ork" of "work"), in some embodiments, the application presents the tagged user as one of the search tables. address. Together, these behaviors make searching the UI a powerful way to get results on a map from multiple sources. In addition to allowing the user to initiate a search, in some embodiments, the presence of a text field in the primary map view also allows the user to see the query corresponding to the search results on the map and remove the search by clearing the query. result.

A bookmark control 170 (eg, a button) allows an application to bookmark orientations and routes. The position control item 145 allows the current position of the device to be specifically marked on the map. In some embodiments, once the location control is selected, the application is when the device moves The current location of the piece remains at the center of the map. In some embodiments, the control can also identify the direction in which the device is currently pointing. The mapping application of some embodiments uses the coordinates (e.g., longitude, altitude, and latitude coordinates) of the GPS signals received by the device at the location of the device to identify the orientation of the device. Alternatively or in combination, the mapping application uses other methods (eg, cell tower triangulation) to calculate the current orientation.

The 3D control item 150 is a control item for viewing a map in three dimensions (3D) or checking a route. The mapping application provides 3D controls as a fast mechanism for entering and exiting 3D. This control also serves as an indicator that (1) the current view is a 3D view, and (2) a 3D perspective can be used for a given map view (eg, a reduced map view may not have a 3D view available) ). In some embodiments, the 3D control item 150 provides at least three different appearances corresponding to some of these indications. For example, the 3D control item turns gray when the 3D view of the map is unavailable, becomes black when the 3D view is available but the map is in the 2D view, and turns blue when the map is in the 3D view. In some embodiments, the 3D control item has a fourth appearance (eg, a button that displays a building image or shape) when the immersive 3D map rendering is available at a given zoom level. The immersive and non-immersive 3D renderings are further described in U.S. Patent Application Serial No. 13/632,035, filed on Sep. in.

The page curl control item 155 is a control item that allows the application to minimize the number of screen control items by placing a specific infrequently used action in the primary UI screen, via the "page" displayed on the map. Curl control to access the secondary UI screen. In some embodiments, the page curl is permanently displayed on at least some of the views provided by the application. For example, in some embodiments, the application permanently displays the page curl on the start page (described in the second stage 110), and the application provides a start page to allow a user to browse or search for a position or identify a route.

Page curl indicates another set of controls that are conceptually "behind" the current view The orientation. When the page curl control item 155 is selected, the application renders a "peel" current view to display an animation of another view of another set of display controls. The third stage 115 illustrates one example of this animation. As shown in this stage, the stripping of the start page reveals a number of controls, in this example, the drop pin, print, show traffic, list, standard (standard), satellite (satellite), hybrid (hybrid) control items. In some embodiments, the operations performed by such controls are the same as those performed by similar controls in currently available smartphones, such as the iPhone operating iOS®.

The use of page curl allows the application to display more maps while providing access to other functionally unobtrusive methods provided by another set of controls. Additionally, in some embodiments, the application does not use page curling in map views where additional functionality is considered inappropriate for current tasks. For example, in some embodiments, the application does not display this page curl when rendering the map view during navigation.

Again, in some embodiments, the third stage 115 illustrates the user dragging a corner or an edge of the page to peel the page. However, in other embodiments, the animation of the stripped page is displayed by merely touching the page curl control item 155 without dragging the corners or edges.

B. Adaptive button cluster

As noted above, in some embodiments, the mapping application adaptively adds control items to the set of floating control items and removes control items to enable this cluster while maintaining a consistent appearance and interaction model between different tasks. Adapt to their tasks. 2 illustrates an example of an application adaptively modifying a floating control item cluster to add and remove list view control items 235. This example is provided in the context of the use of the indicator indicator 160 to obtain a route between two orientations.

This example is also provided in accordance with six stages 205 to 530 of interaction with the mapping application. The first stage 205 illustrates the selection of the direction indicator 160. The second stage 210 next illustrates that the user has typed the route in the start field 245 and the end field 250. The route generation control item 240 is selected after the start and end directions. The second stage 210 also shows that the mapping application displays a number of newly used route generation requests below the fields for typing the start and end orientations.

The third stage 215 shows two routes 260 and 261 that the mapping application has identified for the provided start and end orientations. In some embodiments, the mapping application promptly prompts one of the routes to map the recommended route recommended by the application to the route indicating the eye-catching prompt. This phase also illustrates the beginning of the animation that shows the list view control item 235 slipping out of the 3D icon 150. Some embodiments of the mapping application display when there is a chance to display a list of items (the list is a list of instructions in a route, or a list of search results when multiple results are found for a given query) A list control is used as one of the floating controls. In some embodiments, touching the list control item brings up a modal list view. Having a modal list view keeps the mapping application simple and keeps the map in front and centered. In some embodiments, the manifest view itself is adapted and optimized for the type of manifest displayed, as the search results will be displayed along with star ratings (when available) and the routing steps will include instruction arrows.

The fourth stage 220 displays the selection of the clear control item 255 to clear the identified routes 260 and 261 from the illustrated map. In response to this selection, routes 260 and 261 are removed from the map, and an animation start display list control item 235 is slid back to the 3D control item 150 as illustrated in the fifth stage 225. The sixth stage 230 shows the application UI after the animation has ended and the list control has been removed from the set of floating control items.

Another floating control used by the mapping application of some embodiments is a compass. Figure 3 illustrates an example of an application adaptively modifying a floating control item cluster to add and remove a compass 300. This example is provided using location control item 145 to view the context of the current location and orientation of the device on the map presented by the device. In some embodiments, the position control item 145 can cause the mapping application to operate in three different states. For example, when the position control item 145 is not selected, the mapping application displays a place Diagram view. Upon receiving the first selection of the position control item 145, the mapping application shifts the map to display a region of the map that includes the current orientation of the device at the center of the region. Since then, some embodiments of the mapping application track the current orientation of the device as it moves.

In some embodiments, the mapping application maintains the current orientation indicator at the center of the display area and shifts the map from one zone to another as the device moves from one zone to another. When the mapping application is receiving the second selection of the position control item 145 while maintaining the current orientation of the device at the center of the displayed area, the mapping application displays the origin of the map in the direction the device is currently facing. Identify one of the current positions to simulate light projection. When the mapping application is displaying a simulated light projection while the position control item 145 is selected again, the mapping application returns to the state prior to receiving the first selection. That is, the projection will disappear and the current position of the device will not be tracked.

The examples illustrated in this figure are provided in accordance with five stages 305 to 325 of interaction with the mapping application. The first stage 305 illustrates that the mapping application is displaying a map area that happens to not include the current orientation of the device (ie, the current orientation indicator is not displayed in the map area).

The second stage 310 illustrates that the position control item 145 is selected once. As described above, the first selection of the position control item 145 will cause the map to be shifted to display a map area having one of the current orientation indicators 326 at the center. The third stage 315 shows the result of selecting the position control item 145. Some embodiments identify the current location of the device by using the current orientation indicator 326. The current orientation indicator 326 has a different appearance in different embodiments. For example, the current orientation indicator 326 of some embodiments has the appearance of colored dots (eg, a blue dot) on the map. The identification of the current location is useful when the user has explored (eg, via a gesture action) that the displayed map is such that the device does not currently display the user's current orientation on the map.

The fourth stage 320 illustrates that the position control item 145 is selected again. In some embodiments The second selection of the position control item 145 will cause the application to display the simulated light projection 345 from the identified current position 326 in the map in the direction that the device is currently facing. This projection helps the user identify the direction the device is facing at any time. In some embodiments, this projection is always directed toward the top of the device (i.e., the orientation along which the search field 165 is positioned when the device is held in the longitudinal direction).

This projection 345 is illustrated in the fifth stage 310. This phase also shows that in this mode, the mapping application presents a floating compass 300. This compass serves as an indicator that the user can use to identify one of the directions to the north pole. In some embodiments, the compass is in the shape of two isosceles triangles adjoining the bottom, one of the triangles pointing north (in a direction away from the adjacent bottom) and having a color that distinguishes it from another triangle (for example, orange). As further described below, the compass can also be used to resume northward orientation after the user has rotated the 2D or 3D view of the map. In some embodiments, the compass may remain in the map view after the mapping application receives another selection of the position control item 145. In some embodiments, the compass does not disappear until the mapping application receives a user input to remove the compass (eg, select a compass).

The fifth stage 325 also shows that the map has been rotated to maintain the projection direction toward the top of the device. This is because the device has faced a different direction than the direction toward the top of the device in the previous stage 320. As the direction of the device moves, the direction of the compass 300 will also move relative to the top of the device. The compass has moved to indicate that the device is facing the northwest.

In some embodiments, the mapping application changes the appearance of the position control item 145 once after the first selection and changes the appearance of the position control item 145 again after the second selection. The fifth stage 325 shows the appearance of the position control item 145 after the second selection, which is different from the appearance of the position control item 145 after the first selection.

C. 2D or 3D

1. 3D button

In some embodiments, the mapping application can be in 2D mode or 3D mode. Shows one of the directions in the map. This allows the user to view one of the orientations in the map in either 2D mode or 3D mode. As described above, one of the floating control items is a 3D control item 150 that allows a user to view the map in three dimensions (3D) or to inspect a route. This control also serves as an indicator that (1) the current view is a 3D view, and (2) a 3D perspective can be used for a given map view (eg, a reduced map view may not have a 3D view available) ).

4 illustrates a manner in which the mapping application of some embodiments provides 3D control 150 as a fast mechanism for entering 3D mode for three-dimensional viewing of map orientation. This figure illustrates this operation in four stages 405 through 420. The first stage 405 illustrates the selection of the 3D control item 150 by the user when viewing the two-dimensional presentation of the area near the current orientation 425 of the user. For simplicity of description, the top column, floating control, and page curl are not depicted in this figure.

The second stage 410 shows a three-dimensional representation of the user's current orientation on the map. As noted above, in some embodiments, the mapping application generates a 3D view of the map by presenting the map view from a particular location in the three dimensional scene that can be conceptually considered to capture the location of the virtual camera of the map view. This manifestation will be further described below by referring to FIG. 5.

The third stage 415 shows the user browsing around the current orientation by performing a toggle operation (eg, by dragging a finger across the touch sensitive screen of the device). This toggle operation changes the 3D map view presented on the device to display a new orientation on the 3D map. This new orientation is illustrated in the fourth stage 420.

In some embodiments, when the local drawing application is operating in the navigation mode (ie, when the local drawing application is presenting the turn to the prompt navigation view), the mapping application presents a 3D view of the map. In order to provide a visual difference between the 3D view of the map during navigation and the 3D view of the map during map browsing, the mapping application of some embodiments uses different style sheets that define the rendered graphics in different ways. For example, some embodiments of the mapping application use a gray defined for the building, a white for the road, and a circle for the neighborhood in the 3D view of the map during the map browsing. Corner style sheet. The mapping application of an embodiment uses a style sheet defined for the white of the building, the gray for the road, and the sharp corners for the street in the 3D view of the map during navigation. In some embodiments, the mapping application applies the style sheets to the same map basemap for a given area of the map. In other embodiments, the mapping application applies the style sheets to different map basemaps (eg, map basemaps, navigation basemaps, etc.) for the given zone. The use of a style sheet to visualize the map is further described in the above-incorporated U.S. Patent Application Serial No. 13/632,035.

2. Virtual camera

FIG. 5 presents a simplified example to illustrate the concept of virtual camera 505. When a 3D map is rendered, the virtual camera is conceptualized by the location in the 3D map scene (the device visualizes the scene from that location to produce a 3D view of the map). Figure 5 illustrates one of the orientations of a 3D map scene 535 comprising four objects, two objects and two intersecting roads. To illustrate the virtual camera concept, this figure illustrates three scenarios, each of which corresponds to a different virtual camera orientation (i.e., a different presentation position) and a different view displayed on the device.

The first stage 510 shows a virtual camera pointing down at a first angle (eg, -30°) at a first perspective position to a 3D scene. In this position, the camera is pointed at an orientation that can be the rest position of the device or the orientation being explored, or a moving position in front of the moving orientation of the device (in the case of a map for navigation). In some embodiments, the preset position of the camera will be in a particular orientation relative to the current orientation, but this orientation can be modified as the user rotates the map. Presenting the 3D scene from the first perspective results in a 3D map view 525.

The second stage 515 shows a virtual camera pointing down at a larger second angle (eg, -45[deg.]) at a different second perspective position. Presenting the 3D scene from this perspective results in a 3D map view 530 in which the buildings and roads are smaller than their illustrations in the first map view 525.

The third stage 520 shows the virtual camera from the top down view, which faces down to 2D The map 545 corresponds to an orientation of the orientation in the 3D map scene 535 used to visualize the 3D views 525 and 530. The scene that emerges from this perspective is a 2D map view 540. Unlike the 3D rendering operations of the first and second stages, which in some embodiments are transmissive 3D rendering operations, the rendering operation in the third stage is relatively simple, as the operation only requires cropping the application or the zoom level specified by the user. One of the identified 2D maps. Thus, the virtual camera representation in this case slightly unduly complicates the description of the operation of the application, since cutting a portion of the 2D map is not a perspective rendering operation.

As in the third stage 520, in some embodiments, when the camera switches from the 3D perspective to the 2D top-down view, the mapping application switches from the 3D scene to the cropped 2D scene from a particular perspective. This is because, in these embodiments, the application is designed to simplify the rendering operation using one of the easier and non-essential perspective artifacts. However, in other embodiments, the mapping application uses a perspective rendering operation to visualize a 3D scene from a top-down virtual camera position. In such embodiments, the resulting 2D map view is slightly different from the map view 540 illustrated in the third stage 520 because any object that is far from the center of the view is distorted, with the object being at a distance from the center of the view. The farther away, the greater the distortion.

In various embodiments, the virtual camera 505 moves along different trajectories or arcs. Two such tracks 550 and 555 are illustrated in FIG. Of these two trajectories, the camera moves in an arc and rotates more downward as the camera moves up on the arc. Track 555 differs from track 550 in that, in track 555, the camera moves backward from the current orientation as it ascends along the arc.

When moving along one of the arcs, the camera rotates to maintain the desired orientation on the map at the focus of the camera. In some cases, one of the desired orientation devices is in a stationary orientation or the user is viewing a stationary orientation on the map. In other cases, the desired orientation is a moving orientation in front of the moving orientation of the device as the user moves with the device.

In addition to using the navigation app to control the camera (for example, from 3D to when bypassing the corner) In addition to 2D) (or not using a navigation application to control the camera), some embodiments also allow the user to adjust the position of the camera. Some embodiments allow the user to make commanded gestures with two fingers to adjust the distance (height) and angle of the camera. Some embodiments even allow for controlling the camera with a variety of types of gestures.

Figure 6 conceptually illustrates perspective adjustment features provided by the mapping application of some embodiments. In particular, Figure 6 illustrates virtual camera 600 in three different stages 605 through 615 that demonstrate the position of virtual camera 600 in response to perspective adjustment. As shown, Figure 6 illustrates one of the orientations of a 3D map 635 comprising four objects, two objects and two intersecting roads.

The first stage 605 shows the virtual camera 600 pointing down at the 3D map 635 at a first perspective position (eg, 45 degrees) relative to the horizon. In this position, camera 600 is pointed at an orientation that can be the rest position of the device or the orientation being explored, or a moving position in front of the moving orientation of the device (when the map is used for navigation). In some embodiments, the preset position of camera 600 will be in a particular orientation relative to the current orientation, but this orientation can be modified as the user rotates the map. Presenting the 3D map view based on the location of the virtual camera 600 results in a 3D map view 625.

The second stage 610 shows a virtual camera 600 pointing at a 3D map 635 at a lower perspective angle with respect to a smaller second angle (eg, 30 degrees) relative to the horizon at a different second perspective location. Stage 610 also shows that the user has provided a perspective angle for adjusting the view of the 3D map 635 by touching the screen with two fingers and dragging the two fingers in an upward direction (eg, a toggle action). Input. The scene rise is accomplished by the virtual camera 600 reducing and reducing the angle of view relative to the horizon. Using a virtual camera 600 positioned at this angle to visualize a 3D map view results in a 3D map view 630 in which the buildings and roads are higher than their graphical representations in the first map view 625. As shown by the dashed pattern of virtual camera 600, virtual camera 600 moves further down the arc 650 while tilting more upward (eg, pitching).

The third stage 615 exhibits a point at a higher third angle (eg, 80°) at a different third perspective position relative to one of the horizons at a higher perspective angle (eg, virtual camera 600) Focus) virtual camera 600. Stage 615 also shows that the user has provided an input for adjusting the perspective angle of the view of the 3D map 635 by touching the screen with two fingers and dragging the two fingers in a downward direction (eg, a toggle action). . Scene reduction or flattening is accomplished by the virtual camera 600 raising and increasing its angle relative to the horizon. As shown at stage 615, in some embodiments, when the virtual camera 600 is positioned in a top-down or near-top-down position such that the 3D map view rendered using the virtual camera 600 appears as 2D, the mapping application The program flattens the building in the 3D map 635 (i.e., reduces the z-axis component of the polygon to the ground level). Using the virtual camera 600 positioned at this angle in the third stage 615 to visualize a 3D map view results in a 3D map view 640, where the building appears smaller and flatter than the illustration in the second map view 630 And the road looks smaller. As shown by the dashed pattern of virtual camera 600, virtual camera 600 moves further up the arc 650 while tilting more downward (eg, pitching).

In some embodiments, when the local drawing application receives an input for adjusting the perspective angle for viewing the 3D map 635, the virtual camera 600 can be moved in this manner. In some of these embodiments, when the zoom level reaches a particular zoom level, the mapping application switches to generate a top-down mode of the 2D map view (where the appearing position is straight down).

As moving along an arc, the virtual camera rotates to maintain the desired orientation on the map at the focus of the camera. In some cases, one of the desired orientation devices is in a stationary orientation or the user is viewing a stationary orientation on the map. In other cases, the desired orientation is a moving orientation in front of the moving orientation of the device as the user moves with the device.

3. The gesture to enter or exit 3D

In addition to 3D controls, some embodiments of the mapping application allow one The user transitions a map view from a two-dimensional (2D) presentation to a 3D presentation via a gesture input to the multi-touch interface of the device. For example, the two user input functions enable the user to "push down" a 2D map view into a 3D map view or "pull up" a 3D map view into a 2D map view. This can also be seen as pulling a virtual camera from a 2D (from the top) view to a 3D (side angle) view via two indicative actions.

Different embodiments use different two-indicative action operations to push the 2D map view down into a 3D map view, or pull the 3D map view up into a 2D map view. Figure 7 illustrates an example of two indicative actions for downsampling a 2D map into a 3D map. This diagram presents this example in four phases of the operation of the UI of the mapping application. The first stage 705 shows the 2D map view that the application UI presents around the current orientation 725 of the device.

The second stage 710 then displays the beginning of the two indicative action operations with the 2D view 740 pushed down until the 3D view is rendered. In some embodiments, the application identifies a pushdown to the 2D map when it detects that the two contact systems are placed horizontally or approximately horizontally on the 2D map and move up together. Some embodiments require that the movement exceed a certain amount in order to impose an inertia that counteracts the push of the 2D map to the 3D map, and thereby prevent this transition from occurring unexpectedly.

Other embodiments use other schemes for transitioning from a 2D map to a 3D map via a schematic action input. For example, when a user places two fingers vertically with respect to each other and exerts a large force on the upper finger to trigger one of the sensors (eg, gyroscopes, etc.) of the device or trigger the rotation of the finger. At some point, the application of some embodiments performs this transition. Still other embodiments require performing an inverse operation to transition from a 2D map view to a 3D map view. For example, some embodiments require two horizontally aligned fingers to move down on a 2D map in unison to push the 2D view down into a 3D view.

The third stage 715 shows the fingers after the user's two fingers have moved up a certain amount on the screen of the device. This stage also shows that the 2D map 740 has been 3D map Replace with 745. The fourth stage 720 shows a 3D map 745 at the end of the two indicative movements. In this phase, the 3D control item 150 appears in a bold prompt to indicate that the current map view is a 3D map view.

In some embodiments, the 3D map view can be pulled up into a 2D map view by performing an opposite two-finger operation. In particular, in these embodiments, the mapping application is detected when the local mapping application detects that the 3D map is uniformly moving downwards by more than a threshold amount of two horizontal or near horizontal contacts. Transition between 3D maps and 2D maps.

D. Animation when entering and exiting 3D

While transitioning from a 2D map view to a 3D map view, some embodiments provide an animation showing that objects that appear flat in a 2D map view are raised and become larger in a 3D map view. This animation, which is shown in the U.S. Patent Application Serial No. 13/632,027, entitled "Displaying 3D Objects in a 3D Map Presentation", filed on September 30, 2012, is incorporated herein by reference. description. U.S. Patent Application Serial No. 13/632,027, incorporated herein by reference. Figure 8 illustrates this animation in three stages. The first stage 805 shows the user selecting the 3D control item 150 when viewing the 2D map view. The second stage 810 and the third stage 815 show subsequent views (although not necessarily continuous views) provided by the mapping application after the mapping application begins to provide the 3D map view. As the zoom level increases between the second and third phases, the height of the building in the map view is increased to provide an animation that is moving from the 2D view to the 3D scene.

When transitioning from a 3D view to a 2D view, the mapping application of some embodiments provides an inverse animation that shows the objects in the scene shrink until the objects collapse into flat objects in the 2D map.

In some embodiments, the mapping application provides a 2D to 3D or 3D to 2D transition when the local mapping application is operating in navigation mode or route inspection mode. These two modes of operation of the mapping application are further described below.

Figure 9 illustrates, in six different stages 905 through 930, the mapping application of some embodiments changes the appearance of the 3D control to indicate different 2D and 3D states of the map view. The first stage 905 illustrates that the mapping application is displaying a map and floating controls including the 3D control 150. The mapping application is displaying the map in 2D at a specific low zoom level as shown (the map has not been enlarged a lot). The 3D control 150 is displayed using a first appearance (eg, the grey letter "3D") to indicate that the 3D map material is not available at this particular zoom level. The first stage 905 also shows that the mapping application is receiving user gesture input to zoom in on the map (i.e., to increase the zoom level).

The second stage 910 shows that the mapping application is displaying the map at a zoom level that is higher than the zoom level used to display the map in the previous stage 905. However, the 3D control item 150 is maintaining the first appearance because the 3D map material is not available even at this particular higher zoom level. The second stage 910 also shows another schematic action input that the mapping application is receiving to further zoom in on the map.

The third stage 915 shows that the mapping application is displaying the map at a zoom level that is higher than the zoom level used to display the map in the previous stage 910. The mapping application has changed the appearance of the 3D control 150 to a second appearance (eg, "3D" of black letters) to indicate that the 3D map material is available at this zoom level. When the mapping application receives the selection of the 3D control 150, the mapping application of some embodiments will change the appearance of the 3D control 150 to a third appearance (eg, the "3D" of the blue letter) and Display the map in 3D (for example, by turning the straight down view from 2D into a perspective view). This third appearance can thus indicate that the map is displayed in 3D. The third stage 915 shows that the mapping application is receiving another illustrative action input to further zoom the map to a higher zoom level. The third stage 915 shows that the mapping application of some embodiments is displaying the buildings in the map as gray squares.

The fourth stage 920 shows that the mapping application is being compared to its previous stage 915 The zoom level used by the map is displayed in a zoom level to display the map. The mapping application has changed the appearance of the 3D control 150 to a fourth appearance (eg, a building icon of the first color as shown) to indicate 3D immersive map data for visualizing the immersive 3D map view. Available at this zoom level. The fourth stage 920 also shows that the mapping application is receiving the selection of the 3D control item 150.

The fifth stage 925 and the sixth stage 930 show subsequent views (although not necessarily continuous views) provided by the mapping application after the mapping application begins to provide the 3D immersive map view. In some embodiments, the zoom level is unchanged between the fifth and sixth stages, but the height of the building in the map view is increased to provide an animation that is moving from the 2D view to the 3D immersive view . Again, from stages 920 to 925, the mapping application has changed the appearance of the 3D control to a fifth appearance (eg, a building icon of the second color as shown) to indicate that the map is in a 3D immersive view. display.

E. Browse

Toggle

In some embodiments, the mapping application allows the user to explore around one of the directions displayed in the map via a variety of mechanisms. For example, as described above, some embodiments of the mapping application allow a user to surround an orientation by performing one or more toggle operations on the touch sensitive screen of the device (eg, by dragging a finger) Browse. These actions move the view rendered by the application to a new orientation on the map. An example of a toggle operation in a 3D map view is described above with reference to FIG.

2. Rotate

In some embodiments, the mapping application also allows a user to rotate a 2D or 3D map via a gesture input. In some embodiments, the mapping application is a vector mapping application that allows direct manipulation of the map (such as rotation and 2D/3D manipulation) while browsing the map. However, some of the effects on the map can be fascinating Disorienting. In the absence of an easy way to return to the north-up orientation (ie, the orientation of the north direction aligned with the top of the device), some users may have difficulty interacting with the map view. To address this issue, some embodiments of the mapping application provide floating compass controls on the map. As mentioned, this compass acts both as an indicator pointing north and as a button to restore north orientation. To further minimize clutter on the map, the mapping application only displays this button when the map is rotated.

Figure 10 illustrates an example of rotating a 2D map and using a compass to straighten a rotated map in some embodiments of the invention. This figure illustrates this example in four phases. The first stage 1005 illustrates a 2D map view 1025. The second stage 1010 illustrates the rotation of this map view via two indicative actions. In this example, the user performs the gesture by placing two fingers on the map view and pulling down a finger while pushing up a finger. This rotational movement of the finger causes the application to rotate the map into a rotated map view 1030. In some embodiments, the mapping application calculates a midpoint between the two fingers and uses the midpoint as an anchor for rotation. In some such embodiments, if one of the two fingers does not move, the mapping application uses the location where the finger is not moved as an anchor point. In some embodiments, when the position control item 326 is present in the view (eg, by selecting the position control item 145), the mapping application uses the orientation of the position control item as the anchor of the rotation regardless of the orientation of the finger.

The second stage 1010 also shows that in response to the rotation of the map, the application has presented a compass 300 on the map to indicate the north direction on the rotated map. The third stage 1015 then shows the user selecting the compass 300. The fourth stage 1020 then shows that after selecting the compass, the application rotates the map back to the map view 1025 (ie, oriented northward).

Figure 11 illustrates another example of a rotating map in some embodiments of the invention. This figure illustrates this example in four stages 1105 through 1120. In this example, the map is a 3D map. Thus, the first stage 1105 illustrates the 3D map view 1105. The second stage 1110 illustrates This map view is rotated by two indicative actions. As previously mentioned, in this example, the user performs the gesture by placing two fingers on the map view and pulling down a finger while pushing up a finger. This rotational movement of the finger causes the application to rotate the map into a rotated map view 1130. In this example, the rotation system surrounds the current position of the device because, as described above, the current orientation indicator 326 is present in the map view 1125.

The second stage 1110 also shows that in response to the rotation of the map, the application has presented a compass 300 on the map to indicate the north direction on the rotated map. The third stage 1115 then displays a further rotation of the map in response to the other two indicative actions of the user. The compass 300 still indicates the north direction but has rotated with the rotated map. The fourth stage 1120 then shows the map and the further rotation of the compass 300.

In some embodiments, the mapping application does not allow the user to rotate the 2D or 3D map at certain zoom levels. For example, when zooming out of the map (to a low zoom level), the mapping application does not rotate the map when it receives a gesture input from the user to rotate the map (eg, a two-finger rotation operation). In some embodiments, the module of the mapping application responsible for moving the virtual camera checks the current zoom level and decides to ignore the instructions if the map should not be rotated at the current zoom level.

In some other embodiments, the application rotates the map a certain distance when the user provides a gesture input for rotating the map, but rotates the map back to the preset orientation when the user releases or stops the gesture input ( For example, North).

In some embodiments, the mapping application provides an inertial effect for the rotation of the map. When a user provides a particular type of gesture input (eg, an input that terminates at an angular rate or a translation rate greater than the threshold rate) to rotate the map, the mapping application generates an inertial effect that causes the map to continue to rotate and decelerate to a stop. . In some embodiments, the inertial effect provides the user with a more realistic interaction with the map that mimics behavior in the real world.

Figure 12 illustrates the inertia effect for the rotary operation in three different stages 1205 to 1215. Should be rotated together. For the sake of simplicity, the inertial effect is shown in this figure in terms of a 2D map view. However, the mapping application of some embodiments provides an inertial effect when viewing a map in 3D mode. The first stage 1205 presents a 2D map view 1220 of the 2D map. In some embodiments, the mapping application executes a program 1300, which is described below with reference to FIG. 13, to perform a rotating operation.

As shown, the 2D map view 1220 includes a number of streets that extend in a parallel or vertical direction. The first stage 1205 also shows that the user is providing input to rotate the 2D map view 1220. Specifically, the user is performing by touching two fingers on two directions on the touch screen and rotating the two fingers in a clockwise direction (as indicated by the two arrows depicted in the figure). Used to rotate one of the 2D map views 1220 to illustrate the action. In this example, a striking reminder of the fingertip is illustrated for illustrative purposes. In some embodiments, the mapping application does not actually display a prominent prompt around the fingertips.

The second stage 1210 displays a 2D map immediately after the user has completed input to rotate the 2D map. For this example, the user completes the input by lifting the two fingers off the touch screen of the device, as indicated by the eye-catching prompts around the fingertips that are no longer displayed. Additionally, the second stage 1210 displays a 2D map view 1225 of the 2D map rendered by the mapping application. As shown, the mapping application has rotated the 2D map from the 2D map view 1220 to the 2D map view 1225 in a clockwise direction. The street shown in the first stage 1205 has been rotated approximately 45 degrees in a clockwise direction.

Different embodiments of the mapping application utilize different methods to implement the inertial effects of the rotating operation. For example, in some embodiments, the mapping application determines whether the user stops moving the finger or lifts the finger away from the touch screen based on an average of one of the fingers or the fingers. The angular (or translational) rate of the user's input as it approaches the instant. The mapping application of some embodiments treats each stop as the end of the input when the user repeatedly stops the finger without lifting the finger and begins to move the finger again, while in other embodiments, the mapping application The program treats the operation as One input until the user lifts his finger off the screen.

The mapping application uses the angular rate to determine the angular amount (eg, degree) for the inertial effect, and determines that the virtual camera used to view the 2D map decelerates the angular rate (eg, in constant, exponential, logarithm, etc.) The manner in which the determined angular amount is rotated. In some embodiments, the mapping application visualizes and displays an animation of the inertial effect (eg, a deceleration rotation of the 2D map from the 2D map view 1225 that rotates the 2D map by the determined angular amount).

In some embodiments, the mapping application itself does not analyze the user's gesture input. For example, the mapping application of these embodiments does not determine the angular rate of input by the user. Rather, the mapping application of these embodiments receives the angular rate determined by the operating system of the device executing the mapping application. The operating system of the device has an interface for receiving a gesture input from the user. The operating system analyzes the received input and provides the analysis to the mapping application. The mapping application will determine the inertia effect to apply based on the analysis of the input.

The third stage 1215 illustrates a 2D map after the mapping application has visualized and displayed an animation of inertial effects. As shown, a 2D map view 1230 of the 3D map rendered by the mapping application is displayed. After the user completes the input in the second stage 1210, in the third stage 1215, the mapping application has rotated the 2D map clockwise more. As shown, the 2D map view 1230 in the third stage 1215 shows a street that rotates clockwise more than the street shown in the 3D map view 1225.

In some embodiments, the mapping application also provides operations for operations other than rotating the map (such as moving a pan map or entering or exiting a 3D operation (eg, mobile browsing, rotation, 2D entry into 3D)) Inertia effect. The inertial effect for these other operations is further described in the above-incorporated U.S. Patent Application Serial No. 13/632,035. FIG. 13 conceptually illustrates a procedure 1300 for some embodiments for rotating a map view based on a gesture input. In some embodiments, the local drawing application is in a map view mode (eg, For example, in the azimuth browsing mode, the navigation mode, the 2D viewing mode, the 3D viewing mode, etc., and the mapping application receives a gesture through the touch screen of the device executed by the mapping application, the mapping application execution program 1300 .

The program 1300 begins by receiving (at 1310) one of the gestures for rotating the map view. In some embodiments, one of the gestures for rotating the map view includes a multi-touch gesture that is received via the touch screen (eg, touching the touch screen with multiple fingers simultaneously). In this example, the program 1300 receives a two-point touch rotation gesture.

Next, the routine 1300 identifies (at 1320) the rotational component of the received gesture. The routine 1300 of some embodiments identifies the rotational component of the gesture by recognizing the amount of rotation of the touch point of the gesture. For example, in some such embodiments, the program 1300 identifies the amount of rotation of the touch point of the gesture by: (1) determining the initial orientation from one touch point to the initial of the other touch point a first vector of orientations; (2) a second vector determining a second orientation from the one touch point to a second orientation of the other touch point; and (3) based on an initial orientation of the touch points and The second orientation of the touch points determines the direction of rotation.

The routine 1300 then determines (at 1330) whether the amount of rotation is within a margin. When the routine 1300 determines that the amount of rotation is not within the threshold amount, the routine 1300 ends. Otherwise, routine 1300 determines (at 1340) an axis of rotation based on the gesture. In some embodiments, the routine 1300 determines the axis of rotation by: (1) identifying one of the vectors along one of the initial orientations from one touch point to the other of the initial touch points; and (2) A point on the map view corresponding to the point along the vector (eg, a point on the map that coincides with the point along the vector) is determined. The program 1300 uses the determined point on the map view as the orientation of the axis (eg, the z-axis) around which the map view is rotated.

Next, the routine 1300 adjusts (at 1350) the map view based on the axis of rotation and the amount of rotation. In some embodiments, the program 1300 adjusts the map view by rotating the map view around the determined axis of rotation in the determined direction of rotation. Do not The same embodiment uses different coordinate spaces for the map. For example, the map of some embodiments uses a Mercator unit coordinate space. In such embodiments, the program 1300 adjusts the position of the virtual camera relative to the map to adjust the map view. As another example, in some embodiments, the map uses the World Geodetic System (eg, WGS 84) as the coordinate space for the map. In some such embodiments, the program 1300 adjusts the map relative to the position of the virtual camera to adjust the map view.

Finally, the program 1300 visualizes (at 1360) the adjusted map view for display on the device. In some embodiments, the rendered map view is an image representing one of the adjusted map views. Next, the routine 1300 ends.

In some embodiments, the 3D map can be rotated at a zoom level of the defined range and/or set. For example, in some embodiments, the mapping application allows the 3D map to rotate at a defined number of highest zoom levels (eg, zoom levels 10 through 20) and prevent the 3D map from remaining at the lower zoom level (eg, Zoom level 1 to 10) rotates down. In some such embodiments, the mapping application receives no input to rotate the 3D map when the local drawing application receives an input to rotate the 3D map under one of the zoom levels defined to not allow the rotation. In other such embodiments, the mapping application generates instructions to rotate the 3D map when the input of the 3D map is rotated at a zoom level that is not allowed to rotate, but the mapping application generates instructions to rotate the 3D map, but The mapping application simply ignores these instructions. Those of ordinary skill in the art will recognize that in different embodiments, the zoom level that allows rotation operations on a 3D map may be defined in many different ways.

3. Legend and name rotation

The mapping application of some embodiments uses novel techniques to adjust the text and/or symbols appearing in the map view or to keep the text and/or symbols unadjusted as the local map view is rotated. Figure 14 illustrates an example of this novel method in accordance with four stages 1405 through 1420 of UI operations. In this example, the name Apple Inc. appears at a position that is 1 Infinite Loop, Cupertino California.

In the first stage 1405, the name Apple Inc. is upright in a particular map view. In the second phase 1410 and the third phase 1415, the map view is rotated in response to the two-finger rotation operation of the user. In these two phases, the name Apple Inc. is shown to be slightly rotated at an angle that is much smaller than the angle of rotation of the map. The name Apple Inc. behaves as if the name was pinned to the map at its center or at the top, but the name of the name points down. Therefore, each time the map rotates, the name rotates slightly, but the center of gravity of the name causes it to rotate less and eventually returns the name to its upright position. This upright position of the name Apple Inc. is shown in the fourth stage 1420. This stage shows the map view after the rotation operation has completed.

However, maintaining a constant upright position of all text and/or symbols in a rotated map may be a bit pleasing if the map has many text characters or symbols and many of the characters or symbols are counter-rotating to keep straight up. Distraction. Thus, for some of the characters and/or symbols, some embodiments of the mapping application use an alternate mechanism to adjust the orientation of the characters and/or symbols during rotation.

Figure 15 illustrates one such alternative example in accordance with four stages 1505 through 1520 of UI operations. In this example, the name of the street is the character that is rotated after the map view has been rotated by a margin.

In the first stage 1505, the street name is aligned with the upward and rightward direction of travel on the street. In the second phase 1510 and the third phase 1515, the map view is rotated in response to the two-finger rotation operation of the user. In these two phases, there is no street name rotation because the map has not rotated the necessary threshold. However, by the time the map is rotated to its orientation in the fourth stage 1520, the map has rotated sufficiently to pass a limit, which would require some of the street names (streets 1 to 4) to be rotated to maintain the names and Alignment of the upward direction of travel.

4. Zoom and bounce

Figure 16 illustrates the user transitioning from a 3D map view to a two-point action action An example of a 2D map view. This figure illustrates this transition in four stages 1605 through 1620. In the first three phases 1605 through 1615, the user performs a pinch-in operation that causes the application to zoom out the 3D view presented in the first phase in successive steps until the view becomes the 2D view illustrated in phase four 1620. .

Alternatively or in combination with the perspective adjustment features described above with reference to Figure 6, the mapping application of some embodiments allows the user to zoom in and out of the view of the 3D map (e.g., by providing with two fingers) Action input). Figure 17 illustrates zoom adjustment features provided by the mapping application of some embodiments. In particular, Figure 17 illustrates virtual cameras 1712 in three different stages 1701 through 1703 that demonstrate the movement of virtual camera 1712 in response to zoom adjustments. As shown, Figure 17 shows one of the orientations of the 3D map 1710, which contains two buildings and two roads forming a T-shaped junction.

The first stage 1701 presents a 3D map 1710 in which a virtual camera 1712 at a particular location points to a 3D map 1710. In this position, camera 1712 is pointed to an orientation that can be the rest position of the device or the orientation being explored, or a moving position in front of the moving orientation of the device (in the case of a map for navigation). Presenting the 3D map view based on the location of the virtual camera 1712 results in a 3D map view 1714.

The second stage 1702 shows a virtual camera 1712 pointing to the 3D map 1710 at a different zoom level position. Stage 1702 shows that a user has provided input for increasing the zoom level of the view of the 3D map 1710 by having two fingers touch the screen of the device close to each other and moving the fingertip while the finger touches the screen. Separate (for example, an expansion gesture).

The magnification adjustment is accomplished by the virtual camera 1712 moving along line 1750 near the 3D map 1710. In some embodiments, the mapping application uses a line 1750 along which the virtual camera 1712 is moved as a line formed by the front end of the virtual camera 1712 and the focus of the virtual camera 1712. The mapping application of some embodiments causes the virtual camera 1712 to be along one of the front end of the virtual camera 1712 and the 3D map 1710 based on the user's input. The orientation forms a line movement to magnify the view of the 3D map 1710.

Presenting a 3D map view using the virtual camera 1712 at this location results in a 3D map view 1724 where the buildings and roads appear closer than the locations shown in the 3D map view 1714. As indicated by the dashed pattern of virtual camera 1712, virtual camera 1712 moves along line 1750 near 3D map 1710.

The third stage 1703 shows a virtual camera 1712 pointing to the 3D map 1710 at a different zoom level position. In this stage 1703, the user has provided input to reduce the zoom level of the 3D map 1710 by causing the two fingers to touch the screen of the device far apart and to point the finger while touching the screen. The tips move closer together (for example, a pinch gesture).

The reduction adjustment is accomplished by moving virtual camera 1712 along line 1755 away from 3D map 1710. In some embodiments, the mapping application uses a line 1755 along which the virtual camera 1712 is moved as a line formed by the front end of the virtual camera 1712 and the focus of the virtual camera 1712. The mapping application of some embodiments moves the virtual camera 1712 along a line formed by one of the front end of the virtual camera 1712 and the 3D map 1710 based on the user's input to magnify the view of the 3D map 1710.

Presenting a 3D map view using the virtual camera 1712 at this location results in a 3D map view 1734 where the buildings and roads appear farther than the locations illustrated in the 3D map view 1724. As shown by the dashed pattern of virtual camera 1712, virtual camera 1712 moves away from 3D map 1710 along line 1755.

As described above, FIG. 17 illustrates a number of example zoom adjustment operations and corresponding movements of the virtual camera in the 3D map to visualize the 3D map view of the 3D map. Those of ordinary skill in the art will recognize that many different scaling adjustments are possible. In addition, the mapping application of some embodiments performs a zoom adjustment operation in response to additional and/or different types of input (eg, touch screen, two touch screens, etc.).

Figure 18 conceptually illustrates the use of a mapping application provided by some embodiments. The position of the virtual camera is maintained within a range defined by the arc. In particular, FIG. 18 illustrates virtual camera 1800 at three different stages 1805 through 1815 that exhibit the position of virtual camera 1800 maintained within a defined range of arcs 1850. As shown in FIG. 18, one of the orientations in the 3D map 1835 includes two buildings and two roads forming a T-shaped junction.

The first stage 1805 shows the virtual camera 1800 at a particular location along one of the arcs 1850. As shown, the arc 1850 represents a defined range (eg, an angular extent) within which the virtual camera 1800 can move. The first stage 1805 also exhibits three positions 1855 through 1865 along the arc 1850 (eg, a perspective perspective). In this example, the mapping application causes the virtual camera 1800 to be along the arc 1850 at a high perspective end of the arc 1850 in a manner similar to that described above with respect to FIG. 5 (eg, when the virtual camera 1800 is tilted downward) When it is at maximum, it moves between the position of the arc 1850 and the position 1855. Presenting a 3D map view based on the location of the virtual camera 1800 in the first stage 1805 results in a 3D map view 1825.

When the virtual camera 1800 passes the position 1855 while moving toward the low perspective end of the arc 1850, the mapping application reduces the speed at which the virtual camera 1800 moves toward the low perspective end of the arc 1850, regardless of the input provided by the user. (for example, deceleration). In some embodiments, the mapping application causes the speed of the virtual camera 1800 to decrease at a constant rate, while in some embodiments, the mapping application causes the speed of the virtual camera 1800 to decrease at an exponential rate. Additional and/or different methods for reducing the speed of virtual camera 1800 are used in some embodiments.

The second stage 1810 shows that the virtual camera 1800 has moved to a position along the arc 1850 at or near the low perspective end of the arc 1850. As shown, the user is providing input for adjusting the perspective angle of the view of the 3D map 1835 by touching the screen with two fingers and dragging the two fingers in an upward direction (eg, a toggle gesture). . In response to the input, the mapping application is tilting the virtual camera 1850 up The virtual camera 1800 is moved toward the low perspective end of the arc 1850. When the virtual camera reaches position 1865 along arc 1850, the mapping application prevents virtual camera 1800 from moving lower and beyond position 1865, even if the user continues to provide input for reducing the perspective of the view of 3D map 1835 ( For example, the user continues to drag two fingers up on the screen) as well.

In some embodiments, the mapping application causes the virtual camera 1800 when the user stops providing input to reduce the perspective angle of the view of the 3D map 1835 (eg, the user lifts two fingers off the touch screen) The position "bounces" or "fast moves" from position 1865 along arc 1850 to position 1860. When the mapping application is generating or visualizing a 3D map view of the 3D map 1835 based on the view of the virtual camera 1800 during a bounce or fast moving motion, the resulting 3D map view provides a 3D map view that briefly bounces down or moves quickly A bounce animation to indicate to the user that the perspective of the map view cannot be reduced more. Presenting a 3D map view using the virtual camera 1800 positioned at this angle results in a 3D map view 1830 in which the buildings and roads are higher than the map view 1825.

The third stage 1815 shows the mapping application responding to the virtual camera 1800 after the user has stopped providing input to have the virtual camera 1800 bounce or quickly moved to position 1860. Different embodiments use different techniques to implement bounce or fast movement of the virtual camera 1800. For example, the mapping application of some embodiments begins to cause virtual camera 1800 to rapidly accelerate in a defined distance along arc 1850, or until virtual camera 1800 reaches a defined speed. Next, the mapping application causes the virtual camera 1800 to decelerate along the arc 1850 at the remaining distance from the position 1860. Other ways to implement bounce or fast moving effects are used in some embodiments. Presenting a 3D map view using the virtual camera 1800 positioned at position 1860 along the arc 1850 in the third stage 1815 results in a 3D map view 1840, which is slightly more visible in the map view 1840 than the map view 1830. Small and flat, and the road looks a little smaller.

As noted above, Figure 18 illustrates one technique for preventing a virtual camera from moving beyond the low perspective end of the arc. Instead of preventing the virtual camera from moving beyond the low perspective end of the arc or in combination with preventing the virtual camera from moving beyond the low perspective end of the arc, some embodiments of the mapping application utilize a high perspective end for preventing the virtual camera from moving beyond the arc One of the similar technologies. In addition, FIG. 18 shows an example of the following position: slowing down the position of the virtual camera along one of the arcs; preventing the virtual camera from moving through one of the positions of the arc; and the virtual camera moving quickly or bouncing back To a position along one of the arcs. Different embodiments define these locations in many different ways. For example, in some embodiments, the position of the virtual camera along the arc is slowed to be the same or similar to the position of the arc along which the virtual camera quickly moves or bounces back.

5. Display module

Figure 19 conceptually illustrates a process or map rendering pipeline 1900 that is executed by a mapping application of some embodiments to visualize a map for display at a client device (e.g., on a display of a client device). In some embodiments, the map rendering pipeline 1900 can be collectively referred to as a map rendering module. A more detailed version of this process line is described in U.S. Patent Application Serial No. 13/632,035, which is incorporated herein by reference. As illustrated, processing pipeline 1900 includes a basemap skimmer 1905, a set of grid builders 1915, a set of grid creation processors 1910, a controller 1975, a basemap provider 1920, a virtual camera 1930, and a map rendering engine 1925. .

In some embodiments, the basemap skimmer 1905 performs various programs for capturing a map basemap in response to a request from the grid builder 1915 for a map basemap. As described below, the grid builder 1915 identifies an existing map basemap required to create a respective grid of map maps (either stored on a map drawing service server or on a device executing processing pipeline 1900). Cache memory). The basemap extractor 1905 receives a request for a map basemap to determine where to draw the map basemap (eg, from a map drawing service, one of the cache devices on the device, etc.), and Unzip the map basemap as needed.

These grid builders 1915 (also referred to as basemap sources) that personalize some embodiments are implemented by basemap provider 1920 to establish different layers of the view basemap. Depending on the type of map being displayed by the mapping application, the basemap provider 1920 can perform individualized different numbers and different types of grid builders 1915. For example, for a low-flying (or satellite) view map, the basemap provider 1920 may only perform a single grid builder 1915, as some embodiments of the low-altitude overhead map do not contain data. Multiple layers. In fact, in some embodiments, the low-altitude overhead map contains a built-in grid generated at the mapping service where a low-altitude overhead image (taken by satellite, airplane, helicopter, etc.) is used as the texture of the grid. However, in some embodiments, an individualized additional mesh builder can be implemented for generating tags to overlay the low-level overhead views when the application is in the hybrid mode. For vector maps of 2D or 3D representations (i.e., non-satellite image maps), some embodiments perform a personalized individual grid builder 1915 to create a grid for incorporation into the map for: land cover polygon data (eg, parks, water bodies, etc.), roads, landmarks, point labels (eg, park labels, etc.), road labels, traffic (if traffic is shown), buildings, dot matrix data (for specific items under a specific zoom level) ), and other layers of the data. The resulting low-altitude view map is described in detail in PCT Application No. PCT/EP2011/054155 entitled "3D Streets". PCT Application No. PCT/EP2011/054155 is incorporated herein by reference.

The mesh builder 1915 of some embodiments receives the "empty" view basemap from the basemap provider 1920 and passes the "established" view basemap back to the basemap provider 1920. That is, the basemap provider 1920 sends one or more view basemaps (not shown) to each of the grid builders 1915. Each of the view basemaps indicates one of the regions of the world for which a grid is drawn. Upon receiving this view basemap, the grid builder 1915 identifies the required map basemap from the map drawing service and sends its manifest to the basemap skimmer 1905.

Upon receiving the basemap from the basemap skimmer 1905, the grid builder uses the vector data stored in the basemap to create a polygon mesh of the area depicted by the view basemap. In some In an embodiment, the mesh builder 1915 uses several different mesh creation processors 1910 to build the mesh. Such functions may include a grid generator, a triangometer, a shadow generator, and/or a texture decoder. In some embodiments, such functions (and additional mesh building functions) are available to each of the mesh builders, with different mesh builders 1915 using different functions. Each mesh builder 1915 passes its mesh layer filled view basemap back to the basemap provider 1920 after building its mesh.

The basemap provider 1920 receives from the controller 1975 a particular view (i.e., volume or view frustum) representing the map view to be displayed (i.e., the volume visible from the virtual camera 1930). The basemap provider performs any culling (e.g., identifies surface areas that will be displayed in the underlay of the view), and then sends the view basemaps to the mesh builder 1915.

The basemap provider 1920 then receives the established view basemap from the mesh builder, and in some embodiments, the basemap provider performs picking (eg, shifting) on the established mesh using a particular view from the virtual camera 1930. Except for surface areas that are too far away, objects that are completely behind other objects, etc.). In some embodiments, basemap provider 1920 receives established view basemaps from different mesh builders at different times (eg, due to different processing times to complete higher complexity and lower meshes) , at different times, etc., before the necessary basemap extractor 1905 receives the necessary map basemap). Once all of the layers of the view basemap have been passed back, the basemap provider 1920 of some embodiments places the layers together and releases the data to the controller 1975 for visualization.

Virtual camera 1930 creates a volume or surface for pipeline 1900 to appear and sends this information to controller 1975. Based on the particular orientation and orientation from which the map will be rendered (i.e., the point in the 3D space from which the user "views" the map), the virtual camera recognizes a field of view for actual transmission to the basemap provider 1920. In some embodiments, when the local mapping application is rendering a 3D perspective for navigation, the virtual camera's field of view is determined according to an algorithm that generates a new virtual at regular intervals based on the movement of the user device. Camera orientation and orientation.

In some embodiments, controller 1975 is responsible for managing basemap provider 1920, virtual camera 1930, and map rendering engine 1925. In some embodiments, multiple basemap providers may be physically implemented, and the controller places together several view basemaps (eg, a map basemap and a building basemap) to produce a handoff to the map rendering engine. One of the scenes of 1925.

The map rendering engine 1925 is responsible for generating a map for output to a display device based on a mesh base map (not shown) transmitted from the virtual camera. The map rendering engine 1925 of some embodiments has several subroutines. In some embodiments, each different type of map element is visualized by a different subroutine, wherein the visualization engine 1925 handles the cloaking of different object layers (eg, placing the label above or behind different buildings, in land cover) Roads, etc. are generated above the objects). Examples of such visualization programs include road visualization programs, building visualization programs, and label display programs, vegetation display programs, dot matrix traffic display programs, dot matrix road display programs, satellite display programs, polygon display programs, and background dot matrix display programs. Wait.

The operation of the rendering pipeline 1900 in some embodiments will now be described. Based on user input to view a particular map area at a particular zoom level, virtual camera 1930 specifies an orientation and orientation from which to view the map area, and sends the view frustum or volume to controller 1975 . Controller 1975 performs the individualization of one or more basemap providers. Although a basemap provider 1920 is shown in this figure, some embodiments allow for the simultaneous execution of individualized multiple basemap providers. For example, some embodiments perform individualized basemaps for buildings and separate basemaps for map maps.

The basemap provider 1920 performs any sorting necessary to generate an empty view basemap that identifies the area of the map area that needs to be meshed, and sends the empty view basemap to the mesh builder 1915 for plotting the map Different layers (eg, roads, land covers, POI tags, etc.) perform individualization of the grid builders. The grid builder 1915 receives a list of information from the mapping service that identifies that it is available on the mapping service server. The same base map (that is, as a node of a quadtree). The grid builder 1915 requests a base map extractor 1905 that passes the requested map basemap back to the grid builder 1915.

Once a particular mesh builder 1915 has received its map basemap, the mesh builder begins to use the vector data stored in the map basemap to create a net for transmitting the basemap of the basemap provider 1920. grid. After creating a grid for its map layer, the grid builder 1915 sends the established view basemap back to the basemap provider 1920. The basemap provider 1920 waits until it has received all of the view basemaps from the various mesh builders 1915, then layeres the view basemaps together and sends the completed view basemap to the controller 1975. The controller stitches together the returned basemaps (eg, the map view basemap and the building view basemap) from all of its basemap providers and sends this scenario to the rendering engine 1925. The map rendering engine 1925 uses the information in the map basemap to draw the scene for display.

II. Position search

A. Search field behavior

1. Search field function and appearance

In some embodiments, the search field of the mapping application is another UI tool that the application uses to smooth transitions between different modalities. In some embodiments, a user can initiate a search by tapping in the search field. The touch guide application presents an animation that (1) presents a screen keypad and (2) opens a search table filled with valuable completions. This table has some important subtleties. When the search field is touched and before the word is edited, or when the search field is empty, the table contains a list of "recently used", in some embodiments, "recently used" is requested by the user. Recent search and route guidance. This makes it very easy to quickly bring out the results of recent accesses.

After making any edits in the search field, by the source from the local end (for example, the book The signing, contact, recent search, recent route guidance, etc.) and the remote server suggest that the search for both is completed to populate the form. Incorporating the user's contact card into the search interface adds additional flexibility to the design. When the display is recently used, in some embodiments, one of the routes from the current orientation to the user's home is always provided, while in other embodiments, the route is provided in the context of the content deemed "appropriate". Also, when the search term matches at least a portion of an address tag (e.g., "Wo" of "Work"), in some embodiments, the application presents the tagged address of the user who completed as one of the search tables. Together, these behaviors make searching the UI a powerful way to get results on a map from multiple sources. In addition to allowing a user to initiate a search, in some embodiments, the presence of a search field in the primary map view also allows the user to see the query corresponding to the search results on the map and remove the query by clearing the query. Search results.

a) View recent use

As described above, the search table displays a list of newly searched terms and one of the searched route directions when the search field is initially touched and before any search terms are provided or edited, or when the search field is empty. Figure 20 illustrates four phases 2005 to 2020 for the interaction of a user of a search list having a list of recent searches and recent route directions for the user with an application executing on the user's device.

The first phase 2005 shows the device after the mapping application has been opened. As described above, the UI of the mapping application has a start page, in some embodiments, the start page (1) displays a map of the current orientation of the device, and (2) is configured in the top column 140 and acts as a float control. Several UI controls. In the first phase 2005, the user taps the currently empty search field 165. The top column 140 includes a guide control item 160 and a bookmark control item 170.

The second stage 2010 illustrates that the application displays the lookup table 2040 after receiving the user's touch on the search field. This search form is displayed regardless of whether the user provides any search terms in the search field. The search form 2040 provides a list of suggested search completions, which The suggested search completion includes the newly searched words and directions. In particular, the search form indicates that the user has recently searched for "John Smith" and "Pizzeria". Each of the search completions listed in the search form also indicates certain other useful information. For example, the icon 2045 displayed next to "John Smith" indicates that the person is included in a list of contacts on the user's device, and as indicated by the bookmark icon 2050, "Pizzeria" is currently stored as a bookmark.

The search form also lists the user's new route guidelines. These new route guides include the guidance to "Royal Burgers" as explained at the bottom of the search form 2040. Again, the search form 2040 lists one of the options for obtaining a home location from the user to the home address of the user, which is illustrated as the first item of the search form 2040. In some embodiments, a route from the current orientation to one of the user's homes is always provided when the recent use is shown. In addition, the mapping application of some embodiments displays the recent route guidance only when the search field is empty. That is, once the user begins typing a search query, the mapping application does not include the new route guidance in the list of suggested search completions.

The second stage 2010 also illustrates that the mapping application of some embodiments removes the navigation control item 160 and the bookmark control item 170 from the top column 140. The mapping application inserts a cancellation control 2055 that cancels the lookup table 2040 and returns to the map view shown in the previous stage 2005.

The third stage 2015 indicates that the user has selected the guidance option to "Home" listed as the first item in the search form. By providing some of the most frequently requested user search and guidance requests (including the option of the home guide) at the top of the search form, the application provides the user with no need to navigate the application in large numbers to receive such results. The ability to quickly obtain information for the most general requests of users.

The fourth stage 2020 illustrates displaying a mapping application corresponding to one of the directions from the user's current orientation to the user's home. The mapping application of some embodiments also removes the search field 165 and the cancellation control 2055 from the top column 140 and places the clear control. Item 255 and start control item 2060. In some embodiments, the start control item 2060 is used to initiate navigation based on the selected route. In some embodiments, the mapping application centers the current orientation indicator in the display area such that the center of the display area displays the route from the current orientation.

Users can also provide search queries in the search field. When a user types a complete search term in a search field, the mapping application of some embodiments provides a list of items that match or include the search terms that have been typed in the search field so far. For each particular search, the user has the option to select from a list of items displayed in the search table, or the user can select the keypad on the search term when it relates to the map and the user's current location. Search button to perform a complete search for the search term.

b) Complete search terms

Figure 21 illustrates, in four stages 2105 through 2120, an example of a user typing a search query and performing a search in a search field. In the first stage 2105, the user touches the search field 165. In this example, assume that the user has not yet performed a search before typing the search query, or that the search history has been cleared by the user or the mapping application. Therefore, the mapping application does not provide a search form with newly searched terms and directions.

The next stage 2110 shows the device after the user has typed the search term "Pavilion". The search table 2155 describes a list of search completions for the query term "Pavilion" typed by the user. The search results listed include the proposed search for "Pavilion Market", "Pavilion Theaters" and guidance from the user's current location to the "Bowling Pavilion". However, in some embodiments, the text "current orientation" is not displayed for the search of the route. The truth is, as shown, the mapping application displays the address of the destination. This is because the mapping application of some embodiments assumes that the user typing a letter indicates that the user intends to reach the destination of the matching search query, and therefore, the destination address is compared to the indication that the route is from the current location to the destination. For more useful information for users.

In addition, the list of suggested search completions in the search table does not display any bookmarks or contacts, because there is no matching item matching "Pavilion" that is locally stored on the user's device in this example. In addition, because the user has not performed any recent searches or guidelines for "Pavilion," in some embodiments, all of the suggested search completions listed in the lookup table have been obtained from the remote server. Information is obtained from the remote server as described further below.

In addition, the search completions listed may include matching the completion of a local geographic (eg, street, neighborhood, city, state, or country). For example, "Pavilion Street" or "City of Pavilion" can appear in the search completion list when this street or city exists. Moreover, when the user types a part of an address (for example, "220 Pavilion"), if the address exists (for example, "220 Promenade Drive, Skycity, CA"), the remote server can retrieve the address for this address. The most meaningful completion.

The third stage 2115 indicates that the user ignores any of the suggested search completions listed in the search table 2155 and instead selects the "Search" button on the keypad. The fourth stage 2120 illustrates a map with one of the pushpins 2190 for "Pavilion Theaters." In some embodiments, the mapping application adjusts the zoom level of the map, as further described below. In some of these embodiments, when an orientation is not in the map at the current zoom level, the mapping application does not display the pin for the orientation. Therefore, the pin for the "Bowling Pavilion" is not shown in the map. The mapping application has also removed the cancellation control 2055 from the top column 140 and restored the navigation control 160 and bookmark control 170 in the top column 140.

c) partial search terms and auto-complete

After any edits in the search field, the mapping application of some embodiments immediately populates the search table with automatic search completion. That is, when the user types a search term in the search field, the mapping application provides a list of suggested search completions based on the characters that have been typed at a particular time. Mapping application of some embodiments from Local sources (eg, bookmarks, contacts, recent searches, recent route directions, etc.) are also obtained from the remote server for such suggested searches.

Figure 22 illustrates four stages 2205 through 2220 of the user's initial search query and instant display of a search list with a list of recommended search completions. In the first stage 2205, the user is touching the search field 165 to initiate a search. The second stage 2210 illustrates that the mapping application renders the screen keypad 2250 and the user uses the keypad 2250 to type the letter "P" into the search field. Upon receipt of this first letter, the application immediately presents a lookup table with a list of suggested search completions collected from various sources (eg, local device and remote server recommendations).

The search form will continue to adjust and refine the proposed search in the search form as it receives more user input (ie, more alphanumeric characters and symbols) and query terms in the search field. List of. In some embodiments, the mapping application adjusts and improves the list as the user provides more input, even if the user misspelled the word being typed. For example, when the user types "Piza", the mapping application will display the search with the correct spelling word "Pizza". The mapping application of some embodiments uses a spell check and correction mechanism and other materials (eg, search history, etc.) to find similar spelling words to generate a list of suggestions for the search completion.

Each search can be sourced from a variety of sources, either locally on the user's device or from a remote source and server. The mapping application of some embodiments lists the search completion from the local source prior to the search completion from the remote source and server. For example, the search charts described in the second stage 2210 are listed from the top to the bottom of the list in the order of "Paul", "Pizza", "Police Station" and "Promenade". Several searches have been completed. "Paul" is a contact card from the user's device; "Pizza" is derived from a previous user search in one of the search history files stored on the user's device; and to "Police Station" to The guidelines are derived from a newly searched route guide. As mentioned above, in some embodiments In the search for the route, the text "Current Orientation" is not displayed. The fact is that some of the mapping applications of these embodiments display the address of the destination. In some cases, the mapping application does not indicate that the route starts from the current orientation and does not display the address of the destination. For example, the guide to "Police Station" does not show the address separately, as the search completion itself includes the address of the police station.

However, "Promenade" is the search obtained from the remote server. The remote map server may suggest this based on a search query that has been used by other users of the map server from the current orientation of the device. Therefore, "Promenade" is listed at the bottom of the search table 2255 after the three suggestions obtained at the local end of the mapping application are completed. As further described below, the mapping application of some embodiments sorts the search completions obtained by the local end.

In some embodiments, the suggested completion and search results of the mapping application are based on the current orientation of the device. That is, the suggested completion and search results within the area of the map located within one of the current orientations of the device. Alternatively or in combination, the map currently displayed in the display area is the area on which the recommendations of the mapping application of some embodiments are based and the search results are based. In these embodiments, the mapping application prefers the search completion and search results within the currently displayed area of the map.

In addition, the mapping application considers other factors when defining and adjusting the list of suggested search completions. In some embodiments, the mapping application considers the time factor. For example, the mapping application divides the search history (that is, the list of search completions used previously) into different time periods of the day (eg, late night, morning, etc.), different time periods of one week, different time periods of January. And/or different time periods of the year, and prefer the search completion and search results for the specific time period set to which the current search time belongs.

The third stage 2215 indicates that the user selects "Pizza" from the list of search completions displayed in the search table. The fourth stage 2220 illustrates that the mapping application now displays a map with the orientation of "Pizza Place" illustrated as a banner 2290 and a pin on the map. The user can then select various icons displayed on the banner to perform a variety of functions, including obtaining comments on the restaurant, invoking navigation to the restaurant, or receiving directions to the restaurant, and various other features as further described below. .

The banner 2290 includes a route extraction control item 2295 (illustrated as a display of a display car) for extracting one of the routes from the current orientation to the pin (eg, a driving route) without leaving the map view. The route extraction control is also used to initiate the navigation experience. For example, the mapping application of some embodiments provides one or more routes from the current orientation of the device to the orientation of the pushpin upon receiving a selection of the route extraction control. When selecting a route, the mapping application can begin to operate in navigation mode or in route inspection mode.

Figure 23 illustrates three stages 2305 through 2315 of the user's initial search query and the instant display of a search list with a list of recommended search completions. The three stages 2305 through 2315 of Figure 23 are similar to stages 2205, 2215 and 2220 of Figure 22, except that the map is in the 3D view. In the first stage 2305, the user is touching the search field 165 to initiate a search. The second stage 2310 illustrates that after receiving one of the letters in the search field 165, the application immediately presents a search form with a list of suggested search completions collected from various sources (eg, local device and remote server recommendations). .

The second stage 2310 also indicates that the user selects "Pizza" from the list of search completions displayed in the search list. The third stage 2315 illustrates that the mapping application now displays a map having the orientation of "Pizza PLC1" and the orientation of "Pizza PLC2" (the banner is not shown) respectively illustrated on the map as associated pins 2390 and 2395. . The user can then select various icons displayed on the banner to perform a variety of functions, including obtaining comments on the restaurant, invoking navigation to the restaurant, or receiving directions to the restaurant, and various other features as further described below. .

d) prefer the local end result

In order to provide some search completion within the search table, some embodiments should be mapped The program analyzes various local information stored in the user's device. For example, each user's device may contain a list of contacts containing a number of contact cards. Each contact card can contain a variety of information and tags for each contact. For example, each contact card may contain a contact tag with information about the following (if applicable): contact name and last name, company name, home address, work address, mobile phone number, work phone number , email address, URL, and various other information.

Similarly, the contact list may contain a specific contact card corresponding to one of the specific users of the mapping application, and the mapping application may designate the specific contact card as a "ME card." The mapping application can frequently access the user's ME card to take advantage of certain information required by certain application features, including the current location from the user to the user's home address or work address. The characteristics of the guidelines are provided in a number of different contexts within the mapping application. In particular, the mapping application of some embodiments lists the search for the mapping application obtained from the ME card at the top of the search table.

Figure 24 illustrates four stages 2405 through 2420 of the user's instructions for entering a partial address and obtaining a home address from the user of the contact or ME card originating from the user. In particular, Figure 24 illustrates that the mapping application of some embodiments lists the home address of the user at the top of the search table 2455. In the first stage 2405, the user taps the search field to begin the process of typing the user's search query information.

During the second phase 2410, the user has typed a portion of the number "12" that can at least partially match an address or a search term. In some embodiments, the application first matches the search query typed by the user with the information contained in the ME card of the user stored on the user's device and the contact list of the user. If the application detects any matching contact tags between the search query and the user's ME card, then the application of some embodiments will display the information found in the identified contacts as listed at the top of the search form. The suggested search is complete. In some embodiments, the mapping application only matches the information The information found in the identified contact is displayed as a suggested search when the address of the contact is made. Under the suggested search, the mapping application displays the text (eg, "Current Orientation") to indicate that the route is from home to the home. However, as described above, the mapping application of some embodiments instead displays the destination address instead of displaying the text, or displaying the destination address in conjunction with displaying the text, or not displaying the text and destination address. The application will display additional matching contact cards below the search from the ME card. In some embodiments, the mapping application can also render a search that is unrelated to the ME card. For example, when the user types "12", the mapping application will present the matching search completion (including the social networking website message) from the previous search of the local end and the matching search completion from the remote server.

The second stage 2410 illustrates the application automatically presenting the tagged home address of the user of the ME card originating from the user as completion in the lookup table. The application detects a match between the user's typed query "12" and the user's ME card containing the "1234 A Street, Santa..." home address tag. Since the match originates from the user's ME card, the application prioritizes the information from the local source and displays the information at the top of the list near the suggested search completion in the search form. The search form also shows other search completions, including "Bob Smith", "12 Hour Fitness" and "John Doe", all of which originate from various local sources and remote sources. For example, Bob Smith is currently stored in the contact list on the user device.

The third stage 2415 describes the user's guidance for choosing a home. The fourth stage 2420 illustrates the application displaying a map having a route corresponding to the user's current orientation to the user's home.

The application can also analyze other information or tags stored on the user's contact list or contact card. Figure 25 illustrates an example of a guideline for a user to type a partial search term and obtain a work address to a user originating from the user's contact card in four stages 2505 through 1820. Specifically, this figure illustrates some embodiments of the mapping application at A guide to the work address is listed at the top of the search form or near the top of the search form.

In the first stage 2505, the user touches the search field 165 to begin the process of typing the user's search query. During the second phase 2510, the user has typed a partial search term "Wo", and the application detects it as "Work" stored in the work tag field of the user's contact card (or ME card) or Part of the address label for "A's Work". In some embodiments, the application renders the user's tagged work address to complete as one of the lookup tables. As shown, the user's tagged work address is at the top of the search table 2555. Under the suggested search, the mapping application displays the text (eg, "Current Orientation") to indicate that the route is from home to the home. However, as described above, the mapping application of some embodiments may instead display the destination address instead of displaying the text, or display the destination address in conjunction with displaying the text, or not displaying the text and destination address.

As described above, the mapping application of some embodiments is near the top of the list of items in the search table, but displays a list of contacts that match and originate from the user's device under the information of the ME card that matches and originates from the user. Any information. For example, the search form 2555 is also near the top of the search form, but below the user's tagged work address, another contact card originating from the list of contacts stored in the user is listed for "Bob". Contact information for Woods. The search form is followed by "World Market" as a suggested search provided by a remote server.

The order in which each suggested search is completed in the search table may be derived from various ranking algorithms and heuristic learning methods that rank the strength of the relationship between the search query term and the suggested search completion. One such heuristic learning method is further described below. In some embodiments, the search completion originating from the local source (e.g., a contact list) typically has a higher priority than the information originating from the remote server. These search completions are also displayed at the top of the search form.

The third stage 2515 indicates that the user selects the finger corresponding to "Work" from the search table. The list item cited. The fourth stage 2520 illustrates the application displaying a map having a route corresponding to the guidance from the user's current orientation to the user's work.

e) Bookmarks

In some embodiments, the search completion listed in the search table can also be obtained by accessing a variety of other information stored locally on the user's device. For example, some embodiments may analyze bookmark information stored on a user's device. Each bookmark may contain various orientation information that the user has indicated as a location of interest. Figure 26 illustrates four stages 2605 through 2620 of the user selecting a partial search query and a list of search completions in the search list.

In the first stage 2605, the user taps the search field to begin the process of typing the user's search information. During the second phase 2610, the user has typed a partial search term "Bur" in the search field. The application matches this part of the query terms to various local and remote recommendations. Application matching includes guidelines for "Burt Smith", "Burger Palace" and to "Royal Burgers". For this search query, the application renders the user's tagged bookmarks as one of the suggested searches in the search form. In particular, the application has made "Bur" match the "Burger Palace" because the restaurant is currently stored as a bookmark in the user's device, as indicated by the bookmark icon 2630 next to "Burger Palace."

In some embodiments, information matching the bookmarks of the user's device may be displayed in the search list in a particular sort order. Some embodiments display a bookmark-based search completion below the search completion of the contact list from the user. However, the bookmark-based search can still be displayed above any of the remote server search suggestions. The search field in stage 2610 indicates that the contact "Burt Smith" is still displayed at the top of the list of suggested search completions because the search is completed from a list of contacts on the user's device. Similarly, the bookmarks for users of "Burger Palace" are displayed as the second item in the search form, and the guidance from the current position to "Royal Burgers" is displayed at the bottom of the list. unit.

In some embodiments, the lookup table may define different priorities for displaying items originating from the source on the device. For example, some embodiments may incorporate the search history and the frequency with which the user selects different suggested search completions into consideration factors to determine the particular order by which the suggested search is completed in the search table. For example, if the user frequently searches for and selects the "Burger Palace" corresponding to the bookmark on the device, the application can display the suggested search completion at the top of the list, and will correspond to the contact card "Burt Smith". The display is displayed as the second item in the list displayed in the search table. The third stage 2615 shows the user selecting a bookmark for "Burger Palace." The fourth stage 2620 shows the pushpins and banners for the "Burger Palace".

f) sorting the search completion

As described above, for any particular search query, the search table is populated by search completion from 1) local sources (eg, bookmarks, contacts, recent searches, recent route directions, etc.) and 2) remote server sources. The specific display order in which the suggested search is completed in the search table is derived using a variety of heuristic learning methods. In some embodiments, in general, the display order causes the search completion from the local source to take precedence over the search from the remote source.

Figure 27 conceptually illustrates a procedure 2700 performed by some embodiments for determining the order in which the suggested searches are completed from different sources in a search table. In some embodiments, the program 2700 is executed by a mapping application. The program 2700 of some embodiments begins when the user begins searching for a search query in the field.

The program 2700 begins by capturing or receiving (at 2705) the search query typed in the search field. The program 2700 then retrieves (at 2710) the matching information from one or more local sources. As noted above, in some embodiments, the local source includes a user's contact list, bookmarks, search history, and recent guidance. The program 2700 can match the query terms with certain information and tags stored in the contact card (including address tags, phone numbers, names or URLs, and other information stored in the contact card). The program can also search The query matches other local information. Other local information includes bookmarks and user search history information.

Next, the program 2700 determines (at 2715) the display order of the retrieved matches from the local source. In some embodiments, the program 2700 first sorts the matches from each of the local sources based on certain criteria (eg, the frequency of use of the completion, the strength of the association between the search query and the match, etc.) and only selects from A certain number (for example, three) of the top of each source is matched. In some embodiments, the program 2700 sorts the retrieved matches based on the local source. For example, program 2700 displays the matches in the order of ME cards, contact lists, bookmarks, and search history. Other embodiments may have a different order. The program 2700 then displays (at 2720) the retrieved matches from the local source in the lookup table in accordance with the determined display order (at 2715).

The program 2700 then receives or retrieves (at 2725) the search suggestion from a remote source (eg, a remote map server) by sending the search query to the remote source. In some embodiments, the program 2700 simultaneously sends the search query to the remote source and views it in the local source to find the matching information. In some embodiments, the server may apply its own search ranking algorithm to identify particular search suggestions and score the particular search suggestions. The server can then send a particular number of identified search results to the mapping application, and the program 2700 can use its own heuristic learning method (eg, the frequency of use of the completion, the strength of the association between the search query and the match, etc.) The identified search results are sorted and filtered (at 2730). For example, in some embodiments, the program 2700 can suggest the top three server search suggestions in the list of suggested search completions in the search table. Next, the program 2700 displays (at 2735) a match from the remote source under the match from the local source. The program 2700 then ends.

Some embodiments may immediately present the local search suggestions and adjust such suggestions to include such remote server recommendations when the remote server receives the remote server recommendations, which provides a "quasi" instant feeling for the search program. For example, if the search table provides enough screen space to column After ten individual search completions or suggestions, the program initially lists all ten such search suggestions from the local export source (eg, bookmarks, contacts, search history). The program can then replace the local search suggestions with the suggestions received from the server when the advice received from the server is obtained via the network. Program 2700 can continually update a particular list of search suggestions when the server receives information that can be considered more important than the information listed in the search table.

g) Display the search results as a list

28 illustrates an example of performing a mapping application of some embodiments on a device 2800 (eg, a tablet device, such as the iPad® sold by Apple, Inc.), with smaller devices (eg, smart phones, such as Apple) Device 2800 has a relatively large display area compared to the display area of the iPhone® sold by Inc.. In particular, Figure 28 illustrates the interaction of a user for displaying a list of search results in a device having a relatively large display area with a mapping application in four different stages 2805 through 2820.

The first stage 2805 shows that the mapping application has a top column 2806 that includes a set of controls, including a search field 2830 and a list view control item 2835 for displaying a list of search results. In some embodiments, the mapping application displays the list view control item 2835 in the top column 2806 when the search is completed based on one of the search queries as shown. In other embodiments, the mapping application places the list view control item 2835 in the search field 2830. In still other embodiments, the mapping application slides the list view control item 2835 by causing the list view control item 235 to slide out of the 3D icon 2890.

In some such embodiments, the mapping application displays a list view control item 2835 when the local drawing application displays the search results in the map. In this example, the first stage 2805 shows that the mapping application has performed a search using "Pizza" as a search query. The mapping application displays the search results as two pushpins 2840 and 2845 in the map view. The mapping application of some embodiments is also shown for the two An information banner 2846 of one of the pushpins indicating that the point of interest (POI) represented by the pushpin is the most suggested result. The first stage 2805 also shows that the user is selecting the list view control item 2835.

The second stage 2810 shows that the mapping application is displaying a list 2850 of POIs that the mapping application has discovered using the search query. In this example, the manifest has three POIs. The first two POIs correspond to the push pins 2845 and 2840, respectively. The mapping application does not display a pin corresponding to the third POI "Pizza Planet" because the third POI is not located within the map of the map including the first two POIs. In some embodiments, when one of the POIs selected from the list is not within the zone of the currently displayed map, the mapping application shifts the map to display another zone.

The third stage 2815 shows that the mapping application is receiving a selection of the third entry. The fourth stage 2815 shows that the mapping application has shifted the map to display another area of the map that includes the pin 2855 corresponding to the third POI. In some embodiments, the mapping application displays an animation for a duration to show that the map is being shifted to another area of the map. In some embodiments, the mapping application displays an information banner for the third POI because the pin for the POI is the only pin in the map area.

h) Software architecture

Figure 29 illustrates an example architecture of a mapping application that provides a list of suggested search completions based on a search query. In this example, the mapping application 2900 of some embodiments is executed in device 2905. As shown, the mapping application 2900 includes a search completion manager 2910, a local source manager 2915, a remote source manager 2920, a manifest manager 2925, a search query parser 2930, a recent search completion repository 2935, and a recent route. Guide the repository 2940. This figure also illustrates the search and map server 2960. The mapping application 2900, device 2905, and search and map server 2960 can each have a number of other modules, but are not depicted in this figure for simplicity of discussion.

The search query parser 2930 receives the user input manager via one of the devices 2905 Search query typed (not shown). The query parser 2930 sends the parsed query to the search completion manager 2910, such that the search completion manager 2910 can generate a search request for the remote source manager 2920 and the local source manager 2915. The search query parser 2930 also receives a touch input on one of the search fields (eg, search field 165) and notifies the search completion manager of the input so that the search completion manager can search for the repository 2935 and the recent search. The Route Guidance Repository 2940 draws on the recent search completion and recent route guidance.

When the search completion manager 2910 receives a notification from the search query parser that the user has touched one of the search fields when the search field is empty, the search completion manager 2910 finds the recent search completion repository 2935 and the recent route guide 2940. . In some embodiments, the search completion manager retrieves the search completion and route guidance used in a certain period of time (eg, hours, days, weeks, etc.) prior to receiving the touch input.

The search completion manager 2910 also directs the remote source manager 2920 and the local source manager 2915 to find the search completion based on the parsed search query. The search completion manager 2910 then receives the search completion and route directions returned by the remote source manager 2920 and the local source manager 2915.

The search completion manager collects the search completion and route guidance received from the remote source manager 2920 and the local source manager 2915, respectively, and filters out any duplicate completions and guidelines. The search completion manager then sends these completions and guidelines to the inventory manager 2925.

The inventory manager 2925 sorts the search completion and driving directions based on certain criteria. As mentioned above, these criteria include the use of search completion and route guidance time, completion and route guidance from local sources or remote sources. The manifest manager 2925 then passes the sorted list to one of the display managers (not shown) of the device 2905 so that the list can be displayed to the user.

The search completion manager also forwards the search request (that is, the full search query selected from the search completion list or the search field is typed when the user selects "type" or search for the control item. The search query is selected and the route guidance is selected, and the requests and the directions are passed to a search request manager (not shown) that will use the search requests to search or calculate a route. The search completion manager 2910 stores the search requests (ie, the search for actual search) and the selected route guides (ie, the start and destination directions) in the recent search completion repository 2935 and The new route guides the repository 2940.

The Recently Completed Repository 2935 and the New Route Guidance Repository 2940 are used to store the newly used search request and the memory space that has been used to calculate the route. In some embodiments, the two repositories are used for fast access to the cache.

The local source manager 2915 looks up the contact repository 2950 and the bookmark repository 2955 to find contacts (eg, ME cards) and bookmarks that at least partially match the parsed search queries received from the search completion manager 2910. The local source manager 2915 then generates a search completion based on the matched contacts and bookmarks and returns the search completions to the search completion manager 2910. Contacts and bookmarks stored in the repositories 2950 and 2955 are generated, maintained, and/or accessed by an application executing on the device 2905, and the applications include a mapping application 2900.

The remote source manager 2920 sends the parsed search query received from the search completion manager 2910 to one or more servers (not all illustrated) including the search and map server 2960. The remote source manager 2920 receives the search completion and/or route guidance returned from the server 2960 in response to the search query sent to the search and map server 2960. The remote source manager 2920 then sends the completion and route directions to the search completion manager 2910.

As shown, the search and map server includes a search completion repository 2965 and a route guidance repository 2970. In some embodiments, the search and map server stores the search request and route directions for calculating the route in the repositories 2965 and 2970. The search and map server 2960 receives the search requests and routes from the executing individual device (including device 2905) executing the mapping application of some embodiments (such as the mapping application 2900). Guidelines. The search and map server then generates the suggested search completion and route directions to device 2905. In some embodiments, the search and map server includes two servers that respectively supply map data and generate routes. The search completion repository 2965 and the route guidance repository 2970 of some embodiments are used to store the data storage structure of the search request and the route guidance.

2. Clear search results via the search field

In addition to allowing a user to initiate a search, in some embodiments, the presence of a search field in the primary map view also allows the user to see the query corresponding to the search results on the map and remove it by clearing the query. They searched for results. Figure 30 illustrates the user clearing results from map 3000 in three stages 3005 through 3015.

The first stage 3005 illustrates that the map displays a pin 3025 for "Pizza Place." This pushpin 3025 may have been placed on the map 3000 by a variety of different mechanisms. For example, the user may have placed the pin on the map and received a lookup in the opposite direction, or the user may have typed a search query for one of "Pizza Place 321".

The second stage 3010 illustrates the user selecting the "X" button 3030 in the search field 165 to clear any search queries displayed in the search field 165. In addition, when the search query is cleared, all search results (pins) associated with the displayed search query displayed on the map will also be cleared from the map 3000. The third stage shows that after the user selects the "X" button 3030, the search field 165 is now empty and the pin for "Pizza Place" is no longer displayed on the map.

Figure 31 illustrates four stages 3105 through 3120 for the purpose of clearing the interaction of the user of the selected search result displayed on the map with the application executing on the user's device.

The first stage 3105 shows the device after the mapping application has been opened. The second stage 3105 illustrates that the application displays the lookup table 3140 after receiving the user's touch on the search field. This search form is displayed regardless of whether the user provides any search terms in the search field. The search form 3140 provides a list of suggested search completions, including the newly searched terms and route directions. In detail, the search form indicates Users have recently searched for "John Smith" and "Pizzeria." The search form also lists the user's new route guidance. These new route guidance include the guidance to "Royal Burgers" as explained at the bottom of the search form 3140. Again, the search table 3140 lists an option to obtain guidance from the user's current location to the user's home address, which is illustrated as the first item of the search table 3140. The top column 140 includes a guide control item 160 and a bookmark control item 170.

The second stage 3110 describes the guidelines for the user to select "Home". The second stage 3110 also illustrates that the mapping application of some embodiments removes the navigation control item 160 and the bookmark control item 170 from the top column 140. The mapping application inserts the cancel control item 2055.

The third stage 3115 illustrates that the mapping application displays a route corresponding to one of the directions from the user's current location to the user's home. As shown, the route has two push pins for the start and end points of the route. The mapping application of some embodiments also removes the cancel control item 2055 from the top column 140 and places the clear control item 255 and the start control item 2060. The third stage 3115 also illustrates the selection of the purge control item 255. The fourth stage 3120 indicates that the search field 165 is now empty, and the push pins for the start and end points of the route are no longer displayed on the map because the mapping application of some embodiments is receiving the clear control item 255. These buttons are removed from the map at the time of selection.

B. Map shows the zoom level setting of the search results

When the user is viewing the map in a particular view and performing a search query, some embodiments will transition to a new map view containing the search results of the user's query. A particular type of transition may include continuously adjusting the map zoom level and may include displaying an animation between the original map view and the new map view. The application considers a number of factors when deciding on the particular type of transition and whether to provide an animation between different map views. Some factors may include the distance between different map views given a particular zoom level, the information available to provide animation between the map views, the data bandwidth capabilities of the user's internet connection, and various other factor.

32 illustrates a procedure 3200 performed by some embodiments for determining a particular type of transition displayed between a current map view of a user and a target map view containing search results for a user performing a search query. In some embodiments, the program 3200 is executed by a mapping application. In some embodiments, the program 3200 begins when the mapping application generates a search result based on a user's search query.

The program 3200 begins by capturing (at 3205) the search results. The program then defines (at 3210) the original zone and the target zone. In some embodiments, the program 3200 considers the map being displayed to the user. Program 3200 defines this map display as having a current map view of the original map area. The program 3200 then determines a target map view with one of the target map areas proposed, which needs to display the target map view to the user to provide an optimal map view showing some or all of the search results.

In some embodiments, the program 3200 initially defines (at 3210) the original zone and the target zone at the same zoom level. In some such embodiments, the program 3200 initially maintains the zoom level of the original region and sets the zoom level of the target region to the zoom level of the original region. Program 3200 also sets the orientation of the target zone to the orientation of the original zone. Moreover, different embodiments locate the target zone in different ways. For example, in some embodiments, the program 3200 defines a target zone to include at least one search result. Again, the program 3200 of some embodiments defines the target zone by obtaining an average coordinate of the search results and setting the center of the target zone to the average coordinate.

Next, routine 3200 determines (at 3215) whether the original zone and the target zone at least partially overlap. When the routine 3200 determines (at 3215) that the two zones at least partially overlap, the routine 3200 continues to 3225, which is described further below.

When the program 3200 determines (at 3215) that the original zone does not overlap the target zone, the routine 3200 determines (at 3220) whether the two zones are separated by more than a threshold distance. In some embodiments, the program 3200 dynamically calculates this threshold distance based on the current zoom level of the original zone and the target zone. For example, the calculated threshold is inversely proportional to the scaling levels. That is, the more the regions are enlarged, the shorter the calculated threshold distance is.

When the program 3200 determines (at 3220) that the two zones are above the threshold distance, the program 3200 displays (at 3230) the target zone, but does not display animation from the original zone to the target zone. Otherwise, the program displays (at 3235) an animation from the original zone to the target zone. Different embodiments use different animation techniques. For example, in some embodiments, the program 3200 transitions from the original zone to the target zone using cross-fade of the original zone and the target zone. In some embodiments, the program 3200 can transition from the original zone to the target zone as if the viewpoint of the virtual camera overlooking the original zone is moving to the target zone.

When the program 3200 determines (at 3215) that the original zone at least partially overlaps the target zone, the program determines (at 3225) whether to modify the target zone. Operation 3225 is described in more detail below by referring to FIG. The program 3200 then determines (at 3240) whether to display an animation to the target zone. Operation 3240 is described in greater detail below by referring to FIG.

Figure 33 illustrates a procedure 3300 executed by some embodiments for determining whether to modify a target zone when the target zone at least partially overlaps the original zone originally defined by the mapping application. In some embodiments, the program 3200 is executed by a mapping application.

The program 3300 begins by: determining (at 3305) whether (1) the original region includes any search results and (2) whether the zoom level of the original region is less than a threshold zoom level (ie, the original region is not zoomed out) A threshold zoom level). When the program determines (at 3305) that the original region does not include any search results or that the zoom level of the original region is not less than the threshold zoom level, then the process 3300 continues to 3315, which is further described below.

When the program determines (at 3305) that the original region includes at least one search result and the zoom level of the original region is less than the threshold zoom level, the program 3300 uses (at 3310) the original region as the target region. Program 3300 then proceeds to 3335, which is described further below.

When the program determines (at 3305) that the original region does not include any search results or that the zoom level of the original region is not less than the threshold zoom level, routine 3300 determines (at 3315) whether the original region includes any search results. When the program 3300 determines (at 3315) that the original zone includes at least one search result, the process 3300 continues to 3335, which is further described below.

When the program 3300 determines (at 3315) that the original region does not include the search results, the program 3300 expands (at 3320) the original region to include at least one search result and uses the expanded original region as the target region. Different embodiments extend the original zone in different ways. For example, in some embodiments, the program 3300 is expanded in all directions from the center of the original zone to include at least one search result, while in other embodiments, the program 3300 is not in all directions from the center of the original zone. Expanded to include at least one search result. In some such embodiments, the program 3300 expands in a manner that includes search results that are closest to the boundaries of the original region.

Next, routine 3300 determines (at 3325) whether (1) whether the most important result is outside the target zone and (2) whether all of the search results in the target zone are significantly less important. Different embodiments evaluate the importance of search results in different ways. For example, some embodiments quantify the proximity of a search query to a search result and use the proximity of the quantization to determine importance. In particular, the program 3300 of some embodiments can treat the closest search result as the most important search result. Other embodiments use other techniques to assess the importance of the search report. Moreover, when the difference between the quantized proximity of the two search results is greater than a margin, the routine 3300 of some embodiments will consider a search result to be significantly less important than another search result.

When the program 3300 determines (at 3325) that the most significant result is outside the target zone and all of the search results in the target zone are significantly less important, the program 3300 expands (at 3330) a certain size to include one or more search results. Program 3300 then loops back to 3325 to make another determination to see if the target zone is to be further extended.

When the program 3300 determines (at 3325) that the most significant result is not outside the target zone or that all of the search results in the target zone are not significantly less important, the program 3300 is necessary to ensure that the target zone can accommodate any UI associated with the search results ( For example, the information banner) is further extended (at 3335) to the target zone. The program 3300 then ends.

Figure 34 illustrates a procedure 3400 performed by some embodiments for (1) determining whether to display from the original region when the target region at least partially overlaps with the original region originally defined by the mapping application and when considering the target region to be modified Animation to the target area. In some embodiments The program 3400 is executed by the mapping application.

The routine 3400 begins by determining (at 3405) whether the zoom levels of the original and target regions differ by more than a first margin. In some embodiments, the first threshold difference represents a higher margin difference between the zoom level of the original zone and the target zone. In this case, the zoom level of the original area and the target area is considered to be significantly different.

When the program 3400 determines (at 3405) that the zoom levels are significantly different, the program 3400 displays (at 3410) the target area, but does not display animation from the original area to the target area. When the program 3400 determines (at 3405) that the zoom levels are not significantly different, the routine 3400 determines (at 3415) whether the zoom levels differ by more than a second margin. In some embodiments, the second threshold difference represents a lower margin difference between the zoom level of the original zone and the target zone. When the difference between the zoom levels is lower than the higher threshold and the lower threshold, the zoom level of the original area and the target area is considered to be moderately different.

When the program 3400 determines (at 3415) that the zoom levels of the original and target regions are moderately different, the program 3400 displays (at 3420) an animation from the original region to the target region. When the routine 3400 determines (at 3415) that the zoom levels of the original and target regions are neither moderately nor significantly different, the routine 3400 determines (at 3425) whether the original region includes all of the search results.

When the program 3400 determines (at 3425) that the original zone includes all of the search results, the process ends. Otherwise, the process 3400 continues to 3430 to determine if displaying the animation may result in more search results being visible. In some embodiments, the program 3400 checks the animation to see if any search results will appear when the animation is displayed.

When program 3400 determines (at 3430) that displaying the animation may result in more search results being visible, program 3400 displays (at 3420) an animation from the original zone to the target zone. Otherwise, the program 3400 ends.

Figure 35 illustrates four stages in which the application displays to the target map area containing the corresponding search results without providing any animation between the current map view and the target map view. 3505 to 3520. The first stage 3505 illustrates a primitive area of a map showing, for example, Cupertino, California. The map is displayed at a specific zoom level for one of the various highways. If the user's thumb and index finger are moving in the outward direction, the user is also adjusting the map (via a gesture input) to zoom into a more detailed view.

The second stage 3510 illustrates that the map is now at a more detailed zoom level (i.e., zoomed in), and the individual streets displayed therein include "First Street", "Main Street" and "Second Street". The user also taps the search field 165 to initiate a search. The third stage 3515 indicates that the user types the search query "Smithsonian" into the search field and selects "Smithsonian Museum, Washington, DC" from the suggested search completion list in the search table 3555.

When Washington, DC was selected, the app immediately displays a map of Washington DC without any animation. In this example, because Cupertino, CA and Washington, DC are separated by a considerable screen distance for the current map view and the specific zoom level, the application immediately jumps to the map of Washington, DC without providing any animation. For this given search, the application has determined that the screen distance between the map area displayed in stage 3510 and the target map area required to display the Washington DC is greater than a certain threshold, and thus, provided for a given zoom level Animation is not reasonable or feasible.

In some embodiments, the mapping application displays a message when the target map area is too far from the current displayed map area or the user's current orientation (eg, a distance of more than a few hundred miles or thousands of miles) (For example, "Did you mean XYZ place in location A...?") to ask the user if he or she really wants to search for a distant target area. Alternatively or in combination, the mapping application can present the message to the user by voice (eg, by reading the message). In some embodiments, the mapping application does not provide search results until the user responds to the message. In some embodiments, in addition to the message, the mapping application also provides alternative search results. For example, the mapping application can provide search results that can be found in or near the currently displayed area (eg For example, a list of "Smith's Onion, Cupertino, CA") may provide a search for a search that is similar but with a search query that is closer to one of the currently displayed regions. If the user selects an alternative result, the mapping application will display the search results on a region of the map that is closer to the currently displayed region.

Figure 36 illustrates four stages 3605 through 3620 of the situation in which the application detects the search results within the original current map view and therefore does not have to scale the map or display an animation to any new target map area. The first stage 3605 illustrates the user viewing the map 3630 of Cupertino, California. Map 3630 is under a particular zoom level showing one of various highways. If the user's thumb and forefinger are moving in the outward direction, the user is also adjusting the map to zoom in to a more detailed view.

The second stage 3610 indicates that the map is now under a more detailed zoom level, and the displayed individual streets include "First Street", "Main Street" and "Second Street". The user also taps the search field to initiate a search. The third stage 3615 indicates that the user types the search query "Coffee Shop" into the search field and selects the coffee shop located in "First Street" from the suggested search completion list in the search table. When a coffee shop is selected, the application displays the same current map view that the user is viewing before the search request, as shown in the fourth stage 3620. Since the search results for the coffee shop located in the first street can be viewed in the user's current map view, the application does not have to adjust the zoom settings or provide any animation to display the target map area. The application has set the target map area with the relevant search results as the current map area, and in this case, avoids changes between views in different areas of the map.

37 illustrates, in four different stages 3705 through 3720, the mapping application of some embodiments reduces the current map area view to present a number of search results found based on the search query. The first stage 3705 illustrates the mapping application after the user has typed the search query "Tech Companies Cupertino". The search table 3755 displays a list of search results including a previous search query 3760. As shown, the user is searching for the table 3760 Select search query 3760. The mapping application of some embodiments stores search results for searches using a mapping application.

The second stage 3710 displays a map of the current orientation under the detailed zoom level, wherein the displayed individual streets include "First Street", "Main Street" and "Second Street". Since the search results the tech companies in Cupertino are not located within the original current map area of the current map view, the application of some embodiments extends the map view such that the target area includes all search results located in the target area. The mapping application of some embodiments also determines that the animation of the map view from the current map area to the target area is required because the zoom level of the current area and the target area are significantly different.

The third stage 3715 illustrates the maps at different zoom levels. The mapping application only briefly displays the map under this zoom level as part of the animation displayed by the mapping application in order to zoom out the map to a zoom level for displaying a target area larger than the original area. In some embodiments, the mapping application displays a 2D/3D transition as part of the animation.

The fourth stage 3720 illustrates the map at the zoom level of the target area. That is, the mapping application has completed displaying the animation from the original zone to the target zone displayed at the second stage 3710.

In some embodiments, the mapping application changes the duration of the animation for transitioning from the original zone to the target zone based on the amount of variation involved in the transition. For example, the mapping application of some embodiments animates the transition for a short duration when the original zone is not far from the target zone or when the original zone overlaps the target zone. When the distance between the two zones is relatively large (eg, hundreds of miles), the mapping application displays a longer animation. In some such embodiments, the mapping application may not display animation at all when the distance between the two zones is extremely large (eg, thousands of miles).

III. Controls for previewing items on the map

Some embodiments of the present invention provide for presenting different types of points of interest (POI) A novel user interface for detailed information. This user interface is referred to as a "detailed information stage" in the above and below description. In some embodiments, the detailed information screen includes a display area for displaying an image of the POI and a plurality of index tabs under which different types of information about the POI are grouped and presented to the user.

The mapping application of some embodiments provides a number of ways of displaying the detailed information screen for the POI. As described above, the mapping application of some embodiments displays a banner above each of the pins displayed as search results. The user can select one of the POI banners to open a detailed information screen for the POI. The mapping application also allows the user to open a detailed information screen for a POI by selecting a POI for a list of POIs presented by the search results of a search query from the mapping application of some embodiments. The mapping application allows the user to open the detail screen after placing a pin in one orientation. In addition, the mapping application allows the user to open a detailed information screen for the current orientation.

FIG. 38 conceptually illustrates a GUI 3800 which is a "detailed information screen" of the selected POI. In particular, FIG. 38 illustrates a mapping application of some embodiments in six different stages 3805 through 3830 that display a 3D animation of the POI in the media display area 3835 of the GUI 3800. This figure illustrates that the GUI 3800 includes a media display area 3835, an index tab 3840, an information display area 3845, and a top column 3850.

The media display area 3835 of some embodiments is for displaying different media of the POI. In some embodiments, when the GUI 3800 is launched, the mapping application initially displays a 3D animation of the POI. For example, when a POI is a building, the mapping application displays an animated 3D view of the surroundings of the building and building. In some embodiments, the mapping application displays the building as if it were viewed from a camera mounted on a helicopter hovering around the top of the building.

Different embodiments produce 3D animations (3D video presentation) in different ways. For example, a 3D animation is made up of objects that orbit the earth along a track or who fly at a lower altitude. A video capture device of a human-driven aircraft (eg, satellite, space shuttle, airplane, helicopter, etc.) captures one of the video clips.

In some embodiments, the mapping application generates a 3D video presentation by performing a blending operation (eg, a three-dimensional perspective blending operation) on a number of images captured by a flying object (such as a helicopter, airplane, satellite, etc.) for a particular orientation. Such images may be still images or images from a portion of one of the video clips captured by such objects.

In some embodiments, the 3D rendering operation produces a video clip from the images by transitioning through the plurality of images for a set amount of time. In some embodiments, this transition results in multiple video frames being generated by capturing different subsets of the position from different perspective representations in the 3D scene at different times.

In some embodiments, the mapping application generates a 3D video presentation by moving the virtual camera over and around the POI (eg, a building) and its surroundings in a 3D immersive map view or in a low-altitude overhead view. For example, the mapping application can move the virtual camera as if the virtual camera was capturing the POI and the surrounding environment from the flying object that wraps around the top of the building. The virtual camera and the 3D immersive map view are described in detail in the above-incorporated U.S. Patent Application Serial No. 13/632,035.

When the material for the animated 3D view of the POI is not available (eg, data is not available in the map server or other local storage), the mapping application of some embodiments finds the next available type of image for display on the display. In area 3835. For example, the mapping application can display a satellite view of the POI.

When the data for the animated 3D view of the POI is available, but it takes some time to obtain the necessary information to display the animated 3D (eg, a slow network connection due to the source of the device to the necessary data), some embodiments of the mapping application The program identifies an available type of media for use under the POI and first displays the media in the media display area 3835. For example, the mapping application of some embodiments displays the POI satellite in the media display area 3835. image. In some embodiments, to provide an animation effect, the mapping application rotates the satellite image of the POI (eg, clockwise) rather than statically displaying the 2D satellite image.

When sufficient data for displaying an animated 3D view is obtained, the mapping application of some embodiments switches from displaying a satellite image of the POI to an animated 3D view displaying the POI. Different embodiments of the mapping application use different effects to make this switch. For example, some embodiments of the mapping application cross-fade a POI 2D satellite image into an animated 3D view. In other embodiments, the mapping application can use the Ken Burns effect to display a 3D animated view from satellite imagery.

In some embodiments, the mapping application determines the type of media of the POI initially displayed in the media display area 3835 based on the type of POI selected. For example, when the POI is a restaurant, the mapping application of some embodiments initially displays images of cooking dishes served by the restaurant or internal images of the restaurant. When displaying such images, the mapping application of different embodiments uses different effects to display different images. The different effects that the mapping application can use include Ken Burns effect, vignetting effect, crossfade, tilt, slide show, and more.

The mapping application of some embodiments overlays the information text on the media displayed in the media display area 3835. In some embodiments, the information text is displayed to the left of the proximity media display area 3835, as shown in the third stage 3815. However, the orientation of the message text can be anywhere (eg, center) in the media display area 3835. In some embodiments, the mapping application applies different effects to the portion of the media display area that overlays the information text, making the text legible. For example, the mapping application can change the color of the portion or blur the portion. In other embodiments, the mapping application does not modify the image to make the information text legible. The reality is that the mapping application adjusts the information text to make it legible when the portion of the image that is overlaid changes.

The mapping application of some embodiments may also switch from other types of media that were originally displayed when the GUI 3800 was launched. For example, when the user When an input item is displayed among the items displayed under the "Media" index tab (not shown), the mapping application displays the image associated with the selected input item in the media display area 3835, or in the media display area 3835. Plays the video associated with the selected entry.

Index tab 3840 is an index tag for displaying different sets of input items grouped for different types of information associated with different index tags. In some embodiments, as shown, the GUI 3800 initially includes an "Info" index tab, a "Reviews" index tab, and a "Photos" index tab. When the information index tab is selected, the mapping application displays the input related to the overall information about the POI in the information display area 3845. As shown, the overall information about the POI includes the phone number, the URL for the POI, the address, and the like. When a comment index tab is selected, the input to be displayed includes all comments collected by the news gathering entity (eg, Yelp, Facebook, Twitter, etc.) and supplied to the mapping application. Similarly, when a photo index tab is selected, the items to be displayed include photos collected by the information collection entity. The index tabs and entries displayed in the information display area 3845 are described in more detail below.

The top column 3850 of some embodiments includes a "previous page" button 3895 for returning to the state prior to launching the GUI 3800. When the map with the search results has been displayed before the GUI 3800 is displayed, the "Previous Page" button 3895 will instruct the mapping application to return to displaying the map with the search results. When the list of POIs has been displayed before the GUI 3800 is displayed, the "Previous Page" button 3895 instructs the mapping application to return to the display list.

The operation of the GUI 3800 will now be described. In the first stage 3805, as a result of typing a search query "Famous Building", the mapping application displays a pin 3860 and a banner 3865. In the next stage 3810, the user selects arrow 3875 to launch the "Details Info Screen" for this POI.

In the third phase 3815, the GUI 3800 has been launched. The mapping application displays an initial collection of components of the GUI 3800 that includes a top column 3850, a media display area 3835, an index tab 3840, and an information display area 3845. In the media display area 3835, The mapping application displays an animated 3D view of famous buildings and other buildings near famous buildings.

The mapping application also displays informational text about famous buildings to the left of the media display area 3835. The information displayed includes the name of the building, the address, the star rating, and the number of comments, as shown in the media display area 3835. Behind the text, the mapping application initially displays images of famous buildings. As shown, the building appears to be faded because the mapping application has faded portions of the image that appear behind the message text to make the text more prominent and legible. At this stage 3815, the information display area 3835 displays overall information about the building (e.g., phone number, building URL, address, etc.) because the information indexing tag, in some embodiments, is a preset index tag selection.

The next stage 3820 shows that the virtual camera's viewpoint has changed, making the famous building appear next to the displayed information text. Some other nearby buildings are displayed behind the news text. The virtual camera's point of view also began to circle around the top of the famous building.

The next stage, 3825, shows that the virtual camera has moved to the other side of the famous building. As shown, the "FMS BLDG" displayed on one side of the building now appears in the southwest direction of the media display area 3845 to show that the virtual camera has moved counterclockwise relative to the top of the building. The "H" in the circle at the top of the building also appears to have rotated from the previous stage of 3820. In addition, because the viewpoint of the virtual camera has changed, different neighboring buildings are displayed behind the information text.

The next stage, 3830, shows that the virtual camera has moved to one side of the famous building. The virtual camera continues to move and is now on the side of the building where "FMS BLDG" is no longer visible. The "H" in the circle at the top of the building appears to be further rotated. The mapping application of some embodiments continues to display this animated 3D animated view (ie, will cause the virtual camera to continue to hover on top of the building) until the user provides additional input (eg, enters to close the GUI 3800, Input photo selection under the photo index tab Wait).

In some embodiments, the mapping application uses a 3D rendering operation to generate a 3D rendering in its other modes of operation. For example, in some embodiments, the mapping application uses this operation whenever the user performs a search for a particular orientation or specifies other search criteria, or whenever the user explores one of the orientations on the map. A 3D video presentation. Figure 39 illustrates five different stages 3905 through 3925 illustrating that the mapping application uses 3D rendering operations to present one instance of a particular search result.

The first stage 3905 illustrates the mapping application display lookup table 3940 after receiving the first letter of the search query typed by the user in the search field 165. As shown, the search form 3940 includes a number of search completions including: "X Corp.", "X Station 555..." and "Promenade X". The first phase 3905 also stated that "X Corp." was selected.

The second stage 3910 illustrates a 3D map view 3910 as indicated by the eye-catching 3D control item 150. In some embodiments, the mapping application automatically displays the 3D animation of the POI when the user views the POI in 3D mode. Some of the mapping applications of these embodiments still allow the user to rotate the map view (eg, with two indicative actions). In some embodiments, the mapping application begins rendering a 3D animation of the POI after a certain amount of time (eg, a few seconds) without receiving input from the user. The second phase 3910 also illustrates that the mapping application begins to render a 3D animation of the building. As shown, 3D animation is showing sides 1 and 2 of the building of X Corporation, with side 2 having the name X Corporation. In this example, the 3D animation is rendered from a 3D video taken from a flying object that is spiraled counterclockwise around the top of the building.

The third stage 3915 illustrates that the viewpoint has changed and the building appears to rotate clockwise as the flying object spirals counterclockwise. The 3D presentation is showing the sides 2 and 3 of the building of X Corporation. As shown, the "H" mark on the top of the building has also been rotated.

The fourth stage 3920 and the fifth stage 3925 show that when the flying object is hovered clockwise Further rotation of the building. The mapping application of some embodiments repeats the 3D rendering until the user provides one of the inputs to stop or change the animation (eg, two indicative actions, an input to exit the 3D mode, etc.).

FIG. 40 conceptually illustrates the GUI 3800. Specifically, FIG. 40 illustrates the mapping application of some embodiments initially displaying the animation of the satellite image of the POI in the media display area 3835 of the GUI 3800 and obtaining sufficient data for the 3D animation in eight different stages 4005 to 4040. Switch to the 3D animation of POI when displaying 3D animation.

In the first stage 4005, as a result of the key search query "MyWork Building", the mapping application displays the pin 4060 and the banner 4065. The user has also selected the lower right corner of the map to strip the map and display one of the group buttons described above. The next stage 4010 shows the user selecting the "List" button 4070 to cause the mapping application to display the search results as a list.

In a third stage 4015, the mapping application displays a list of POIs after the user has selected the list button 4070 in the previous stage 4010. In this example, the list happens to include only one POI because the search query is adequately targeted to a particular outcome. In the next stage 4020, the user selects the entry 4075 to launch the "Details Info Screen" for this POI. As shown, the user has selected the "MyWork Building" POI.

In the fifth stage 4025, the GUI 3800 has been launched. However, in contrast to stage 3815 described above with reference to Figure 38, the mapping application displays a satellite image of one of the actual buildings associated with the "MyWork Building" POI. The satellite image also shows other buildings near the building, rather than an animated 3D view of the building. The satellite image is a 2D image of the top of the building taken at a considerable distance (ie, from a satellite) from the top of the building. As shown, the mapping application also fades portions of the image that are overlaid by the information text to make the text clear and legible.

The next phase of the 4030 show mapping application has rotated the satellite image clockwise to animate the satellite imagery. In the next stage 4035, the mapping application is using the building The 3D animated view cross-fades satellite imagery because the mapping application has enough information (for example, from a map server or other source of data) to display a 3D animated view of the building.

In the next stage, the 4040 shows that the virtual camera for the 3D animated view has been moved to the other side of the "MyWork Building". As shown, the black corner of the building now appears in the east of the media display area 3835 to show that the virtual camera has moved counterclockwise relative to the top of the building. Also, because the viewpoint of the virtual camera has changed, different neighboring buildings are displayed behind the information text, as shown.

Figure 41 conceptually illustrates the GUI 3800. In particular, Figure 41 illustrates, in six different stages 4105 through 4130, when the image of the POI is more meaningful to the user and contains more information, the mapping application of some embodiments is initially in the media display area 3835 of the GUI 3800. The image of the POI is displayed instead of the animated image of the building. For example, when the selected POI is a commercial establishment (eg, a restaurant or a coffee shop), the mapping application determines the appropriate image to display based on the user's expectations. For example, the mapping application can display images of food and beverages available in restaurants or display images of interiors of coffee shops, as such images may be more external than images showing the buildings in which the businesses are located. Meet user expectations.

The first stage 4105 and the second stage 4110 are similar to stages 3805 and 3810, respectively, wherein the mapping application displays a collection of POIs from which the user can select a POI. The second stage 4110 shows the user selecting "Little Coffee Shop".

In the third phase 4115, the GUI 3800 has been started. However, in contrast to stages 3810 and 4025 described above with reference to Figures 38 and 40, the mapping application displays a collection of images (e.g., images of coffee, donuts, etc.) rather than images of buildings. . As described above, such images are collected by an information gathering entity such as Facebook, Twitter, etc., and the mapping application obtains information about the selected POI from the entities.

As also mentioned above, the mapping application of different embodiments uses different techniques to Display images. In this example, the mapping application is using the Ken Burns effect to display the images sequentially. At this stage 4115, the mapping application displays an image of one cup of coffee and a piece of muffin provided by Little Coffee Shop (assuming that the owner of the image or the owner of the store uploaded the image to an information collection entity such as Yelp) .

The next stage, the 4120 show mapping application, has zoomed in on this cup of coffee and muffin as part of the image display using the Ken Burns effect. The next phase of the 4125 show mapping application is using the internal image of the Little Coffee Shop to cross-fade the imagery of coffee and muffins. The next stage, the 4130 show map drawing application, has fully magnified the internal image.

Figure 42 conceptually illustrates a procedure 4200 performed by some embodiments for displaying different types of images when launching a "details information screen" for displaying detailed information about the POI. In particular, program 4200 is executed for displaying media in a media display area of the detailed information screen (e.g., media display area 3835 shown above with reference to Figures 38, 40, and 41). In some embodiments, the program 4200 is executed by a mapping application. The program begins when the mapping application displays the results of a search query.

Program 4200 begins by receiving (at 4205) the selection of the POI. Program 4200 receives the selection in one of several different manners. For example, program 4200 receives the selection when the user selects one of the banners displayed above the pushpin displayed on the POI (the user wishes to find more information about the POI). The program 4200 can also receive the selection when the user selects one of the POIs from a list of POIs displayed by the mapping application of some embodiments when the user selects a "list" button.

Program 4200 next determines (at 4210) a preferred order for displaying different types of images. As mentioned above, the mapping application of some embodiments displays different types of images. In some embodiments, the different types of images include images for animated 3D views, satellite images, general map images, and commercial related images (eg, served dishes) Images, images of interior layouts, images of employees of merchants, etc.).

In some embodiments, the program 4200 determines a preferred order based on the type of POI selected. For example, when the POI is a merchant such as a restaurant, the program 4200 prefers to display images of dishes that can be served by the restaurant. When the POI is a famous landmark such as the Empire State Building, the program 4200 prefers to display an image of the building and its surroundings. The program 4200 analyzes the data of the selected POI to determine the type of the POI when determining the preferred order.

There are also images of different levels for a particular type of image. For example, for landmark images, images of different levels include animated 3D images, satellite images, general map images, and the like. These different image levels will contain different amounts of data, and therefore it takes a different amount of time to retrieve the data via the network. For example, an animated 3D image will likely contain the largest amount of data and thus it takes the longest time to download the images from the source of the data via the network.

The program 4200 then determines (at 4215) whether the material for the image of the current level is available from the source. In some embodiments, the program 4200 obtains data from a map server or other server that is one of the servo data upon receiving a request. However, not every POI has an image of each level in the server. For example, a building that is not well known or well known will likely not have imagery for displaying a 3D animated view of the building. In some embodiments, the current level of the image to be initially displayed is preset to a 3D animated image level.

When the program 4200 determines (at 4215) that the data for the image of the current level is not available, the program 4200 selects (at 4220) the image of the next level to be displayed for the POI. For example, when an image for an animated 3D view of the selected POI is not available, the program 4200 selects (at 4220) the satellite image of the POI. The program 4200 then loops back to 4215 to determine if the material for the next level of image is available.

When the program 4200 determines (at 4215) that the data for displaying the image of the current level is available, the program 4200 determines (at 4225) whether all of the data has been received and the mapping Whether the application is ready to display images of the current level. In some cases, when the local rendering application is executed with a slow network connection to obtain image data from the remote server, there may not be enough image material to display the current level of the POI.

When the program 4200 determines (at 4225) that sufficient material has been obtained for displaying the image of the current level, the process 4200 continues to 4230, which is further described below. When the program 4200 determines (at 4225) that the data for displaying the image of the current level is not available, the program 4200 displays (at 4235) the image of the next level that is ready for display. That is, the program 4200 displays (at 4235) one of the images of the next level that sufficient data has been obtained for the images. When there is no sufficient data for displaying the images in the next level of image, the program 4200 displays the normal background image (a black image) in the media display area.

The program 4200 then determines (at 4240) whether the mapping application has obtained sufficient material for the image of the current level. For example, when the program 4200 displays a satellite image of the POI in the media display area, the program 4200 checks if sufficient material for the animated 3D view has been obtained. When the program 4200 determines (at 4240) that the data for the image of the current level has been insufficient, the program loops back to 4235 and continues to the media while checking whether the data for the image of the current level is ready. The image of the next level is displayed in the display area.

When the program 4200 determines (at 4240) that sufficient material has been obtained for the image of the current level, the program switches (at 4245) the image of the next level being displayed in the media display area to the image of the current level. For example, when the data for the 3D animated view is being displayed for display while the satellite image of the POI is being displayed, the program 4200 switches from the satellite image of the POI to the animated 3D view of the POI. Different embodiments use different techniques for this switching. For example, the program 4200 can apply the Ken Burns effect to make a transition from an image of the next level to an image of the current level. Program 4200 next displays (at 4230) the image of the current level. The program 4200 then ends.

Figure 43 conceptually illustrates the GUI 3800. In particular, Figure 43 illustrates, in four different stages 4305 through 4320, that the index tab 3840 has not been scrolled away from the "detailed information screen" of the selected POI (i.e., GUI 3800). In some embodiments, the GUI 3800 is scrollable. That is, components of GUI 3800, such as media display area 3835, table 3840, and information display area 3845, move up or down as the user scrolls up or down GUI 3800.

As noted above, the index tag 3840 is used to display index tags for different sets of input items grouped for different types of information associated with different index tags. That is, some embodiments of the mapping application obtain POI-related material from different data collection entities (eg, tweets from Facebook, Yelp, Yahoo, Twitter, blogs, etc., RSS feeds, updates), and are based on data. The type of data contained in the data is classified into different groups. For example, the mapping application classifies the data segments carrying the comments about the POI into a "comment" group, and displays the data segments as the information display area 3845 when the user selects the "comment" index tab. Inputs. Different embodiments use different techniques to identify the type of information that a piece of data is carrying. For example, the mapping application looks for a set of keywords in the data section.

Examples of index tags that a user may create or map an application may additionally provide include "activities" or "events" index tags that, when selected, will include any time correlation with respect to the POI News. For example, if the selected POI is a Major League ballpark, the entry under this index tab may include information about the scheduled game of the team associated with the pitch. As another example, when the selected POI is a movie theater, the selection of the input item enables the mapping application to launch a ticketing application (eg, Fandango), which the user can use to purchase the movie in the movie theater. Ticket for the movie. Those of ordinary skill in the art will recognize that many other possible index tags having various functionalities corresponding to the type of index tag can be created.

In some embodiments, the mapping application allows the user to create a new group by defining a mapping application to filter a number of keywords of the obtained data segment. group. In such embodiments, the mapping application adds a new index tag for one of the new groups, and lists the data segments including the keywords when the new index tag is selected. When the mapping application includes a limited number of index labels that can be displayed for one of the POI details information screens, the mapping application of some embodiments enables the index labels 3840 to be scrolled (eg, horizontally) for use The index tags 3840 can be scrolled and any desired index tags can be selected. The mapping application of some embodiments also allows the user to remove unwanted index tags.

As described above, the GUI 3800 can be scrolled in the vertical direction. However, regardless of how the user scrolls through the GUI 3800, the index tabs 3840 will not be scrolled away from the screen of the device. That is, for example, when the GUI 3800 is scrolled up such that the index tabs 3840 would otherwise leave the screen, the mapping application of some embodiments keeps the index tabs 3840 within the screen display area and displays the information. Area 3845 slides under index tab 3840.

An example operation of the GUI 3800 when the user scrolls the GUI 3800 is described by referring to the four stages 4305 to 4320 of FIG. The first stage 4305 shows a GUI 3800 that is launched after the user selects the map for the "Little Coffee Shop" pin and banner or selects the POI from the list of POIs.

The second stage 4310 shows the user making an upward swiping gesture from one of the directions of the GUI 3800. The third stage 4315 shows that the media display area 3835, the index tab 3840, and the information display area 3845 have moved up within the screen. In particular, the media display area 3835 has almost completely scrolled away from the screen, appearing to have slid under the top column 3850. The mapping application has also extended the information display area 3845 to display more entries for the selected information index tab. The user is also performing another upward dialing gesture (or continuing the initial up toggle gesture with or without a pause) to further scroll up the GUI 3800.

The fourth stage 4315 shows that the index tabs 3840 have moved up to the top of the top row 3850 and the user moves the GUI 3800 up further. However, these index labels The 3840 neither leaves nor slides under the top column 3850. The mapping application has also stopped expanding the information display area 3845. As the user further scrolls up the GUI 3800, the mapping application causes the input items displayed in the information display area 3845 to be slid under the index tab 3840 and the top column 3850 and further undisplayed in the information display area 3845. Multiple entries appear from the bottom of the information display area 3845, as shown in the fourth stage 4320.

The fourth stage 4320 also illustrates that the mapping application of some embodiments displays a set of selectable UI items 4360 through 4380. UI Project 4360 is used to show guidance from current orientation to POI. UI Project 4365 is used to show guidance from the POI to the current orientation. UI Project 4370 is used to add this POI to the contact list of the mapping application. UI project 4375 is used to share this POI with other mapping applications for other devices for other users. UI item 4380 is used to add this POI as a bookmark.

Figure 44 conceptually illustrates the GUI 3800. In particular, FIG. 44 illustrates four different stages 4405 through 4420 of a mapping application of some embodiments for launching a third party application when a user selects an entry displayed in the information display area 3845.

In some embodiments, the mapping application launches a third party application when an input item is selected from a list of one of the inputs displayed when one of the "Detailed Information Screen" tabs for a selected POI is selected. Or open the third party's website in one of the browser applications executed on the device where the mapping application is executed. This third-party application is usually the source of the selected input (for example, Yelp). For example, when the user taps on one of the comments displayed in the information display area 3845, the mapping application of some embodiments launches the third party application (eg, a Yelp application) to display the selected comment. All text or allow users to add new comments. In such embodiments, the mapping application will also provide the means for the user to return to the "Detailed Information Screen" (eg, GUI 3800) for the POI. For example, the mapping application can display a "previous page" button in the top column for third-party applications. When selected, it will be redisplayed on the "Detail Information Screen" of the POI.

In other embodiments, the mapping application does not launch a third party application when an entry is selected from the list of entries. The mapping application will change to "in-place" to display the information associated with this entry. That is, for example, the mapping application can expand the entry in the information display area 3845 and display the full comment or provide a means to add a new comment without leaving the mapping application. The mapping application of these embodiments will utilize an application programming interface (API) to request and obtain complete comments from the source. In some embodiments, the API is provided by a source (eg, Yelp).

The first stage 4405 of FIG. 44 illustrates the user selecting the comment index tab 4450. In the second stage 4410, the mapping application displays a number of comments related to Little Coffee Shop upon receiving the selection. As shown, these comments originate from different sources such as Twitter, Facebook, Yelp, and the like. In some embodiments, each comment entry includes a limited amount of information. The mapping application of some of these embodiments allows a user to view a full review when selecting a particular entry.

The second stage 4410 displays the user's list of comments selection comments 4455 displayed in the information display area 3845. In this example, as shown, the comment 4455 is derived from Yelp. The third stage 4415 shows that the mapping application has launched the Yelp application. The Yelp app displays the entire contents of the comment 4455. The top column 4460 of the page includes a "Previous Page" button that, when selected, causes the mapping application to again display the "Review" index tab via the selected GUI 3800. The third stage 4415 also shows that the user selects the "previous page" button. The fourth stage 4420 shows the GUI 3800 displayed again. This stage shows the same GUI 3800 as the GUI 3800 at stage 4410.

Figure 45 conceptually illustrates the GUI 3800. In particular, Figure 45 illustrates four different stages 4505 through 4520 of a mapping application of some embodiments for launching a third party application when a user selects a UI project for a third party application.

The first stage 4505 illustrates that the user selects the comment index tab 4550 when the information index tab 4555 is the currently selected index tab. In a second stage 4510, the mapping application displays a comment related to Little Coffee Shop in response to receiving a selection of a review index tag. As shown, each comment entry includes a thumbnail image of the person, a star rating of the person, etc., the date the comment was uploaded, and a comment (depicted as a line). These comments originate from different sources such as Twitter, Facebook, Yelp, etc. The second stage 4510 also indicates that the user is scrolling up the GUI 3800.

The third stage 4515 illustrates that the mapping application of some embodiments displays a set of selectable UI items 4560 through 4575 near the bottom of the extended information display area 4545 as the GUI 3800 is scrolled up. The UI Project 4560 is used to launch a third party application (eg, Yelp's mobile application) or a website (eg, Yelp's website) to view more comments about the POI. UI project 4565 is used to launch another third party application (eg, Facebook's mobile application) or a website (eg, Facebook's website) to trigger special features provided by the third party application (eg, signing in from Facebook ( Check-in)). UI project 4570 is used to add quick tips. In some embodiments, the quick reminder is that the mapping application does not have to rely on a third type of application (ie, without having to go through the third party application or website). UI project 4575 is used to add comments. In some embodiments, the selection of UI item 4575 causes the mapping application to launch a third party application or a website to leave a comment. The third phase 4515 also shows the choice of UI project 4560.

The fourth stage 4520 describes a third party application that allows the user to add comments about the POI (eg, Yelp's mobile application).

In some embodiments, the information provided by a third party application (eg, Yelp) may be different for different users based on the user's personal preferences for a particular third party application. In order to determine a preference setting for a particular user, the mapping application communicates with the third party application to determine the user's preference settings and captures the user's preferences Information produced. In some embodiments, in order to display personalized information from a user of a third party application, the user must install the third party application on the same device that the user uses to execute the mapping application. In addition, in some embodiments, the user must also currently log in to a third party application. For example, the user must download the Yelp application to the same device that the user uses to execute the mapping application, and the user must log in to the Yelp application when accessing the Yelp feature from the mapping application. If the user satisfies these conditions, the specific information about the POI that will be displayed to the user using the mapping application will be tailored to the user's personal preferences. Therefore, different users will see different information about the POI based on the user's personal preferences.

In order to apply preferences for specific users, mapping applications and third-party applications must first verify certain information. The mapping application initially authenticates to the third party application that the user is currently logged into the third party application. After verifying that the user is currently logged into the application, the mapping application forwards the data related to the particular POI of the user's interest (eg, the identification of a particular POI) to the third party application. The third-party application retrieves information about the POI of a particular user and passes the information back to the mapping application. In some embodiments, the mapping application then displays "in-place" information to the user based on the user's preferences (eg, does not transfer to a third-party application).

In some embodiments, the mapping application obtains authentication information (eg, tokens) from a third party application. The mapping application uses this token to access a server that provides information about the POI to a third-party application. For example, the Yelp application has been authenticated and authorized to access the Yelp server. The mapping application can then be authorized to access the Yelp server by using authentication information obtained from a Yelp application executing on the same device. In such embodiments, the server maintains the user's personal preferences such that the local mapping application requires information about the POI (eg, comments). At the time, the server returns information that matches the user's preferences. In other embodiments, the user is not required to be logged into a third party application. In these embodiments, the mapping application allows the user to log in directly to the server via the mapping application.

Figure 46 illustrates two mapping application execution entities executing on two different devices of two different users 4601 and 4602 (users not shown), the two execution individuals exhibiting the two different Two different sets of information about the same POI obtained by a particular third-party application executing on the device. Figure 46 illustrates the mapping application for each user in three stages 4605 through 4615.

During the first phase 4605, two users are viewing the map view of the mapping application. Both users have used the search bar to search for "Little Coffee Shop". The two users also select arrows (not shown, blocked by the fingers 4603 and 4604 of the users 4601 and 4602, respectively) to activate the detailed information screen of the POI. In the second phase 4610, the GUI 3800 has been launched. As shown, the mapping application displays various information about the POI, including address, phone number, website URL, and user comments. Both users 4601 and 4602 also select the comment index tab 4550 to obtain information about the user reviews of the coffee shop.

In a third stage 4615, the GUI 3800 presents comments obtained from a third party application (eg, Yelp). However, the displayed user comments are different for the two users 4601 and 4602 because the comments are based on the user's personal preferences. The first user sees three comments by Jane, Bo, and Sue, while the second user sees comments from Jon, Brad, and Nat. This can occur when users 4601 and 4602 have specified different personal preferences for a particular third party application. The first user 4601 can indicate to the third party application (i.e., Yelp in this example) that the user 4601 only wants to see the comments made by the "food expert" and thus displays comments from experts Jane, Bo, and Sue. . The second user 4602 may have indicated that the user 4602 would like to see comments from each individual, and thus display Jon, Brad, and Nat from potential experts and not experts. comment. Thus, each user obtains information about a particular POI from a third party application that is customized and tailored to the user's personal preferences.

Figure 47 conceptually illustrates the GUI 3800. In particular, Figure 47 illustrates, in three different stages 4705 to 4715, the mapping application of some embodiments displays one of the index labels on an index tab for the selected POI of the selected POI, and when the flag is selected Display a specific piece of information.

In some embodiments, the mapping application displays one of the tags on one of the index tabs of the GUI 3800 to indicate that one of the entries will be displayed to include special information about the POI when the index tag is selected. For example, the tag may have a "deal" tag for the display POI, and the information about the offer may be included in one of the inputs that are displayed when the tag or the index tag of the tag is selected. Among them. Thus, the tag acts as an unread token indicating that there are entries that have not been viewed by the user since the input was obtained from the respective source of the entry.

The first stage 4705 shows the GUI 3800. The comment index tag 4450 has a tag 4750 attached to the index tag. In some embodiments, when there is an entry that includes information about the offer for the POI, the tag 4750 appears on the index tab 4450. The mapping application of different embodiments uses tags of different appearances. For example, in some embodiments, the tag is similar to an entity tag that can be attached to one of the files. The indicia also includes one or more dollar signs to indicate that the POI provides a saving offer to its customers.

The next stage 4710 displays the selection of the marker 4750 (eg, by tapping). The third stage 4715 shows that the mark has disappeared from the index tab 4450 and the offer of the offer is displayed in the information display area 3845. In some embodiments, the mapping application instead launches a third party application or opens a third party website in a browser application executed by the mapping application executing on the device. The third-party application or web page will then display the details of the offer for the selected POI.

Figure 48 conceptually illustrates the device 4820 shown in a relatively large display area. An example of a "details screen" (for example, GUI 3800) of the POI in the display area. An example of such a device is a tablet device (eg, an iPad® sold by Apple Inc.). In particular, Figure 48 illustrates the interaction of a user for displaying a "Detailed Information Screen" for a particular POI with a mapping application in three different stages 4805 through 4815. As illustrated, device 4820 provides a larger screen display area 4825 for viewing map rendering than a device having a relatively small display area (eg, a smart phone such as the iPhone® sold by Apple Inc.). application. The larger display area allows the mapping application to efficiently utilize the screen space to display different GUIs within the same map view and minimize switching to different GUI images. In detail, when the user selects the arrow for a specific POI, the mapping application opens the "Detailed Information Screen" for the POI directly overlaid on the map view of the mapping application without changing to a new one. GUI page.

In the first stage 4805, the mapping application displays a pin 4830 and a banner 4835. This banner allows users to type in the results of a search query for "Little Coffee Shop". The second stage 4810 illustrates the user selecting arrow 3875 to launch the "Details Info Screen" for this POI. In the third stage 4815, the mapping application has launched GUI 3800 for the detailed information screen. The GUI 3800 is fully displayed in the map view of the mapping application. In some embodiments, the mapping application completely displays the "Detailed Information Screen" for a particular POI when the user is viewing the mapping application in portrait orientation. In some embodiments, when the user views the mapping application on the horizontally oriented tablet, the mapping application displays the "Detailed Information Screen" for the POI, but may require the user to scroll through the "Detailed Information Screen". To view all the information.

IV. Route generation

As mentioned above, the mapping application closely integrates the search and route identification experience by providing a number of different ways to obtain guidance. One way is to select a UI control item (eg, a button) via one of the main map views (eg, in the upper left corner), the UI control The item, when selected, presents a modal interface for editing the guide and enables the user to request more customized routes, such as routes or walking routes that are not starting from the current orientation, rather than just driving the route.

In some embodiments, the mapping application allows the user to check for such customized routes by sliding the display of the driving control instructions into and out of the UI page of the display route. This mode of operation of the mapping application is referred to as a route inspection mode or a (manual) stepping mode, which is one of several operational modes by which the mapping application of some embodiments can operate. Examples of such modes of operation include a navigation mode, a map browsing mode, and a route inspection mode.

The junction is where two or more road sections meet. The route between the starting position and the destination position in the route map. A typical route has zero or many joints along the path between the two orientations. The driving command for the joint in the route identifies the direction of the road segment from the junction. In some embodiments, the mapping application provides the user with driving instructions for only some of the joints along the route, as the user may not need to be in each of the routes in order to reach the destination orientation. Perform driving control at the joint. For example, the user of the carrying device can recognize that the user only needs to go straight through several joints before reaching the joint to be turned to reach the destination orientation. In this patent application, when a joint has a driving command to be displayed, the driving command is referred to as a "step."

In navigation mode, the mapping application of some embodiments provides the user with a collection of steps for a route between the current orientation of the device and a destination orientation. Typically, the mapping application provides these steps to the user visually and with audio in navigation mode. When the user carrying the device deviates from the route, the mapping application of some embodiments tracks the orientation of the device and recalculates the new route from the offset orientation to redirect the user from the off orientation to the destination orientation. In other words, the mapping application of some embodiments operating in the navigation mode requires the device to always be on the route. Again, in The mapping application of some embodiments of the navigation mode operation displays the steps by a "fast display" step instead of sliding the steps in and out of the display area. Moreover, in some embodiments, the information in the steps displayed by the mapping application (ie, the driver control instructions) is dynamic when operating in the navigation mode. That is, as the device moves along the route, information such as estimated arrival time, time remaining to the destination orientation, current orientation from the device to the destination orientation, or the remainder of the next step with the next step Distance, etc.) Updated by the mapping application.

In the route inspection mode, the mapping application of some embodiments allows the user to slide the steps in and out of the display area to check each step in the route. Alternatively, the mapping application allows the user to manipulate the map (eg, by zooming in and out, sliding the map in different directions) to display different joints in the route. When a joint having one step is displayed in the display area as a result of the user's manipulation of the map, the mapping application slides the step in (and the previously displayed steps are currently displayed) This step is shown by any intermediate steps between steps sliding in and out. In this manner, the user can check the route by manually sliding the steps into and out of the display area or by manipulating the map to display certain joints of the route in the display area.

A. Route start and search

Figure 49 illustrates an example of interaction between a user using a route selection guide and a mapping application in accordance with four stages 4905 through 4920. Specifically, this figure illustrates the mapping application starting to operate in route inspection mode. The first stage 4905 illustrates the device after the user has selected the steering control item 160 (not shown in this figure). The first stage 4905 also illustrates that the user has entered the start and end directions of the route in the start field 245 and the end field 250.

The second stage 4910 illustrates the selection of the route generation control item 240. In some embodiments, when selecting a route generation control item, the mapping application sends start and end position information to a remote server to obtain a route. The third stage, 4915, shows two routes. Route 1 and Route 2, in some embodiments, the mapping application visualizes the two routes on the map based on route information obtained from the remote server. The third stage 4915 also states that the mapping application has selected route 1 by default. The user selects the start control item 4950 for starting navigation according to the selected route. The mapping application of some embodiments begins operating in the route check mode upon receiving a selection of the start control item 4950.

The fourth stage 4920 illustrates the mapping application display instruction flag 4930. In some embodiments, the instruction flag 4930 is used to browse a series of selected directions to the prompting instruction flag (the instruction flags are not all illustrated in the figure) The first sign in the middle. The mapping application allows the user to navigate through the selected route by sliding the markers along a particular axis (eg, horizontally). These scrollable instruction flags are described in more detail below. In some embodiments, the mapping application allows the user to browse the selected route when the starting orientation of the selected route is not the current orientation of the user. Again, when the local mapping application is in this mode for allowing the user to view or check the selected route (as shown in stage 4920), some embodiments of the mapping application disable page curling or not displaying the page. curly.

In addition to typing the start and end orientations of the route in the start field 245 and the end field 250, the mapping application of some embodiments also allows the user to select a route from a list of previously searched routes. Figure 50 illustrates an example of interaction between a user using a route selection guide and a mapping application in accordance with four stages 5005 through 5020. This example is provided in the context of the use of the guidance control 160 to obtain a route between two orientations.

The first stage 5005 illustrates a mapping application that displays a map of the street views of the city. The user is initiating a touch of the pointing control item 160 located at the upper left corner of the display next to the search field 165. The second stage 5010 next illustrates the application presenting a lookup table 5055 with a list of recent directions that the user has previously searched for. In this example, as shown, the user selects a route to the police station.

The third stage 5015 illustrates displaying a map of the selected route having the current orientation of the device to the destination of the selected route. This stage 5015 also illustrates the selection of the list view control item 235. The fourth stage 5020 illustrates a list of one of the steering prompt instructions that the mapping application presents to reach the destination. As shown, each instruction in the list includes a direction icon 5035 that shows the direction of the particular steering associated with the instruction. In some embodiments, each instruction in the list appears to be identical to the corresponding instruction flag 4935 described above with reference to FIG.

Figure 51 conceptually illustrates an example of displaying route selection guidelines in a relatively large display area of the device. An example of such a device is a tablet device (eg, an iPad® sold by Apple Inc.). Specifically, Figure 51 illustrates the interaction of the user to display a set of route selection guidelines with the mapping application at three different stages 5105 through 5115. As illustrated, the device provides a larger screen display area for viewing the mapping application when compared to the display area of a smaller device (eg, a smart phone such as the iPhone® sold by Apple Inc.) . The larger display area allows the mapping application to efficiently utilize the screen space to display different UI items within the map view of the mapping application and minimize changes to the UI picture. For example, when the user selects a list of the route selection guides, the mapping application displays the list of route selection guides that are directly overlaid on the map without changing to a different UI screen.

The first stage 5105 illustrates a tablet device 5120 that executes a mapping application of some embodiments that is displaying a map view of a particular route between two orientations. In particular, the user has obtained a route between the current orientation of the user and the orientation of the POI "Pizza Place". The user may have obtained this route in several ways, including searching for features, placing pushpins on the map, and various other mechanisms. The mapping application is also displaying a collection of floating controls including the list view control item 145.

The second stage 5110 shows that the user is selecting the list view control item 145 to obtain a list of route selection guidelines. The third stage 5115 indicates that the mapping application is now displayed. A list of route selection guidelines that are superimposed on one of the map views of the mapping application.

In some embodiments, when the user selects an individual route selection guide from the list of route selection guidelines, the mapping application displays a corresponding portion of the route associated with the selected route selection guide on the map. If the corresponding portion of the route is not within the currently displayed map area, the mapping application shifts the map so that the area containing the map of the corresponding portion is displayed.

B. Route display and review

In some embodiments, when the mapping application presents the identified route to the user, the application allows the user to select and scroll through a collection of selectable UI items that represent the sign along the junction of the selected route. . As the user scrolls through each of the markers, the portion of the route associated with the marker currently in focus is presented or highlighted (eg, via a color eye-catching prompt or via another geometry that marks the portion (eg, Circle or other mark)). This mode of operation of the mapping application of some embodiments is referred to as a route inspection mode. The mapping application operating in this mode allows the user to inspect the road by manipulating UI items that represent the mandatory signs of some of the joints of the route. In some embodiments, (1) when the route being inspected is between two orientations (both of which are not the current orientation of the device on which the mapping application is executed), and (2) when the route is targeted The mapping application operates in the route inspection mode when calculated by walking (not driving).

Figure 52 illustrates one example of a route check mode in accordance with four stages 5205 through 5220 of a set of scrollable command flags that a user scrolls through a particular route selected by the user. The first stage 5205 illustrates that the user initiates a selected route between the start and end directions by touching the start control in the top column 140. As described above, the second stage 5210 illustrates the first scrollable flag 5225 (a selectable UI item) presented for a particular route, as indicated by the "1 of 1" text displayed at the center of the top column 140. Again, map The drawing application is displaying the current juncture indicator 5290 at the juncture indicated by the displayed flag 5225. Further details regarding the current joint point indicator are described in U.S. Patent Application Serial No. 13/632,002, filed on Sep. U.S. Patent Application Serial No. 13/632,002 is incorporated herein by reference. The second stage 5210 also illustrates the user's initial leftward toggle action on the first scrollable marker. The toggle gesture causes the marker to shift to the left of the map. In some embodiments, the user can touch the flag to shift it to the left (or right) of the map and display the next flag.

The third stage 5215 illustrates that a portion of the first scrollable flag 5225 has been scrolled away from the map display area and one of the new marks 5235 for the route has become partially visible. The user can see that the new logo shows a right turn arrow. The mapping application has not moved the current juncture indicator 5290 because the flag 5225 is still the current flag.

The fourth stage 5220 illustrates the display after the user has completed the toggle action to cause the first marker to leave the map. The mapping application now displays a second flag 5235 of the list of routing instructions as indicated by the "2 of 2" text displayed at the top column 140. This sign indicates that after 0.1 miles, the user needs to turn right into the 7th street. In addition, the application has zoomed in on one portion of the map display area and highlighted the new section 5250 of the route corresponding to the flag currently being rendered in focus. The application has also moved the current joint indicator 5290 to the joint indicated by the second flag 5235.

Alternatively or in combination, the user can view a particular scrollable point associated with a particular joint by selecting a different joint of the route (eg, by tapping) or navigating the map (via a gesture input) The logo to scroll through each logo. Figure 53 illustrates the user navigation map to scroll through different scrollable markers in accordance with three stages 5305 through 5315.

The first stage 5305 illustrates a map with overlaid signs (corresponding to the "2 of 2" sign in the route) for a particular joint of the route between the start point and the end point. The application has also highlighted the corresponding part of the route for this flag. The sign is stated at 0.1 After miles, the user needs to turn right into the 7th street. The first stage 5305 also illustrates that the user initiates a toggle gesture for navigating the map (eg, swiping the user's finger to the right) to view a different area of the map.

The second stage 5310 illustrates a new zone of the map displayed after the toggle gesture corresponding to the shift to the left. The third stage 5315 illustrates that after the completed toggle gesture, a new scrollable marker is now overlaid on the map, corresponding to the portion of the route that is now displayed in that particular area of the map. This mark is the third mark in the route, as indicated by the "3 of 3" text displayed at the top center of the map. This sign indicates that after 350 feet, the user will arrive at the destination.

To navigate a collection of route selection guidelines, the user has the option of scrolling through the markers overlaying the map or navigating the map to scroll through the different markers. Also, when the user touches a particular segment of the route, the mapping application scrolls through the different markers to display one of the particular segments corresponding to the route. In some embodiments, the mapping application displays a logo for the point of engagement of one of the touched portions that is closest to the route.

This scrolling feature of the mapping application allows the user to quickly determine all necessary controls while traveling between the two orientations. This may be particularly useful in driving situations where it is expected that the upcoming turn will require a large number of lane changes.

In some embodiments, the directional arrows shown in the scrollable command flag are simple arrows. In other embodiments, when there is sufficient space on the logo or presentation for the use of the larger logo, the mapping application of some embodiments in the navigation mode identifies the edge to be used by using a larger graphical direction indicator Driving control performed at the junction of the route, the graphical direction indicator includes (1) a prominent stylized arrow roughly indicating the path of the vehicle, and (2) a line corresponding to other elements of the junction point that are not emphasized And a collection of curves. In some embodiments using this method, the right turn at the T-junction will be indicated by a large arrow with a right angle engaged with the smaller darker section, which is parallel to the large arrow One of the sections extends. In some embodiments, the smaller section is also pushed open to the side such that the path employed by the carrier is dominant. More details on these arrows are described in U.S. Patent Application Serial No. 13/632,121, filed on Sep. 30, 2012, entitled " Context-Aware Voice. U.S. Patent Application Serial No. 13/632, the disclosure of which is incorporated herein by reference. In some embodiments, the mapping application replaces the instructions with directional icons with seemingly realistic road traffic signs.

Figure 54 illustrates an example of displaying a set of scrollable instruction flags for a particular route selected by a user. The mapping application is executed by the device 5400 having a relatively large display area. An example of such a device is a tablet device (eg, iPad®). This figure illustrates the interaction of the user stepping through the command flags with the mapping application in two different stages 5405 and 5410.

When the mapping application is executing on a device with a large display area, the mapping application displays more flags in the display area at any given time. In some embodiments, the mapping application displays a list of markers in the top portion of the display area, with the current marker being in the middle of the top portion. The number of markers that the mapping application can display varies depending on the orientation of the device. That is, the mapping application can display more marks when the display area is in the landscape orientation than when the display area is in the portrait orientation.

The first stage 5405 shows that the mapping application is displaying one of the three markers 5415 to 5425 and the fourth marker 5430. In this example, flags 5415 through 5430 represent first through fourth instructions having a selected route of a total of six steps. As indicated by the top column 5435, the second command of the route is the current command, and the flag 5420 is highlighted and placed in the middle of the top portion of the display area to indicate that the flag 5420 is indicating the current command. The first stage 5405 also shows that the user is dialing the sign 5420 to the left.

The second stage 5410 shows that the mapping application is displaying a flag 5425 for the third instruction of the route in the middle of the top portion of the display area. In this example, map drawing The application has also highlighted the flag 5425, and the segment corresponding to the route of the flag is highlighted, as shown. The top column indicates the third of the six instructions for the current instruction. Again, most of the flag 5415 now slides out of the display area and the flag 5430 is now fully displayed. The mapping application is also displaying a portion of the fifth flag 5445, which represents the fifth instruction of the route.

The mapping application of some embodiments allows the user to switch to the overview mode when reviewing a selected route by scrolling the command flag. In the overview mode, the mapping application of some embodiments adjusts the zoom level of the map so that the full route can appear on the map. The mapping application also allows the user to return to the mode by which the user can continue to review the instructions. Figure 55 illustrates an example of user interaction with an application for switching to the overview mode when reviewing the selected route, in accordance with three stages 5505 through 5515.

The first stage 5505 is identical to the stage 5315 described above with reference to FIG. That is, the user has scrolled to the last instruction flag 5520. The next stage 5510 illustrates the selection of the overview control item 5525.

The third stage 5515 illustrates the map in the overview mode. The mapping application of some embodiments, in response to receiving the selection of the overview control 5525, displays the map in the overview mode. The mapping app has zoomed out the map so that the full route is displayed on the map. In some cases, when the current orientation of the device is very close to the destination orientation (eg, within 100 meters), the mapping application only displays portions of the route from the current orientation of the device to the destination orientation.

Again, the top column 5530 shows the destination (in this example, the police station) 7 minutes away or 0.5 miles from the current orientation of the device or the starting orientation of this particular route. The top column 5530 now includes a continuation control item 5540 that, in some embodiments, is used to continue navigation or inspection of the selected route. The mapping application also displays the list view control item 235 in the map.

The top column 5530 also shows an end control item 5570. Drawing application is showing up When an overview of the selected route is displayed, the local mapping application receives the selection of the end control item 5570, and the mapping application of some embodiments stops checking the selected route by returning to the map browsing mode. The mapping application of some embodiments returns to the map browsing mode by: removing the selected route from the map; putting back the page curl; using other controls including the guide control, the search field, and the bookmark control. A collection replaces the information and controls in the top column. The mapping application of some embodiments does not shift the map to another zone when switching from the check mode to the map browsing mode. The mapping application of some embodiments leaves a pin in the map for the start and end orientations when the mapping application enters the map browsing mode.

Figure 56 conceptually illustrates a procedure 5600 performed by some embodiments to allow a user to view a logo for a set of instructions for a joint in a route between a starting orientation and an ending orientation. In some embodiments, the program 5600 is executed by a mapping application. The program 5600 begins when the mapping application has calculated one or more routes between the starting and ending directions.

Program 5600 begins by receiving (at 5605) the selection of the route. As shown in Figure 49 above, the mapping application of some embodiments provides a recommended route when there are two or more generated routes between the starting orientation and the ending orientation. When the user does not select another route, the mapping application will use the recommended route as the selected route upon receiving a selection of a start control item, such as start control item 4950.

Next, the program 5600 receives (at 5610) one of the user inputs for initiating the browsing mode. In some embodiments, the mapping application enters the browsing mode when the user selects a start control item, such as start control item 4950. At 5615, the program 5600 of some embodiments then displays one of the first joints (i.e., the starting orientation) for the route and the corresponding joint of the marker (i.e., the first joint) on the map.

The program 5600 then receives (at 5620) a user input. In some embodiments, the user input includes any gesture interaction with the mapping application. For example In other words, the user can zoom or toggle the map by touching one or more of the maps. The user can also touch, toggle, etc. the currently displayed logo.

The program 5600 then determines (at 5625) whether the user input is for moving the currently displayed logo. In some embodiments, when the user touches the currently displayed logo or toggles the currently displayed logo in a certain direction, routine 5600 determines that the user input is used to move the logo. When the program 5600 determines that the user input is not used to move the currently displayed logo, the routine 5600 continues to 5635, which is described further below.

When the program 5600 determines that the user input is used to move the currently displayed logo, the program 5600 displays (5630) an adjacent flag (if possible) based on the user input. For example, the program 5600 displays one or a previous flag for the next or previous joint in the route based on the user input. Program 5600 also displays the corresponding joints of the route. In some embodiments, the program 5600 can be scaled or shifted to another area of the map to display the corresponding joint of the logo being displayed. Program 5600 then loops back to 5620 to receive another user input.

When the program 5600 determines (at 5625) that the user input is not used to move the currently displayed flag, the routine 5600 determines (at 5635) whether the input is used to display a juncture that is different from the currently displayed juncture. In some embodiments, when the user manipulates the map (eg, toggle, zoom, etc.) to display another region of the map or when the user touches a portion of the route that is closer to another junction of the displayed route, The program determines that the input is used to display a joint. When the routine 5600 determines (at 5635) that the user input is not used to display another joint, the routine 5600 continues to 5645, which is further described below.

When the program 5600 determines (at 5635) that the user input is used to display another joint, the routine 5600 displays (at 5640) another joint and the corresponding mark of the joint. This flag may not be the adjacent flag of the currently displayed logo. Program 5600 then loops back to 5620 to receive another user input.

When the program 5600 determines (at 5635) that the user input is not used to display another joint At time, routine 5600 determines (at 5645) whether the user input is used to present an overview of the route. In some embodiments, when the local mapping application receives a selection of an overview control, program 5600 determines that the input is used to display an overview of the route. When the program 5600 determines (at 5645) that the user input is not used to present an overview of the route, the routine 5600 continues to 5670, which is further described below.

When the program 5600 determines (at 5645) that the user input is used to display an overview of the route, the program 5600 of some embodiments displays (at 5650) the full route in the map. The program also receives another user input while displaying an overview of the route. The program 5600 then determines (at 5655) whether the input is used to end the browsing mode. In some embodiments, when the local mapping application receives a selection of an end control item, such as the end control item 5570 described above with reference to FIG. 55, the program 5600 determines that the input is used to end browsing. mode. When the program 5600 determines (at 5655) that the user input is used to end the browsing mode, the program 5600 ends.

When the program 5600 determines (at 5655) that the user input is not used to end the browsing mode, the program determines (at 5660) whether the input is used to exit the overview of the route. In some embodiments, when the local mapping application receives a selection of a continuation control item, such as the continuation control item 5540 described above with reference to FIG. 55, the program 5600 determines that the input system is used to exit the overview. . .

When the program 5600 determines (at 5660) that the input is not used to exit the overview mode, the program loops back to 5650 to display the route and receive another user input. When the program 5600 determines (at 5660) that the input is used to exit the overview mode, the program exits the overview of the route and displays (at 5665) the flag and its corresponding joint before the presentation overview. The program then loops back to 5620 to receive another user input.

When the program 5600 determines (at 5645) that the input received (at 5620) is not an input for presenting an overview of the route, the routine 5600 determines (at 5670) whether the input is used to end the browsing mode. In some embodiments, the local drawing application receives a control over the end When the selection of the recipe is made, the program 5600 determines that the input is used to end the browsing mode. When the program 5600 determines (at 5670) that the user input is used to end the browsing mode, the program 5600 ends. Otherwise, the program then loops back to 5620 to receive another user input.

C. Navigation mode

Figure 57 illustrates an example of a device 5700 that performs a mapping application of some embodiments. This figure also shows an example of launching route navigation in this application. Figure 57 shows six phases 5705, 5710, 5715, 5717, 5719, and 5721 interacting with the mapping application. The first stage 5705 shows a UI 5720 that includes several icons of several applications in the docking area 5725 and on the pages of the UI. One of the illustrations on this page is an illustration of a mapping application 5730. The first stage shows the user selecting the mapping application by touching the screen of the device on the screen in the orientation of the application.

The second stage 5710 shows the device after the mapping application has been opened. As shown in this stage, the UI of the mapping application has a start page, in some embodiments, the start page (1) displays a map of the current orientation of the device, and (2) is configured in the top column 5740 and acts as a float. Several UI controls for the control.

The third stage 5715 of FIG. 57 illustrates the selection open guidance entry page 5780 for the guidance control item 5760, which is shown in the fourth stage 5717. The guidance control is one of three mechanisms through which the mapping application can be directed to identify and display a route between the two orientations; the other two institutions are (1) for the selected item in the map. One of the control items displayed in the information banner, and (2) a new route displayed by the device in the search field 5765. Therefore, the information banner control and the search field 5765 are two UI tools that the application uses to make the transition between different modalities smooth.

The fourth stage 5717 illustrates the user selecting one of the tables 5782 that is automatically populated in the recent guidance. The fifth stage 5719 then displays the three routes between the specified start and end directions specified via page 5780 on the 2D map view. This stage also shows the second The choice of route and some information about this route in one of the columns at the top of the layout. This column is shown to include start and end buttons. The start button is shown as being selected in the fifth stage.

As shown in the sixth stage 5721, the selection of the start button directs the application to enter the steering alert navigation mode. In this example, the application has entered the 2D Steering Navigation mode. In other embodiments, the application will enter the 3D Steering Navigation mode by default. In this mode, the application displays a realistic logo 5784 that identifies the distance to the next junction of the navigation route and some other relevant information. The application also displays a top column that includes some information about the navigation and an end and overview button that are used to end the navigation and to obtain the remainder of the navigation route or the entire portion of the navigation route (in other embodiments). Overview.

The application further displays the floating 3D control item 5750 and the floating list control item described above. It should be noted that the inventory control item is adaptively added to the floating control item cluster when entering the route inspection and route navigation modes, and the position indicator is removed from the floating control item when entering the route navigation mode. Also, in the transition from the route inspection mode to the route navigation mode, the application, in some embodiments, performs an animation that involves the page curl fully unfolding before the application transitions to the navigation presentation.

In some embodiments, the animation transition includes a self-navigation presentation removal top column, its associated control and floating control, and moving the marker 5784 to the top edge of the presentation after a short period of time after the navigation presentation is initiated. As further described below, in some embodiments, the application requires the user to tap on the navigation map to restore the top column, its controls, and the float controls, and ask another touch to remove the controls from the map again. item. Other embodiments provide other mechanisms for viewing and removing such controls.

The navigation application of some embodiments can display navigation in 2D mode or 3D mode. As described above, one of the floating control items is a 3D control item 5750 that allows a user to view the navigational presentation in three-dimensional space (3D). Figure 58 illustrates the navigation of some embodiments. The program provides a 3D control 150 as a fast mechanism for entering the 3D navigation mode. This figure illustrates this operation in three stages 5805 through 5815. The first stage 5805 illustrates the user selecting the 3D control item 150 while viewing the two-dimensional navigation presentation.

The second stage 5810 illustrates the navigational presentation in transitioning to a 3D rendering. As shown in this figure, the 3D control item appears as a prominent prompt at this stage to indicate that the navigation presentation has entered the 3D mode. As described above, in some embodiments, the navigation application generates a 3D view of the navigation map by presenting the map view from a particular location in the three-dimensional scene that is conceptually considered to be the location of the virtual camera that captured the map view. This manifestation will be further described below by referring to FIG.

The third stage 5815 then illustrates the navigational presentation at the end of the transition to a 3D look. As shown by the difference between the heights of the buildings in the second and third phases, in some embodiments, the transition from 2D to 3D navigation includes an animation that shows that the three-dimensional object in the navigation map becomes larger.

The navigation application of some embodiments is capable of displaying a navigation map from multiple perspectives. The application can display the map in three-dimensional (3D) or two-dimensional (2D). The 3D map is a simulation of the virtual scene seen by the virtual camera. Figure 59 presents a simplified example to illustrate the concept of virtual camera 5912. When a 3D navigation map is rendered, the virtual camera is conceptualized by the location in the 3D map scene from which the device visualizes the 3D view of the scene. Figure 59 illustrates the orientation of four objects in a 3D navigation map scene 5910 that includes two buildings and two intersecting roads. To illustrate the virtual camera concept, this figure illustrates three scenarios, each of which corresponds to a different virtual camera orientation (i.e., a different presentation position) and a different view displayed on the device.

The first stage 5901 shows a virtual camera 5912 pointing down to the 3D scene 5910 at an angle (eg, at an angle of 30 degrees to the horizon) at the first location. The application generates a 3D map view 5918 by presenting the 3D scene from the position and angle shown in stage 5901. From this position, the camera is pointed at one of the positions of a moving position in front of the system. Make a virtual photo Camera 5912 remains behind the current orientation of the device. In this case, "behind the current orientation" means backward along the defined path of the navigation application in the opposite direction to the current direction of device movement.

The navigation map view 5918 appears as if it were taken by the camera from the device's orientation indicator 5916. The orientation and angle of the virtual camera places the orientation indicator 5916 at the bottom of the proximity navigation map view 5918. This also results in a large portion of the picture being filled with streets and buildings in front of the current orientation of the device. In contrast, in some embodiments, the orientation indicator 5916 is at the center of the picture, with one half of the picture representing things in front of the device and the other half representing things behind the device.

The second stage 5902 shows a virtual camera 5912 pointing down to the scene 5910 at a second, larger angle (eg, -45°) at a different location. The application visualizes scene 5910 from this perspective, resulting in a 3D navigation map view 5928. Buildings and roads are smaller than their illustrations in the first navigation map view 5918. Again, virtual camera 5912 is located above scene orientation indicator 5916 in scene 5910. This again causes the position identifier to appear in the lower portion of the 3D map view 5928. The orientation and orientation of the camera again causes the majority of the picture to show that the person navigating needs to know what is in front of the car carrying the device.

The third stage 5903 shows the virtual camera 5912 from the top down view, which faces downwardly toward one of the orientations on the 2D map, which corresponds to the orientation in the 3D map scene 5910 used to visualize the 3D views 5918 and 5928. The scene that emerges from this perspective is the 2D map view 5938. Unlike the 3D rendering operations of the first and second stages, which in some embodiments are perspective 3D rendering operations, the rendering operations in the third phase are relatively simple, since the operation only requires cropping the application or user specified One part of the 2D map identified by the zoom level. Thus, the virtual camera representation in this case slightly unduly complicates the description of the operation of the application, since cutting a portion of the 2D map is not a perspective rendering operation.

In some embodiments, as further described below, the virtual camera can be moved by changing the zoom level for viewing the map after the map enters the 3D mode. In some of these embodiments, the application switches to generate a top-down mode of the 2D view when the zoom level reaches a particular zoom level (where the appearing position is straight down). As in the third stage 5903, in some embodiments, when the camera switches from the 3D perspective to the 2D top-down view, the mapping application switches from rendering the 3D scene from a particular perspective to cropping the 2D scene. This is because, in these embodiments, the application is designed to use a simplified rendering operation that is easier and does not create unnecessary perspective artifacts. However, in other embodiments, the mapping application uses a perspective rendering operation to visualize a 3D scene from a top-down virtual camera position. In such embodiments, the resulting 2D map view is slightly different from the map view 5938 illustrated in the third stage 5903 because any object that is far from the center of the view is distorted, with the object being farther from the center of the view. , the greater the distortion.

In various embodiments, virtual camera 5912 moves along different trajectories. Two such trajectories 5950 and 5955 are illustrated in FIG. In both of these trajectories, the camera moves in an arc and rotates more downward as the camera moves up on the arc. Track 5955 differs from track 5950 in that in track 5955, the camera moves backward from the current orientation as it moves up the arc.

When moving along one of the arcs, the camera rotates to maintain a point in front of the azimuth indicator at the focus of the camera. In some embodiments, the user can close the three-dimensional view and navigate purely with the two-dimensional view. For example, an application of some embodiments allows the 3D mode to be turned on and off by using the 3D button 5960. The 3D button 5960 is indispensable for the turn-by-turn navigation feature, which acts as an indicator and a toggle switch in the turn-by-turn navigation feature. When 3D is turned off, the camera will maintain a 2D navigation experience, but when 3D is turned on, there may still be some top-down when the 3D viewing angle is not appropriate (for example, when bypassing a corner that may be blocked in 3D mode) perspective.

As another way to allow the user to get a navigation experience, the mapping application of some embodiments provides a UI item in an information banner that appears next to the pin representing the POI. Figure 60 illustrates an example in accordance with three stages 6005 through 6015 of the interaction of the user with the mapping application to obtain routing instructions. This example is provided in the context of the use of car icon 6030.

The first stage 6005 illustrates the map in the 3D map view. As shown, the 3D control item 150 appears to be eye-catching to indicate that the map is in a 3D map view. The first stage 6005 also illustrates two information banners for the two push pins of the search resulting from performing a search with the displayed search query "Pizza". The user selects the car icon 6030. As noted above, the car icon 6030 is for displaying one or more routes to the orientation indicated by a pushpin, and the banner including the car icon 6030 is associated with the pushpin. The banner 6040, which includes the car icon 6030, also displays a brief description of the place, a star rating, and the arrow used to launch the "Detailed Information Screen" for the POI.

The second stage 6010 illustrates the mapping of some embodiments to the two routes, Route 1 and Route 2, shown in the previous stage 6005 for the selection of the car icon 6030. The user has selected route 1, as indicated by the banner 6050 of the eye-catching prompt. The user also selects the start control item 2060. As noted above, in some embodiments, the start control item 4950 is used to initiate navigation based on the selected route.

The third stage 6015 illustrates the mapping application display instruction flag 6060, which is used for the flag of the first instruction. The mapping application has replaced the clear control item 255 and the start control item 2060 with the end control item 5570 and the overview control item 6075 in the top column 140. The end control item 5570 is used to end the navigation of the route, and the overview control item 6075 is used to display the full route in the map view by adjusting the zoom level of the displayed map (if the adjustment zoom level is necessary to display the full route). In some embodiments, the mapping application displays the estimated arrival time, the amount of time it takes to reach the destination, and the remaining distance from the destination in the top column 140, as shown.

When the mapping application receives a selection of the end control item 5570 while the mapping application is operating in the route inspection mode, the mapping application of some embodiments stops the selected route by returning to the map browsing mode. Check. The mapping application of some embodiments returns to the map browsing mode by the following operations: removing the selected route from the map, putting the page curl back, using the navigation control, the search field, and the bookmark control. A collection of controls replaces the information and controls in the top column. That is, the mapping application causes the appearance of the UI page to return to a UI page similar to the UI page shown in the first stage 6005. The mapping application of some embodiments does not shift the map to another zone when switching from the check mode to the map browsing mode.

It should be noted that although the route history entry and fast route navigation controls in the search field do not perform actions that cannot be achieved with a selectable direction item, the two serve to make it easier to obtain the most general route. Important accelerator.

Some embodiments use a movie transition from a 2D map view to a 3D map view or vice versa. For example, when the local drawing application receives a selection of the 3D control 150 when displaying a starting position of one of the routes, the mapping application starts from the 2D map view and is used for one of the first virtual cameras of the 2D map. The view smoothly transitions to a new virtual camera 3D view that is placed larger and points in the direction of the beginning of the route. In this case, the virtual camera view performs a combination of panning, zooming, and rotating operations to reach the beginning of the route for navigation. That is, the virtual camera moves on the arc and rotates more upward as the camera moves down the arc. Again, the mapping application can rotate the arc itself to align the virtual camera viewpoint with the initial road segment of the route. In other words, the mapping application rotates the map during the movie transition.

Figure 61 illustrates a device 6100 that displays a mapping application as the application transitions from a non-immersive map view for map browsing to an immersive map view for navigation through six stages 6105 through 6130.

The first stage 6105 shows that the user selects the fast route of the position "Pizza Place". Button to generate a route from the user's current orientation (near the center of the screen of device 6100) to the selected orientation. The second stage 6110 illustrates that the mapping application displays route 6135 for reaching the location "Pizza Place." In the second phase 6110, the user selects the "Start" UI control item 6140. So the app starts to navigate.

As shown at the third through sixth stages 6115 through 6130, some embodiments use a movie transition from a 2D (or 3D) non-immersive map view to a 3D immersive map view. The application display begins with its current state (shown at 6110) and smoothly transitions from the first virtual camera view to the new virtual camera view, which is placed larger and points in the direction of the beginning of the route. In this case, the virtual camera can perform a combination of panning, zooming, and rotating operations to reach the beginning of the route for navigation. As shown in such stages, the virtual camera moves and rotates into its final orientation as shown in the sixth stage 6130, which is behind the navigation orientation indicator (ie, the locating disc).

V. Multi-mode mapping application

62A-62B conceptually illustrate a state diagram 6200 that depicts the different states of the integrated mapping, search and navigation application (eg, the applications described in the above sections) of some embodiments and the status of such states The transition between the two. Those of ordinary skill in the art will recognize that an application of some embodiments can have many different states associated with all of the different types of input events, and state diagram 6200 is particularly focused on a subset of such events. State diagram 6200 depicts and references various illustrative action interactions (e.g., multi-touch gestures) for changing the state of the application. Those skilled in the art will recognize that various other interactions (such as cursor controller gestures and button selection, keyboard input, trackpad/trackpad input, etc.) can also be used for similar selection operations.

When the user initially opens the mapping application, the application is in state 6205 (map browsing state). In this state 6205, the application will have generated and displayed a map view. In order to generate and display this map view, the application of some embodiments identifies a desired set of one of the map basemaps for a zone, requesting such map basemaps (eg, to A mapping service server generates a view of the map base map according to a specific orientation, orientation and perspective of a virtual camera, and visualizes the map view to a device display. When in state 6205, the map view is static. With the application under state 6205, the user can perform numerous operations to modify the map view, search for entities (eg, places of interest, addresses, etc.), retrieve routes for navigation, and the like.

In some embodiments, the integrated application is displayed on a device having an integrated touch sensitive display. The various gesture interactions on the map allow the application to perform different modifications to the map view (eg, move browsing, rotate, zoom, modify the perspective of the map perspective, etc.). When the integrated application receives a gesture interaction on the map display (rather than a touch input to various floating or non-floating controls overlaid on the map display), the application transitions to state 6210 to perform the gesture Input identification.

The gesture input recognition state 6210 distinguishes between different types of gesture inputs and translates these types of inputs into different map view modification operations. In some embodiments, the mapping application receives a gesture input as translated by an operating system of a device having an integrated touch sensitive display. The operating system translates the touch input into a gesture type and orientation (eg, a "touch" at coordinates (x, y), a "pinch" operation with separate touch inputs at two different orientations, etc.). In state 6210, the integrated mapping application of some embodiments translates such input into different map view modification operations.

When the application receives a first type of gesture input (eg, two separate touch inputs that move together in a map view with a rotational motion), the application transitions to state 6215 to rotate the map. In order to rotate the map view, some embodiments modify which portion of the virtual camera's decision map is rendered to establish the orientation and/or orientation of the map view. For example, when in 3D mode, the mapping application rotates the virtual camera around a particular location (eg, the center of the touch input, the center of the display, the orientation indicator that identifies the orientation of the user, etc.). As the first type of gesture action input continues, the mapping application remains in state 6215 to continue rotating the map.

When the user releases the first type of gesture input, the application of some embodiments transitions to state 6230 to perform an inertia calculation. In some embodiments, after the user releases certain types of touch inputs, the application continues to perform associated map view modifications for a certain amount of time and/or distance. In this case, after the user releases the rotation input, the application transitions to the inertia calculation state 6230 to calculate the amount of additional rotation and the time at which the rotation should be performed. In some embodiments, the application decelerates the current rotation (angle) rate of the rotation from the map as if a "frictional" force was applied to the map. Thus, the inertial calculations of some embodiments are based on the speed of the first type of gesture input. From state 6230, the application transitions back to the map modification state that the application was previously in. That is, when the application transitions from state 6215 (rotation state) to inertia calculation state 6230, the application then transitions back to state 6215 after performing the inertia calculation. After the rotation of the map is complete, the application transitions back to state 6205.

When the application receives a second type of gesture input (eg, a single touch input that moves over the map view), the application transitions to state 6220 to cause the map to move through. In order to make the map view mobile browsing, some embodiments modify which portion of the virtual camera's decision map is rendered to establish the orientation of the map view. This causes the map to appear to slide up in the direction from the direction in which the second type of gesture input is derived. In some embodiments, when the local map view is in the 3D perspective mode, the mobile browsing program involves correlating the orientation of the touch input with one of the orientations on the flat map to avoid sudden improper jumps in the map view. As the second type of gesture input continues, the mapping application remains in state 6220 to continue to move the map for browsing.

When the user releases the second type of gesture input, the application of some embodiments transitions to state 6230 to perform an inertia calculation. In some embodiments, after the user releases certain types of touch inputs, the application continues to perform associated map view modifications for a certain amount of time and/or distance. In this case, after the user releases the mobile browsing input, the application transitions to the inertia computing state 6230 to calculate the mobile map view. The extra amount (ie, moving the virtual camera) and the time at which this movement should be performed. In some embodiments, the application decelerates the current browsing rate of the mobile browsing motion from the map as if a "frictional" force was applied to the map. Thus, the inertial calculations of some embodiments are based on the speed of the second type of gesture input. From state 6230, the application transitions back to the map modification state that the application was previously in. That is, when the application transitions from state 6220 (mobile browsing state) to inertia computing state 6230, the application then transitions back to state 6220 after performing the inertia calculation. After the mobile browsing of the map is complete, the application transitions back to state 6205.

When the application receives a third type of gesture input (eg, two separate touch inputs that move closer or separate), the application transitions to state 6225 to zoom in or out of the map. In order to change the zoom level of the map view, some embodiments modify which portion of the virtual camera's decision map is rendered to establish the orientation (i.e., height) of the map view. This causes the map view to include more (if reduced) or less (if enlarged) portions of the map. In some embodiments, as the user zooms in or out, the application draws different map basemaps (for different zoom levels) to generate and visualize the new map view. As the third type of gesture input continues, the mapping application remains in state 6225 to continue zooming in or out of the map.

When the user releases the second type of gesture input, the application of some embodiments transitions to state 6230 to perform an inertia calculation. In some embodiments, after the user releases certain types of touch inputs, the application continues to perform associated map view modifications for a certain amount of time and/or distance (ie, moving the virtual camera to a higher position) Or lower). In this case, after the user releases the zoom input, the application transitions to the inertia calculation state 6230 to calculate the additional amount of zoomed map view (ie, moving the virtual camera) and the time at which the move should be performed. In some embodiments, the application decelerates the zooming movement from the current zooming or zooming rate of the map (i.e., the speed at which the virtual camera changes altitude) as if a "frictional" force was applied to the camera. Thus, some embodiments The inertial calculation is based on the speed of the third type of gesture input. From state 6230, the application transitions back to the map modification state that the application was previously in. That is, when the application transitions from state 6225 (zoom state) to inertia computation state 6230, the application then transitions back to state 6225 after performing the inertia calculation. After the zoom of the map is complete, the application transitions back to state 6205.

For simplicity, state diagram 6200 illustrates a map move browsing, zooming, and rotation procedure using the same inertial calculation program (state 6230). However, in some embodiments, each of these different map modification programs actually uses a different inertia calculation to identify the deceleration and stop of their particular type of movement. Additionally, some embodiments calculate and modify the inertia variables upon receipt of an input rather than when the user removes the gesture input.

When the application receives a fourth type of gesture input (eg, two separate touch inputs that move up or down consistently on the touch-sensitive display), the application transitions to state 6235 to modify the perspective of the map. In order to change the perspective of the map, some embodiments move the virtual camera along a circular arc on the map, thereby modifying both the orientation and orientation of the virtual camera (when the camera maintains the center of its field of view at a particular orientation on the map) Time). In some embodiments, different zoom levels use different arcs along which the virtual camera moves. Each of these arcs has a top point at which the virtual camera points straight down to provide a 2D perspective of the map. In addition, each arc has a bottom point that is movable to the lowest point on the arc of the virtual camera. Thus, in some embodiments, the fourth type of gesture input can cause the application to change between a 2D map view and a 3D perspective map view. As the fourth type of gesture input continues, the mapping application remains under state 6235 to continue modifying the perspective of the map.

When the user releases the fourth type of gesture input, the application of some embodiments transitions to state 6240 to perform an inertia calculation. In some embodiments, after the user releases certain types of touch inputs, the application continues to perform associated map view modifications for a certain amount of time and/or distance (ie, moving the virtual camera to a higher position) or Lower place). In this case, after the user releases the perspective change input, the application transitions to the inertia calculation state 6240 to calculate an additional amount of the perspective angle of the modified map view (ie, moving the virtual camera along the arc of the virtual camera) and The time at which this move should be performed. In some embodiments, the application decelerates the rate at which the movement changes the perspective angle from the map (i.e., the speed at which the virtual camera moves along its arc) as if a "frictional" force was applied to the camera. Thus, the inertial calculations of some embodiments are based on the speed at which the fourth type of gesture input is performed.

Additionally, for the perspective angle changing operation, some embodiments transition to the rebound calculation state 6245. As illustrated, the perspective angle changing operation has, in some embodiments, the maximum and minimum perspective angular shifts allowed, which may depend on the zoom level of the current map view. Therefore, in addition to the inertia calculation, the application also performs the rebound calculation at state 6245. The rebound calculation uses inertia calculation to determine if the maximum point along the virtual camera arc will be reached, and if the maximum point is reached, the rate at which the virtual camera is at this point is determined. Some embodiments allow the virtual camera to move slightly past the maximum point to reach a "rebound" point at which the application causes the virtual camera to steer on its arc, thereby moving the camera back toward the maximum point. Some embodiments include bounce-back functionality only at one end of the virtual camera arc (e.g., at the bottom of the arc), while other embodiments include this functionality at both ends of the arc. From the rebound calculation state 6245, the application transitions back to the inertia calculation state 6240, and then transitions back to the perspective angle change state 6235 to display the map view movement. Additionally, when the user performs the fourth type of touch input for a sufficiently long time and the perspective angle reaches the other maximum point, the application transitions directly from state 6235 to state 6245 to calculate the rebound information, and then transitions back to state 6235. After the modification of the perspective of the map is completed, the application transitions back to state 6205.

The above state is related to various multi-touch gestures on the map presentation, and the integrated map drawing, search and navigation application translates the multi-touch gestures into different modifications to the map presentation. Various other touch inputs can also cause the application to change state and execute Various functions. For example, some embodiments overlay a 3D selectable item on a map view (eg, as a floating control) and select (eg, by tapping the input) the 3D item to cause the application to transition to 6235 to modify the map. The perspective angle of the view. When the map view starts in the 3D perspective, the application modifies the perspective to a 2D view; when the local map view starts in the 2D view, the application modifies the perspective to a 3D view. After the modification, the application returns to state 6205.

When the user is viewing the map under state 6205, the application presents various tags as part of the map view. Some of these tags indicate a place of interest or other orientation. When the user selects certain tags (eg, for certain businesses, parks, etc.), the application transitions to state 6250 to display a banner for the selected location (eg, an information display banner), and then returns to the map browsing state (where the banner Displayed on the map). In some embodiments, the banner includes (1) a quick route navigation UI control (eg, a button) that causes the application to retrieve a route from the current orientation of the device to the selected orientation (eg, a driving route) Without leaving the map view, and (2) a UI UI control (eg, a button) that causes the application to provide additional information about the orientation.

When the user selects the UI control button, the application transitions from state 6205 to state 6255 to display one of the selected regions. In some embodiments, the preliminary area displays one of the selected orientations of the media presentation (eg, 3D video presentation, low altitude view of the selected orientation, a series of images captured for the orientation, etc.), and various Information (contact information, comments, etc.). The application remains in state 6255 as the user performs various operations to navigate the preparation area and view the information in the preparation area. When the user selects the UI control to transfer back to the map view, the application transitions to state 6205.

From the map browsing view, users can easily access the search function of the application. When a particular UI control item (eg, a search column) is selected, the application transitions to the search keying suggestion state 6260. In the search for typing state, some embodiments show that the user can borrow Touch the screen keypad with one of the search terms. The search term can be a business name, an address, a type of location (eg, a coffee shop), and the like. When the user types in a character, the application remains in state 6260 and provides suggestions based on recent searches, typed letters, and the like. Some embodiments may use prefix-based suggestions (eg, suggestions starting with typed characters), as well as other suggestions (eg, spelling corrections to add characters at the beginning of a typed string, swap resources, etc.) ). In some embodiments, in addition to the orientation, the selection may also include a newly typed route. If the user chooses to cancel the UI control at this stage, the application does not perform a search and then moves back to state 6205.

When the user selects a search term (a suggested word or a word typed entirely by the user), the application transitions to state 6265 to display the search result on the map view, and then transitions to display the search result to State 6205. Some embodiments display the search results as selectable items on the map (eg, pushpins); selection of one of the items results in a transition to state 6250 to display a banner for the selected item. Additionally, the application of some embodiments automatically selects one of the search results (eg, a "best" result) and displays the banner as part of state 6265.

Since the application is a tightly integrated mapping, search, route selection and navigation application, users can easily access the route selection function from the map browsing state. When a particular UI control item (eg, a route entry button) is selected, the application transitions to route entry state 6270. In the route entry state, some embodiments display a touch screen keypad that the user can use to type the orientation (eg, address, place name, place type, etc.) into the "to" and "from" fields for request. One route. As the user types in the characters, the application remains in state 6270 and provides suggestions based on recent routes, recent searches, auto-completion similar to auto-completion described for search typing, and the like. If the user chooses to cancel the UI control at this stage, the application will move back to state 6205 without taking the route.

When the user selects a route (for example, by typing "to" and "from") The application transitions to route display state 6275. In this state, the application displays one or more routes from the first selected orientation to the second selected orientation on the map view (eg, by overlaying the route line in a map view). Some embodiments automatically select the first of the routes. In the case where the application remains under state 6275 (but the display of the route is modified to indicate the selection of other routes), the user can select any of the other routes (eg, by tapping on the unselected route) ). Additionally, when in state 6275, the application of some embodiments displays different UI controls related to route selection and navigation, including guidance list controls, navigation start controls, and other controls.

Also, various gesture interactions on the map displaying the route can cause the application to perform different modifications to the map view (eg, move browsing, rotate, zoom, modify the perspective of the map perspective, etc.). In the case where all gesture action map modification operations (eg, as a result of states 6215 through 6245) are available, the application transitions when the integrated application receives a gesture interaction on the map display while in the route display state 6275 State 6210 is performed to perform a gesture input identification. That is, the application translates the gesture input into a mobile browsing, rotation, zooming, and/or perspective angle changing operation similar to that described above for states 6215 through 6245, with similar inertia and back for virtual camera movement. Bullet feature. Although operations 6215 through 6245 return to map browsing state 6205, the resulting operation from route display state 6275 returns to route display state 6275.

In some embodiments, route display state 6275 may also be entered from other states. For example, if the user selects the quick route UI control on the banner while in state 6205, the application retrieves one or more routes from the current orientation of the device to the orientation associated with the banner. Additionally, some embodiments display the previously requested route in the search suggestion at state 6260. When the user selects one of these suggested routes, the application transitions directly from state 6260 to state 6275 to display one or more routes on the map.

From the route display state 6275, the application can be converted into various modes depending on the different control items selected by the user. When the user selects the UI control to clear the route At the time, the application transitions back to state 6205 to display a map that does not have any routes. In addition, the integrated application can enter one or more navigation modalities from the route display state 6275.

When the selected route displayed at state 6275 begins with the current orientation of the device and the user selects a navigation start control, the application transitions to navigation state 6280. In some embodiments, the application displays a movie transition from a map view to a more immersive 3D view for navigation. In the navigation state 6280 of some embodiments, the virtual camera follows the user's orientation along the selected route to present an upcoming portion of the route. When the route is completed (the device reaches the destination orientation) or the user selects the control to end the navigation, the application transitions to state 6205 to present the map browsing view 6205.

In some embodiments, when in navigation mode 6280, various gesture interactions on the map displaying the route may cause the application to perform different modifications to the map view (eg, mobile browsing, rotation, zooming, modifying map perspective) Angle, etc.). In some embodiments, only some of the described map modification operations are available in the navigation mode. For example, some embodiments allow a user to zoom in or out of the map, but do not allow any other modifications to the map. Thus, when the user provides a gesture input, the gesture input recognition state 6210 filters out the type of gesture input that is not associated with the zoom operation (and then, the application returns to state 6280). Upon receiving a typed gesture input associated with the zoom operation, the gesture input recognition state recognizes the input and the application transitions to a state similar to state 6225 to change the zoom level of the map (in some embodiments, With inertia calculation).

Other embodiments may allow for different map modification operations to be implemented. For example, in some embodiments, all of the schematic action map modification operations (eg, the results of states 6215 through 6245) are available while in the navigation mode. Some embodiments allow for a subset of action map modification operations to be illustrated, including scaling and limited mobile browsing operations. In receiving a type of gesture input associated with mobile browsing, some embodiments of the mobile browsing operation move the virtual camera (when in navigation mode) laterally, then returning the virtual camera to edge Pointing the route. Although operations 6215 through 6245 return to map browsing state 6205, the resulting operation from navigation state 6280 returns to navigation state 6280.

When the selected route displayed at state 6275 begins with an orientation other than the current orientation of the device (or route walking route) and the user selects the navigation start control, the application transitions to step mode or route check at state 6285. mode. In some embodiments, the application displays driving control along the route (eg, as a navigational marker) one at a time. By providing a gesture input to the driver (eg, a toggle action), the user can view different controls while in the route check mode. The driving controls are overlayed on a map and at least a portion of the route is displayed on the map.

As in the route display mode, various gesture interactions on the map allow the application to perform different modifications to the map view (eg, move browsing, rotate, zoom, modify the perspective of the map perspective, etc.). When the integrated application receives the gesture interaction on the map display while in step mode 6285, the application transitions to state 6210 to perform the gesture input recognition, while all gestures map modification operations (eg, state 6215 to The result of 6245) is available. That is, the application translates the gesture input into a mobile browsing, rotation, zooming, and/or perspective angle changing operation similar to that described above for states 6215 through 6245, with similar inertia and back for virtual camera movement. Bullet feature. Although operations 6215 through 6245 return to map browsing state 6205, the resulting operation from step mode 6285 is returned to step mode 6285.

Moreover, in some embodiments, the gesture input identification identifies at least one type of gesture input on the displayed driver for switching between controls. When a particular type of gesture input (eg, a toggle gesture) is received on the displayed driver (rather than on the map view), the application transitions to change the state of the displayed driver (not Shown), then return to state 6285.

When the integrated application receives a gesture interaction on the displayed map while in stepped state 6285, the application transitions to state 6210 to perform a gesture action Identification is entered, while all gesture action map modification operations (eg, the results of states 6215 through 6245) are available. When the modification operation is complete, the application returns to state 6285. When the user selects a control to end the stepping through the ride, the application transitions to state 6205 to present a map view.

Additionally, in some embodiments, the application can transition from step mode 6285 to automatic step state 6290. When the user selects an orientation tracking control while the application is in state 6285, the application transitions to automatic stepping mode 6290, which is a different navigation mode. When in some embodiments the automatic stepping mode, the integrated mapping, search, and navigation application displays the device's closest proximity to the control (eg, as measured by the junction at which the control is performed). The automatic stepping mode automatically displays the different driving controls as the device moves (eg, along the route) to a position that is closer to one of the different driving controls. When the user deselects the azimuth tracking control, the application transitions back to step mode 6285. When the user selects a control to end navigation while in the automatic step state 6290, the application transitions to state 6205 to present a map browsing view.

As in step mode 6285, various gesture interactions on the map allow the application to perform different modifications to the map view (eg, move browsing, rotate, zoom, modify map perspective, etc.). When the integrated application receives the gesture interaction on the map display while in the automatic step mode 6290, the application transitions to state 6210 to perform the gesture input recognition, while all the gesture map modifications are performed (eg, state 6215) The result to 6245) is available. That is, the application translates the gesture input into a mobile browsing, rotation, zooming, and/or perspective angle changing operation similar to that described above for states 6215 through 6245, with similar inertia and back for virtual camera movement. Bullet feature. Although operations 6215 through 6245 return to map browsing state 6205, the resulting operation from automatic stepping mode 6290 returns to automatic stepping mode 6290. Additionally, some embodiments automatically turn off the azimuth tracking control when the user moves the map through a particular distance, in which case the application returns to step mode state 6285. Non-automatic stepping state 6290.

VI. Electronic System

Many of the above features and applications are implemented as software programs designated as a set of instructions recorded on a computer readable storage medium (also referred to as a computer readable medium). When such instructions are executed by one or more computing or processing units (eg, one or more processors, processor cores, or other processing units), the instructions cause the processing units to execute the instructions The action indicated in . Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, random access memory (RAM) chips, hard disk drives, erasable programmable read only memory (EPROM), electrically erasable In addition to programmable read-only memory (EEPROM). Computer-readable media does not include carrier and electronic signals that are transmitted wirelessly or via a wired connection.

In this specification, the term "software" is intended to include a firmware resident in a read-only memory that can be read into a memory for processing by a processor or an application stored in a magnetic storage. Also, in some embodiments, multiple software inventions can be implemented as sub-parts of a larger program while still being invented by dissimilar software. In some embodiments, multiple software inventions may also be implemented as separate programs. Finally, any combination of separate programs for implementing the software invention described herein is within the scope of the invention. In some embodiments, a software program, when installed to operate on one or more electronic systems, defines one or more specific machine implementations that execute and perform the operations of the software program.

A. Mobile device

The multi-modal mapping application of some embodiments operates on mobile devices such as smart phones (eg, iPhone®) and tablets (eg, iPad®). Figure 63 is an example of an architecture 6300 of such a mobile computing device. Examples of mobile computing devices include smart phones, tablets, laptops, and the like. As shown, the mobile computing device 6300 includes one or more processing units 6305, a memory interface 6310, and a peripheral device interface 6315.

Peripheral device interface 6315 is coupled to various sensors and subsystems, including camera subsystem 6320, wireless communication subsystem 6325, audio subsystem 6330, I/O subsystem 6335, and the like. Peripheral device interface 6315 allows for communication between processing unit 6305 and various peripheral devices. For example, orientation sensor 6345 (eg, gyroscope) and acceleration sensor 6350 (eg, an accelerometer) are coupled to peripheral device interface 6315 to facilitate orientation and acceleration functions.

Camera subsystem 6320 is coupled to one or more optical sensors 6340 (eg, a charge coupled device (CCD) optical sensor, a complementary metal oxide semiconductor (CMOS) optical sensor, etc.). Camera subsystem 6320 coupled to optical sensor 6340 facilitates camera functions, such as image and/or video data capture. Wireless communication subsystem 6325 is used to facilitate communication functions. In some embodiments, the wireless communication subsystem 6325 includes a radio frequency receiver and transmitter, and an optical receiver and transmitter (not shown in FIG. 63). Such receivers and transmitters of some embodiments are implemented to operate on one or more communication networks, such as a GSM network, a Wi-Fi network, a Bluetooth network, and the like. The audio subsystem 6330 is coupled to a speaker to output audio (eg, output voice navigation instructions). In addition, the audio subsystem 6330 is coupled to a microphone to facilitate voice enabled functions, such as speech recognition (eg, for searching), digital recording, and the like.

The I/O subsystem 6335 relates to the transfer between the input/output peripheral devices (such as a display, touch screen, etc.) and the data bus of the processing unit 6305 via the peripheral device interface 6315. The I/O subsystem 6335 includes a touch screen controller 6355 and other input control items 6360 to facilitate transfer between the input/output peripheral devices and the data bus of the processing unit 6305. As shown, the touch screen controller 6355 is coupled to the touch screen 6365. The touch screen controller 6355 uses any of a number of touch sensitive technologies to detect contact and movement on the touch screen 6365. Other input controllers 6360 are coupled to other input/control devices, such as one or more buttons. Some embodiments include proximity touch sensitive screens and corresponding controls that detect proximity touch interactions rather than touch interactions or touch proximity interactions, as well as proximity touch interactions. Device.

The memory interface 6310 is coupled to the memory 6370. In some embodiments, the memory 6370 includes volatile memory (eg, high speed random access memory), non-volatile memory (eg, flash memory), volatile memory, and non-volatile memory. A combination, and / or any other type of memory. As illustrated in FIG. 63, the memory 6370 stores an operating system (OS) 6372. OS 6372 includes instructions for handling basic system services and for performing hardware dependent tasks.

The memory 6370 also includes: communication instructions 6374 for facilitating communication with one or more additional devices; graphical user interface instructions 6376 for facilitating graphical user interface processing; image processing for facilitating image related processing and functions Instruction 6378; input processing instructions 6380 for facilitating input related (eg, touch input) programs and functions; audio processing instructions 6382 for facilitating audio related programs and functions; and camera instructions for facilitating camera related programs and functions 6384. The above described instructions are merely illustrative, and in some embodiments, memory 6370 includes additional and/or other instructions. For example, memory for a smart phone can include phone instructions to facilitate phone related programs and functions. Additionally, the memory can include instructions for a multimodal mapping application. The above identified instructions need not be implemented as separate software programs or modules. The various functions of the mobile computing device can be implemented in hardware and/or software (including one or more signal processing and/or special application integrated circuits).

While the components illustrated in Figure 63 are shown as separate components, one of ordinary skill in the art will recognize that two or more components can be integrated into one or more integrated circuits. Additionally, two or more components may be coupled together by one or more communication busses or signal lines. Again, although many of these functions have been described as being performed by one component, those skilled in the art will recognize that the functions described with respect to Figure 63 can be divided into two or more integrated circuits. .

B. Computer system

Figure 64 conceptually illustrates another example of an electronic system 6400 in which some embodiments of the present invention are implemented. Electronic system 6400 can be a computer (eg, a desktop, personal computer, tablet, etc.), a telephone, a PDA, or any other type of electronic or computing device. This electronic system includes various types of computer readable media and interfaces for various other types of computer readable media. The electronic system 6400 includes a bus 6405, a processing unit 6410, a graphics processing unit (GPU) 6415, a system memory 6420, a network 6425, a read-only memory 6430, a permanent storage device 6435, an input device 6440, and an output device. 6445.

Busbars 6405 collectively represent all of the system, peripheral, and chipset busbars that communicatively connect the numerous internal components of electronic system 6400. For example, bus 6405 communicatively connects the processing unit 6410 with read-only memory 6430, GPU 6415, system memory 6420, and persistent storage device 6435.

From among these various memory units, the processing unit 6410 retrieves the instructions for executing and the materials for processing to perform the procedures of the present invention. In various embodiments, the processing unit can be a single processor or a multi-core processor. Some instructions are passed to GPU 6415 and executed by GPU 6415. The GPU 6415 can offload various calculations or supplement the image processing provided by the processing unit 6410. In some embodiments, CoreImage's core occlusion language can be used to provide this functionality.

Read-only memory (ROM) 6430 stores the static data and instructions required by the processing unit 6410 and other modules of the electronic system. On the other hand, the permanent storage device 6435 reads and writes to the memory device. This device is a non-volatile memory unit that stores instructions and data even when electronic system 6400 is turned off. Some embodiments of the present invention use bulk storage devices such as magnetic or optical disks and their corresponding disk drives, integrated flash memory as the permanent storage device 6435.

Other embodiments use removable storage devices (such as floppy disks, flash memory devices, etc. and their corresponding disk drives) as permanent storage devices. Similar to persistent storage device 6435, system memory 6420 reads and writes to the memory device. However, unlike storage devices 6435, system memory 6420 is a volatile read and write memory, such as random access memory. System memory 6420 stores some of the instructions and materials required by the processor during the execution phase. In some embodiments, the program of the present invention is stored in system memory 6420, persistent storage device 6435, and/or read only memory 6430. From among the various memory units, the processing unit 6410 retrieves instructions for executing and processing the data to perform the procedures of some embodiments.

Bus 6405 is also coupled to input device 6440 and output device 6445. The input devices 6440 enable a user to communicate information to the electronic system and commands to the electronic system. The input devices 6440 include alphanumeric keyboards and indicator devices (also referred to as "cursor control devices"), cameras (eg, webcams), microphones or the like for receiving voice commands. The output devices 6445 display images produced by the electronic system or otherwise output the data. The output devices 6445 include printers and display devices such as cathode ray tubes (CRTs) or liquid crystal displays (LCDs), as well as speakers or similar audio output devices. Some embodiments include devices that function as both an input device and an output device, such as a touch screen.

Finally, as shown in FIG. 64, bus 6405 also couples electronic system 6400 to network 6425 via a network adapter (not shown). In this way, the computer can be part of a computer network (such as a local area network ("LAN"), a wide area network ("WAN"), or an intranet (such as the Internet) or a network of the Internet (such as the Internet). Any or all of the components of electronic system 6400 can be used in conjunction with the present invention.

Some embodiments include electronic components, such as microprocessors, storage and storage of computer program instructions in a machine readable or computer readable medium (alternatively referred to as computer readable storage media, machine readable media or Machine readable storage media). Some examples of such computer readable media include RAM, ROM, CD-ROM, CD-R, rewritable compact disc (CD-RW), read only audio and video discs (eg, DVD-ROM, dual-layer DVD-ROM), a variety of recordable / rewritable DVDs (for example, DVD- RAM, DVD-RW, DVD+RW, etc.), flash memory (eg SD card, mini SD card, micro SD card, etc.), magnetic and/or solid state drive, read-only and recordable Blu-Ray® Discs, ultra-high-density discs, any other optical or magnetic media, and floppy disks. The computer readable medium can store a computer program executable by at least one processing unit and including a set of instructions for performing various operations. Examples of computer programs or computer programs include machine code (such as machine code generated by a compiler), and files including higher level code executed by a computer, electronic component or microprocessor using an interpreter.

Although the above discussion mainly refers to a microprocessor or multi-core processor executing software, some embodiments are implemented by one or more integrated circuits (such as special application integrated circuits (ASIC) or field programmable gate arrays (FPGA). ))carried out. In some embodiments, such integrated circuits perform instructions stored on the circuit itself. Additionally, some embodiments implement software stored in programmable logic device (PLD), ROM or RAM devices.

As used in this specification and any claims of this application, the terms "computer", "server", "processor" and "memory" are all referring to electronic devices or other technical devices. These terms exclude groups of people or people. For the purposes of this specification, the term display means to be displayed on an electronic device. As used in this specification and any claims of this application, the terms "computer-readable medium", "multiple computer-readable medium" and "machine-readable medium" are completely limited to the storage of information in a computer readable form. Tangible physical objects. These terms exclude any wireless signals, cable download signals, and any other temporary signals.

VII. Map service environment

Various embodiments may operate in a map service operating environment. Figure 65 illustrates a map service job environment in accordance with some embodiments. The map service 6530 (also referred to as a mapping service) may provide map services for one or more of the client devices 6502a through 6502c in communication with the map service 6530 via various communication methods and protocols. In some embodiments, the map service 6530 provides map information and other map related material, such as two-dimensional map image data (eg, a bird's eye view of a road imaged using satellite imaging), three-dimensional map image material (eg, having Such as traversing maps of three-dimensional features of buildings), route and guidance calculations (eg, ferry route calculations or guidance for pedestrians between two points), instant navigation data (eg, two- or three-dimensional steering tips) Navigation data), location data (for example, where the client device is currently located), and other geographic information (eg, wireless network coverage, weather, traffic information, or nearby points of interest). In various embodiments, the map service material may include regionalized tags for different countries or regions. The regionalization tag can be used to present map tags (eg, street names, city names, points of interest) in different languages on the client device. Client devices 6502a through 6502c may utilize such map services by obtaining map service data. Client devices 6502a through 6502c may implement various techniques for processing map service data. Client devices 6502a through 6502c may then provide map services to various entities including, but not limited to, users, internal software or hardware modules, and/or other systems or devices external to client devices 6502a through 6502c.

In some embodiments, the map service is implemented by one or more nodes in a distributed computing system. Each node can be assigned one or more services or components of the map service. Some nodes may be assigned the same map service or component of the map service. In some embodiments, the load balancing node will distribute access or requests to other nodes within the map service. In some embodiments, the map service is implemented as a single system, such as a single server. Different modules or hardware devices within the server may implement one or more of the various services provided by the map service.

In some embodiments, the map service provides a map service by generating map service materials in various formats. In some embodiments, the map service material in one format is map image material. The map image data provides the image data to a client device such that the client device can process the image material (eg, visualize and/or display the image data as a two- or three-dimensional map). Map image data (two-dimensional or three-dimensional) can specify one or more map basemaps. The map basemap can be part of a larger map image. The map map of a map is assembled to produce the original map. The basemap can be generated from map imagery, route selection or navigation data or any other map service data. In some embodiments, the map basemap is based on A map of the dot matrix, where the basemap size can be any size greater than and less than the 256 pixels by 256 pixel basemap typically used. A bitmap-based map base map can be encoded into a number of standard digital image representations including, but not limited to, bitmap (.bmp), graphics interchange format (.gif), joint photography expert group (.jpg, . Jpeg, etc.), portable network graphics (.png) or tagged video file format (.tiff). In some embodiments, the map basemap is based on a vector map of the map, encoded using vector graphics including, but not limited to, scalable vector graphics (.svg) or graphics archive (.drw). Some embodiments also include a base map with a combination of vectors and bitmap data. Data or other information related to the map base map may also be included in or included with the map base map to provide more map service data to the client device. In various embodiments, map maps are encoded for transmission using various standards and/or protocols, some of which are described in the examples below.

In various embodiments, the map basemap can be constructed from image data of different resolutions, depending on the zoom level. For example, for low zoom levels (eg, world or global views), the resolution of the map or image data does not have to be as high as the resolution at a high zoom level (eg, city or street level). For example, when in a global view, it may not be necessary to visualize street-level artifacts, as such objects would be too small to be ignored in many cases.

In some embodiments, the map service performs various techniques for analyzing the map base map prior to encoding the base map for transmission. This analysis optimizes the performance of map services for both client devices and map services. In some embodiments, the complexity of the map base map is analyzed according to vector-based graphics techniques, and the map base map is constructed using complex and uncomplicated layers. The map base map can also be analyzed for general image data or patterns that can be visualized as image textures, and the map base map can be constructed by relying on image masks. In some embodiments, the bitmap-based image material in the map base map contains certain mask values that are associated with one or more textures. Some embodiments are also directed to being associated with certain map styles containing style identifiers Analyze the map basemap with the specified characteristics.

In some embodiments, other map services generate map service material that is separate from the map basemap and that relies on various data formats. For example, a map service providing location data may utilize a data format that conforms to a location service agreement such as, but not limited to, a Radio Resource Location Service Protocol (RRLP) for code division multiple access (CDMA). TIA 801, Radio Resource Control (RRC) Location Agreement or LTE Location Agreement (LPP). Embodiments may also receive or request data from a client device that identifies device capabilities or attributes (eg, hardware specifications or operating system versions) or communication capabilities (eg, as determined by wireless signal strength or wired or wireless network type) Device communication bandwidth).

The map service can obtain map service materials from internal or external sources. For example, satellite imagery used in map imagery may be obtained from an external service or internal system, storage device, or node. Other examples may include, but are not limited to, GPS assisted servers, wireless network coverage databases, commercial or personal directories, weather data, government information (eg, construction engineering updates or road name changes), or traffic reports. Some embodiments of the map service may update the map service material (eg, wireless network coverage) for analysis of future requests from the client device.

Various embodiments of the map service are responsive to requests from the client device for the map service. Such requests may be requests for a particular map or part of a map. Some embodiments format the request for a map as a request for a particular map basemap. In some embodiments, the request also supplies a starting location (or current orientation) and a destination orientation for the map service for route calculation. The client device may also request the map service to present information, such as a map texture or style sheet. In at least some embodiments, the request is also one of a series of requests to implement a turn-by-turn navigation. Requests for other geographic information may include, but are not limited to, current location, wireless network coverage, weather, traffic information, or nearby points of interest.

In some embodiments, the map service analyzes client device requests to optimize device or map service operations. For example, the map service can identify the orientation of the user device. Sending more map service data in one of the areas of poor communication (eg, weak wireless signal) and transmitting communication to generate a client device or send instructions to utilize different client hardware (eg, directional sensor) ) or software (for example, using wireless location services or Wi-Fi positioning instead of GPS-based services). In another example, the map service can analyze the request of the client device for the vector-based map image data, and determine the map image data based on the bitmap to better optimize the map image data according to the complexity of the image. Embodiments of other map services may perform similar analysis on the client device request, and thus, the above examples are not intended to be limiting.

Various embodiments of the client device (e.g., client devices 6502a through 6502c) are implemented on different types of portable multifunction devices. Client devices 6502a through 6502c utilize map service 6530 via various communication methods and protocols. In some embodiments, client devices 6502a through 6502c obtain map service material from map service 6530. The client devices 6502a through 6502c request or receive map service data. The client devices 6502a through 6502c then process the map service data (e.g., visualize and/or display the material) and may send the data to another software or hardware module on the device or to an external device or system.

According to some embodiments, the client device implements techniques for visualizing and/or displaying a map. These maps may be requested or received in a variety of formats, such as the map basemap described above. A client device can present a map in a two- or three-dimensional view. Some embodiments of a client device display a virtual camera in a map as soon as the user or system is allowed to provide an input to manipulate the map, thereby changing the map display based on the position, orientation, and field of view of the virtual camera. Various forms and input devices are implemented to manipulate the virtual camera. In some embodiments, the virtual camera is manipulated via a touch input of some single or combined gesture (eg, touch and hold or toggle). Other embodiments allow the physical orientation of the device to be manipulated to manipulate the virtual camera. For example, a user device can be tilted up from its current position to manipulate the virtual camera to rotate up. In another example, a client device can be tilted forward from its current position to move the virtual camera forward. Implementable Other input devices to the user device include, but are not limited to, audible inputs (eg, spoken words), physical keyboards, mice, and/or joysticks.

Some embodiments provide various visual feedbacks for virtual camera manipulation, such as displaying possible virtual camera manipulation animations when transitioning from a two-dimensional map view to a three-dimensional map view. Some embodiments also allow for input to select a map feature or object (e.g., a building) and highlight the object, thereby creating a blurring effect that maintains the three dimensional sense of the virtual camera.

In some embodiments, a client device implements a navigation system (e.g., steering alert navigation). The navigation system provides guidance or route information that can be displayed to the user. Some embodiments of the client device request guidance or a route calculation to the map service. The client device can receive map image data and route data from the map service. In some embodiments, a client device implements a steering alert navigation system that provides an instant route based on location information and route information received from a map service and/or other positioning system, such as a Global Positioning Satellite (GPS) system. Guidance information. The client device can display map image data reflecting the current orientation of the user device and update the map image data in real time. A navigation system can provide audible or visual guidance to travel along a route.

According to some embodiments, a virtual camera is implemented to manipulate navigation map material. Some embodiments of the client device allow the device to adjust the virtual camera display orientation to a biased route destination. Some embodiments also allow the virtual camera to simulate the inertial motion of the virtual camera through the turn.

The client device implements various techniques to utilize map service material from the map service. Some embodiments implement techniques for optimizing the visualization of two-dimensional and three-dimensional map imagery. In some embodiments, the client device stores the presence information at the local end. For example, the client stores a style sheet containing image data of the style identifier, which provides a presentation guide. In another example, a general image texture can be stored to reduce the amount of map image data transmitted from the map service. In various embodiments, the client device is implemented to visualize two dimensions and Various modeling techniques for 3D map image data, examples of which include (but are not limited to): generating 3D buildings based on 2D building footprint data; modeling 2D and 3D map objects to determine user device communication environment Generating a model for determining whether a map label can be seen from a virtual camera location; and generating a model for smoothing transitions between map image data. In some embodiments, the client device also prioritizes or prioritizes the map service data using certain techniques. For example, the client device detects the motion or rate of the virtual camera, and if it exceeds some threshold, loads and visualizes less detailed image data for certain regions. Other examples include: rendering a vector-based curve as a series of points; preloading map imagery of areas that are poorly communicating with the map service; adapting the texture based on the display zoom level; or visualizing the map image data based on complexity.

In some embodiments, the client device communicates using various data formats that are separate from the map basemap. For example, some client devices implement assisted Global Positioning Satellite (A-GPS) and communicate with location services that utilize a data service conforming to a location service agreement, such as, but not limited to, a radio resource location service. Protocol (RRLP), TIA 801 for Code Division Multiple Access (CDMA), Radio Resource Control (RRC) Location Agreement, or LTE Location Agreement (LPP). The client device can also receive GPS signals directly. Embodiments may also send data (in the case of a map service request or not request) that identifies the capabilities or attributes of the client device (eg, hardware specifications or operating system versions) or communication capabilities (eg, such as based on wireless signal strength) Or the communication bandwidth of the device determined by the wired or wireless network type).

Figure 65 illustrates one possible embodiment of a work environment 6500 for map service 6530 and client devices 6502a through 6502c. In some embodiments, devices 6502a, 6502b, and 6502c communicate via one or more wired or wireless networks 6510. For example, wireless network 6510 (such as a cellular network) can communicate with a wide area network (WAN) 6520 (such as the Internet) by using gateway 6514. In some embodiments, the gateway 6514 provides a packet-oriented mobile data service (such as Integrated Packet Radio Service (GPRS)), or Other mobile data services that allow wireless networks to transmit data to other networks, such as the WAN 6520. Likewise, access device 6512 (e.g., an IEEE 802.11g wireless access device) provides communication access to WAN 6520. Devices 6502a and 6502b can be any portable electronic or computing device capable of communicating with a map service. Device 6502c can be any non-portable electronic or computing device capable of communicating with a map service.

In some embodiments, both voice and data communications can be established via wireless network 6510 and access device 6512. For example, device 6502a can be dialed via wireless network 6510, gateway 6514, and WAN 6520 (eg, using Transmission Control Protocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)). Answer a call (for example, using the Voice over Internet Protocol (VoIP) protocol), receive and send an e-mail message (for example, using Easy Mail Transfer Protocol (SMTP) or Post Office Protocol 3 (POP3)), and retrieve electronic files And/or streaming (such as web pages, photos and videos). Similarly, in some implementations, devices 6502b and 6502c can make and receive calls, access and receive email messages, and retrieve electronic files via access devices 6512 and WAN 6520. In various embodiments, any of the illustrated client devices can use persistent connections established in accordance with one or more security protocols, such as Secure Communications Layer (SSL) protocols or Transport Layer Security (TLS) protocols. To communicate with map service 6530 and/or other services 6550.

Devices 6502a and 6502b can also establish communications by other means. For example, wireless device 6502a can communicate with other wireless devices (eg, other devices 6502b, mobile phones, etc.) via wireless network 6510. Similarly, devices 6502a and 6502b can establish peer-to-peer communication 6540 by using one or more communication subsystems, such as Bluetooth® communications from Bluetooth Special Interest Group, Inc. (Kirkland, Wash.) (eg, personal area network) road). Device 6502c can also establish inter-stage communication (not shown) with device 6502a or 6502b. Other communication protocols and topologies can also be implemented. Devices 6502a and 6502b may also receive Global Positioning Satellite (GPS) signals from GPS satellites 6560.

Devices 6502a, 6502b, and 6502c may be via one or more wired and/or wireless networks 6510 or 6512 communicates with the map service 6530. For example, map service 6530 can provide map service data to presentation devices 6502a, 6502b, and 6502c. The map service 6530 can also communicate with other services 6550 to obtain data to implement the map service. The map service 6530 and other services 6550 can also receive GPS signals from the GPS satellite 6560.

In various embodiments, map service 6530 and/or other services 6550 are configured to process search requests from any of the client devices. The search request may include, but is not limited to, a query for a business, address, residential location, point of interest, or some combination thereof. The map service 6530 and/or other services 6550 can be configured to pass back results related to a variety of parameters including, but not limited to, the type entered into the address column or other text entry fields (including abbreviations and/or Or other shorthand notation), current map view (eg, the user can view another orientation on the multifunction device while staying in one orientation), the user's current orientation (eg, the current map view does not include search results) In case) and current route (if any). In various embodiments, such parameters may affect the composition of the search results (and/or the ranking of the search results) based on different priority weights. In various embodiments, the returned search results may be a subset of results selected based on particular criteria including, but not limited to, the number of times the search results (eg, a particular point of interest) have been requested, A measure of the quality associated with the search results (eg, the highest user or editorial review rating) and/or the number of reviews for the search results (eg, the number of times the search results have been reviewed or rated).

In various embodiments, map service 6530 and/or other services 6550 are configured to provide automated completion of search results displayed on a client device, such as within a mapping application. For example, auto-complete search results can be filled in as part of the screen when the user types one or more search keywords on the multi-function device. In some cases, this feature can save user time because the desired search results can be displayed before the user types in the full search query. In various embodiments, the auto-complete search results may be search results (eg, bookmarks or contacts) found by the user on the client device, by map service 6530, and/or other services 6550 elsewhere (eg, from the Internet) Search results and/or such findings A combination of search results. As in the case of a command, any of the search queries can be entered by the user via voice or via typing. The multifunction device can be configured to graphically display the search results in any of the map displays described herein. For example, a pin or other graphical indicator can specify the orientation of the search results as a point of interest. In various embodiments, in response to the user selecting one of the points of interest (eg, a touch selection, such as a touch), the multifunction device is configured to display additional information regarding the selected point of interest, Includes, but is not limited to, images of ratings, comments or commentary clips, business hours, store status (eg, open doors, permanent closures, etc.) and/or storefronts of points of interest. In various embodiments, any of this information can be displayed on a graphical information card that is displayed in response to the user selecting a point of interest.

In various embodiments, map service 6530 and/or other services 6550 provide one or more feedback mechanisms for receiving feedback from client devices 6502a through 6502c. For example, the client device may provide feedback on the search results to the map service 6530 and/or other services 6550 (eg, specify ratings, comments, temporary or permanent outages, errors, etc.); this feedback may be used to update Information about points of interest to provide more accurate or updated search results in the future. In some embodiments, map service 6530 and/or other services 6550 can provide test information to a client device (eg, an A/B test) to determine which search results are optimal. For example, the client device can receive two search results at random intervals and present the two search results to the user, and allows the user to indicate the best result. The client device can report the best results to map service 6530 and/or other services 6550 based on selected testing techniques (such as A/B testing techniques, where baseline control samples are compared to various single variable test samples to improve results) ) to improve future search results.

While the invention has been described with respect to the specific embodiments of the present invention, it will be understood that the invention may be embodied in other specific forms without departing from the spirit of the invention. For example, many of the figures illustrate various touch gestures (eg, touch, tap twice, toggle gestures, hold down gestures, etc.). Of course Instead, it can be gestured via different touches (eg, toggle instead of touch, etc.) or by non-touch input (eg, using a cursor controller, keyboard, trackpad/track pad, proximity touch sensitive screen, etc.) ) to perform many of the illustrated operations. In addition, several figures conceptually illustrate the procedure. The specific operations of such programs may not be performed in the precise order shown and described. Specific operations may not be performed in a series of sequential operations, and in different embodiments, different specific operations may be performed. In addition, the program can be implemented using several subroutines or as part of a larger macro program.

140‧‧‧top column

5205‧‧‧First stage

5210‧‧‧ second stage

5215‧‧‧ third stage

5220‧‧‧ fourth stage

5225‧‧‧First scrollable sign

5235‧‧‧New sign

5250‧‧‧New section

5290‧‧‧ current joint indicator

Claims (20)

An electronic device for displaying a route, the electronic device comprising: a display screen; at least one processing unit; and a storage device for storing a map application, the map application providing a display when executed by the processing unit The area is for displaying a set of map and graphical user interface (GUI) items on a touch sensitive display screen of the electronic device, the display area being displayed on the display screen, the map application having An instruction set for displaying a route between a starting orientation and a destination orientation on the displayed map; and displaying a plurality of movable GUI items, each of the movable GUI items for providing a driving instruction To guide a user through the route, each driving instruction is associated with an area of the map, wherein when the first movable GUI item of one of the first driving instructions is displayed, displayed on the display area a first area of the map associated with the first driving instruction, and wherein when displaying one of the second driving instructions, the second movable GUI item is displayed in the display area Displaying a second region of the map associated with the second driver command, wherein in response to the user performing a swipe gesture on the first region of the map to be in the touch The second area of the map is displayed on the sensitive display screen, the first movable GUI item moves out of the display area and the second movable GUI item moves into the display area. The device of claim 1, wherein the map application further comprises a set of mobile fingers A set of instructions for moving the first region of the map out of the display region and moving the second region of the map into the display region in response to the toggle gesture. The device of claim 1, wherein each of the movable GUI items includes a navigation flag similar to one of the road traffic signs in the map showing one of the routes. The device of claim 1, wherein the toggle gesture is a first toggle gesture in a first direction, wherein the user is on the touch sensitive display screen in a second direction When a second toggle gesture is performed on the second zone of the map, the second movable GUI item moves out of the display area and the first movable GUI item moves into the display area. The device of claim 1, wherein the first driving control command and the second driving control command are adjacent driving control commands in a driving control command sequence. The device of claim 1, wherein the first driving command and the second driving command are not adjacent driving commands in a driving command sequence. The device of claim 1, wherein one of the driving command sequences is for guiding the user at one of the junctions in the route. The device of claim 1, wherein the map application further comprises a plurality of sets of instructions for performing the steps of: providing a user interface (UI) item for displaying an overview of the route; and receiving the pair for When one of the UI items of the overview is selected, one of the driving instructions in the sequence is displayed to scroll the list. A non-transitory machine readable medium storing a map application for providing a graphical user interface (GUI) when executed by at least one processing unit of a device, the GUI comprising: a first display area for Display a collection of user interface (UI) items, Each UI item provides a driving command in a sequence of driving instructions for guiding a user through a route between a starting position and a destination position, each of the driving instructions in the sequence Corresponding to a certain area of the map; and a second display area for displaying one of the maps, wherein a first driving instruction provided by a first UE item is displayed in the first display area, When the user performs a toggle gesture on the first area of the map on the touch sensitive display screen, the first area of the map moves out of the second display area and corresponds to the sequence a second area of the map of a second driving instruction is moved into the second display area, wherein in response to the toggle gesture, the first UI item providing one of the first driving instructions is also moved out of the first display And providing a second UI item of the second driving instruction to the first display area. The machine readable medium of claim 9, wherein the first display area is overlaid on the second display area such that the UI items appear to move over the map displayed in the second display area. The machine-readable medium of claim 9, wherein a specific area of the map associated with a particular driver command includes a joint point through which the particular driver command directs the user, wherein the particular The point at which the driver's control command directs the user occurs in a manner different from the other joints of the particular zone. The machine readable medium of claim 9, wherein the first and second driving instructions are adjacent driving instructions in the driving instruction sequence. A method for executing a device for a mapping application, the device comprising a display area for displaying a map and a set of graphical user interfaces on a touch sensitive display screen of the device (GUI) project, the method comprising: displaying a first position between a starting position and a destination position on the displayed map And displaying a plurality of movable GUI items, each of the movable GUI items for providing a driving instruction to guide a user to pass the route, and each driving instruction is associated with a certain area of the map, wherein Displaying a first movable GUI item provided by one of the first driving instructions, displaying a first area of the map associated with the first driving instruction on the display area, and wherein displaying a second When the second controllable GUI item is one of the driving instructions, displaying a second area of the map associated with the second driving instruction on the display area, wherein the first part of the map is in response to the user Implementing a swipe gesture on the area to display the second area of the map on the touch sensitive display screen, the first movable GUI item moves out of the display area and the second movable GUI item moves in The display area. The method of claim 13, further comprising moving the first region of the map out of the display region and moving the second region of the map into the display region in response to the toggle gesture. The method of claim 13, wherein each of the movable GUI items includes a navigation flag similar to one of the road traffic signs in the map showing one of the routes. The method of claim 13, wherein the toggle gesture is a first toggle gesture in a first direction, wherein the user is on the touch sensitive display screen in a second direction When a second toggle gesture is performed on the second zone of the map, the second movable GUI item moves out of the display area and the first movable GUI item moves into the display area. The method of claim 13, wherein the first driving instruction and the second driving instruction An adjacent driving control instruction in a driving command sequence. The method of claim 13, wherein the first driving instruction and the second driving instruction are not adjacent driving instructions in a driving instruction sequence. The method of claim 13, wherein one of the driving command sequences is for guiding the user at one of the points in the route. The method of claim 13, further comprising: providing a user interface (UI) item for presenting an overview of the route; and displaying upon receiving a selection of one of the UI items for presenting the overview One of the drive commands in the sequence can scroll through the list.