Annotation of map geometry vertices

• US 9,489,754 B2
• Filed: 09/30/2012
• Issued: 11/08/2016
• Est. Priority Date: 06/06/2012
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Arikan, Okan, Dumont, Vincent
• Primary Examiner(s): Hoang, Peter
• Application Number:
  US13/631,999
• Publication Number:
  US 20130328915A1
• Time in Patent Office: 1,500 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G01C 21/3815 Road data
• CPC Class Codes: G01C 21/3819 Road shape data, e.g. outline of a route
• CPC Class Codes: G01C 21/3867 Geometry of map features, e.g. shape points, polygons or for simplified maps
• CPC Class Codes: G01C 21/387 Organisation of map data, e.g. version management or database structures
• CPC Class Codes: G01C 21/3878 Hierarchical structures, e.g. layering
• CPC Class Codes: G01C 21/3881 Tile-based structures
• CPC Class Codes: G06T 11/00 2D [Two Dimensional] image generation
• CPC Class Codes: G06T 11/20 Drawing from basic elements, e.g. lines or circles
• CPC Class Codes: G06T 11/60 Editing figures and text; Combining figures or text
• CPC Class Codes: G06T 17/05 Geographic models
• CPC Class Codes: G06T 7/0004 Industrial image inspection
• CPC Class Codes: G09G 5/00 Control arrangements or circuits for visual indicators common to cathode-ray tube indicators and other visual indicators image data processing or generation, in general G06T

Abstract

Some embodiments provide a method for a mapping service. The method receives a set of road segments for a map region. For each road segment in the set, the method generates a geometry that includes a set of vertices that define a boundary for the road segment. The geometries are included as part of a map tile for the map region. The map tiles are for downloading to user devices that render map presentations using the geometries. For several of the vertices, the method stores data with the vertices that specifies for the device at least one aspect of rendering the road for the map presentation.

Claims

1. A non-transitory machine readable medium storing a program for execution by at least one processing unit, the program comprising sets of instructions for:

at a set of servers, receiving a set of road segments for a map region;

for each road segment in the set of road segments;

generating a geometry comprising a plurality of vertices that define a boundary for the road segment, wherein the geometries are included as part of a map tile for the map region, the map tiles for downloading to user devices that render map presentations using the geometries; and

storing data with a set of at least two of the vertices specifying for the user device at least one aspect for rendering, for the map presentation, the boundary of the road segment defined by the vertices, wherein the data stored for a first one of the vertices specifies a first set of stylistic characteristics for rendering a first portion of the boundary of the road segment and the data stored for a second one of the vertices specifies a second set of stylistic characteristics for rendering a second portion of the boundary of the road segment, wherein at least one stylistic characteristic in the second set of stylistic characteristics is different than stylistic characteristics in the first set of stylistic characteristics.

2. The non-transitory machine readable medium of claim 1, wherein data stored for a particular vertex specifies for the user device to render a type of road casing.

3. The non-transitory machine readable medium of claim 1, wherein data stored for a particular vertex specifies for the device to render a curb along a side of the road.

4. The non-transitory machine readable medium of claim 3, wherein data stored for the particular vertex further specifies a height for the curb.

5. The non-transitory machine readable medium of claim 1, wherein data stored for a particular vertex specifies for the device to render a sidewalk along a side of the road.

6. The non-transitory machine readable medium of claim 5, wherein data stored for the particular vertex further specifies a width for the sidewalk.

7. The non-transitory machine readable medium of claim 1, wherein data stored for a particular vertex specifies for the device to render a bridge casing with a shadow underneath a side of the road.

8. The non-transitory machine readable medium of claim 7, wherein the particular vertex is part of a geometry for a road segment that passes over another road segment.

9. The non-transitory machine readable medium of claim 7, wherein data stored for the particular vertex further specifies a height for the bridge casing.

10. The non-transitory machine readable medium of claim 1, wherein data stored for a particular vertex specifies that a side of the road segment is internal to a road and for the device to not render a road casing for the side.

11. The non-transitory machine readable medium of claim 1, wherein the first vertex specifies the first set of stylistic characteristics for rendering the first portion of the boundary extending from the first vertex to the second vertex, wherein the second vertex is subsequent to the first vertex.

12. The non-transitory machine readable medium of claim 11, wherein the first vertex is on the first portion of the boundary of the road segment, wherein a third vertex on a third portion of the boundary of the road segment specifies a third set of stylistic characteristics for rendering the third portion of the boundary extending from the third vertex to the first vertex.

13. The non-transitory machine readable medium of claim 1, wherein each vertex specifies the stylistic characteristics of a corresponding portion of the boundary that starts at the vertex and emanates a particular direction from the vertex.

14. The non-transitory machine readable medium of claim 13, wherein each boundary portion that starts at a particular vertex ends at a next vertex that does not specify the stylistic characteristics of the boundary portion.

15. The non-transitory machine readable medium of claim 1, wherein at least one vertex of the plurality of vertices has two boundary portions connected to the vertex, wherein the vertex specifies the stylistic characteristics of one of said boundary portions and the stylistic characteristics of the other boundary portion connected to the vertex is specified by a different vertex.

16. A method for defining geometries for roads in a map region, the method comprising:

defining a geometry for a particular road segment, the geometry comprising a set of vertices connected by edges, each vertex associated with a single edge;

specifying a first set of stylistic characteristics for a first edge of the geometry by annotating a first vertex associated with the first edge; and

specifying a second set of stylistic characteristics for a second edge of the geometry by annotating a second vertex associated with the second edge, wherein at least one stylistic characteristic in the first set of stylistic characteristics is different than stylistic characteristics in the second set of stylistic characteristics and at least one stylistic characteristic in the second set of stylistic characteristics is different than stylistic characteristics in the first set of stylistic characteristics.

17. The method of claim 16, wherein the different stylistic characteristics between the first and second sets of stylistic characteristics specify different types of road casings for the edges of the road segment geometry.

18. The method of claim 16, wherein the road segment is for downloading and rendering by a mapping application running on a user device.

19. The method of claim 18, wherein the mapping application renders the first edge differently than the second edge based on the differences between the first and second sets of stylistic characteristics.

20. The method of claim 18, wherein the mapping application renders the first edge with a curb and the second edge without a curb based on the differences between the first and second sets of stylistic characteristics.

21. A system comprising:

a set of processing units for executing sets of instructions; and

a non-transitory machine readable medium for storing a program which when executed by at least one of the processing units generates map tiles, the program comprises sets of instructions for;

defining a road graph from a set of road segments and a set of junctions;

generating geometries for road segments in the road graph, each of the geometries comprising a plurality of vertices that define a boundary for a corresponding road segment; and

for each road segment, specifying a set of non-positional properties of the boundary for the road segment in the vertices of the geometry for the road segment, wherein at least two vertices of a particular geometry for a particular road segment each contain different sets of non-positional properties with respect to each other.

22. The system of claim 21, wherein the specified non-positional properties comprise different road casings for a user device to render when rendering the road segment.

23. The system of claim 22, wherein the set of instructions for specifying non-positional properties of the boundary of the road segment comprises a set of instructions for specifying different road casings for different types of road segments.