Mapillary Python SDK
Mapillary's official Python SDK for GeoSpatial Data
Explore the docs »
View Demo
·
Report Bug
·
Request Feature
·
See Documentation
Table Of Contents
About
Mapillary's Python SDK provides an easy mechanism for accessing and retrieving information from Mapillary's web application.
For more information, please visit Mapillary and Mapillary's Blog.
Getting Started
Installation
To get started, simply install mapillary by running,
pip install mapillary
A quick demo,
"""
Getting image coordinates from a nearby set of coordinates
"""
# Importing mapillary
import mapillary.interface as mly
# JSON import
import json
# Get image points close to in the given coordinates
data = mly.get_image_close_to(longitude=31, latitude=30).to_dict()
# Save the data as JSON
file_name = "get_image_close_to_1.json"
with open(file_name, mode="w") as f:
json.dump(data, f, indent=4)
You can check out all the implemented functionality from the demo.
Or you can check out the documentation!
Development
Formatting/Linting
To run the formatter black, and the linter flake8, run,
flake8 mapillary & black mapillary
Or, if you are on Linux, you can simply run,
make style
This runs the style policy from the Makefile.
Dev Setup
Aliases for setting up the environment have been provided in Makefile to reduce burden of replication.
The steps to execute are, in order of running them,
make setup-dev: Install developer dependenciesmake build: Build the packagemake local-install: Install package locally in the dev environment
To use the new package installed locally, first use pipenv to change into the environment that the package was installed into by running,
pipenv shell
Then run,
python # assuming running python opens the Python3 shell
Then import and use as required,
# import package here
import mapillary.interface as mly
# more code to follow here
Trouble shooting
If you get messed up dependencies, feel free to delete the Pipfile.lock file with rm Pipfile.lock, then start again with the first step in Dev Setup.
If you ever need to start with a clean build, you can always run make clean which will clean the dist directory, then you can simply start again from the second step in Dev Setup.
Upgrading A Package
If you upgrade any package in Pipfile, be sure to run pipenv install to update the Pipfile.lock as well.
Possible Issues
Failed installation/dev setup because of libgeos_c.so or libgeos_c_1.so
With UNIX based systems, you would to install the `geos` package with you package manager.
In debian systems, sudo apt install geos.
In arch based systems, sudo pacman -S geos.
Contributing
We welcome contributions! See CONTRIBUTING for details on how to get started, and our code of conduct.
Acknowledgements
- Christopher Beddow - for leading the project
- Saif Ul Islam - for developing the SDK under MLH fellowship
- Omar Ali - for developing the SDK under MLH fellowship
Links
More About Mapillary
Legal
3 maintainers
Release files for mapillary 1.0.16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mapillary-1.0.16.tar.gz | 121.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mapillary-1.0.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 191.8 kB
Release files / mapillary-1.0.16.tar.gz
| Download URL | mapillary-1.0.16.tar.gz |
|---|---|
| Size | 121.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3dc86f05cf8fc944e0d93b75c1a7ac42a844dec82aa617b600953ce992534f1f
|
|
BLAKE2b-256 checksum How to use checksums |
4740989003f2c88d23ac644eeb07fa9997f6aafeaea4fabe0c14ff994dc73a28
|
| 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 Sep 8, 2026.
Transparency logRelease files / mapillary-1.0.16-py3-none-any.whl
| Download URL | mapillary-1.0.16-py3-none-any.whl |
|---|---|
| Size | 69.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be80537fdffb055ab7ac43181de6dfba4030f93806ac900d147030ff457ee557
|
|
BLAKE2b-256 checksum How to use checksums |
2ca07d4bdbb23d8ee1edf6710f2e07d192d49e80357dec5a0246cc728edee290
|
| 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 Sep 8, 2026.
Transparency log
