Landez builds MBTiles files either from a remote tile service URL or from a local Mapnik stylesheet.
The land covered is specified using a list of bounding boxes and zoom levels.
It uses mbutil from Mapbox https://github.com/mapbox/mbutil at the final stage to build the MBTiles file.
INSTALL
Landez requires nothing but python remote mode (specifying a tiles URL), but requires mapnik if the tiles are drawn locally.
sudo aptitude install python-mapnik
USAGE
Remote tiles
Using a remote tile service (Cloudmade by default):
import logging
from landez import MBTilesBuilder
logging.basicConfig(level=logging.DEBUG)
mb = MBTilesBuilder(remote=True, cache=False)
mb.add_coverage(bbox=(-90.0, -180.0, 180.0, 90.0),
zoomlevels=[0, 1])
mb.run()
Please respect Tile usage policies <http://wiki.openstreetmap.org/wiki/Tile_usage_policy>
Local rendering
Using mapnik to render tiles:
import logging
from landez import MBTilesBuilder
logging.basicConfig(level=logging.DEBUG)
mb = MBTilesBuilder(stylefile="yourstyle.xml", filepath="dest.mbtiles")
mb.add_coverage(bbox=(-90.0, -180.0, 180.0, 90.0),
zoomlevels=[0, 1])
mb.run()
LICENSE
Lesser GNU Public License
8 maintainers
Metadata
8 maintainers
Release files for landez 1.1
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 |
|---|---|---|---|---|
| landez-1.1.tar.gz | 8.1 kB | Without provenance | Details for landez-1.1.tar.gz |
Release files / landez-1.1.tar.gz
| Download URL | landez-1.1.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ba15531eea1c94e201e67145a3eb9954c02c7fac81e8c9a49cd7e80bc28204e
|
|
BLAKE2b-256 checksum How to use checksums |
e400cdd05337aae52ed4711bdbd84550eed24954d3c30fd0f92a71c24bcaf78e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for landez 1.1
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.
