<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Stadia Maps Newsletter</title>
        <link>https://stadiamaps.com/blog/</link>
        <description>The Stadia Maps newsletter: product news, new features, and highlights from our blog and changelog.</description>
        <lastBuildDate>Tue, 30 Jun 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Stadia Maps Newsletter</title>
            <url>https://stadiamaps.com/images/og/stadia-maps-1200x630-og.png</url>
            <link>https://stadiamaps.com/blog/</link>
        </image>
        <copyright>© 2026 Stadia Maps, Inc.</copyright>
        <atom:link href="https://stadiamaps.com/blog/newsletter/rss.xml" rel="self" type="application/rss+xml"/>
        <item>
            <title><![CDATA[The Stadia Maps Newsletter №15 – June 2026]]></title>
            <link>https://stadiamaps.com/blog/june-2026-newsletter</link>
            <guid isPermaLink="false">https://stadiamaps.com/blog/june-2026-newsletter</guid>
            <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Two new leaders join Stadia Maps, updated changelog with RSS feed, and latest blog posts on water features, routing privacy, and transportation alternatives.]]></description>
            <content:encoded><![CDATA[<p><img src="https://stadiamaps.com/images/og/june-2026-newsletter.png" alt="The Stadia Maps Newsletter №15 – June 2026" /></p><hr><h2 id="welcome-to-our-growing-leadership-team">Welcome to Our Growing Leadership Team</h2><p>Building a company around a conviction that maps are critical infrastructure, not an ad product, takes a particular kind of person, and two of them just joined Stadia Maps. Rob Yoegel and Rick Myers both spent years at Linode (now Akamai), building a developer-loved business in a market full of cynical alternatives. <a href="https://stadiamaps.com/blog/two-leaders-join-stadia-maps/">Read the full announcement here.</a></p><h2 id="explore-our-platform">Explore Our Platform</h2><ul><li><a href="https://docs.stadiamaps.com/" rel="external" target="_blank">API Documentation</a></li><li><a href="https://stadiamaps.com/products/">Platform Features &#x26; Overview</a></li><li><a href="https://stadiamaps.com/blog/">Company Blog</a></li></ul><hr><h2 id="we-updated-our-changelog-yes-really">We Updated Our Changelog (Yes, Really)</h2><p>Moving forward, we're committing to keeping it current. If you want updates without checking back manually, <a href="https://stadiamaps.com/changelog/">our changelog now has a long-overdue RSS feed</a>, too.</p><hr><h2 id="latest-from-our-blog">Latest From Our Blog</h2><h3 id="how-we-fixed-water-feature-rendering-across-all-zoom-levels-in-our-basemaps"><a href="https://stadiamaps.com/blog/fixing-missing-water-interactive-basemaps/">How We Fixed Water Feature Rendering Across All Zoom Levels in Our Basemaps</a></h3><p>We shipped a significant update to the data pipeline behind our Interactive Basemaps. The change fixes a class of visual inconsistencies at low- and mid-zoom levels, such as missing rivers, shifting coastlines, islands that suddenly appear, and major water features that pop into detail abruptly rather than transitioning smoothly.</p><h3 id="the-invisible-costs-of-routing-privacy-pricing-and-avoiding-the-mau-trap"><a href="https://stadiamaps.com/blog/invisible-costs-of-routing-privacy-pricing-mau-trap/">The Invisible Costs of Routing: Privacy, Pricing, and Avoiding the "MAU" Trap</a></h3><p>Beyond performance, the long-term viability of any motor vehicle routing project hinges on two "invisible" variables: data privacy architecture and billing predictability. Stadia Maps eliminates the risks of third-party data harvesting and "MAU"-based pricing traps by providing a private-by-design infrastructure and transparent, usage-only billing.</p><h3 id="beyond-the-car-routing-for-the-other-90-of-transport"><a href="https://stadiamaps.com/blog/beyond-the-car-routing-for-specialized-fleets/">Beyond the Car: Routing for the Other 90% of Transport</a></h3><p>Standard "car-first" routing APIs often fail to account for the unique legal and physical constraints of specialized fleets. Stadia Maps bridges this gap by leveraging the Valhalla routing engine and OpenStreetMap data to provide granular, modal-specific routing for everything from 10-ton trucks and e-bikes to low-speed vehicles (LSVs).</p><h3 id="why-basic-openstreetmap-routing-needs-real-time-traffic"><a href="https://stadiamaps.com/blog/why-osm-routing-needs-real-time-traffic/">Why Basic OpenStreetMap Routing Needs Real-Time Traffic</a></h3><p>OpenStreetMap (OSM) provides a world-class geographic foundation, but it remains a static dataset. Without real-time traffic integration, routing engines must rely on algorithmic proxies like road class and legal speed limits, which often lead to unreliable ETAs and logistics bottlenecks.</p><hr><h2 id="whats-coming-next">What's Coming Next</h2><p>In our next issue, we'll start a new blog series on Geocoding &#x26; Search and introduce a new feature highlighting some of our customers.</p><p><em>— Luke, Ian, and the entire Stadia Maps team</em></p><hr><p>Have feedback or questions? <a href="https://stadiamaps.com/support/">We'd love to hear from you.</a></p>]]></content:encoded>
            <category>Stadia Maps Newsletter</category>
            <category>Mapping Infrastructure</category>
            <category>Routing APIs</category>
            <category>Basemaps</category>
            <category>Geocoding</category>
            <category>Developer Platform</category>
            <enclosure url="https://stadiamaps.com/images/og/june-2026-newsletter.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>