Embed GPX traces directly in Jekyll/Octopress posts and pages. Uses Leaflet to display maps.
Disclaimer: minimalistic work from a ruby noob, definitely open to suggestions
gpx_trace.rb in the (_)plugins directoryleaflet-custom.css in the source/stylesheets directoryleaflet.html in the source/_includes directory{% if page.enable_gpx_traces %}{% include leaflet.html %}{% endif %} to source/_includes/custom/head.html which loads Leaflet on pages that require itleaflet_tile_url and leaflet_tile_attrib properties in _config.yml to Leaflet tile URL template (directly embedding API key and style ID in the URL rather than using templating) and attribution. For low traffic OpenStreetMap tiles may be used, larger sites should use alternate servicesFirst define a template for the map, for example at _traces/my_template.tpl:
{% for track in gpx.tracks %}
{% assign id = helper.unique_id %}
<figure>
<div class="leaflet-custom bigmap" id="{{ id }}"></div>
<figcaption>{{ track.name }}</figcaption>
</figure>
<script>$(function() {
var bounds;
var map = L.map('{{ id }}');
var segment;
{% for segment in track.segments %}
segment = {{ segment.points_json }};
bounds = bounds ? bounds.extend(segment) : new L.LatLngBounds(segment);
L.polyline(segment, {color: 'red'}).addTo(map);
{% endfor %}
map.fitBounds(bounds);
L.tileLayer('{{ helper.tile_url }}', { attribution: '{{ helper.tile_attrib }}', maxZoom: 18 }).addTo(map);
})</script>
{% endfor %}
The template receives arguments:
gpx: the GPX trace as an objecthelper: a helper object containing tile configuration and ways to obtain unique map identifiersPages that include traces must declare it in Jekyll's front-matter:
---
enable_gpx_traces: true
---
and the custom tag can be used any number of times in the page:
{% gpx_trace _traces/track.gpx _traces/my_template.tpl %}
with arguments being:
source directorysource directory