Mapping App Traffic Rendering via Vector Tiles
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional methods for displaying traffic data on maps overlay dynamic information onto static images, leading to mismatch issues at different zoom levels, occlusion of road details, and version compatibility challenges between traffic and map data.
Innovation Solution
A mapping application that employs a novel data structure and encoding scheme to correlate static road data with dynamic traffic data, allowing for concurrent rendering of roads and traffic information, and provides a 3D perspective view with a virtual camera, while also compressing routes by removing unnecessary control points.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traffic data is overlaid on static road images, then traffic information can be displayed on the map, but the traffic data does not always perfectly match the road layout at all zoom levels
Solution Approach 1:
The patent segments the map into vector tiles that can be independently rendered at different zoom levels. Each vector tile contains geometric data that can be scaled without loss of precision, allowing traffic data to match the road layout accurately at any zoom level. This resolves the contradiction by enabling both high matching accuracy and zoom level adaptability through independent tile rendering.
Solution Approach 2:
The patent implements dynamic rendering where vector tiles are rendered in real-time based on the current zoom level and viewport. Instead of using static raster images, the system dynamically generates map sections with precise geometric relationships between roads and traffic data, ensuring accurate matching across all zoom levels while maintaining adaptability.
2Reliability
If traffic data is overlaid on static road images, then traffic information can be displayed, but the representation of traffic data often occludes the detail (e.g., names and structure of roads)
Solution Approach 1:
The patent resolves this contradiction by moving from 2D overlay to 3D spatial arrangement. Traffic features are rendered as three-dimensional objects that can be positioned above, below, or beside road features in the vertical dimension. This allows traffic information to be displayed without occluding road details, as the renderer can selectively display features based on their vertical positions and the current view angle.
3Reliability
If traffic data is tightly coupled to static road image version, then rendering consistency can be maintained, but every time a client device upgrades to a new version of the static road image, the traffic server has to upgrade the traffic data accordingly
Solution Approach 1:
The patent extracts the road geometry data from static raster images and represents it using standalone vector tile specifications. This allows traffic data to reference road geometries through stable, version-independent identifiers. When road data updates, only the vector tile definitions need to change, while traffic data remains compatible through its reference-based structure, eliminating the need for synchronized updates and improving data update efficiency.
4Adaptability or versatility
If multiple versions of static road images are supported, then compatibility with different client devices can be maintained, but the traffic server has to support multiple versions of static road images
Solution Approach 1:
The patent implements a universal vector tile format that serves as a common representation for all zoom levels and device types. Instead of maintaining separate data structures for different client versions, the system uses a single vector tile specification that can be rendered across all devices. This universal format eliminates version management complexity while maintaining broad device compatibility.
Data Source
AI summary
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.