Representing traffic along a route

• US 10,783,703 B2
• Filed: 09/21/2018
• Issued: 09/22/2020
• Est. Priority Date: 06/10/2012
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Moore, Christopher D., Pahwa, Aroon, Hu, Yaohua
• Primary Examiner(s): Patel, Shardul D
• Application Number:
  US16/138,776
• Publication Number:
  US 20190026940A1
• Time in Patent Office: 732 Days
• Field of Search: 701117, 701118, 701400, 701410, 701420, 345855, 345419, 345473
• CPC Class Codes: G01C 21/3626 Details of the output of route guidance instructions traffic control systems for road vehicles involving transmission of navigation instructions to the vehicle G08G1/0968
• CPC Class Codes: G01C 21/367 Details, e.g. road map scale, orientation, zooming, illumination, level of detail, scrolling of road map or positioning of current position marker
• CPC Class Codes: G01C 21/3676 Overview of the route on the road map
• CPC Class Codes: G01C 21/3694 Output thereof on a road map
• CPC Class Codes: G06Q 10/047 Optimisation of routes or paths, e.g. travelling salesman problem
• CPC Class Codes: G06T 17/05 Geographic models
• CPC Class Codes: G06T 17/20 Finite element generation, e.g. wire-frame surface description, tesselation
• CPC Class Codes: G06T 2200/24 involving graphical user interfaces [GUIs]
• CPC Class Codes: G08G 1/0962 having an indicator mounted inside the vehicle, e.g. giving voice messages
• CPC Class Codes: G08G 1/0967 Systems involving transmission of highway information, e.g. weather, speed limits transmission of navigation instructions to the vehicle G08G1/0968
• CPC Class Codes: G08G 1/096716 where the received information does not generate an automatic action on the vehicle control
• CPC Class Codes: G08G 1/096741 where the source of the transmitted information selects which information to transmit to each vehicle
• CPC Class Codes: G08G 1/096775 where the origin of the information is a central station
• CPC Class Codes: G08G 1/096816 where the complete route is transmitted to the vehicle at once
• CPC Class Codes: G08G 1/096827 where the route is computed onboard
• CPC Class Codes: G08G 1/096861 where the immediate route instructions are output to the driver, e.g. arrow signs for next turn
• CPC Class Codes: H05K 999/99 dummy group

Abstract

Some embodiments provide a mapping application that has a novel way of displaying traffic congestion along roads in the map. The mapping application in some embodiments defines a traffic congestion representation to run parallel to its corresponding road portion when the map is viewed at a particular zoom level, and defines a traffic congestion representation to be placed over its corresponding road portion when the map is viewed at another zoom level. The mapping application in some embodiments differentiates the appearance of the traffic congestion representation that signifies heavy traffic congestion from the appearance of the traffic congestion representation that signifies moderate traffic congestion. In some of these embodiments, the mapping application does not generate a traffic congestion representation for areas along a road that are not congested.

Claims

1. A non-transitory machine readable medium storing a mapping program executable by at least one processing unit associated with a computing device, the program for representing traffic on a map, the program comprising sets of instructions for:

defining a linking data layer to correlate dynamic traffic data with static road data, wherein the linking data layer is represented as linking traffic tiles, the traffic data is represented as dynamic traffic tiles, and the road data is represented as static road tiles, and wherein the linking traffic tile includes linking data;

in response to a view tile request requesting a view of a portion of the map, identifying a dynamic traffic tile, a linking traffic tile, and a static road tile that corresponds to the portion;

building a first view tile using the linking traffic tile, the dynamic traffic tile, and the first static road tile; and

rendering the first view tile on the map to represent traffic congestion along the portion of the map.

2. The non-transitory machine readable medium of claim 1, wherein the linking data maps a traffic segment to a corresponding road segment.

3. The non-transitory machine readable medium of claim 1, wherein the program further comprises sets of instructions for identifying a road in a static road tile using a feature identifier field included within the linking data.

4. The non-transitory machine readable medium of claim 1, wherein the program further comprises sets of instructions for identifying a portion of a road for which traffic data is provided in a corresponding dynamic traffic tile.

