Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time



  • Clone this repo

  • Use pip to install the code:

    pip install --editable .

    (The --editable flag is optional, but very useful in development)

GDAL dependencies

Providing GDAL requires packaging the dependencies GDAL binaries and deps + Python bindings

The repository is shipped with a pre-packaged wheel (GDAL-2.4.0-cp36-cp36m-manylinux1_x86_64.whl) ready to be installed witht he following command:

pip install GDAL-2.4.0-cp36-cp36m-manylinux1_x86_64.whl

The wheel has been built from running the following commands:

git clone
cd gdalmanylinux
make wheel

The command will generete a set of wheels - one for each supported Python version - under gdalmanylinux/wheels directory.

AWS lambdas deployment

In a nutshell, run:

zappa deploy smbbackend  # the first time
zappa update smbbackend  # subsequent deployments
set-lambda-env smbbackend

The lambdas can be deployed with zappa. Check the zappa_settings.json file for more details on available stages.

Deploy a lambda to aws with the following:

zappa deploy smbbackend  # first time deployment
zappa update smbbackend  # subsequent deployments
zappa undeploy smbbackend  # remove deployment

Environment variables

The AWS console can be used to set environment variables for each lambda function. In addition, the smbbackend/ file may also be used. It works by looking at the current local environment and searching for variables with a special naming. These vars are pushed to the lambda's environment.

This file is also installed as a console script named set-lambda-env when you install this package with pip.

  • Set local environment variables with the following naming convention:

  • Run the script, providing the name of the zappa stage an argument


For setting the DB_HOST=somehost env variable for the savemybike-ingesttrack-dev lambda, you would do the following:


Alternatively you could define all environment files in a file, then export all variables to the current environment and finally run the script


The current zappa configuration expects to find the following environment variables:


Although it is possible to specify these in the zappa configuration file, we keep their definition outside of it in order to keep the config more portable

Using test data

The tests/data directory contains a spatialite DB with some test data. This data can be loaded by running:

convert-spatialite --output_dir /tmp tests/data/smb_test_data.sqlite

DB_HOST="<db-host>" \
DB_NAME="<db-name>" \
DB_USER="<db-user>" \
DB_PASSWORD="<db-password>" \
DB_PORT="<db-port>" \
ingest-tracks <uuid-of-the-user-who-will-own-tracks> /tmp/track_1.csv /tmp/track_2.csv

The convert-spatialite and inges-tracks scripts become available when the package is installed via pip. They can be combined in order to provide test data to multiple users