lektor-leaflet-geojson
Lektor template filter to convert geojson objects to Leaflet maps
Installation
pip install lektor-leaflet-geojson
Usage
Import the leaflet JS and CSS. You can skip this step if you are managing Leaflet yourself (e.g: with NPM)
{{ import_leaflet('1.7.1') }} {# using a specified version #}
{{ import_leaflet() }} {# default to "latest" #}
The |map() filter can be used to render a GeoJSON feature on a map. Pass some inline CSS to style the map div.
{{
'{"type": "Feature", "geometry": {"type": "Point", "coordinates": [125.6, 10.1]}}' | map("height: 300px; width: 300px;")
}}
Metadata
Release files for lektor-leaflet-geojson 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lektor_leaflet_geojson-0.3.0.tar.gz | 2.9 kB | With provenance | Details for lektor_leaflet_geojson-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lektor_leaflet_geojson-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for lektor_leaflet_geojson-0.3.0-py3-none-any.whl |
Total release size: 6.8 kB
Release files / lektor_leaflet_geojson-0.3.0.tar.gz
| Download URL | lektor_leaflet_geojson-0.3.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccc9d3a15a1bd415afecb8affb55f2e2f6e51edcb3f86330d093b436cc0fdbf9
|
|
BLAKE2b-256 checksum How to use checksums |
48b150631f35adfe82a9700bb3f9b17d81ef2e2f9d89674f8a22c95c68d7033c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logRelease files / lektor_leaflet_geojson-0.3.0-py3-none-any.whl
| Download URL | lektor_leaflet_geojson-0.3.0-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9cbe36efe2d7122dbb92e6b5b0272b1fe3239e3f1ad6ece9433dfe189d12a38a
|
|
BLAKE2b-256 checksum How to use checksums |
06f4a8d88f3433c62c588f68ab2becd7b5c70c0945709cab72bfc17f19932d6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logSecurity for lektor-leaflet-geojson 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for lektor_leaflet_geojson-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.