<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Maps on Pi Stack</title><link>https://www.pistack.xyz/tags/maps/</link><description>Recent content in Maps on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/maps/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Hosted Geospatial &amp; Mapping Servers: Nominatim, TileServer GL &amp; GeoServer Guide 2026</title><link>https://www.pistack.xyz/posts/self-hosted-geospatial-mapping-servers-nominatim-tileserver-gl-geoserver-guide-2026/</link><pubDate>Fri, 17 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/self-hosted-geospatial-mapping-servers-nominatim-tileserver-gl-geoserver-guide-2026/</guid><description>&lt;p>Building location-aware applications means relying on maps, geocoding, and spatial data. The default path for most developers is Google Maps Platform — geocoding APIs, tile servers, routing engines, all billed per request. But when your application scales, those costs multiply fast. More importantly, you hand over your entire location data pipeline to a single vendor.&lt;/p></description></item></channel></rss>