SVG Floorplan Metadata Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional building floorplan navigation systems are inefficient and error-prone due to the need for separate files for visual representation and metadata, requiring tedious updates when changes are made to the floorplan, especially when resizing or repositioning elements.

Innovation Solution

The use of Scalable Vector Graphics (SVG) format to encapsulate building floorplans and metadata, allowing for dynamic display and real-time updating of metadata alongside graphical elements, enabling interactive editing and synchronization within a single program.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate files are used for visual representation and metadata, then the floorplan system can store and retrieve information, but the system becomes complex and error-prone when updates are needed

Engineering Contradiction:
Improvesynchronization accuracyVSAvoidfile management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines the visual floorplan representation and metadata into a single integrated SVG file format. Each graphical element in the SVG contains embedded metadata attributes (such as room numbers, coordinates, and dimensions) directly associated with its visual components. This eliminates the need for separate metadata files and manual synchronization processes, thereby reducing file management complexity while improving synchronization accuracy between visual elements and their corresponding data.

Inventive Principle:
Principle #5Merging (Combining)

2Ease of manufacture

If manual updates are performed in separate metadata files, then changes can be made to floorplan data, but the process becomes tedious and error-prone

Engineering Contradiction:
Improveediting easeVSAvoidupdate time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The SVG-based system enables self-service updating where modifications to visual elements automatically update their associated metadata. When a user edits a graphical element's position, size, or other attributes in the SVG file, the corresponding metadata is updated automatically through the integrated structure. This eliminates the need for manual metadata updates in separate files, significantly reducing update time and effort while maintaining data accuracy.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If image resizing is performed, then the floorplan can be adapted to different displays, but separate coordinate scaling is required which is tedious and error-prone

Engineering Contradiction:
Improvedisplay adaptabilityVSAvoidcoordinate accuracy
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The SVG format provides dynamic scaling capability where coordinate systems automatically adjust when the floorplan is resized. The integrated metadata structure contains coordinate information that scales proportionally with visual elements, eliminating the need for manual coordinate rescaling. This dynamic adaptation maintains coordinate accuracy across different display sizes while preserving the adaptability of the floorplan to various screen resolutions and dimensions.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10956497B1Use of scalable vector graphics format to encapsulate building floorplan and metadata
Publication Date: 2021.03.23 UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA)
  • US10956497B1 patent drawing
  • US10956497B1 patent drawing
  • US10956497B1 patent drawing

AI summary

Disclosed herein are embodiments of systems, methods, and products comprises an analytic server, which uses scalable vector graphic (SVG) format to encapsulate building floorplan and metadata. The analytic server creates a floorplan map in SVG format that includes both a graphic map and a specification file. When a user issues an information request by clicking on one graphical element, the analytic server determines the object identifier of the clicked graphical element, queries the specification file to receive metadata about the clicked graphical element based on the object identifier, and renders a user interface to display the metadata about the graphical element. When the user modifies the graphical element, the analytic server determines new data of the graphical element and updates the corresponding object metadata with the new data in the specification file.