Map Rendering Tracking Table Reduces Vertex Data Bandwidth
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current digital map rendering techniques using vector image data are processor-intensive and require high bandwidth due to the need to transmit and re-transmit redundant vertex data points, which increases processing time and bandwidth requirements.
Innovation Solution
An image rendering system that employs a tracking table to store and reuse frequently used vertex data points, using a vector code to identify and retrieve these points from a tracking table instead of re-transmitting them, thereby reducing data transmission and processing load.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If vector image data is used to render digital map images, then image flexibility and scalability are improved, but processing time and bandwidth requirements increase
Solution Approach 1:
The system pre-processes and stores vertex data in a tracking table before rendering operations. By organizing vertex data in advance and identifying frequently used vertices, the system reduces the computational burden during actual rendering, thus decreasing processing time while maintaining vector image flexibility
Solution Approach 2:
The system applies different processing strategies to different parts of the vector data. Frequently used vertices are identified and stored in a tracking table for quick access, while other vertices are processed normally. This localized optimization reduces overall processing time without compromising the flexibility of the entire vector image system
2Measurement precision
If vector image data with high detail is transmitted, then image quality is improved, but bandwidth requirements increase
Solution Approach 1:
The system identifies and discards redundant vertex data by storing frequently used vertices in a tracking table. When the same vertices are needed again, they are recovered from the tracking table instead of being re-transmitted, thus reducing bandwidth requirements while maintaining high image quality
Solution Approach 2:
Instead of re-transmitting identical vertex data, the system creates references or pointers to vertices already stored in the tracking table. This copying mechanism allows high-detail images to be rendered with reduced data transmission, as the actual vertex data is shared across multiple image objects
3Reliability
If redundant vertex data points are re-transmitted, then data completeness is improved, but data transmission volume increases
Solution Approach 1:
The system performs preliminary identification of frequently used vertices and stores them in a tracking table before transmission. This advance preparation ensures that redundant vertex data is recognized and eliminated, maintaining data completeness while reducing transmission volume
Solution Approach 2:
The tracking table acts as an intermediary between the vector image data and the transmission process. It stores frequently used vertices and provides them to the rendering system without requiring re-transmission, thus ensuring data completeness while minimizing transmission volume
Data Source
AI summary
A graphics or image rendering system, such as a map image rendering system, receives image data from an image database, such as a map database, in the form of vector data having image object elements defined as sets of vertex data points. The image rendering system stores and tabulates the vertex data points used to render an image object element. A code specifies a number of vertex data points that can be obtained from a tracking table as well as an amount of vertex data points to be sent from the image database. An image rendering engine uses the stored and transmitted vertex data points to render the image object element to be displayed.