Skip to content
aequilibrae - Python package for transportation modeling
Branch: master
Clone or download
Latest commit 292048c Jun 18, 2019

README.rst

AequilibraE

AequilibraE is the first comprehensive Python package for transportation modeling, and it aims to provide all the resources not easily available from other open-source packages in the Python (NumPy, really) ecosystem.

Project status

https://travis-ci.org/AequilibraE/aequilibrae.svg?branch=master https://coveralls.io/repos/github/AequilibraE/aequilibrae/badge.svg?branch=master Documentation Status

What is available

  • Synthetic gravity/IPF
  • Traffic assignment
  • Network Skimmin & node-to-node path computation
  • Fast Matrix format based on NumPy
  • GTFS Import

What is available only in QGIS

Some common resources for transportation modelling are inherently visual, and therefore they make more sense if available within a GIS platform. For that reason, many resources are available only from AequilibraE's QGIS plugin, which uses AequilibraE as its computational workhorse and also provides GUIs for most of AequilibraE's tools. Said tool is developed independently, although in parallel, and more details can be found in its GitHub repository.

What is not available yet

  • GTFS exporters
  • Traffic assignment
  • Thorough documentation
  • AEQ Project

What is not planned to be available any time soon

As AequilibraE's focus is to provide resources that are not yet available in the open source world, particularly the Python ecosystem, some important tools for transportation model won't be part of AequilibraE any time soon. Examples of this are:

History

Before there was AequilibraE, there was a need for something like AequilibraE out there.

The very early days

It all started when I was a student at UCI-ITS and needed low level access to outputs of standard algorithms used in transportation modelling (e.g. path files from traffic assignment) and had that denied by the maker of the commercial software he normally used. There, the first scratch of a traffic assignment procedure was born. After that, there were a couple of scripts developed to implement synthetic gravity models (calibration and application) that were develop for a government think-tank in Brazil IPEA. Around the same time, another student needed a piece of code that transformed a GIS link layer into a proper graph, where each link would become the connection between two nodes. So there were three fundamental pieces that would come to be part of AequilibraE.

The first take on a release software

Having all those algorithms at hand, it made sense combining them into something more people could use, and by them it seemed that QGIS was the way to go, so I developed the very first version of AequilibraE.

It was buggy as hell and there was very little, if any, software engineering built into it, but it put Aequilibrae on the map.

The first reasonable version

The first important thing I noticed after releasing AequilibraE was that the code was written in procedural style, even though it would make a lot more sense doing it in a Object-Oriented fashion, which let me down the path of creating the objects (graph, assignment results, matrix) that the software still relies on and were the foundation blocks of the proper API that is in the making. That version was release almost 3 years ago.

Evolving into proper software

A few distinct improvements deserve to be highlighted.

  • The separation of the GUI and the Python library in two repositories
  • Introduction of Unit Tests and automatic testing using Travis
  • Welcome of new collaborators: Jamie Cook, Andrew O'Brien and Yu-Chu Huang
  • Introduction of style-checking with Flake8 and Black
  • Development of proper documentation (undergoing) and a recommended development virtual environment

Other relevant Repositories

External hyperlinks, like Python.

The other most important repository associated with this project is the one for the QGIS GUI That is where everything started.

The other important repository is the one with the examples of usage of this code. That repository will problay be replaced with proper documentation for this project, but one thing at a time.

You can’t perform that action at this time.