Giorgos Sarigiannidis

A map block for Gutenberg which uses <a href="https://www.openstreetmap.org" rel="nofollow ugc">OpenStreetMap</a> and <a href="https://leafletjs.com" rel="nofollow ugc">Leaflet.js</a>. It needs no API keys and works out of the box (or, out of the Block, if you prefer). Benefiting from Gutenberg’s potential, the plugin tries a different take on how to add your locations on the map and rethinks a few things, UX-wise.
Instead of manually adding coordinates for each one of your markers, just click-and-drop them directly on the map. You want to adjust their position? Just drag them wherever you want. And instead of filling-in custom fields to set each marker’s popup content, just open that popup and start writing in it, the Gutenberg way (it supports WYSIWYG editing, with links, images, and all). It even stores the map’s zoom level as you use it so that you don’t have to set it by hand.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/FGe7zJnrIgo?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<ul>
<li><a href="https://github.com/gsarig/ootb-openstreetmap" rel="nofollow ugc">Follow the project’s development on GitHub</a></li>
<li><a href="https://github.com/gsarig/ootb-openstreetmap/releases" rel="nofollow ugc">Release history</a></li>
<li><a href="https://github.com/users/gsarig/projects/1" rel="nofollow ugc">Roadmap</a></li>
<li><a href="https://github.com/gsarig/ootb-openstreetmap?tab=readme-ov-file#hooks" rel="nofollow ugc">Hooks🪝</a></li>
<li><a href="https://github.com/gsarig/ootb-openstreetmap?tab=readme-ov-file#shortcodes" rel="nofollow ugc">Shortcodes</a></li>
</ul>
<h4>Features</h4>
<ul>
<li>No need for API keys. Just install and use it.</li>
<li>Support for multiple markers.</li>
<li>Support for a different icon per marker.</li>
<li>Support for polygons and polylines.</li>
<li>Marker clustering: group nearby markers into clusters that expand as you zoom in.</li>
<li><a href="https://www.gsarigiannidis.gr/wordpress-gutenberg-map-block-openstreetmap/" rel="nofollow ugc">Dead-simple interface</a>. Don’t search for coordinates and don’t get overwhelmed by too many fields when using multiple markers. Just point and click on the map to add your marker where you want it and edit it’s popup content directly from there.</li>
<li><a href="https://www.gsarigiannidis.gr/openstreetmap-place-search/" rel="nofollow ugc">Place search</a>. Find locations by typing keywords.</li>
<li>Remembers the zoom that you set when adding the markers and stores it so that you don’t set it by hand (which you can do anyway if you prefer).</li>
<li>AI integration which allows you to add markers by using commands in natural language. Just say “please” to activate (e.g. “Please, show me where GOT was filmed”). Requires an API key from an AI Provider, or a site-level AI connector on WordPress 7.0+. <a href="https://www.gsarigiannidis.gr/openstreetmap-openai-integration/" rel="nofollow ugc">Read more</a>.</li>
<li>Query Maps: Supports creating a map out of maps added on other posts or post types. This can be quite powerful when, for example, you have a custom post type for “Places” with each place having its own map, and you want to dynamically gather-up all the places on a single map.</li>
<li>Shortcode support: You can use the shortcode <code>[ootb_query]</code> as an alternative way to use the aforementioned Query Maps feature (see the FAQ for more info).</li>
<li>Support for a location custom field, which can be used to store a post’s or post type’s location, following the <a href="https://codex.wordpress.org/Geodata" rel="nofollow ugc">Geodata guidelines</a>. Read more in the <a href="https://github.com/gsarig/ootb-openstreetmap/releases/tag/2.8.0" rel="nofollow ugc">v.2.8.0 release notes</a>.</li>
<li>Adjust the map height.</li>
<li>Change the default marker icon with a custom one.</li>
<li>Enable or disable map dragging.</li>
<li>Enable or disable touch zoom.</li>
<li>Enable or disable double-click zoom.</li>
<li>Enable or disable scroll wheel zoom.</li>
<li>Set a minimum and maximum limit that the user can zoom on the frontend. Setting the same value to both fields will lock the zoom at that level.</li>
<li>Support for other Layer Providers: MapBox (using your own API key) and Stamen.</li>
<li>Option to export locations in a JSON file</li>
<li>Option to import locations from a JSON file</li>
</ul>

Out of the Block: OpenStreetMap

Just because we don't need an API license key, and we can have multiple pins per map among other things, for me this is the best mapping block. And of course, the plugin works exactly as advertised.

Until now, I was using my own map block I had created with ACF Pro, but that was just simple Google Map embed, which again did not require an API key, but was restricted to one pin per map, and of course no live data like traffic and other visuals, along with no street view.

Well done, and thank you,
Nick.

The best map block


In 5 minutes I had a map with a marker. Easy!


Loved it!

A map block for Gutenberg using OpenStreetMap and Leaflet that needs no API keys and works out of the box. Or should we say, ...Out of the Block?

axelkeller

Displays a GPX track as segmented polylines, the way points and the elevation profile. 
Open Street Map (OSM) is used as background which can be switched between a plane view and a topographic one. 
The view can be changed to full screen mode. Moving the cursor over the elevation profile the corresponding point is marked on the path interactively.
GPX tracks uploaded to the server in advance are stored into separate repositories that are ordered according to the categories setup in wordpress. 
Thus different collections of tracks can be handled and the tracks choosen from.
During upload a GPX track can be smoothed and/or its elevation data replaced by Open-Elevation Service data. 
The latter is provided because many elevation data tracked by mobiles are not quite correct.
GPX trackpoints can be edited on the map interactively.
Features
<ul>
<li>Admin page GPX Files for uploading tracks 
– Selecting category for repository 
– Replacing the description of the track (tag <code><name></code> in the GPX file) 
– Smoothing tracks during upload, thus reducing track points 
– Replacing elevation data of track points using Open-Elevation Service during upload</li>
<li>Display of a specific, uploaded GPX track 
– PHP-function for inserting the view into a page 
– Selecting full screen mode and scaling the map 
– Switching between plane and topographic view</li>
<li>Editing trackpoints on the map 
– Adding, moving, deleting track points 
– creating, splitting polylines</li>
<li>Display of a list of GPX files from which a track can be selected 
– separated list for each category 
– Setting width and color of the path 
– Shortcode for inserting the list into a page</li>
<li>Elevation profile 
– Interactive path marker 
– Name of the track 
– Distance of the track 
– Maximum/minimum elevation 
– Elevation loss/gain 
– Trail duration</li>
</ul>

GPX Viewer

Display GPX tracks with their elevation profile on OSM maps, edit them interactively

Out of the Block: OpenStreetMap vs GPX Viewer