5. The non-transitory machine readable medium of claim 1, wherein the linking data includes an offset field specifying a starting geometry vertex and a length field specifying a length of a road segment.

6. The non-transitory machine readable medium of claim 5, wherein the program further comprises sets of instructions for causing a mesh builder to traverse along the road segment according to the offset field and the length field to identify at least one traffic segment along the road segment.

7. The non-transitory machine readable medium of claim 1, wherein the program further comprises sets of instructions for:

selecting a feature identifier within the linking data associated with the linking traffic tile;

identifying, from within the static road tile, a road segment associated with the feature identifier;

identifying, from within the traffic tile, a traffic segment associated with the feature identifier; and

representing traffic on the road segment that corresponds to the traffic segment on the mapping application display.

8. A method implemented using a computing device, the computing device comprising a computing device display, one or more processors and a memory device, the method comprising:

defining a linking data layer to correlate dynamic traffic data with static road data, wherein the linking data layer is represented as linking traffic tiles, the traffic data is represented as dynamic traffic tiles, and the road data is represented as static road tiles, and wherein the linking traffic tile includes linking data;

in response to a view tile request requesting a view of a portion of the map, identifying a dynamic traffic tile, a linking traffic tile, and a static road tile that corresponds to the portion;

building a first view tile using the linking traffic tile, the dynamic traffic tile, and the first static road tile; and

rendering the first view tile on the map to represent traffic congestion along the portion of the map.

9. The method of claim 8, wherein the linking data maps a traffic segment to a corresponding road segment.

10. The method of claim 8, further comprising identifying a road in a static road tile using a feature identifier field included within the linking data.

11. The method of claim 8, further comprising identifying a portion of a road for which traffic data is provided in a corresponding dynamic traffic tile.

12. The method of claim 8, wherein the linking data includes an offset field specifying a starting geometry vertex and a length field specifying a length of a road segment.

13. The method of claim 12, further comprising causing a mesh builder to traverse along the road segment according to the offset field and the length field to identify at least one traffic segment along the road segment.

14. The method of claim 8, further comprising:

selecting a feature identifier within the linking data associated with the linking traffic tile;

identifying, from within the static road tile, a road segment associated with the feature identifier;

identifying, from within the traffic tile, a traffic segment associated with the feature identifier; and

representing traffic on the road segment that corresponds to the traffic segment on the mapping application display.

15. A mobile device comprising:

a display;

a storage device storing road data, traffic data, and linking traffic data;

a processor; and

a non-transitory computer readable medium storing a mapping application program comprising instructions that are executable by the processor, the program comprising instructions for;

defining a linking data layer to correlate dynamic traffic data with static road data, wherein the linking data layer is represented as linking traffic tiles, the traffic data is represented as dynamic traffic tiles, and the road data is represented as static road tiles, and wherein the linking traffic tile includes linking data;

in response to a view tile request requesting a view of a portion of the map, identifying a dynamic traffic tile, a linking traffic tile, and a static road tile that corresponds to the portion;

building a first view tile using the linking traffic tile, the dynamic traffic tile, and the first static road tile; and

rendering the first view tile on the map to represent traffic congestion along the portion of the map.

16. The device of claim 15, wherein the linking data maps a traffic segment to a corresponding road segment.

17. The device of claim 15, wherein the program further comprises instructions for identifying a road in a static road tile using a feature identifier field included within the linking data.

18. The device of claim 15, wherein the program further comprises instructions for identifying a portion of a road for which traffic data is provided in a corresponding dynamic traffic tile.

19. The device of claim 15, wherein the linking data includes an offset field specifying a starting geometry vertex and a length field specifying a length of a road segment.

20. The device of claim 19, wherein the program further comprises instructions for causing a mesh builder to traverse along the road segment according to the offset field and the length field to identify at least one traffic segment along the road segment.

21. The device of claim 15, wherein the program further comprises instructions for:

selecting a feature identifier within the linking data associated with the linking traffic tile;

identifying, from within the static road tile, a road segment associated with the feature identifier;

identifying, from within the traffic tile, a traffic segment associated with the feature identifier; and

representing traffic on the road segment that corresponds to the traffic segment on the mapping application display.