Adds a searchable trip planner with place search, waypoint ordering, route previews, and Google Maps handoff links.

acodebeard

<p>Waypoints: Trip Planner adds a configurable trip-planning interface to a page or<br />
post. Visitors can search Google place results, add stops to a waypoint list,<br />
reorder their trip, preview the route when map embeds are configured, and open<br />
the finished route in Google Maps.</p>
<h3>Credits</h3>
<p>Special thanks to <a href="https://github.com/hagan" rel="nofollow ugc">Hagan</a> and<br />
<a href="https://github.com/datapoke" rel="nofollow ugc">Datapoke</a> for development help.</p>
<h3>Configuration</h3>
<p>Manage settings in Settings > Waypoints: Trip Planner.</p>
<p>Current settings include:</p>
<ul>
<li>Default location label, address/search phrase, latitude, longitude, and Place ID.</li>
<li>Allowed start modes, max waypoints, result count, distance unit, map preview,<br />
and Google Maps handoff toggles.</li>
<li>Editable categories and interface copy.</li>
<li>Browser-facing Maps Embed API key.</li>
<li>Server-side Places API and Geocoding API keys.</li>
<li>Google API timeout and cache TTLs.</li>
<li>Rate-limit value and trusted proxy CIDRs for public endpoint protection.</li>
<li>Admin-only API call counter for troubleshooting request behavior.</li>
</ul>
<h3>External services</h3>
<p>Waypoints: Trip Planner uses Google services for place results, place details,<br />
geocoding, embedded map previews, and Google Maps handoff links.</p>
<p>The plugin can send data to Google from the server when:</p>
<ul>
<li>a visitor runs a category or custom place search</li>
<li>the plugin geocodes a configured or visitor-provided starting area</li>
<li>the plugin resolves selected waypoint place details</li>
</ul>
<p>The plugin can also send data to Google from the visitor’s browser when:</p>
<ul>
<li>the frontend loads a Google Maps Embed preview from <code>https://www.google.com/maps/embed/v1/search</code> or <code>https://www.google.com/maps/embed/v1/directions</code></li>
<li>a visitor opens the generated Google Maps handoff link</li>
</ul>
<p>Depending on the interaction, data sent to Google can include:</p>
<ul>
<li>search phrases</li>
<li>configured or visitor-provided starting locations</li>
<li>selected Google Place IDs</li>
<li>visitor IP address and the browser-facing Maps Embed API key when the browser loads an embedded map preview</li>
<li>origin text plus waypoint and destination Place IDs when the browser loads an embedded directions preview</li>
<li>route waypoint information needed to build map previews or handoff URLs</li>
</ul>
<p>Google provides these services. Review their terms and privacy information:</p>
<ul>
<li>https://policies.google.com/privacy</li>
<li>https://cloud.google.com/maps-platform/terms</li>
</ul>


Alternatives to Waypoints: Trip Planner

Top alternatives