Open-Source Software
Reuse, adapt, and improve digital mobility solutions
Explore ACCESS-related open-source software through a curated catalogue connected to approved code repositories. Repository records explain what each tool does, who it is for, what is required to use it, and how to assess whether it fits a particular mobility, institutional, and technical context.
The ACCESS website should provide an accessible, plain-language overview of each software project, while the authoritative repository remains the location for source code, documentation, releases, issues, and technical collaboration.
Open source means that software is available under a licence that permits specified forms of use, inspection, modification, or redistribution. It does not mean that implementation is automatically low-cost, risk-free, maintained, secure, accessible, or suitable for every context.
Explore Software by Purpose
Planning and Decision Support
Tools for scenario analysis, readiness assessment, options comparison, network planning, prioritisation, and institutional decision-making.
Explore Planning SoftwareMobility Data and Analytics
Tools for processing, integrating, analysing, mapping, visualising, or monitoring mobility data.
Explore Data SoftwarePublic Transport
Software supporting schedules, GTFS, operations, passenger information, service monitoring, and multimodal integration.
Explore Public Transport SoftwareUrban Freight and Logistics
Routing, fleet management, loading-space management, logistics analysis, emissions, and operational tools.
Explore Freight SoftwareLow-Carbon Mobility and Impact
Tools supporting emissions estimation, Avoid–Shift–Improve analysis, electrification, accessibility, safety, or climate monitoring.
Explore Impact SoftwareParticipation and Inclusion
Tools supporting stakeholder engagement, accessibility, inclusive planning, feedback, or public communication.
Explore Participation SoftwareBrowse and Filter Repositories
Approved software repositories will appear here once they are published.
Repository Card
Present software as responsive catalogue cards rather than embedding a repository platform directly. Each card should provide enough information for users to judge relevance before leaving the ACCESS website.
- Project name and plain-language summary
- Intended users and problem addressed
- Use case, mobility area, and thematic tags
- Primary programming language and operating environment
- Current version or latest release
- Maintenance and implementation status
- Licence
- Documentation status
- Related country, city, pilot, dataset, course, case, or toolkit
- External actions: View repository, Read documentation, View releases, or Report an issue
Software Detail Page
- Purpose and expected public value
- Intended users and institutional context
- Functions and main use cases
- Mobility area and related ACCESS themes
- Development origin and relationship to ACCESS
- Current version, release date, and maturity
- Maintenance status and responsible organisation
- Technical architecture and primary programming language
- Operating environment, hosting, and infrastructure requirements
- Dependencies, standards, integrations, and data inputs
- Installation, configuration, deployment, and update guidance
- Licence and required attribution
- Privacy, security, cybersecurity, safeguards, and data-governance considerations
- Accessibility and language support
- Known issues, limitations, and risks
- Estimated implementation, hosting, integration, training, and maintenance needs
- Documentation, repository, releases, issue tracker, and contribution guidance
- Related resources, datasets, cases, Learning Pathways, and Courses and Trainings
- Last verified date and support route
Before Adopting Software
- 1.
Define the Need
Confirm the mobility problem, intended users, public value, and expected result.
- 2.
Review Suitability
Check functionality, maturity, licence, documentation, standards, accessibility, and known limitations.
- 3.
Assess Readiness
Review data, infrastructure, skills, institutional ownership, procurement, finance, safeguards, and maintenance capacity.
- 4.
Test Safely
Use sample or non-sensitive data where possible, document results, and involve intended users.
- 5.
Plan Implementation
Define hosting, integration, configuration, responsibilities, training, support, security, monitoring, and budgets.
- 6.
Maintain and Improve
Track releases, issues, user feedback, vulnerabilities, documentation, local adaptations, and upgrade requirements.
Adoption Checklist
- Does the software address a clearly defined public or institutional need?
- Is the repository active, documented, and maintained?
- Is the licence compatible with intended use, modification, and redistribution?
- Are dependencies, standards, integrations, and data requirements understood?
- Can available infrastructure and staff support deployment and maintenance?
- Have privacy, security, cybersecurity, accessibility, inclusion, and safeguards been assessed?
- Are hosting, integration, customisation, training, support, and lifecycle costs budgeted?
- Can the institution retain access to its data and avoid unnecessary vendor or platform dependency?
- Is there a plan for testing, user feedback, monitoring, upgrades, incident response, and continuity?
- Are local adaptations documented and contributed back where appropriate and permitted?
Software Status Labels
Early idea or specification; no usable public release.
Active development; functionality or documentation may be incomplete.
Available for controlled testing with stated limitations.
Used in an approved real-world setting with active maintenance.
Documented release intended for broader use under stated conditions.
Receiving limited fixes or essential updates but little new development.
No longer actively maintained; retained for reference with a warning and alternatives where available.
Contribute and Collaborate
Technical collaboration should take place through the authoritative repository and its approved contribution processes.
- Read the contribution guide and code of conduct.
- Search existing issues before opening a new one.
- Report bugs with reproducible information and without exposing sensitive data.
- Suggest improvements through the repository issue or discussion process.
- Submit changes through the approved review workflow.
- Document local adaptations, translations, integrations, and lessons.
- Respect licence, attribution, security, privacy, and community standards.
- Do not submit credentials, personal data, confidential information, or security-sensitive details to public repositories.
Featured Software
Display a rotating selection of approved and current software records. Featured items should be drawn dynamically from the central content system and should not be entered separately on this page.
An ACCESS-developed or adapted software tool
A repository connected to an implementation case
A reusable analytical or planning tool
A software project with related tutorials or learning resources
Do not feature a repository until its owner, relationship to ACCESS, licence, public URL, current status, documentation, security and privacy considerations, accessibility information, and maintenance arrangements are confirmed.
Connect Software with Data, Learning, and Practice
- 1Need
- 2Readiness
- 3Selection
- 4Testing
- 5Implementation
- 6Maintenance
- 7Improvement and Reuse
Every software record should connect users with relevant datasets, technical guidance, tools, implementation cases, Learning Pathways, Courses and Trainings, and Community of Practice exchange. Experience from implementation should improve documentation, training, future releases, and adoption guidance.