Skip to main content

django-mbtiles serves maps from MBTiles files using Django. It mainly relies on landez.

Checkout LiveMbtiles a simple maps catalog project that takes advantage of django-mbtiles.

INSTALL

Last stable version:

pip install django-mbtiles

Last development version:

pip install -e git+https://github.com/makinacorpus/django-mbtiles.git#egg=django-mbtiles

USAGE

  • Add mbtilesmap to your INSTALLED_APPS

  • Make sure you have 'django.core.context_processors.static' in your context processors

  • Include mbtilesmap urls into your project

urlpatterns = patterns('',
    ...
    ...
    url(r'^', include('mbtilesmap.urls', namespace='mb', app_name='mbtilesmap')),
)
  • Add the HTML header and call the template tag

{% load mbtilesmap_tags %}
...
{% block head %}
{% mbtilesmap_head %}
{{ block.super }}
{% endblock head %}

...
...
{% mbtilesmap filename %}

MBTiles files can be loaded from subfolders with MBTILES_ROOT setting.

{% mbtilesmap filename catalog="subfolder" %}

Example

You can find a working demo project (MBTiles maps browser livembtiles) in the example/ folder of the source tree (see dedicated README.rst file).

Cache with nginx

  • Declare a cache zone in the http section :

http {
    ...
    proxy_cache_path  /var/cache/nginx levels=1:2 keys_zone=master:10m inactive=7d max_size=1g;
    proxy_temp_path /var/tmp/nginx;
}

Cache name will be master, index will be 10m, will last 7d and have a maximum size of 1g.

  • Serve from cache for a specific location :

location @proxy {
    ...
    proxy_cache             master;
    proxy_cache_key         $$scheme$$host$$uri$$is_args$$args;
    proxy_cache_valid       200  7d;
    proxy_cache_use_stale   error timeout invalid_header;
}

See example project’s buildout for deployment automation.

AUTHORS

makinacom

LICENSE

  • Lesser GNU Public License

CHANGELOG

1.3.0 (2013-09-18)

  • Safety check if root folder is empty, with no sub-folders

  • Add grids urls in TileJSON

1.2.1 (2013-09-16)

  • Setup was zip safe, fixed it.

1.2 (2013-09-13)

  • Changed behaviour, looks for subfolders instead of multiple paths in MBTILES_ROOT

1.1 (2013-09-11)

  • Add ability to load MBTiles files from several folders

1.0

  • Initial version

Metadata

Release files for django-mbtiles 1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-mbtiles 1.3
File Size Uploaded Provenance Actions
django-mbtiles-1.3.zip 56.6 kB Without provenance Details for django-mbtiles-1.3.zip

Release files / django-mbtiles-1.3.zip

Download URL django-mbtiles-1.3.zip
Size 56.6 kB
Tags Source
SHA-256 checksum
How to use checksums
496c3daeeec8ac4b68561f1a1a994c21082fdfe2febd2426b0c4372115b86597
BLAKE2b-256 checksum
How to use checksums
fb8db09b15a01cb250e89e1ca39e11b21c45a7c3011cfc053c98352bbb2ba3fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for django-mbtiles 1.3

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page