OpenFLAME: A Federated Spatial Naming Infrastructure

TL;DR

OpenFLAME tackles the problem of restricted, centralized spatial maps by introducing a federated mapping infrastructure built around map servers and zones. It leverages DNS to implement a scalable discovery layer and uses S2-based geo-domains to support location-aware registration and querying across overlapping map coverings. The work delivers a map-centric design with concrete DNS records (MAPSERVER, MAPZONE, MAPDS) and end-to-end services for tile rendering, geocoding, routing, and localization, demonstrated through a DNS-based prototype and evaluation against centralized baselines. This federated approach enables indoor and outdoor mapping with privacy, incremental deployment, and cross-organization collaboration, potentially transforming spatial applications like AR and robotics by democratizing map data and services.

Abstract

Spatial applications, i.e., applications that tie digital information with the physical world, have improved many of our daily activities, such as navigation and ride-sharing. This class of applications also holds significant promise of enabling new industries such as augmented reality and robotics. The development of these applications is enabled by a system that can resolve real-world locations to names, or a spatial naming system. Today, mapping platforms provided by organizations like Google and Apple serve as spatial naming systems. These maps are centralized and primarily cover outdoor spaces. We envision that future spatial applications, such as persistent world-scale augmented reality, would require detailed and precise spatial data across indoor and outdoor spaces. The scale of cartography efforts required to survey indoor spaces and their privacy needs inhibit existing centralized maps from incorporating such spaces into their platform. In this paper, we present the design and implementation of OpenFLAME stands for Open Federated Localization and Mapping Engine, a federated spatial naming system, or in other words, a federated mapping infrastructure. It enables independent parties to manage and serve their own maps of physical regions. This unlocks scalability of map management, isolation, and privacy of maps. The discovery system that identifies maps hosted at a given location is a primary component of our system. We implement OpenFLAME on top of the existing Domain Name System (DNS), which enables us to leverage its existing infrastructure. We implement map services such as address-to-location mapping, routing, and localization on top of our federated mapping infrastructure.

Figures (20)

• Figure 1: Centralized map architecture.
• Figure 2: OpenFLAME architecture.
• Figure 3: OpenFLAME data organization and query model.
• Figure 4: S2 cell covering for a given map boundary.
• Figure 5: Converting S2 cell index to geo-domain.