Pelican plugin to embed OpenStreetMap maps in Markdown articles using a {% place %} shortcode.

These details have not been verified by PyPI

Project description

pelican-osm

pelican-osm is a Pelican plugin that embeds interactive OpenStreetMap maps into your articles using a simple {% place %} shortcode. It integrates with Leaflet.js and loads place data from YAML files.

Features

{% place %} shortcode renders an independent interactive map per shortcode
{% place_list %} shortcode renders a sortable table of places with tag filtering, row count, optional grouping, and multi-level collapsible summary headers
Multi-value fields (e.g. multiple visit dates) render as joined cells with sort behaviour configurable via JSON Schema hints
YAML files converted to GeoJSON at build time — JS fetches them at runtime
Flexible spec syntax: single file, single place via #id, entire folder, or comma-separated mix
File-level metadata (anime title, tags, country…) applied as defaults to every place in the file
Per-place popup with auto-generated OSM and Google Maps links
tags list rendered as clickable badges — click to filter the table by tag
urls list rendered as labelled links in the popup and list table
All extra YAML fields displayed in the popup automatically
Horizontal scroll photo gallery in popups with lightbox viewer (swipe on mobile)
Optional marker clustering via Leaflet.markercluster (auto-detected)
Lazy map initialization — maps only load when scrolled into view
Reset view button (↺) to return to the original map bounds
Deep linking — link directly to a place via URL hash (e.g. page.html#place_id)
Error/empty state messages when data fails to load
Auto-detects <html lang> for built-in translations (zh, ja), with full override via window.OSM_I18N
Optional JSON Schema validation for place YAML — drop a _schema.yaml next to your files and the plugin enforces it at build time
Fully class-based CSS — every visual detail overridable via custom properties
Dark mode support

How it works

content/places/japan/mygo.yaml   →   output/static/places/japan/mygo.geojson
                                              ↑
                              browser fetches at runtime via Leaflet

Each YAML file under OSM_PLACES_ROOT is converted to a GeoJSON FeatureCollection at build time. The {% place %} shortcode emits a <div> with data-geojson pointing to the corresponding file(s); the bundled JS fetches and renders them.

Installation

pip install pelican-osm

Setup

1. Add to pelicanconf.py

PLUGINS = ["pelican.plugins.osm"]

2. Add Leaflet.js and plugin assets to your base template

<link rel="stylesheet" href="https://unpkg.com/leaflet/dist/leaflet.css">
<script src="https://unpkg.com/leaflet/dist/leaflet.js"></script>

<!-- Plugin assets — auto-copied to output/static/pelican_osm/ on build -->
<link rel="stylesheet" href="/static/pelican_osm/css/osm-map.css">
<script src="/static/pelican_osm/js/osm-map.js" defer></script>

3. Organize your YAML files

Set the root path in pelicanconf.py (default: places/ inside your content folder):

OSM_PLACES_ROOT = "places"  # relative to PATH (content dir), or absolute

Both .yml and .yaml extensions are supported.

content/
└── places/
    ├── taiwan.yml
    └── japan/
        ├── mygo.yaml
        └── ave-mujica.yml

YAML format

locations format (preferred)

The locations key holds the list of places. Every other top-level key becomes a file-level default applied to all places in the file — per-place values always win.

# content/places/japan/mygo.yaml
anime: BanG Dream! It's MyGO!!!!!
tags: [動畫]

locations:
  - id: normal_park
    name: 豊島区立南池袋第二公園
    lat: 35.7225
    lon: 139.7170
    category: 公園
    notes: "「普通」和「理所當然」是什麼呢？"
    date: 2023-06-29
    country: 日本
    city: 東京
    tags: []       # overrides file-level tags for this place
    images: []

Empty strings ("") and empty lists ([]) are automatically stripped — they won't appear in the popup or GeoJSON.

Dict of places (also supported)

The reserved defaults key spreads shared attributes. Each other top-level key is a place id usable in #fragment references.

defaults:
  country: Japan

ueno_park:
  name: 上野公園
  lat: 35.7142
  lon: 139.7742
  date: 2024-03-25

shinjuku:
  name: 新宿
  lat: 35.6938
  lon: 139.7034

Bare list (backwards compatible)

- name: 台北101
  lat: 25.0337
  lon: 121.5645

- name: 太魯閣
  lat: 24.1558
  lon: 121.6213

A leading {defaults: {...}} item sets shared attributes for the whole file.

Shortcode syntax

Each {% place %} shortcode renders its own independent map.

Syntax	Result
`{% place japan/mygo.yaml %}`	All places in one file
`{% place japan/mygo.yaml#normal_park %}`	Single place by id (dict-format key)
`{% place japan/mygo.yaml#豊島区立南池袋第二公園 %}`	Single place by name (fallback)
`{% place japan/ %}` or `{% place japan %}`	All YAML files in a folder, recursively
`{% place . %}`	All YAML files under the root
`{% place japan/mygo.yaml, taiwan.yml %}`	Multiple specs on one map
`{% place_list japan/mygo.yaml %}`	Renders a table of places from one or more YAML specs.

{% place_list japan/tokyo %}
{% place_list japan/tokyo, japan/kyoto %}

Note: Fragment (#) syntax filters which places appear in the popup, but the map still fetches the full GeoJSON file. A future version may support per-feature filtering.

Grouping and summary headers (`place_list`)

{% place_list %} accepts kwargs to bucket rows under shared field values and to surface those values as section headers:

{% place_list pilgrimage group_by="country,city" group_summary_at="country,city" aggregate="date:year" %}

Kwarg	Description
`group_by`	Comma-separated fields. Places sharing the same tuple of these values are bucketed contiguously so the table reads as a tree. Rows are preserved as-is unless `aggregate` is also given.
`aggregate`	`field:op` pairs, comma-separated. Setting this opts into SQL-style collapse: rows sharing a `group_by` tuple merge into one, with the listed fields aggregated (e.g. `year` collects unique years, sorted ascending and comma-joined), other fields taking first-non-empty, and `tags` unioned.
`group_summary_at`	A prefix of `group_by`. Listed fields are removed from data-row columns and emitted as section headers above each group.

When group_summary_at lists multiple fields, each level renders as a nested heading: depth-0 most prominent, deeper levels smaller and indented, each with its own background colour. A subtotal place count appears under every level (configurable via OSM_LIST_GROUP_COUNT_TEMPLATE).

Headers are interactive:

Click a header (or focus + Enter / Space) to collapse its subtree; click again to expand.
Each header has a stable id="osm-group--<slug>" for deep linking — e.g. page.html#osm-group--japan--tokyo. Loading the page with that hash auto-expands all ancestor groups so the target row is visible.

Sorting a column re-orders data rows within each leaf group; group-header rows stay pinned in their YAML/define order so the hierarchy is preserved.

Schema-driven `place_list` hints

The same _schema.yaml you use for validation also drives several display behaviours of {% place_list %}. The schema is loaded at render time for whatever spec the shortcode targets, so you only need to declare each hint once next to the field definition.

# content/places/pilgrimage/_schema.yaml
$schema: "https://json-schema.org/draft/2020-12/schema"
type: object
properties:
  date:
    type: array
    items: { type: string, format: date }
    title: 日期               # ← column header
    x-osm-list-join: ", "     # ← separator for list cells
    x-osm-list-sort: max      # ← canonical sort key (most-recent visit)
  category:
    type: string
    title: 分類
  internal_order:
    type: integer
    x-osm-list-hidden: true   # ← loaded but never rendered as a column

Hint	Values	Effect
`title`	any string	Column header text. Standard JSON Schema keyword.
`x-osm-list-hidden`	`true` / `false`	Drop this field from the table. It's still loaded, so `group_by` / `aggregate` / sort can use it. Works for `tags` / `urls` too.
`x-osm-list-join`	any string (default `", "`)	Separator between list items when a field holds a list (e.g. multiple visit dates).
`x-osm-list-sort`	`min` / `max` / `first` / `last`	Sets the cell's `data-sort-value` so column sorting picks one canonical key. `max` = most-recent visit drives the sort.
`x-osm-list-i18n`	`{ title: { <lang>: <string> } }`	Per-language overrides for `title`. Looked up by the article's `Lang` (or `DEFAULT_LANG`) — full match first (`zh-tw`), then primary subtag (`zh`). Falls through to `title` when nothing matches.

hall:
  type: string
  title: 影廳                    # ← default-locale fallback
  x-osm-list-i18n:
    title:
      en: Hall
      ja: スクリーン

Precedence for column labels: x-osm-list-i18n.title.<lang> → schema.title → OSM_LIST_FIELD_LABELS → auto-derived from key.

x- prefixed keys are JSON Schema's standard extension namespace, so validators ignore them silently. Scalar values render unchanged — datetime.date becomes ISO string, lists are joined per x-osm-list-join.

Nested items: one place, many sub-rows

When a place has multiple variants that share its location — halls within a cinema, seasonal menus at a restaurant, courses on a trail — declare them under an items: list. The map renders one pin per place (items ignored); {% place_list %} flattens, emitting one row per item with parent fields cascaded in.

# content/places/theaters/taiwan.yaml
vieshow-songren:
  name: 松仁威秀影城
  lat: 25.0368737
  lon: 121.5679503
  address: 台北市信義區松仁路58號10樓
  country: 臺灣
  city: 臺北
  district: 信義
  items:
    - hall: "6 廳（TITAN）"
      format: 一般 2D 廳
      recommended_rows: G
      hall_note: 一般 2D 最好的廳
    - hall: "2 廳"
      format: 一般 2D 廳
      recommended_rows: E

Items contract: name, lat, and lon are parent-only — they describe the shared place identity and location, so by definition every item under one parent shares them. If an item dict supplies any of these, the plugin warns and drops it (parent's value wins). Items wanting their own identity column should use a distinct field (hall, course, season, …); other fields cascade with item winning on collision, and tags are unioned (parent first).

The canonical pattern for rendering a tree where each parent is a section header:

{% place_list theaters group_by="country,city,name" group_summary_at="country,city,name" %}

You get headers at country / city / theater, one row per hall under each theater header, and a single map pin per cinema on the map. Without aggregate, group_by only buckets rows for tree rendering — items keep their own values per row.

When name lives in group_summary_at, the plugin hoists it into the section header (alongside the place's 🗺️·📍 map links) and drops the Name column from data rows — each row is then identified by its item-specific field (hall etc.) instead of repeating the parent name.

JSON Schema for items lives under properties.items.items.properties — those title / x-osm-list-* hints are merged in alongside parent-level hints (item-level wins on collision).

Multi-value fields

Want to record multiple visits to the same place? Just write the field as a list:

- name: 某神社
  lat: 35.7
  lon: 139.7
  date: [2024-01-15, 2025-03-12]

The cell joins to 2024-01-15, 2025-03-12. With x-osm-list-sort: max, sorting "Date" descending puts your most-recent visit first.

Place fields

Field	Required	Notes
`name`	✅	Popup title and map caption
`lat`	✅	Latitude (float)
`lon`	✅	Longitude (float)
`tags`	—	List — rendered as inline badges in the popup
`images`	—	List — rendered as a photo gallery in the popup
`urls`	—	List — rendered as links in the popup and list table; see below
(any)	—	All other fields shown as `Key: Value` lines

OSM and Google Maps links are always auto-generated from lat/lon.

`urls` field

The urls field renders clickable links in both the map popup and the place_list table. Three formats are accepted:

# plain string
urls: "https://example.com/my-post"

# single object with optional label
urls:
  label: "2024"
  href: "{filename}posts/review/2024/my-post.md"

# list of objects (multiple links)
urls:
  - label: "2023"
    href: "{filename}posts/review/2023/visit.md"
  - label: "2024"
    href: "{filename}posts/review/2024/visit.md"

The label becomes the link text. When omitted, the link text falls back to the URL's hostname (e.g. example.com).

{filename} references are resolved to absolute URLs using Pelican's content URL map.

GeoJSON output

Every YAML file is converted to a GeoJSON FeatureCollection at build time, mirroring the source directory structure:

content/places/japan/mygo.yaml   →   output/static/places/japan/mygo.geojson
content/places/taiwan.yml        →   output/static/places/taiwan.geojson

The GeoJSON files are standard RFC 7946 and can be used with any GeoJSON-compatible tool (QGIS, Mapbox, etc.).

Configuration

Setting	Default	Description
`OSM_SHORTCODE`	`"place"`	Shortcode tag name
`OSM_PLACES_ROOT`	`"places"`	Root folder for YAML files (relative to `PATH`)
`OSM_MAP_HEIGHT`	`"400px"`	Map height (any CSS length value)
`OSM_MAP_TILE`	OSM standard tiles	Leaflet tile URL template
`OSM_MAP_ATTRIBUTION`	OSM attribution HTML	Attribution string shown on the map
`OSM_STATIC_PREFIX`	`"/static"`	URL prefix for generated GeoJSON files
`OSM_LIST_SHORTCODE`	`"place_list"`	Shortcode name
`OSM_LIST_FIELDS`	`[]` (auto)	Ordered list of field keys to show as columns. When empty, all non-reserved fields found in the data are used.
`OSM_LIST_FIELD_LABELS`	`{}`	Override column header labels, e.g. `{"date": "Visited", "name": "Place"}`
`OSM_LIST_GROUP_COUNT_TEMPLATE`	auto-detected from `Lang` / `DEFAULT_LANG`	Format string for the per-group subtotal under `group_summary_at` headers. `{n}` is the place count. Built-in defaults: `"{n} 個地點"` (`zh`), `"{n} 件"` (`ja`), `"{n} places"` (other). Set to `""` to omit, or to any string to override.
`OSM_VALIDATE_SCHEMA_FILENAMES`	`["_schema.yaml", "_schema.yml", "_schema.json"]`	Filenames the validator looks for. Accepts a string or list.
`OSM_VALIDATE_STRICT`	`False`	Raise `RuntimeError` on validation failure instead of just logging warnings.
`OSM_DISABLE_MARKDOWN_PROTECTION`	`False`	Disable the Markdown preprocessor that shields `{% ... %}` shortcodes from the `attr_list` extension. Only set this if you have a conflicting extension at preprocessor priority 25 — without protection, two shortcodes on adjacent lines can be silently mangled by `attr_list` (bundled with `markdown.extensions.extra`).

Schema validation

Place YAML can be validated against a JSON Schema at build time. Validation is opt-in by file presence — drop a _schema.yaml (or .yml/.json) anywhere under OSM_PLACES_ROOT and the plugin will validate every place YAML in the same folder and its subfolders. No schema present → no validation runs.

1. Install the optional dependency

pip install "pelican-osm[validate]"

If schema files exist but jsonschema isn't installed, the plugin logs a warning and skips validation (your build still succeeds).

2. Drop a schema next to your YAML files

content/places/
├── _schema.yaml              ← applies to every YAML below
├── restaurant.yaml
└── pilgrimage/
    ├── _schema.yaml          ← overrides the parent for this folder
    ├── yuru-camp.yaml
    └── tamako-market.yaml

The plugin uses nearest-ancestor lookup: a YAML is validated against the closest _schema.yaml walking up the directory tree.

3. Example schema

# content/places/pilgrimage/_schema.yaml
$schema: "https://json-schema.org/draft/2020-12/schema"
type: object
required: [anime, locations]
properties:
  anime: {type: string}
  tags:  {type: array, items: {type: string}}
  locations:
    type: array
    items:
      type: object
      required: [name, lat, lon, country, city]
      additionalProperties: false
      properties:
        name:     {type: string, minLength: 1}
        lat:      {type: number, minimum: -90,  maximum: 90}
        lon:      {type: number, minimum: -180, maximum: 180}
        category: {type: string}
        notes:    {type: string}
        date:     {type: string, format: date}
        country:  {type: string}
        city:     {type: string}
        tags:     {type: array, items: {type: string}}
        images:   {type: array, items: {type: string}}

Files starting with _ (e.g. _schema.yaml) are never loaded as place data — they're skipped by both the resolver and the GeoJSON exporter.

Unquoted dates (date: 2026-02-22) are normalized to ISO 8601 strings before validation, so schemas can use type: string, format: date even though PyYAML parses them as datetime.date.

By default, validation failures are logged as warnings. Set OSM_VALIDATE_STRICT = True to raise a RuntimeError and fail the build instead.

Deep linking

Link directly to a specific place by appending its id or name as a URL hash:

https://example.com/my-post.html#normal_park
https://example.com/my-post.html#豊島区立南池袋第二公園

The map will pan to the marker and open its popup automatically. When marker clustering is enabled, the cluster is expanded first.

Tag filtering

Tag badges are clickable in both maps and tables.

In {% place_list %} tables: Clicking a tag filters the table to show only rows with that tag. A filter chip appears next to the row count — click it (or click the same tag again) to clear the filter.

In {% place %} maps: A tag bar appears below the map when places have tags. Click a tag to show only markers with that tag; click again to show all. The map automatically re-fits to the visible markers.

Marker clustering

Leaflet.markercluster is automatically loaded from CDN at runtime. Nearby markers are grouped into clusters that expand on click/zoom. No extra setup is needed.

Customising the CSS

All visual properties are CSS custom properties declared on :root. Override in your own stylesheet (loaded after osm-map.css):

/* Change map height globally */
:root {
  --osm-map-height: 300px;
}

/* Remove rounded corners and shadow */
.osm-map-block {
  --osm-radius: 0;
  --osm-shadow: none;
}

Available custom properties

Property	Default	Controls
`--osm-map-height`	`400px`	Map canvas height
`--osm-radius`	`8px`	Block border radius
`--osm-shadow`	`0 2px 8px …`	Block drop shadow
`--osm-caption-bg`	`#f5f5f5`	Caption bar background
`--osm-caption-color`	`#555`	Caption text colour
`--osm-caption-font-size`	`0.9em`	Caption font size
`--osm-caption-padding`	`0.4em 0.8em`	Caption padding
`--osm-caption-border`	`1px solid #ddd`	Caption top border
`--osm-popup-min-width`	`200px`	Popup minimum width
`--osm-popup-font-size`	`1.3em`	Popup base font size
`--osm-popup-line-height`	`1.6`	Popup line height
`--osm-popup-name-size`	`1.15em`	Place name font size
`--osm-popup-name-weight`	`700`	Place name font weight
`--osm-popup-name-gap`	`0.35em`	Gap below place name
`--osm-badge-font-size`	`0.82em`	Badge font size
`--osm-badge-padding`	`0.15em 0.6em`	Badge padding
`--osm-badge-radius`	`999px`	Badge border radius
`--osm-badge-tag-bg`	`#e8e8e8`	Tag badge background
`--osm-badge-tag-color`	`#444`	Tag badge text colour
`--osm-field-gap`	`0.15em`	Vertical gap between field rows
`--osm-field-color`	`#333`	Field value colour
`--osm-label-color`	`#111`	Field label colour
`--osm-label-weight`	`600`	Field label font weight
`--osm-links-gap`	`0.65em`	Gap above links row
`--osm-links-font-size`	`0.9em`	Links row font size
`--osm-links-color`	`#666`	Links row text colour
`--osm-links-anchor-color`	`#c0392b`	OSM / Google anchor colour

i18n

The plugin auto-detects the page language from <html lang="..."> and applies built-in translations when available. Currently supported: zh (Traditional Chinese), ja (Japanese). All other languages fall back to English.

You can override any string by setting window.OSM_I18N before loading osm-map.js. Manual overrides take priority over auto-detected translations.

<script>
window.OSM_I18N = {
  // Map link labels (defaults: "OSM", "Google")
  osmLink:      "OSM",
  googleLink:   "Google",

  // Place count label below tables (receives row count as argument)
  placeCount:   (n) => `${n} 個地點`,

  // Error/empty state messages
  loadError:    "無法載入地圖資料",
  noPlaces:     "找不到地點",

  // Fallback link text for urls entries with no label.
  // Defaults to the URL's hostname (e.g. "example.com").
  // Only used when the hostname cannot be parsed.
  urlLinkLabel: "Link",

  // Field label overrides — YAML key → display label
  // Unlisted keys fall back to capitalised key name (e.g. "category" → "Category")
  fieldLabels: {
    date:     "日期",
    location: "地點",
    category: "分類",
    type:     "分類",
    work:     "作品",
    series:   "系列",
    note:     "備註",
    notes:    "備註",
    anime:    "作品",
    city:     "城市",
    country:  "國家",
  },
};
</script>
<script src="/static/pelican_osm/js/osm-map.js" defer></script>

fieldLabels is shallow-merged — only list the keys you want to change.

Available i18n keys

Key	Default (en)	Description
`osmLink`	`"OSM"`	OSM link label in popups and tables
`googleLink`	`"Google"`	Google Maps link label
`placeCount`	`(n) => "N places"`	Row count below tables (function)
`loadError`	`"Failed to load map data"`	Shown when all GeoJSON fetches fail
`noPlaces`	`"No places found"`	Shown when no markers match
`urlLinkLabel`	`"Link"`	Fallback text for unlabelled URLs
`fieldLabels`	`{}`	YAML key to display label mapping

License

MIT © Wei Lee

Project details

These details have not been verified by PyPI

Release history Release notifications | RSS feed

This version

0.11.0

Apr 30, 2026

0.10.0

Apr 29, 2026

0.9.0

Apr 29, 2026

0.8.0

Apr 28, 2026

0.7.0

Apr 25, 2026

0.6.0

Apr 19, 2026

0.5.1

Apr 18, 2026

0.5.0

Apr 18, 2026

0.4.2

Mar 26, 2026

0.4.1

Mar 26, 2026

0.4.0

Mar 25, 2026

0.3.1

Mar 14, 2026

0.3.0

Mar 14, 2026

0.2.0

Feb 17, 2026

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pelican_osm-0.11.0.tar.gz (45.5 kB view details)

Uploaded Apr 30, 2026 Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

pelican_osm-0.11.0-py3-none-any.whl (46.1 kB view details)

Uploaded Apr 30, 2026 Python 3

File details

Details for the file pelican_osm-0.11.0.tar.gz.

File metadata

Download URL: pelican_osm-0.11.0.tar.gz
Upload date: Apr 30, 2026
Size: 45.5 kB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for pelican_osm-0.11.0.tar.gz
Algorithm	Hash digest
SHA256	`8f7d413095d6637ddbb72dcffd7f7025983ad8887f8f72f0ede82bef064d136a`
MD5	`998396152c06607e4d2cb1d52dde54f0`
BLAKE2b-256	`230f6ff60dc480d32757490205287f88bbe123922edb025fbb50f7a45c3c7a05`

See more details on using hashes here.

Provenance

The following attestation bundles were made for pelican_osm-0.11.0.tar.gz:

Publisher: publish-to-pypi.yaml on Lee-W/pelican-osm

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: pelican_osm-0.11.0.tar.gz
- Subject digest: 8f7d413095d6637ddbb72dcffd7f7025983ad8887f8f72f0ede82bef064d136a
- Sigstore transparency entry: 1409462156
- Sigstore integration time: Apr 30, 2026
Source repository:
- Permalink: Lee-W/pelican-osm@4b928334b44e3e49072bf4f0b23d23cc1ffc007c
- Branch / Tag: refs/tags/0.11.0
- Owner: https://github.com/Lee-W
- Access: public
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: publish-to-pypi.yaml@4b928334b44e3e49072bf4f0b23d23cc1ffc007c
- Trigger Event: push

File details

Details for the file pelican_osm-0.11.0-py3-none-any.whl.

File metadata

Download URL: pelican_osm-0.11.0-py3-none-any.whl
Upload date: Apr 30, 2026
Size: 46.1 kB
Tags: Python 3
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for pelican_osm-0.11.0-py3-none-any.whl
Algorithm	Hash digest
SHA256	`0430ee4fc7a7c98cd1e1ddfe36d6dcb8b58b33d02397f0ef9a78cdf8db60040c`
MD5	`9123aefa76ed651d4262b03ab3d76f21`
BLAKE2b-256	`8f800ff7a05eec001ba3b43d8637e3bf348c4af17ebdd634be73b711054991f3`

See more details on using hashes here.

Provenance

The following attestation bundles were made for pelican_osm-0.11.0-py3-none-any.whl:

Publisher: publish-to-pypi.yaml on Lee-W/pelican-osm

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: pelican_osm-0.11.0-py3-none-any.whl
- Subject digest: 0430ee4fc7a7c98cd1e1ddfe36d6dcb8b58b33d02397f0ef9a78cdf8db60040c
- Sigstore transparency entry: 1409462168
- Sigstore integration time: Apr 30, 2026
Source repository:
- Permalink: Lee-W/pelican-osm@4b928334b44e3e49072bf4f0b23d23cc1ffc007c
- Branch / Tag: refs/tags/0.11.0
- Owner: https://github.com/Lee-W
- Access: public
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: publish-to-pypi.yaml@4b928334b44e3e49072bf4f0b23d23cc1ffc007c
- Trigger Event: push

pelican-osm 0.11.0

Navigation

Verified details

Maintainers

Unverified details

Meta

Classifiers

Project description

pelican-osm

Features

How it works

Installation

Setup

1. Add to pelicanconf.py

2. Add Leaflet.js and plugin assets to your base template

3. Organize your YAML files

YAML format

locations format (preferred)

Dict of places (also supported)

Bare list (backwards compatible)

Shortcode syntax

Grouping and summary headers (place_list)

Schema-driven place_list hints

Nested items: one place, many sub-rows

Multi-value fields

Place fields

urls field

GeoJSON output

Configuration

Schema validation

1. Install the optional dependency

2. Drop a schema next to your YAML files

3. Example schema

Deep linking

Tag filtering

Marker clustering

Customising the CSS

Available custom properties

i18n

Available i18n keys

License

Project details

Verified details

Maintainers

Unverified details

Meta

Classifiers

Release history Release notifications | RSS feed

Download files

Source Distribution

Built Distribution

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

Grouping and summary headers (`place_list`)

Schema-driven `place_list` hints

`urls` field