Open Data vs. Open Source: Scaling Spatial Metadata & AI Workflows | Amy Rose

Amy Rose (CTO of the Overture Maps Foundation) joins the podcast to explore the structural differences between open-source software and open data. Amy breaks down how Overture—founded by AWS, Meta, Microsoft, and TomTom—builds interoperable global map layers, resolves complex entity definitions across disparate datasets, and why modern agentic AI workflows require record-level metadata rather than dataset-level summaries. 🗽 Catch Us in New York! Ready to explore open data, high-performance computing, and enterprise AI architecture? Join us at OSFF New York on November 4–5, 2026.🎟️ Register Now: https://hubs.ly/Q04n_bZL0🔥 20% OFF DISCOUNT CODE: 26YTOSFFNY20C 🕒 Timestamps:4:36 Interview Start: Amy Rose & The Overture Maps Foundation6:43 From Landscape Architecture to GIS: Amy's Career Journey11:05 Real-World Geo Applications: Transportation, Disaster Recovery & Oak Ridge Lab14:02 What is Overture Maps? Building Interoperable Global Map Data15:38 Open Source Software vs. Open Source Data17:13 Defining High-Quality Data: Fitness for Purpose & Use Cases18:39 Case Study: Built Environment Mapping & Entity Resolution24:05 Why Agentic AI Workflows Require Record-Level Metadata29:45 The Monthly Release Engine: GERS IDs, Bridge Files & Change Logs34:08 Solving Spatial Interoperability: Geometric Joins & Entity Matching42:05 The Future: Native Location Integration in Enterprise AI 📊 The Problem: The Open Data Lineage & Interoperability ChallengeUnlike open-source software—where source code acts as a single point of truth—open data requires merging disparate, opinionated input sources with varying licenses, coordinate systems, and quality levels. Traditional dataset-level metadata fails when applied to autonomous systems or agentic AI workflows, which parse and combine individual records rather than entire tables. Furthermore, performing spatial joins and resolving duplicate entities across different municipal or corporate datasets creates massive computational and manual overhead. 🏗️ The Solution: Overture's GERS Infrastructure & Record-Level MetadataAmy Rose outlines how Overture Maps standardizes global spatial data: Global Entity Reference System (GERS): Assigning persistent, canonical GERS IDs to physical entities (buildings, places, roads) to maintain lineage and bridge external datasets (e.g., Esri, Meta, Microsoft, Google). Record-Level Provenance: Embedding metadata (source, license, transformation steps, coordinate reference frames) directly into individual records rather than appending summary text at the dataset level. Monthly Aggregated Releases: Distributing prepackaged monthly releases alongside bridge files and change logs, allowing downstream consumers to verify fitness for purpose in navigation, logistics, or risk modeling. ⚙️ Why This Matters for Financial & Technical ArchitectureVerifiable Risk & Asset Modeling: Provides clean, open spatial foundations for underwriting flood risk, supply chain logistics, ESG impact, and real estate valuation without expensive manual data wrangling. Trusted AI Agent Evidence: Equips AI models and automated agents with explicit record-level evidence, making spatial queries verifiable and reproducible. 🌐 More about FINOS: https://www.finos.org/ 📧 Join our newsletter: https://www.finos.org/sign-up 🎙️ Listen to our Open Source in Finance Podcast: https://www.youtube.com/@FINOS/podcasts LinkedIn: https://www.linkedin.com/company/finosfoundation#FINOS #OSFFNewYork #OvertureMaps #OpenData #GIS #Metadata #AgenticAI #DataEngineering #SpatialData