<?xml version="1.0" encoding="UTF-8"?><rss 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" version="2.0"><channel><title><![CDATA[Make more than 100 million people happy... by genuinely importing all the carpooling areas mapped on OpenStreetMap!]]></title><description><![CDATA[<p dir="auto">The carpooling areas mapped with the tags "amenity=parking" + "carpool=yes/designated" in OpenStreetMap display properly on Mapy.com. However, all those tagged with "amenity=car_pooling" are missing, and they are significantly more numerous.</p>
<p dir="auto">There are currently 2,643 of them (<a href="https://taginfo.openstreetmap.org/tags/amenity=car_pooling" target="_blank" rel="noopener noreferrer nofollow ugc">https://taginfo.openstreetmap.org/tags/amenity=car_pooling</a>). For comparison, "the carpool=*" tag is only used 1,972 times on OSM (<a href="https://taginfo.openstreetmap.org/keys/carpool" target="_blank" rel="noopener noreferrer nofollow ugc">https://taginfo.openstreetmap.org/keys/carpool</a>). By not supporting this "amenity=car_pooling" tag, more than half the time, looking for a carpooling area on Mapy.com ends in failure</p>
<p dir="auto">Yet, in many countries, this mode of transport is massively popular! The BlaBlaCar app alone has over 100 million users (including 20 million in France alone). As a result, these carpooling hubs are very heavily used, and it is a real shame that users have to switch to a different GPS app to find them.<br />
Would it be possible to include this tag in an upcoming data update?</p>
]]></description><link>https://community.mapy.com/topic/2276/make-more-than-100-million-people-happy...-by-genuinely-importing-all-the-carpooling-areas-mapped-on-openstreetmap</link><generator>RSS for Node</generator><lastBuildDate>Tue, 01 Sep 2026 06:52:06 GMT</lastBuildDate><atom:link href="https://community.mapy.com/topic/2276.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 31 Aug 2026 21:05:50 GMT</pubDate><ttl>60</ttl></channel></rss>