Map Data Server Indoor Outdoor Transition Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current digital mapping applications cannot seamlessly transition between outdoor and indoor map data, leading to delayed display of indoor information and lack of interactive controls for multi-floor buildings until indoor data is fully loaded.

Innovation Solution

A map data server provides metadata with indoor map data as part of the base map, including vector data for building footprints and metadata about the number of floors, allowing the client device to display a widget for selecting floors and reposition the viewport smoothly during transitions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If indoor map data is provided as a separate layer requiring separate requests, then data organization is simplified, but display transition speed and user interaction responsiveness deteriorate

Engineering Contradiction:
Improvedata organizationVSAvoiddisplay transition speed
Core Design Contradiction:
Device complexityVSSpeed

Solution Approach 1:

The patent merges indoor map data with outdoor base map data into a single integrated data structure. The indoor map data is embedded within the same response as the base map, allowing the mapping application to receive both datasets simultaneously without requiring separate requests or waiting for additional data loads, thus resolving the contradiction between simplified organization and fast transition.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent applies preliminary action by providing indoor map data metadata and bounding box information along with the base map data before the user actually needs to view indoor content. This allows the mapping application to prepare indoor map displays and controls in advance, enabling immediate transition when the user zooms into a building footprint.

Inventive Principle:
Principle #10Preliminary action

2Ease of manufacture

If indoor map data is loaded separately after zooming into building footprint, then data loading is simpler, but user interaction capability deteriorates

Engineering Contradiction:
Improvedata loading simplicityVSAvoiduser interaction capability
Core Design Contradiction:
Ease of manufactureVSEase of operation

Solution Approach 1:

The server performs preliminary actions by including indoor map data metadata, bounding box definitions, and floor information in the initial base map response. This allows the mapping application to immediately display floor selection controls and indoor map previews without waiting for additional data loads, maintaining ease of operation while keeping data loading simple through a single integrated response.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary layer of metadata and bounding box information that bridges the gap between simple data loading and rich user interaction. This intermediary data structure enables the mapping application to prepare and display indoor map controls immediately, facilitating seamless user interaction without complex separate loading processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If widget for floor selection is displayed only after indoor data loading, then data structure remains simple, but interface responsiveness deteriorates

Engineering Contradiction:
Improvedata structureVSAvoidinterface responsiveness
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The server performs preliminary actions by embedding floor selection metadata, bounding box information, and indoor map data identifiers in the initial base map response. This allows the mapping application to immediately render the floor selection widget and indoor map controls without waiting for additional data loads, eliminating delays while maintaining a simple integrated data structure.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the indoor map data response into distinct components (metadata, bounding box information, floor data, map features) that can be independently processed and displayed. This segmentation allows the mapping application to immediately display the floor selection widget using the metadata while simultaneously preparing to load detailed indoor map features, improving interface responsiveness without complicating the overall data structure.

Inventive Principle:
Principle #1Segmentation

4Device complexity

If viewport repositioning waits for indoor data loading, then data synchronization is simpler, but transition smoothness deteriorates

Engineering Contradiction:
Improvedata synchronizationVSAvoidtransition smoothness
Core Design Contradiction:
Device complexityVSStability of the object's composition

Solution Approach 1:

The server provides preliminary viewport repositioning information through bounding box definitions included in the base map response. This allows the mapping application to immediately calculate and execute smooth viewport transitions to indoor map views without waiting for detailed indoor data to load, maintaining simple data synchronization while achieving stable, smooth transitions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies dynamics by enabling the viewport to dynamically reposition based on bounding box information received with the base map data. The mapping application can smoothly animate the viewport transition to the indoor map view immediately, creating a fluid user experience while keeping data synchronization simple through pre-provided positioning coordinates.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9417777B2Enabling quick display transitions between indoor and outdoor map data
Publication Date: 2016.08.16 GOOGLE LLC
  • US9417777B2 patent drawing
  • US9417777B2 patent drawing
  • US9417777B2 patent drawing

AI summary

A map data server may provide metadata about available indoor map data that accompanies map data for drawing a base map. For example, map data may include vector data for drawing a footprint of a building, and the metadata may include information about the physical properties of the building (e.g., an indication of how many floors the building has and if detailed map data is available for the indicated floors, etc.). A mapping application running on the client can use this metadata to display an interface that allows a user to select floors or otherwise interact with the floor data. Further, the metadata accompanying map data can include a bounding box, or a bounding polygon, for one or more floors. The mapping application can use these bounding shapes to properly reposition the viewport as map data for a new floor is being loaded, for example.