--- URL: "/" LLMS_URL: "/index.md" layout: "home" hero: name: "Awesome NAPCORE Tools" text: "European Mobility Data Tools Catalogue" tagline: "Discover tools from NAPCORE and the wider community" image: src: "/napcore-logo.png" alt: "NAPCORE Logo" actions: - theme: "brand" text: "See Tools by NAPCORE" link: "/categories/napcore-provided/" - theme: "alt" text: "Browse All Tools" link: "/all/" - theme: "alt" text: "Submit a Tool" link: "/contribute" features: - icon: src: "/icons/open-access.svg" alt: "Open padlock representing open access" width: "48" height: "48" title: "Openly Accessible Tools" details: "Only openly accessible tools are included." link: "/contribute#open-tool-criteria" - icon: src: "/napcore-logo.png" alt: "NAPCORE logo" width: "64" height: "64" title: "By NAPCORE" details: "Lists tools built by the NAPCORE project." link: "/categories/napcore-provided/" - icon: src: "/icons/community.svg" alt: "Honeycomb representing community collaboration" width: "48" height: "48" title: "Community Provided" details: "Community provided tools enlisted too." link: "/contribute" ---

Official NAPCORE Tools

Tools developed directly by the NAPCORE team
[Browse All Tools](/all/)
## Get Involved
### 🎯 Submit a Tool Have a tool that helps with mobility data? Submit it for review by the NAPCORE team through our contribution process. [Learn How to Contribute β†’](/contribute)
### πŸ’¬ Join the Discussion Connect with other mobility data professionals, ask questions, and share your experiences with the community. [GitHub Discussions β†’](https://github.com/napcore-tools/web-awesome_napcore_tools/discussions)
### πŸ“° Read the Blog Stay up to date with news, technical articles, and updates from the NAPCORE team. [Go to Blog β†’](/blog/)
**NAPCORE** - National Access Point Coordination Organisation for Europe
--- URL: "/about.html" LLMS_URL: "/about.md" --- # About Awesome NAPCORE Tools The Awesome NAPCORE Tools is a NAPCORE-led initiative to build, curate, and showcase tools for the European mobility data ecosystem. The aim is to support developers, data publishers, NAP operators, and National Bodies to find and use the right tools for working with mobility data standards like DATEX II, NeTEx, SIRI, and mobilityDCAT-AP. ## Why This Catalogue Exists ### The Challenge The European mobility data ecosystem is rich with standards and tools, but they're scattered across different websites, repositories, and organisations. Finding the right tool, for a specific task can be difficult and time-consuming. ### The Solution The Awesome NAPCORE Tools brings these tools together in one place, with: - **Standardised descriptions** so you can quickly understand what each tool does. - **Clear categorisation** to help you find tools for specific needs. - **Quality curation** to ensure tools are functional and maintained. - **Community input** to discover tools through collective knowledge. ## What We Include ### Tool Types We catalogue tools across nine categories: - Validators - Converters & Transformers - Version Upgrade Tools - SDKs & Libraries - Reference Implementations - Development Tools - Data Quality Tools - Testing Utilities - Metadata Tools ### Standards Covered Tools supporting European mobility data standards: - **DATEX II** - Traffic and travel information - **NeTEx** - Public transport networks - **SIRI** - Real-time public transport information - **mobilityDCAT-AP** - Mobility data metadata - **DCAT-AP** - General data catalogue metadata - And other related standards ## Who This Is For - **Developers and Implementers**: Find tools to help implement mobility data standards in your applications and services. - **NAP Operators and National Bodies**: Discover tools for publishing, validating, checking compliance and managing mobility data on National Access Points. - **System Architects**: Explore tools and components for designing mobility data infrastructure. - **Data Publishers**: Find tools for creating metadata, validating data, and ensuring quality. - **Students & Researchers**: Learn about available tools and reference implementations for academic projects. ## Project Background ### Origins The Awesome NAPCORE Tools was created as part of NAPCORE Task 5.2 to create a centralised resource for discovering tools. As part of NAPCORE's mission to improve not only the interoperability of mobility data and data standards in Europe, but also support and align processes of National Access Points and National bodies, the creation of a shared tool box is a vital step towards a harmonised data ecosystem. #### About NAPCORE **NAPCORE** (National Access Point Coordination Organisation for Europe) is a coordination mechanism for the National Access Points to share insights, experiences and best practises, knowledge and expertise, to act as the backbone of mobility data exchange in Europe. NAPCORE is co-financed by a Programme Support Action under the European Commission's Connecting Europe Facility. The initiative involves: - **33 Beneficiaries**: covering 26 EU Member States and 3 associated partners - **over 30 mobility data platforms**: working on harmonising data sharing across the continent - **Long-term vision**: establishing a future-oriented platform organisation Learn more at [napcore.eu](https://napcore.eu) ### Governance #### Managing Team The catalogue is built and maintained by the NAPCORE Task 5.2 team, with support and contributions from the broader NAPCORE community. #### Review Process As our goal is to ensure quality and relevance in the domain of European mobility data, every tool submission is reviewed according to the quality standards by the managing team with input from the community. The review process happens in public through GitHub Discussions, to ensure transparency. See our [Contribution Guide](/contribute) for more details. #### Tool Inclusion Criteria To maintain quality standards of the tools in the catalogue, the inclusion criteria are: βœ… **Relevant to mobility data**: Supports European mobility data standards or workflows βœ… **Publicly accessible**: Available for use (either open source or free to use) βœ… **Functional**: Currently working and maintained βœ… **Documented**: Has basic documentation or usage instructions ## Statistics ## Keyboard Shortcuts {#keyboard-shortcuts} The catalogue supports keyboard navigation to move quickly between pages. Press **`g`** followed by a second key: | Shortcut | Action | | ----------------- | --------------------------- | | `g` `h` | Go to Home | | `g` `t` | Go to All Tools | | `g` `n` | Go to Tools by NAPCORE | | `g` `s` | Go to Standards | | `g` `c` | Go to Categories | | `g` `a` | Go to About | | `?` | Go to keyboard shortcuts | | `Ctrl` `K` or `/` | Open site-wide search | | `Escape` | Clear the filter search box | ## Development - **Built with**: VitePress (modern static site generator) - **Hosted on**: GitHub Pages - **Open Source**: All catalogue content is open source - **NAPCORE-Curated**: Tools are built or submitted and reviewed by the NAPCORE team - **Community-Driven**: Open to contributions and feedback from the wider community ### Roadmap #### Short Term - **Expand tool coverage** across all categories and Standards - **Improve search and filtering** capabilities - Add **tool comparison features** #### Medium Term - Implement **user ratings** and reviews - Add **tool usage statistics** - Create tool integration **guides** - **Develop API** for programmatic access #### Long Term - Establish **tool certification program** - Create **testing infrastructure** - Build **automated tool discovery** - Expand to **cover more standards** ## Get Involved There are many ways to contribute: - **Submit tools** you've built or use - **Improve documentation** for existing tools - **Share your experience** using catalogue tools - **Suggest improvements** to the catalogue - **Help other users** in discussions - **Stay updated** by subscribing to our blog via [RSS feed](/feed.rss){target="blank"} [Learn How to Contribute β†’](/contribute) ## Contact - **GitHub**: [GitHub repository](https://github.com/napcore-tools/web-awesome_napcore_tools) - **Discussions**: [GitHub Discussions](https://github.com/napcore-tools/web-awesome_napcore_tools/discussions) - **NAPCORE Website**: [napcore.eu](https://napcore.eu) ## Acknowledgments This catalogue is made possible by: - **NAPCORE partners** and participating member states - **Tool developers** who create and maintain these valuable resources - **Community contributors** who submit tools and improvements - **European Commission** through the Connecting Europe Facility ---

NAPCORE - National Access Point Coordination Organisation for Europe

Co-financed by the Connecting Europe Facility of the European Union

--- URL: "/all" LLMS_URL: "/all.md" --- # All Tools --- URL: "/blog" LLMS_URL: "/blog.md" layout: "page" ---
# Awesome NAPCORE Tools Blog Stay updated with the latest news, insights, and updates about mobility data standards, tools, and the European ITS ecosystem.
--- URL: "/blog/posts/2025-12-01-future-post-example.html" LLMS_URL: "/blog/posts/2025-12-01-future-post-example.md" title: "This Post Will Be Published in December" description: "This is an example of a scheduled post that won't appear until its publishDate arrives." date: publishDate: author: "NAPCORE Team" tags: - "example" - "scheduled" published: true --- # This Post Will Be Published in December This post demonstrates the `publishDate` feature. It won't be visible on the blog listing page or in the RSS feed until December 1, 2099. ## How It Works When you add a `publishDate` field to the frontmatter, the post will be hidden until that date arrives: ```yaml --- title: Your Post Title date: 2099-12-01 publishDate: 2099-12-01 # Post won't appear until this date published: true --- ``` ## Use Cases - **Content Scheduling**: Prepare posts in advance and schedule them for future publication - **Announcement Timing**: Coordinate blog posts with product launches or events - **Content Pipeline**: Build a backlog of content that publishes automatically ## Notes - The `publishDate` is checked at build time - If you don't specify `publishDate`, the post is published immediately - The `date` field is used for sorting, while `publishDate` controls visibility - You'll need to rebuild your site for scheduled posts to appear after their publishDate --- _This post will automatically appear on December 1, 2099!_ --- URL: "/blog/posts/2026-08-01-welcome-to-napcore-blog.html" LLMS_URL: "/blog/posts/2026-08-01-welcome-to-napcore-blog.md" title: "Welcome to the Awesome NAPCORE Tools Blog" description: "Introducing the new Awesome NAPCORE Tools blog for updates on European mobility data tools and standards." date: author: "NAPCORE Team" tags: - "announcement" - "napcore" - "datex-ii" published: true --- # Welcome to the Awesome NAPCORE Tools Blog We're excited to announce the launch of the Awesome NAPCORE Tools blog! This blog will be your go-to resource for staying informed about the latest developments in European mobility data exchange and Intelligent Transport Systems (ITS). ## What to Expect The Awesome NAPCORE Tools blog will feature: - **Tool Updates**: Announcements about new tools added to the catalogue and updates to existing tools - **Standards Insights**: In-depth articles about mobility data standards like DATEX II, SIRI, NeTEx, and more - **Best Practices**: Practical guides for working with European mobility data - **Community Stories**: Success stories and case studies from the mobility data community - **Technical Deep Dives**: Detailed explorations of specific tools and integration patterns ## About NAPCORE The National Access Point Coordination Organisation for Europe (NAPCORE) supports the coordination and evolution of National Access Points (NAPs) across Europe. The Awesome NAPCORE Tools serves as a comprehensive catalogue of tools, standards, and resources that facilitate mobility data exchange and ITS implementation. ## Stay Connected This blog is part of our commitment to fostering a vibrant community around European mobility data standards. We encourage you to: - Browse our [tool catalogue](/categories/) to discover available resources - Explore the various [categories](/categories/) of tools and standards - [Contribute](/contribute) your own tools or improvements to the store ## What's Next? Stay tuned for regular updates as we: - Add new tools to the catalogue - Publish guides and tutorials - Share community contributions - Announce events and workshops Thank you for being part of the NAPCORE community. Together, we're building the future of European mobility data exchange! --- _Have questions or feedback? Feel free to reach out through our [contribution page](/contribute)._ --- URL: "/categories" LLMS_URL: "/categories.md" --- # Tool Categories Browse tools by category to find exactly what you need for your mobility data project. --- URL: "/categories/converters.html" LLMS_URL: "/categories/converters.md" document: "category" contributeTip: "Know a reliable converter or open-source mapping tool?" --- # Converters & Transformers ::: details Tools that transform mobility and transport data between different formats, standards, or structures β€” enabling interoperability, integration, and reuse across systems. ### What Are Converters? Converters help you translate datasets or messages from one technical or semantic format to another. They are essential for: - **Interoperability** – connecting systems using different data standards - **Data exchange** – publishing or consuming data in compatible formats - **Modernization** – migrating legacy data to current standards - **Automation** – integrating conversions into data pipelines or APIs Converters often include format mapping, schema translation, and metadata transformation features. ### Types of Converters | Type | Description | Example | | ----------------------------- | --------------------------------------------------------- | ---------------------------- | | **Schema Converters** | Transform data from one schema or structure to another | DATEX II ↔ JSON, XML ↔ RDF | | **Format Converters** | Change encoding or syntax (e.g., CSV β†’ JSON) | GTFS β†’ NeTEx converter | | **Metadata Converters** | Adapt dataset descriptions to standards like DCAT-AP | DCAT-AP ↔ mobilityDCAT-AP | | **Geospatial Converters** | Reproject or transform geographic coordinates or formats | WGS84 ↔ ETRS89 converter | | **Multi-standard Converters** | Handle several formats and provide mapping configurations | Multi-schema data gateway | ### Common Use Cases #### Data Publication Convert internal data to **DATEX II**, **NeTEx**, or **mobilityDCAT-AP** formats for publication on a National Access Point (NAP). #### Data Integration Transform heterogeneous inputs from different systems into a single harmonized schema. #### Migration Convert legacy data (CSV, XML, JSON) into standardized mobility formats for interoperability. #### Metadata Alignment Adapt dataset metadata between **DCAT-AP** and **mobilityDCAT-AP** profiles for consistent cataloguing. ### Example Tool **DATEX II – JSON Converter** - Converts DATEX II XML files into lightweight JSON - Preserves core data model semantics - Useful for APIs and web-based applications - Open source and standard-compliant ### Related Categories ::: ## Available Tools --- URL: "/categories/data-quality.html" LLMS_URL: "/categories/data-quality.md" document: "category" contributeTip: "Know a data quality tool used in transport data management?" --- # Data Quality Tools ::: details Tools that measure, monitor, and improve the quality of mobility and transport data β€” ensuring accuracy, consistency, and reliability across datasets and systems. ### What Are Data Quality Tools? Data quality tools help organisations ensure their data is **fit for purpose** before it is published, exchanged, or used in analytics. They detect issues such as missing values, schema violations, or inconsistent references, supporting better decision-making and regulatory compliance. These tools are often used by: - **Data providers** – to validate and improve datasets before publication - **System integrators** – to ensure data compatibility - **Authorities** – to monitor data quality in National Access Points (NAPs) ### Types of Data Quality Tools | Type | Description | Example | | ----------------------- | ------------------------------------------------- | --------------------------- | | **Validation Tools** | Check schema and rule compliance | DATEX II Validator | | **Profiling Tools** | Analyze datasets to detect patterns and anomalies | Mobility data profiler | | **Monitoring Tools** | Continuously track quality over time | NAP Data Monitor | | **Reference Checkers** | Verify identifiers, codes, and locations | ALERT-C Reference Validator | | **Visualization Tools** | Provide dashboards for data quality KPIs | Quality Metrics Dashboard | ### Common Use Cases #### Pre-Publication Checks Ensure datasets meet standard and structural requirements before being published on a NAP. #### Quality Monitoring Automate recurring checks to monitor dataset quality trends over time. #### Benchmarking Compare datasets or data sources using defined quality metrics (completeness, consistency, timeliness). #### Debugging and Diagnostics Identify missing, inconsistent, or invalid data fields that affect downstream use. ### Example Tool **NAP Data Quality Dashboard** - Provides quality metrics for DATEX II and NeTEx feeds - Supports customizable validation rules - Used by multiple European National Access Points - Open source and modular ### Related Categories ::: ## Available Tools --- URL: "/categories/development.html" LLMS_URL: "/categories/development.md" document: "category" contributeTip: "Built or use a tool that supports development with mobility data?" --- # Development Tools ::: details Tools that support the day-to-day development workflow for mobility data systems. ### What Are Development Tools? Development tools assist engineers and data practitioners in creating, testing, and maintaining mobility data solutions. They include SDKs, libraries, APIs, and utilities designed to simplify working with standards like DATEX II, NeTEx, SIRI, or mobilityDCAT-AP. Typical users include: - **Software developers** building transport applications - **Data engineers** integrating and transforming data feeds - **Researchers** prototyping and testing mobility data workflows ### Types of Development Tools | Type | Description | Example | | ---------------------- | ------------------------------------------------------------- | ---------------------- | | **SDKs & Libraries** | Provide reusable code for reading/writing mobility formats | DATEX II Python SDK | | **CLI Utilities** | Command-line tools for transformation, validation, or testing | NeTEx CLI Tool | | **APIs & Wrappers** | Simplify data access or conversion | SIRI REST API Wrapper | | **Testing Frameworks** | Automate validation and integration testing | Mobility Test Runner | | **Data Simulators** | Generate mock data for development environments | Traffic Feed Simulator | ### Common Use Cases #### Application Development Use SDKs and APIs to quickly integrate mobility data into software applications. #### Data Integration Leverage libraries or converters to harmonize incoming datasets. #### Testing and QA Automate validation, conversion, and functional tests in CI/CD pipelines. #### Simulation and Prototyping Use data simulators or mock feeds to test new transport systems before deployment. ### Example Tool **Mobility Data SDK** - Provides utilities for parsing DATEX II and NeTEx files - Includes validation, transformation, and serialization helpers - Integrates easily with Python and Node.js environments - Open source, with community support ### Related Categories ::: ## Available Tools --- URL: "/categories/metadata.html" LLMS_URL: "/categories/metadata.md" document: "category" contributeTip: "Know a metadata editor, validator, or catalogue management tool for mobility datasets?" --- # Metadata Tools ::: details Tools that help create, manage, and validate metadata for mobility and transport datasets β€” ensuring discoverability, interoperability, and compliance with European data catalogue standards. ### What Are Metadata Tools? Metadata tools assist in describing datasets in a structured and standardized way, enabling users to **find, understand, and reuse** mobility data. They often implement profiles such as **DCAT-AP** and **mobilityDCAT-AP**, required for data publication on National Access Points and open data portals. They are used by: - **Data publishers** – to describe datasets and APIs - **Catalogue administrators** – to manage metadata repositories - **Developers and integrators** – to automate metadata generation and harvesting ### Types of Metadata Tools | Type | Description | Example | | ------------------------------ | ---------------------------------------------------------- | --------------------------------- | | **Metadata Editors** | Create or edit dataset descriptions manually | DCAT-AP Metadata Editor | | **Metadata Validators** | Check metadata against DCAT-AP or mobilityDCAT-AP profiles | mobilityDCAT-AP Validator | | **Catalogue Management Tools** | Manage and publish metadata catalogues | CKAN, GeoNetwork | | **Metadata Converters** | Transform metadata between different profiles | DCAT ↔ mobilityDCAT-AP Converter | | **Harvesting Tools** | Automate metadata synchronisation between catalogues | DCAT Harvester | ### Common Use Cases #### Dataset Publication Create compliant metadata to publish datasets on National Access Points and open data portals. #### Metadata Validation Check dataset descriptions for completeness and compliance with DCAT-AP or mobilityDCAT-AP requirements. #### Catalogue Management Maintain collections of datasets with version control, search, and linked data capabilities. #### Metadata Conversion Transform or map metadata between internal and public catalogue formats. ### Example Tool **mobilityDCAT-AP Validator** - Validates metadata records for compliance with the mobilityDCAT-AP profile - Checks mandatory fields, controlled vocabularies, and references - Supports JSON-LD, Turtle, and RDF/XML - Open source, actively maintained ### Related Categories ::: ## Available Tools --- URL: "/categories/napcore-provided.html" LLMS_URL: "/categories/napcore-provided.md" --- # Tools by NAPCORE --- URL: "/categories/reference-implementations.html" LLMS_URL: "/categories/reference-implementations.md" document: "category" contributeTip: "Have a working demo or reference implementation of a mobility data standard?" --- # Reference Implementations ::: details Working examples and demo applications that showcase best practices for implementing mobility and transport data standards in real-world scenarios. ### What Are Reference Implementations? Reference implementations demonstrate how to correctly use or integrate a specific mobility data standard. They provide **proven, reusable examples** that help developers, data providers, and public authorities understand how to build interoperable solutions. They are useful for: - **Developers** learning how to use a standard in practice - **System integrators** implementing compliant interfaces - **Public authorities** evaluating best practices and conformance ### Types of Reference Implementations | Type | Description | Example | | ------------------------ | ----------------------------------------------------- | ------------------------------- | | **Data Exchange APIs** | Implementations of DATEX II, SIRI, or NeTEx services | DATEX II REST API Reference | | **Publishing Workflows** | Sample pipelines for data publication on NAPs | NeTEx β†’ NAP Publisher Demo | | **Metadata Catalogues** | Example DCAT-AP / mobilityDCAT-AP portals | Open Mobility Metadata Portal | | **End-to-End Solutions** | Complete integration demos showing multiple standards | Cross-Standard Integration Demo | ### Common Use Cases #### Learning and Experimentation Explore working codebases to understand how standards are applied. #### Rapid Prototyping Use example implementations as starting points for new projects. #### Conformance Testing Compare your implementation against reference systems to ensure compliance. #### Demonstrations and Training Support workshops or technical documentation with live examples. ### Example Tool **DATEX II REST API Reference** - Open-source implementation of the DATEX II REST interface - Demonstrates schema validation and payload exchange - Ideal for learning and integration testing - Developed under the CEN/EN 16157 framework ### Related Categories ::: ## Available Tools --- URL: "/categories/references.html" LLMS_URL: "/categories/references.md" document: "category" contributeTip: "Know a public repository or authoritative documentation set?" --- # Reference Documentations ::: details Authoritative documentation and specifications that define the structure, semantics, and usage of mobility and transport data standards. ### What Is Reference Documentation? Reference documentation provides **official definitions and guidance** for implementing European mobility data standards. It includes schemas, UML models, reference guides, and technical specifications that ensure consistent interpretation across implementations. Used by: - **Developers** to implement data exchange formats correctly - **System architects** to design interoperable platforms - **Public authorities** to ensure conformance in data publication ### Types of Reference Documentation | Type | Description | Example | | --------------------------- | ---------------------------------------- | ----------------------------- | | **Standard Specifications** | Core CEN/ISO or EC documents | CEN/EN 16157 (DATEX II) | | **Technical Guidelines** | Best practices and interpretation notes | NeTEx Implementation Guide | | **API Specifications** | REST/GraphQL or SOAP API definitions | SIRI API Reference | | **Data Model Definitions** | UML or XSD reference files | DATEX II UML Model | | **Metadata Profiles** | DCAT-AP extensions and mobility profiles | mobilityDCAT-AP Specification | ### Common Use Cases #### Implementation Support Use as the authoritative source when developing or validating systems. #### Schema and Model Understanding Consult data element definitions, UML diagrams, and constraints. #### Policy and Compliance Align local or national initiatives with European standard specifications. #### Documentation Reuse Integrate excerpts into training materials or technical guides. ### Example Tool **DATEX II Specification Repository** - Contains all CEN/EN 16157 parts - Includes UML models, schemas, and examples - Maintained by the DATEX II community - Freely accessible via GitHub and the official portal ### Related Categories ::: ## Available Tools --- URL: "/categories/route-planners.html" LLMS_URL: "/categories/route-planners.md" document: "category" contributeTip: "Know a route planning engine or API using mobility standards?" --- # Route Planners ::: details Applications and APIs that calculate, visualize, and share routes for transport networks β€” integrating mobility data from multiple standards and sources. ### What Are Route Planners? Route planners compute **optimal travel routes** for vehicles, cyclists, or passengers, using transport datasets and standards such as NeTEx, SIRI, and DATEX II. They enable multimodal transport planning, traffic management, and navigation services. They are used by: - **Public transport operators** for journey planning - **Traffic authorities** for information services - **Developers** creating mobility apps and digital twins ### Types of Route Planners | Type | Description | Example | | ------------------------------ | ---------------------------------------------- | ---------------------------------- | | **Public Transport Planners** | Calculate journeys using timetables and stops | NeTEx / GTFS-based Journey Planner | | **Road Traffic Planners** | Compute road routes and traffic-aware guidance | DATEX II Traffic Routing Service | | **Multimodal Planners** | Combine modes (car, train, bike, walk) | OpenTripPlanner | | **Geospatial Routing Engines** | Compute optimized paths using map data | OSRM, GraphHopper | ### Common Use Cases #### Journey Planning Calculate routes and travel times for multimodal transport networks. #### Traffic Management Integrate road events and congestion data from DATEX II feeds. #### Real-Time Updates Combine static NeTEx data with live SIRI feeds for dynamic route planning. #### Mobility-as-a-Service (MaaS) Power integrated travel apps and regional journey planners. ### Example Tool **OpenTripPlanner** - Supports NeTEx, GTFS, and SIRI data - Provides multimodal routing and real-time updates - Extensible open-source platform widely used across Europe ### Related Categories ::: ## Available Tools --- URL: "/categories/sdks.html" LLMS_URL: "/categories/sdks.md" document: "category" contributeTip: "Developed or used an SDK or library for mobility standards?" --- # SDKs & Libraries ::: details Programming language bindings and reusable libraries that simplify the implementation of mobility and transport data standards. ### What Are SDKs & Libraries? SDKs and libraries provide **ready-to-use code components** for developers working with transport data. They help parse, validate, generate, and exchange standard-compliant datasets without needing to implement low-level logic from scratch. They're ideal for: - **Developers** building transport apps or APIs - **Data engineers** processing or transforming datasets - **Integrators** creating standardized data interfaces ### Types of SDKs & Libraries | Type | Description | Example | | ------------------------ | ------------------------------------------ | ---------------------- | | **Parsing Libraries** | Read and write standard data formats | DATEX II XML Parser | | **Validation Libraries** | Embed schema or business rule validation | NeTEx Rule Validator | | **Conversion Libraries** | Transform data between supported formats | SIRI ↔ JSON Converter | | **API Client SDKs** | Simplify communication with transport APIs | SIRI REST Client | | **Metadata Libraries** | Handle DCAT-AP / mobilityDCAT-AP metadata | DCAT-AP Toolkit | ### Common Use Cases #### Application Development Quickly build standard-compliant APIs or data integrations. #### Data Transformation Convert and harmonize datasets in pipelines or ETL jobs. #### Testing and Validation Integrate schema validation within your application logic. #### Metadata Automation Generate or update DCAT-AP or mobilityDCAT-AP metadata programmatically. ### Example Tool **DATEX II Python SDK** - Parses and generates DATEX II XML files - Supports validation and serialization - Compatible with Python 3 and modern frameworks - Open source, community-maintained ### Related Categories ::: ## Available Tools --- URL: "/categories/testing.html" LLMS_URL: "/categories/testing.md" document: "category" contributeTip: "Know a testing framework or simulator for mobility data systems?" --- # Testing Utilities ::: details Tools and frameworks that support testing of mobility and transport data, services, and systems β€” ensuring reliability, interoperability, and compliance with data exchange standards. ### What Are Testing Utilities? Testing utilities help developers and data providers **verify the correctness and robustness** of their mobility data solutions. They automate testing of data transformations, API endpoints, and validation workflows to catch issues early in the development or publication process. They are commonly used by: - **Developers** building or maintaining data exchange APIs - **Data providers** verifying output against standard schemas - **Quality assurance teams** running automated test suites ### Types of Testing Utilities | Type | Description | Example | | --------------------------------- | ------------------------------------------------------------- | --------------------------- | | **Schema Testers** | Validate files against XSD or JSON Schema definitions | DATEX II Schema Tester | | **Integration Testers** | Test interoperability between systems or services | SIRI API Integration Tester | | **Rule-based Testers** | Check business rules and constraints beyond schema validation | NeTEx Logical Rule Tester | | **Mock & Simulation Tools** | Generate mock data or simulate service responses | Traffic Data Simulator | | **Continuous Testing Frameworks** | Automate validation in CI/CD pipelines | Mobility Data CI Runner | ### Common Use Cases #### Schema and Rule Testing Validate datasets or API responses to ensure structural and logical compliance. #### Integration Testing Verify compatibility between different data providers or transport systems. #### Automated Quality Assurance Run validation tests automatically in CI/CD environments to prevent regressions. #### Mocking and Simulation Simulate transport data or API calls to test system behavior under controlled conditions. ### Example Tool **SIRI Service Tester** - Simulates SIRI StopMonitoring and VehicleMonitoring requests - Validates XML responses against the SIRI schema - Supports configurable scenarios for automated testing - Used in transport system integration projects across Europe ### Related Categories ::: ## Available Tools --- URL: "/categories/validators.html" LLMS_URL: "/categories/validators.md" document: "category" contributeTip: "Know a validator for DATEX II, NeTEx, SIRI, or mobilityDCAT-AP?" --- # Validators ::: details Tools and services that **check the structure and quality of mobility and transport data**, ensuring it complies with European standards such as DATEX II, NeTEx, SIRI, and mobilityDCAT-AP. ### What Are Validators? Validators automatically verify whether datasets conform to technical and business specifications. They are essential for maintaining **data quality, interoperability, and regulatory compliance** in digital mobility ecosystems. Validators typically perform: - **Schema validation** – Checks if files match required XML, JSON, or RDF schemas (e.g., XSD, JSON Schema) - **Business rule validation** – Tests domain-specific logic, cardinality, or value constraints - **Data quality checks** – Detects missing, inconsistent, or implausible values - **Compliance checks** – Confirms datasets meet European standards for publication or exchange ### Types of Validators | Type | Description | | ----------------------------- | --------------------------------------------------------- | | **Schema Validators** | Validate structure and syntax against XSD/JSON schemas | | **Business Rule Validators** | Apply rules beyond the schema (e.g., logical consistency) | | **Multi-standard Validators** | Handle several transport formats together | | **Geographic Validators** | Verify geospatial and reference integrity | ### Common Use Cases #### Pre-Publication Validation Ensure datasets comply with DATEX II, NeTEx, or mobilityDCAT-AP before submission to a **National Access Point (NAP)**. #### Development & Testing Integrate validators in your CI/CD workflow to catch schema or logical errors early. #### Quality Monitoring Run scheduled validations to monitor dataset quality and detect degradation over time. #### Location Reference Validation Validate ALERT-C or RDS-TMC location codes for correctness and alignment with reference tables. ### Example Tool: ALERT-C Locations Tester The **ALERT-C Locations Tester** validates the consistency and correctness of location codes used in traffic messages. - **Operational use**: Czech Road and Motorway Directorate - **Multi-format support**: DATEX II, RDS-TMC, custom XML - **European coverage**: ALERT-C widely used across Europe - **License**: Open source (MIT) ### Related Categories ::: ## Available Tools --- URL: "/categories/version-tools.html" LLMS_URL: "/categories/version-tools.md" document: "category" contributeTip: "Created or used a migration or upgrade tool for mobility standards?" --- # Version Upgrade Tools ::: details Utilities and scripts that help migrate or convert datasets and systems between different versions of mobility and transport data standards. ### What Are Version Upgrade Tools? Version upgrade tools automate the process of **updating data or interfaces** from older to newer standard versions β€” ensuring compatibility, data integrity, and compliance. They're essential when standards evolve (e.g., DATEX II v2 β†’ v3, NeTEx profile updates) and systems need to stay interoperable. They're typically used by: - **Data providers** upgrading published datasets - **System integrators** maintaining interoperability across versions - **Developers** adapting applications to new schema versions ### Types of Version Upgrade Tools | Type | Description | Example | | --------------------------- | ------------------------------------------ | ------------------------------- | | **Schema Migrators** | Convert files between standard versions | DATEX II v2 β†’ v3 Converter | | **Transformation Scripts** | Apply XSLT or mapping rules | NeTEx Profile Transformer | | **Compatibility Checkers** | Verify cross-version compliance | mobilityDCAT-AP Version Checker | | **Migration Assistants** | Interactive tools for data migration | XML Schema Migration Assistant | | **Multi-Profile Upgraders** | Handle regional or custom profile mappings | DATEX II Profile Upgrader | ### Common Use Cases #### Standard Migration Convert existing datasets to newer standard versions to maintain compliance. #### Compatibility Testing Ensure backward compatibility when consuming mixed-version data feeds. #### Automated Conversion Integrate upgrade utilities in pipelines to process datasets dynamically. #### Metadata Synchronization Update catalogue metadata to align with new schema profiles. ### Example Tool **DATEX II Version Migration Tool** - Converts legacy DATEX II v2 datasets to v3 format - Preserves key elements and mappings - Command-line utility with configurable profiles - Used by several European NAPs ### Related Categories ::: ## Available Tools --- URL: "/contribute.html" LLMS_URL: "/contribute.md" --- # Contribute to the Catalogue Help grow the European mobility tools ecosystem by contributing tools, improvements, and feedback. ## How to Submit a Tool We welcome tool submissions from developers, organisations, and mobility data professionals. The submission process is designed to be simple while ensuring quality and relevance. ### Submission Process 1. **Check if tool fits** by reviewing our [criteria](#open-tool-criteria) below 2. **Gather information** listed in [required information](#required-information) 3. **Start a discussion** in our [GitHub Discussions](https://github.com/napcore-tools/web-awesome_napcore_tools/discussions) with the "Tool Submission" category 4. **Wait for review** of your submission by the NAPCORE team and the community 5. **Finish Documentation** after approval, we'll help create the tool page 6. **Publication of the tool in the catalogue!** ## Tool Inclusion Criteria {#open-tool-criteria} To be included in the catalogue, tools should meet these criteria: ### Essential Requirements - βœ… **Relevant to mobility data**: Supports European mobility data standards or workflows - βœ… **Publicly accessible**: Available for use (either open source or free to use) - βœ… **Functional**: Currently working and maintained - βœ… **Documented**: Has basic documentation or usage instructions ### Preferred Characteristics - 🌟 **Open source**: Open source tools are preferred - 🌟 **Standards-compliant**: Supports recognised European mobility standards - 🌟 **Actively maintained**: Regular updates and responsive to issues - 🌟 **Community-driven**: Open to contributions and feedback - 🌟 **Well-documented**: Comprehensive documentation and examples ### We Also Welcome - **Commercial tools** with free tiers or community editions - **Research prototypes or Work-in-progress tool** that demonstrate innovative approaches and/or show promise - **Internal tools** that organizations are willing to share ## Required Information When submitting a tool, please provide: ### Basic Information - **Tool name** - **Brief description** (1-2 sentences) - **Category** (Validators, Converters, SDKs, etc.) - **Current status** (Active, Maintenance, Beta, etc.) ### Links - **Live demo or website** (if applicable) - **Source code repository** (if open source) - **Documentation** - **Issue tracker** ### Technical Details - **Standards supported** (DATEX II, NeTEx, SIRI, mobilityDCAT-AP, etc.) - **License** (MIT, Apache, GPL, proprietary, etc.) - **Maintenance status** (actively maintained, maintenance mode, etc.) - **Key features** (3-5 bullet points) ### Context - **Target audience** (who should use this tool?) - **Use cases** (when should this tool be used?) - **Developer/Organization** - **Development history** (optional but helpful) ### Optional but Helpful - Screenshots or demo videos - Related tools or dependencies - Known limitations - Future roadmap ## Submission Template ```markdown **Tool Name**: [Your Tool Name] **Category**: [Select: Validators / Converters / SDKs / etc.] **Brief Description**: [1-2 sentence description of what the tool does] **Links**: - Webpage: [URL] - Source Code: [URL] - Documentation: [URL] - Repository: [URL] - Demo: [URL] **Standards Supported**: [DATEX II / NeTEx / SIRI / mobilityDCAT-AP / Other] **License**: [MIT / Apache / GPL / Proprietary / Other] **Status**: [Active / Maintenance / Beta / Deprecated] **Key Features**: - Feature 1 - Feature 2 - Feature 3 **Target Audience**: [Who should use this?] **Use Cases**: [When should this tool be used?] **Additional Information**: [Anything else we should know?] ``` ## Review Process ### What Happens After Submission? 1. **Initial Review** (1-3 days): Managing team checks if submission meets basic criteria 2. **Community Input** (3-7 days): Community members can provide feedback 3. **Decision** (within 2 weeks): Tool is approved, needs revisions, or is not suitable 4. **Documentation** (1-2 weeks): If approved, tool page is created 5. **Publication**: Tool appears in the catalogue ### Rejection Reasons Tools may not be included if they: - Are not relevant to European mobility data - Are unmaintained or non-functional - Have no documentation - Don't meet basic quality standards - Duplicate existing tools without clear advantages Don't worry - we'll provide feedback and suggestions if a tool doesn't initially meet criteria! ## Contribution Recognition We recognize and appreciate all contributors: - **Tool contributors** are credited on tool pages - **Content contributors** are listed in project acknowledgments - **Community helpers** are recognized in our discussions ## Other Ways to Contribute ### Improve Existing Tool Pages Found outdated information or want to add more details to a tool page? 1. Click "Suggest changes to this page" at the bottom of any tool page 2. Make your edits 3. Submit a pull request ### Report Issues Found a broken link or incorrect information? - Open an issue in our [GitHub repository](https://github.com/napcore-tools/web-awesome_napcore_tools/issues) - Or mention it in [Discussions](https://github.com/napcore-tools/web-awesome_napcore_tools/discussions) ### Suggest Improvements Have ideas for improving the catalogue? - Share them in [GitHub Discussions](https://github.com/napcore-tools/web-awesome_napcore_tools/discussions) - Propose new categories - Suggest better organization - Request new features ### Share Feedback Using a tool from the catalogue? Share your experience! - Add comments to tool discussions - Share success stories - Report issues directly to tool maintainers - Help other users in the community ## Questions? Need help or have questions about contributing? - **GitHub Discussions**: [Start a discussion](https://github.com/napcore-tools/web-awesome_napcore_tools/discussions) - **Email**: [Contact NAPCORE](https://napcore.eu/contact) ## Code of Conduct We are committed to providing a welcoming and inclusive environment for all contributors. Please: - Be respectful and professional - Provide constructive feedback - Focus on the tools and content, not individuals - Help create a positive community --- ::: tip Quick Start Ready to submit a tool? [Start a GitHub Discussion](https://github.com/napcore-tools/web-awesome_napcore_tools/discussions/new) with the "Tool Submission" category! ::: Thank you for helping build the European mobility tools ecosystem! πŸš€ --- URL: "/standards" LLMS_URL: "/standards.md" --- # Tools by Standard Browse tools organized by the European mobility data standards they support. --- URL: "/standards/datex-ii" LLMS_URL: "/standards/datex-ii.md" --- # DATEX II
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **DATEX II** standard. --- URL: "/standards/dcat-ap" LLMS_URL: "/standards/dcat-ap.md" --- # DCAT-AP
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **DCAT-AP** standard. --- URL: "/standards/gbfs" LLMS_URL: "/standards/gbfs.md" --- # GBFS
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **GBFS** standard. --- URL: "/standards/gtfs" LLMS_URL: "/standards/gtfs.md" --- # GTFS
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **GTFS** standard. --- URL: "/standards/gtfs-realtime" LLMS_URL: "/standards/gtfs-realtime.md" --- # GTFS Realtime
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **GTFS Realtime** standard. --- URL: "/standards/isodis-14819" LLMS_URL: "/standards/isodis-14819.md" --- # ISO/DIS 14819
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **ISO/DIS 14819** standard. --- URL: "/standards/mobilitydcat-ap" LLMS_URL: "/standards/mobilitydcat-ap.md" --- # mobilityDCAT-AP
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **mobilityDCAT-AP** standard. --- URL: "/standards/netex" LLMS_URL: "/standards/netex.md" --- # NeTEx
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **NeTEx** standard. --- URL: "/standards/osm" LLMS_URL: "/standards/osm.md" --- # OSM
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **OSM** standard. --- URL: "/standards/rdf" LLMS_URL: "/standards/rdf.md" --- # RDF
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **RDF** standard. --- URL: "/standards/rds-tmc" LLMS_URL: "/standards/rds-tmc.md" --- # RDS-TMC
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **RDS-TMC** standard. --- URL: "/standards/siri" LLMS_URL: "/standards/siri.md" --- # SIRI
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **SIRI** standard. --- URL: "/standards/transmodel" LLMS_URL: "/standards/transmodel.md" --- # TransModel
::: details {{ $params.details.longTitle }} ### Overview **Domain:** {{ $params.details.domain }} **Status:** {{ $params.details.status }} **More info:** {{ $params.details.link }} {{ $params.details.purpose }} ### Technical Details **Format/Technology:** {{ $params.details.format_technology }} **Maintainer/Origin:** {{ $params.details.maintainer_origin }}
### Related Standards
:::
## Tools Browse all tools that support the **TransModel** standard. --- URL: "/tools" LLMS_URL: "/tools.md" --- # All Tools Browse all available tools in the NAPCORE catalogue. Use the sidebar to filter by category or search above. ## Currently Available Tools ## Submit Your Tool Have a tool that should be listed here? We welcome contributions from the community! [Learn How to Contribute β†’](/contribute) ## Tool Statistics ## Recently Added ::: tip Latest Addition **ALERT-C Locations Tester** - Added October 2025 Validation tool for ALERT-C location references in traffic information ::: --- URL: "/tools/alert-c-tester.html" LLMS_URL: "/tools/alert-c-tester.md" document: "tool" title: "ALERT-C Locations Tester" description: "Validation tool for ALERT-C location references in RDS-TMC and DATEX II traffic information" fullDescription: null categories: - "validators" - "data-quality" - "testing" status: "active" endorsed: false license: "MIT" repository: "https://github.com/tamtamresearch/alert-c-locations-tester" website: null documentation: null demo: null developer: "TamTam Research s.r.o." technology: "Python, SQLite, CLI" language: "Python" type: "CLI Tool" standards: - "datex-ii" - "isodis-14819" - "rds-tmc" tags: - "ALERT-C" - "Validator" - "Python" - "CLI" - "RDS-TMC" - "Location References" lastUpdated: --- ## Overview ALERT-C Locations Tester is a validation tool for ALERT-C location references, which were primarily used in RDS-TMC services but have become popular also in other services such as provisioning road traffic information using DATEX II data formats. The tool generates a location index file from standard TMC format files (ISO/DIS 14819), providing complete enumeration of all possible location references for a given version of location tables. Users can then validate their traffic information content against this index to detect invalid location references that should not be used. ## Key Features - **Location index generation**: Creates comprehensive indices from TMC format files (.DAT) - **Format-agnostic validation**: Works with any traffic information format once location references are extracted - **Multiple output formats**: Generates SQLite databases and CSV files for flexible integration - **Comprehensive validation**: Checks primary location codes, directionality (+/-), and extent values (0-31) - **Large-scale processing**: Handles extensive location tables (45,929+ allocated locations) - **Command-line interface**: Easy automation and integration into CI/CD pipelines - **Extensible**: Reference implementation for DDR.xml format, adaptable to DATEX II and others ## Use Cases 1. **Data quality assurance**: Systematically validate location references before broadcasting or publishing 2. **Compliance verification**: Ensure conformance with ISO/DIS 14819 standard 3. **Pre-publication testing**: Validate traffic information before publishing on National Access Points 4. **Continuous monitoring**: Regular validation to maintain data quality standards 5. **Format migration**: Verify location references when converting between formats 6. **Development testing**: Validate location references during application development ## How It Works ### Two-Stage Approach #### Stage 1: Generate Location Index ```bash # Process TMC location tables to create validation index inv generate-index --location-table=path/to/table.DAT ``` Output: SQLite database and CSV file containing all valid location references #### Stage 2: Validate References ```bash # Extract location references from your traffic data # Compare against the generated index inv validate --content=path/to/traffic-data.xml ``` ## Invalid References Detected The tool identifies various types of invalid location references: - **Extent values above 31**: Maximum allowed extent is 31 - **Non-existent primary location codes**: e.g., location code 0 - **Invalid combinations**: Primary location, direction, and extent that don't exist together - **Undefined locations**: References to locations not defined in the location table version - **Out-of-range values**: Any values outside the valid ranges defined by the standard ## Standards Supported
DATEX II (with ALERT-C) ISO/DIS 14819 RDS-TMC
## Target Audience - Organizations operating RDS-TMC services across Europe - National Access Points managing DATEX II traffic information with ALERT-C referencing - Traffic information service providers - Road infrastructure authorities - NAP operators ensuring data quality - Developers implementing traffic information systems ## Technical Details ### Technology Stack - **Language**: Python - **Database**: SQLite for efficient index storage - **CLI Framework**: Invoke package for command-line interface - **Input Format**: TMC location tables (.DAT files) conforming to ISO/DIS 14819 - **Output Formats**: SQLite database, CSV files ### Location Table Format The tool processes TMC location tables in standard .DAT format according to ISO/DIS 14819. These tables contain: - Primary location codes - Direction information - Extent specifications - Location metadata ### Validation Components The tool validates three key components: 1. **Primary location codes**: Must exist in the location table 2. **Directionality**: Positive (+) or negative (-) direction 3. **Extent values**: Must be between 0 and 31 ## Example Implementation The repository includes a reference implementation for DDR.xml (legacy Czech format), which can serve as a template for: - Extracting location references from DATEX II XML - Processing other traffic information formats - Integrating validation into existing workflows ## Location Table Availability ::: warning Location Tables Not Included ALERT-C location tables are not included in the repository due to licensing restrictions. They are typically available from national traffic information centers. ::: **Example - Czech Location Tables:** Available for free after signing a license agreement at: [Czech NDIC TMC Location Table](https://registr.dopravniinfo.cz/en/sources/cz-ndic_tmc-location-table-v11.0/) Contact your national traffic information center for location tables in other countries. ## Operational Use - **Production deployment**: Currently in operational use by Czech Road and Motorway Directorate (ŘSD) - **Initial funding**: Development funded by ŘeditelstvΓ­ silnic a dΓ‘lnic s.p. (Czech Road and Motorway Directorate) - **Proven reliability**: Validates thousands of location references in production environment ## Why This Tool Matters ALERT-C Locations Tester addresses a critical data quality challenge in European road traffic information systems: ### Data Quality Assurance Systematic validation prevents broadcasting incorrect location information that could mislead drivers and compromise road safety. ### European Relevance ALERT-C is widely used for road traffic location referencing across Europe, both in traditional RDS-TMC and modern DATEX II services. ### Format Independence The two-stage approach (generate index β†’ validate references) makes it adaptable to any traffic information format, including DATEX II, RDS-TMC, legacy national formats, or custom implementations. ### Operational Efficiency Automates validation that would otherwise require manual checking of thousands of location references. ### Compliance Ensures conformance with ISO/DIS 14819 standard for ALERT-C location tables. ### Reusability While developed for Czech use case, the tool can work with any country's ALERT-C location tables in standard TMC format. ## Community & Contributions The maintainers welcome community contributions: - **New location indices**: Contributors can add indices for additional countries - **Format adapters**: Implementations for extracting references from different formats - **Improvements**: Bug fixes, feature enhancements, documentation - **Issues**: Report problems or suggest improvements on GitHub ::: info Community Extensible If you have properly licensed ALERT-C location tables for your country, consider contributing the generated indices to help the wider community! ::: ## Getting Started ### Prerequisites - Python 3.x - TMC location tables for your country (.DAT format) ### Installation ```bash git clone https://github.com/tamtamresearch/alert-c-locations-tester.git cd alert-c-locations-tester pip install -r requirements.txt ``` ### Basic Usage 1. **Generate location index**: ```bash inv generate-index --location-table=your-table.DAT ``` 2. **Implement reference extraction** for your format (use DDR.xml example as template) 3. **Validate your traffic data**: ```bash inv validate --content=your-traffic-data.xml ``` 4. **Review results**: Check output for invalid location references ## Related Tools This tool complements other DATEX II and traffic information tools: - [DATEX II Browser](/tools/datex-browser) - For exploring DATEX II model - [DATEX II Schema Tool](/tools/datex-schema-tool) - For creating DATEX II profiles - Validators for DATEX II content (coming soon to catalog) ## Support - **Issues**: [GitHub Issues](https://github.com/tamtamresearch/alert-c-locations-tester/issues) - **Source Code**: [GitHub Repository](https://github.com/tamtamresearch/alert-c-locations-tester) - **Documentation**: Included in repository --- --- URL: "/tools/datex-2.html" LLMS_URL: "/tools/datex-2.md" document: "tool" title: "DATEX II Documentation" description: "Platform Independent data model for the exchange of traffic and travel information (TTI) for Intelligent Transport Systems (ITS)." fullDescription: "DATEX II is a robust, platform-independent data model and exchange standard used primarily in Europe for the real-time sharing of traffic and travel information (TTI) between traffic management centers, service providers, and end-users." categories: - "references" status: "active" endorsed: true license: "CEN Standard" repository: null website: "https://datex2.eu/" documentation: "https://docs.datex2.eu/" demo: null developer: "DATEX II Project" technology: "Platform Independent Model" language: "XML Schema, JSON" type: "Standard" standards: - "datex-ii" tags: - "Data Model" - "Documentation" - "ITS" - "Road Traffic Data" - "Data Exchange" - "Mobility" lastUpdated: --- ## Overview DATEX II is the essential data exchange standard for Intelligent Transport Systems (ITS), mandated by the European Commission for the exchange of road traffic data. It provides a formal, platform-independent data model (based on UML) that can be implemented using standard formats like XML Schema and JSON. The goal of DATEX II is to achieve semantic interoperabilityβ€”ensuring that systems exchanging data understand the meaning of the information being transferred, regardless of the underlying technical infrastructure. ## Key Data Domains The standard is highly comprehensive, covering a wide array of traffic and travel information types: - **Road Traffic Data**: Traffic volume, speed, travel times, location and length of traffic queues. - **Situations**: Accidents, incidents, roadworks, temporary traffic management measures, weather conditions affecting the road. - **Traffic Regulation**: Speed limits, road closures, lane closures, variable road user charges. - **VMS (Variable Message Signs)**: Information and status of VMS. - **Parking & Fuel**: Availability of parking places and service areas, location of alternative fuel and charging points. ## Location Referencing A key strength of DATEX II is its support for various location referencing methods to precisely define the position of traffic events and data: - **Alert-C**: A simple, established coding system. - **TPEG-Loc**: The standardised location referencing method for TPEG (Transport Protocol Experts Group). - **OpenLR**: Open source dynamic location referencing standard. - **Linear Referencing**: Referencing relative to a known point along a road link. - **Point Coordinates**: Standard latitude/longitude coordinates (GML). ## Technical Architecture - **Core Model**: A single, comprehensive Platform Independent Model (PIM) defined in UML. - **Exchange Mechanisms**: Supports the exchange of data as `PayloadPublication` messages. - **Profiles**: The standard is modular, utilizing **Recommended Reference Profiles** (e.g., RTTI, SRTI, MMTIS) to define subsets of the full model required for specific use cases, simplifying implementation. - **Implementation**: The model is provided via XML Schemas and supports the emerging use of **JSON** for light-weight data exchange. ## Target Audience - **Road and Traffic Authorities/Operators**: For sharing real-time data within and across national borders. - **ITS Application Developers**: Creating services like navigation, journey planning, and dynamic information display. - **Mobility Data Platform Providers**: Building National Access Points (NAPs) for TTI data. - **System Integrators**: Implementing data exchange solutions for Intelligent Transport Systems. ## Why This Standard Matters 1. **Interoperability**: It is the foundation for seamless TTI data exchange across Europe, facilitating the creation of pan-European services. 2. **Mandated Compliance**: Adherence to DATEX II is often a regulatory requirement for public bodies sharing TTI data within the EU. 3. **Comprehensive Coverage**: Covers nearly every aspect of road-related mobility data, from accidents to charging station availability. 4. **Flexibility**: The use of Profiles (like RTTI and MMTIS) ensures implementations are tailored and efficient for specific deployment scenarios. ## Getting Started 1. Visit the [DATEX II Documentation Portal](https://docs.datex2.eu/). 2. Navigate to the **Levels** section to find tailored information for **Basics**, **Using**, **Mastering**, and **Expert** users. 3. Review the **Recommended Reference Profiles** to understand the specific data sets required for standard use cases (e.g., RTTI). 4. Download the necessary XML schemas or JSON specifications from the [Downloads section](https://docs.datex2.eu/downloads/). --- --- URL: "/tools/datex-browser.html" LLMS_URL: "/tools/datex-browser.md" document: "tool" title: "DATEX II Browser" description: "Wikipedia-style browser for exploring the DATEX II data model" fullDescription: "Wikipedia-style browser for exploring the DATEX II data model. Essential daily reference for DATEX II implementers." categories: - "development" - "converters" status: "active" endorsed: true license: "MIT" repository: "https://gitlab.com/tamtamresearch-public/datex2/browser" website: "https://browser.datex2.eu" documentation: null demo: null developer: "TamTam Research s.r.o." technology: "HTML, JavaScript" language: "JavaScript" type: "Web application" standards: - "datex-ii" tags: - "DATEX II" - "Browser" - "Reference" - "Search" firstRelease: 2014 lastUpdated: --- ## Overview DATEX II Browser is a web-based reference tool for browsing and searching the DATEX II data model. It provides Wikipedia-style ease of use for exploring the complete DATEX II specification, including packages, classes, enumerations, enumeration literals, attributes, and data types. The tool covers **6,187 structural elements, terms, and definitions** (DATEX II v3.6), making it an essential daily reference for anyone working with DATEX II. ## Key Features - **Full-text search** across all DATEX II model elements - **Hierarchical browsing** through packages, classes, and relationships - **Multiple version support**: Browse different DATEX II model versions (v2.3, v3.4, v3.6) - **Category filtering**: Search by packages, datatypes, enumerations, enumeration literals, classes, or attributes - **Direct linking**: Each element has a unique URL for easy referencing in documentation or discussions - **Offline capability**: Works offline after initial load - **Mobile-friendly**: Accessible on mobile devices - **Chrome standalone app**: Can be installed as a standalone application - **Static site deployment**: Published via GitLab Pages for reliability and performance ## Use Cases 1. **Quick reference** while implementing DATEX II publications 2. **Understanding relationships** between DATEX II elements 3. **Looking up definitions** of specific terms and concepts 4. **Teaching and learning** DATEX II standard 5. **Creating documentation** with accurate references to DATEX II elements 6. **Resolving ambiguities** in DATEX II specifications ## Available Versions
DATEX II v3.6 (Primary) DATEX II v3.4 DATEX II v2.3
### Version URLs - **v3.6 (Primary)**: [browser.datex2.eu](https://browser.datex2.eu) - **v3.4**: [datexbrowserv34.tamtamresearch.com](https://datexbrowserv34.tamtamresearch.com) - **v2.3**: [datexbrowser.tamtamresearch.com](https://datexbrowser.tamtamresearch.com) ## Target Audience - DATEX II implementers and developers - Traffic engineers working with traffic information systems - Standardization experts - System architects designing NAP solutions - Anyone needing to understand DATEX II terminology and structure ## Technical Architecture - **Frontend**: Modern web application (JavaScript/TypeScript-based) - **Data source**: DATEX II class model (from Enterprise Architect) converted to JSON format - **Conversion tool**: [datex2json](https://gitlab.com/tamtamresearch-public/datex2/browser/datex2json) - custom converter from EA model to JSON - **Deployment**: Static web hosting via GitLab Pages - **Architecture**: Client-side application with full model loaded in browser ## Source Code The tool is open source and available on GitLab: - **Main Group**: [gitlab.com/tamtamresearch-public/datex2/browser](https://gitlab.com/tamtamresearch-public/datex2/browser) - **Frontend**: [gitlab.com/tamtamresearch-public/datex2/browser/frontend](https://gitlab.com/tamtamresearch-public/datex2/browser/frontend) - **datex2json converter**: [gitlab.com/tamtamresearch-public/datex2/browser/datex2json](https://gitlab.com/tamtamresearch-public/datex2/browser/datex2json) ## Development History Originally developed by TamTam Research s.r.o. and presented at DATEX II User Forum in Prague (May 2014). The tool has evolved over the years to support multiple DATEX II versions, with the latest version (v3.6) now hosted at the primary domain browser.datex2.eu. **Presentation**: Available on [SlideShare](https://www.slideshare.net/vlcinsky/datex-ii-browser) (from 2014 User Forum) ## Why This Tool Matters DATEX II Browser fills a critical need in the European mobility data ecosystem: 1. **Accessibility**: Makes the complex DATEX II standard easily accessible without downloading specifications or opening XSD files 2. **Daily use**: Designed for frequent, quick consultations - similar to how developers use Wikipedia or MDN 3. **Proven value**: Has been used by the DATEX II community since 2014 (over 10 years) 4. **Version support**: Handles multiple DATEX II versions, accommodating different implementation needs 5. **European focus**: Directly supports a key European mobility data standard 6. **No installation required**: Instant access via web browser 7. **Community resource**: Benefits the entire DATEX II implementation community 8. **Open source**: MIT licensed, allowing community contributions and transparency ## Related Tools This browser complements other DATEX II tools like: - [DATEX II Schema Generation Tool](/tools/datex-schema-tool) - For creating custom profiles - Validators and converters (coming soon to catalog) ::: tip Developer Note The **datex2json converter** is particularly interesting as it demonstrates how to extract and transform DATEX II model data from Enterprise Architect files into a web-friendly format. This approach could be valuable for other standard-specific browsers. ::: ## Getting Started 1. Visit [browser.datex2.eu](https://browser.datex2.eu) 2. Use the search bar to find specific elements 3. Browse through the hierarchical structure 4. Click on any element to see its full definition and relationships No installation or registration required! ## Support & Community - **Issues & Questions**: [GitLab Issues](https://gitlab.com/tamtamresearch-public/datex2/browser/-/issues) - **DATEX II Community**: [datex2.eu](https://datex2.eu) --- --- URL: "/tools/datex-schema-tool.html" LLMS_URL: "/tools/datex-schema-tool.md" document: "tool" title: "DATEX II Schema Generation Tool" description: "Web-based wizard for creating custom DATEX II profiles and generating schemas" fullDescription: "Web-based wizard for creating custom DATEX II profiles. Generate XML Schema, JSON Schema, or ASN.1 schemas by selecting only the elements you need." categories: - "converters" - "development" status: "active" endorsed: true repository: null website: "https://webtool.datex2.eu" documentation: null demo: null developer: "DATEX II community (datex2.eu)" technology: "Platform Independent Model" language: "XML Schema, JSON" type: "Web Application, Profile Generator" mainContributor: "Jonas JΓ€derberg" standards: - "datex-ii" tags: - "DATEX II" - "Schema" - "Wizard" - "Profile" - "XML Schema" - "JSON Schema" - "ASN.1" lastUpdated: --- ## Overview The DATEX II Schema Generation Tool is a web-based wizard that helps you create custom DATEX II profiles tailored to your specific needs. The full DATEX II model is very comprehensive - this tool lets you select only the elements, profiles, and constraints relevant to your use case, making implementation simpler and more focused. ## Key Features - **Interactive wizard interface** for profile creation - **Model selection**: Choose from available DATEX II models or import your own XMI file - **Element selection**: Pick specific elements, profiles, and constraints - **Multiple output formats**: - XML Schema (XSD) - JSON Schema - ASN.1 - **Profile customization**: Create tailored subsets of the DATEX II model - **Export functionality**: Download generated schemas ## How to Use 1. Visit [webtool.datex2.eu](https://webtool.datex2.eu) and click **[Wizard]** 2. **Select a DATEX II model** (or import your own XMI file) 3. **Choose elements**: Select which elements, profiles, and constraints you want to include 4. **Export schemas**: Download in your preferred format (XSD, JSON Schema, or ASN.1) ## Why This Tool is Useful The full DATEX II model covers a wide range of use cases and scenarios, which means it includes many elements that any single implementation may not need. This tool addresses that challenge by: 1. **Simplifying implementation**: Focus only on relevant elements for your specific use case 2. **Reducing complexity**: Smaller schemas are easier to understand and maintain 3. **Improving performance**: Validation against a subset schema is faster 4. **Better documentation**: A tailored profile serves as clear documentation of your implementation scope 5. **Facilitating interoperability**: Share your profile with partners to clarify your data exchange requirements ## Use Cases 1. **Creating NAP-specific profiles**: National Access Points can define exactly what they support 2. **Service-specific implementations**: Create profiles for specific services (parking, traffic incidents, etc.) 3. **Testing and development**: Generate simplified schemas for easier testing 4. **Documentation**: Export profiles to document implementation scope 5. **Proof of concept**: Quickly create minimal profiles for prototyping ## Standards Supported
DATEX II
## Target Audience - DATEX II implementers defining their profile - NAP operators specifying data requirements - System integrators working with multiple DATEX II systems - Developers creating DATEX II applications - Traffic data managers defining data exchange specifications ## Technical Details - **Platform**: Web-based application - **Input formats**: DATEX II models, XMI files - **Output formats**: XML Schema, JSON Schema, ASN.1 - **Architecture**: Client-side processing (no data leaves your browser) ## Related Tools This schema generation tool works well with: - [DATEX II Browser](/tools/datex-browser) - For exploring the full DATEX II model - DATEX II validators (coming soon to catalog) - DATEX II converters (coming soon to catalog) ## Community & Support - **Official Website**: [datex2.eu](https://datex2.eu) - **Community Forums**: DATEX II User Group - **Documentation**: Available through DATEX II website ::: tip Future Development This tool is currently not open source, but there are discussions about a possible future open source release. Check the DATEX II community channels for updates. ::: ## About DATEX II DATEX II is a European standard for exchanging traffic information and traffic data. It provides a comprehensive model for describing various types of traffic-related information including: - Traffic incidents and events - Traffic conditions and flow data - Road conditions and weather - Traffic management actions - Parking information - Variable message signs - And much more The standard is widely used across European National Access Points and traffic management systems. ## Getting Started 1. **Explore the model**: First, use the [DATEX II Browser](/tools/datex-browser) to understand available elements 2. **Visit the tool**: Go to [webtool.datex2.eu](https://webtool.datex2.eu) 3. **Start the wizard**: Click on the Wizard button 4. **Create your profile**: Select the elements you need 5. **Export and use**: Download your custom schema No installation or registration required! --- --- URL: "/tools/mobilitydcat-generator.html" LLMS_URL: "/tools/mobilitydcat-generator.md" document: "tool" title: "mobilityDCAT-AP Generator Tool" description: "Form-based web interface for generating RDF metadata according to mobilityDCAT-AP" fullDescription: "Form-based web interface that generates RDF metadata according to the mobilityDCAT-AP specification. Perfect for NAP operators and data publishers." categories: - "metadata" - "development" status: "active" endorsed: true license: "Apache-2.0" repository: "https://github.com/mobilityDCAT-AP/mobilitydcatap-ui" website: "https://mobilitydcat-ap.github.io/mobilitydcatap-ui/" documentation: null demo: null developer: "Cefriel" technology: "RDF, JSON" language: "JavaScript, Vue" type: "Web Application, Generator" maintainedBy: "NAPCORE Metadata Working Group" standards: - "mobilitydcat-ap" - "dcat-ap" - "rdf" tags: - "mobilityDCAT-AP" - "RDF" - "Metadata" - "Generator" - "Form" lastUpdated: --- ## Overview The mobilityDCAT-AP Generator Tool is a form-based web interface that generates RDF metadata according to the mobilityDCAT-AP specification. This tool allows users to create structured, machine-readable metadata descriptions for mobility datasets and data services **without needing to write RDF code directly**. It's designed to help data publishers test and experiment with different metadata elements while learning how to properly describe mobility data according to the mobilityDCAT-AP standard. The form is compliant with the **minimum profile of mobilityDCAT-AP**. ## Key Features - **Form-based interface**: No need to write RDF code manually - **Guided metadata creation**: Step-by-step approach to creating compliant metadata - **Learning tool**: Experiment with different metadata elements to understand mobilityDCAT-AP - **Instant RDF generation**: Produces machine-readable RDF output - **Minimum profile compliance**: Ensures generated metadata meets minimum requirements - **Web-based**: No installation required, accessible via browser - **Open source**: Available for review, modification, and self-hosting - **Docker support**: Can be deployed using Docker containers ## Use Cases 1. **Creating metadata** for mobility datasets on National Access Points 2. **Learning mobilityDCAT-AP**: Understanding what metadata elements are required and optional 3. **Testing metadata**: Experimenting with different metadata configurations 4. **Quick prototyping**: Generating sample metadata for proof-of-concept work 5. **Documentation**: Creating example metadata for specifications and guidelines 6. **Training**: Teaching teams how to properly describe mobility data ## Standards Supported
mobilityDCAT-AP DCAT-AP RDF
## Target Audience - NAP operators creating metadata catalogues - Data publishers describing mobility datasets - Developers implementing mobilityDCAT-AP in their platforms - Metadata specialists learning the mobilityDCAT-AP specification - Data portal administrators - Anyone needing to create standardized metadata for mobility data ## About mobilityDCAT-AP mobilityDCAT-AP is a metadata specification developed by NAPCORE to enhance cross-border and cross-sectorial discoverability of mobility-related datasets. It extends DCAT-AP (the European standard for data portal metadata) with mobility-specific elements, providing precise metadata designations for: - Data topics and categories - Data providers and publishers - Data formats and access methods - Geographical coverage - Temporal coverage - Update frequency - Mobility-relevant aspects The specification addresses the fragmented European mobility data ecosystem by enabling harmonized, platform-independent metadata descriptions in both human-readable and machine-readable formats. ### mobilityDCAT-AP Key Info - **Specification v1.1.0**: Released January 2025 - **Governance**: Maintained by NAPCORE Metadata Working Group - **Requirements**: Based on 40 requirements from literature review and stakeholder input - **Adoption**: Early adopters include several European NAPs - **Documentation**: [w3id.org/mobilitydcat-ap](https://w3id.org/mobilitydcat-ap) ## Related Resources - **mobilityDCAT-AP Specification**: [w3id.org/mobilitydcat-ap](https://w3id.org/mobilitydcat-ap) - **Main GitHub Organization**: [github.com/mobilityDCAT-AP](https://github.com/mobilityDCAT-AP) - **Specification Repository**: [github.com/mobilityDCAT-AP/mobilityDCAT-AP](https://github.com/mobilityDCAT-AP/mobilityDCAT-AP) - **Controlled Vocabularies**: [github.com/mobilityDCAT-AP/controlled-vocabularies](https://github.com/mobilityDCAT-AP/controlled-vocabularies) ## Technical Architecture - **Framework**: Built using Cefriel's rapid-triples tool - **Frontend**: Vue.js application - **Deployment**: Static hosting via GitHub Pages - **Output format**: RDF (Resource Description Framework) - **Docker support**: Can be deployed using Docker containers ## Deployment Options 1. **Use the hosted version**: [mobilitydcat-ap.github.io/mobilitydcatap-ui](https://mobilitydcat-ap.github.io/mobilitydcatap-ui/) 2. **Self-host using Docker** 3. **Integrate into existing data portal infrastructure** ## Why This Tool Matters mobilityDCAT-AP Generator Tool addresses critical needs in the European mobility data ecosystem: 1. **Lowers barriers**: Makes metadata creation accessible to non-technical users 2. **Standardization**: Ensures metadata follows the recommended European standard 3. **Educational value**: Helps users understand mobilityDCAT-AP requirements through hands-on experience 4. **NAP adoption**: Supports implementation of mobilityDCAT-AP across National Access Points 5. **European initiative**: Part of official NAPCORE recommendations for metadata harmonization 6. **Quick start**: Enables data publishers to create compliant metadata immediately 7. **Open approach**: Transparent, community-driven tool development 8. **Cross-border interoperability**: Facilitates findability and reusability of mobility data across Europe ## Recent Publication The methodology and design of mobilityDCAT-AP was published in March 2025: **"mobilityDCAT-AP: a Metadata Specification for Enhanced Cross-border Mobility Data Sharing"** Available on arXiv: [2503.11535](https://arxiv.org/abs/2503.11535) ## Getting Started 1. **Visit the tool**: [mobilitydcat-ap.github.io/mobilitydcatap-ui](https://mobilitydcat-ap.github.io/mobilitydcatap-ui/) 2. **Fill in the form**: Provide information about your dataset or data service 3. **Generate RDF**: Click to generate machine-readable metadata 4. **Download or copy**: Use the generated RDF in your data portal or catalog No installation or registration required! ## Implementation Support - **GitHub Issues**: For questions and feedback - **Wiki**: FAQs and practical guidelines - **Direct support**: From NAPCORE Metadata Working Group for early adopters - **Community**: Connect through NAPCORE channels ::: tip Learning Resource This tool is an excellent way to learn mobilityDCAT-AP by doing. Start with a simple dataset description and explore optional fields to understand the full specification capabilities. ::: ## Source Code - **Tool Repository**: [github.com/mobilityDCAT-AP/mobilitydcatap-ui](https://github.com/mobilityDCAT-AP/mobilitydcatap-ui) - **Specification**: [github.com/mobilityDCAT-AP/mobilityDCAT-AP](https://github.com/mobilityDCAT-AP/mobilityDCAT-AP) - **License**: Apache-2.0 (open source) ## Community & Support - **Issues & Questions**: [GitHub Issues](https://github.com/mobilityDCAT-AP/mobilitydcatap-ui/issues) - **Discussions**: NAPCORE Metadata Working Group - **Documentation**: [mobilityDCAT-AP Wiki](https://github.com/mobilityDCAT-AP/mobilityDCAT-AP/wiki) --- --- URL: "/tools/motis.html" LLMS_URL: "/tools/motis.md" document: "tool" title: "MOTIS" description: "Scalable high-performance intermodal travel information system with batteries included" fullDescription: "Scalable high-performance intermodal travel information system / journey planner with \"batteries included\" - geocoding, map tiles, departure boards, and more." categories: - "route-planners" status: "active" endorsed: false license: "MIT" repository: "https://github.com/motis-project/motis" website: "https://transitous.org/" documentation: null demo: null developer: "MOTIS Project" technology: null language: "C++, TypeScript" type: "Web Application" standards: - "netex" - "siri" - "gtfs" - "gbfs" - "osm" tags: - "Journey Planner" - "Router" - "Intermodal" - "Real-time" - "Geocoding" - "GTFS-RT" lastUpdated: --- ## Overview MOTIS is a comprehensive intermodal travel information system and journey planner designed for scalability and high performance. Unlike many routing engines that require external services, MOTIS comes with "batteries included" - providing geocoding, map tiles, departure boards, and many other functionalities out of the box. The system can serve multiple purposes beyond routing: it functions as a real-time data quality monitoring tool (metrics), a conversion utility (SIRI to GTFS-RT), and a modular platform where features can be enabled or disabled based on specific needs, allowing for specialized low-resource configurations. ## Key Features - **Intermodal routing**: Seamless journey planning across multiple transport modes - **Built-in geocoding**: No need for external geocoding services - **Map tile serving**: Integrated map rendering capabilities - **Departure boards**: Real-time departure information displays - **Real-time monitoring**: Quality metrics for real-time data feeds - **Format conversion**: SIRI to GTFS-RT transformation - **Modular architecture**: Enable/disable features as needed for optimized resource usage - **High performance**: Designed for scalability and speed - **Specialized configurations**: Distribute tailored setups with minimal overhead ## Use Cases 1. **Journey planning applications** requiring intermodal routing capabilities 2. **Real-time data quality monitoring** for transport operators 3. **Format conversion** from SIRI to GTFS-RT for data standardization 4. **Low-resource deployments** with customized feature sets 5. **Community routing services** like Transitous 6. **Development and testing** of mobility applications ## Available Standards
NeTEx SIRI GTFS GBFS OpenStreetMap (OSM)
## Target Audience - Journey planning application developers - Transport operators and authorities - Mobility data platform providers - Real-time data quality analysts - Open source mobility communities - System integrators building NAP solutions ## Technical Architecture - **Core**: High-performance routing engine with modular design - **Data formats**: NeTEx, SIRI, GTFS, GBFS, OSM - **Capabilities**: - Routing and journey planning - Geocoding services - Map tile generation - Real-time data processing - Format conversion (SIRI β†’ GTFS-RT) - **Deployment**: Configurable modules for resource-optimized setups - **Architecture**: Scalable multi-modal routing with optional services ## Source Code The tool is open source and available on GitHub: - **MOTIS**: [github.com/motis-project/motis](https://github.com/motis-project/motis) - **Transitous Platform**: [transitous.org](https://transitous.org/) ## Transitous: Community-Powered Global Routing **Transitous** is an open data community initiative that crowd-sources a global mobility data catalog. This community-maintained catalog feeds into a hosted MOTIS router instance, making it available for FOSS (Free and Open Source Software) client applications worldwide. This collaboration demonstrates MOTIS's real-world capability to power large-scale, community-driven mobility services. ## Why This Tool Matters MOTIS addresses key challenges in the European and global mobility ecosystem: 1. **Complete solution**: "Batteries included" approach eliminates dependency on multiple external services 2. **Flexibility**: Modular architecture allows tailored deployments for different use cases 3. **Performance**: Built for high-performance, scalable routing 4. **Open source**: MIT license enables wide adoption and community contributions 5. **Multi-standard support**: Works with major European (NeTEx, SIRI) and global (GTFS) standards 6. **Real-world proven**: Powers production services like Transitous and MOBIDROM 7. **Quality monitoring**: Built-in metrics for real-time data quality assessment 8. **Format bridge**: Converts between SIRI and GTFS-RT, facilitating interoperability ## Related Tools MOTIS complements other mobility tools in the ecosystem: - Real-time validators for SIRI and GTFS-RT feeds - NeTEx converters and validators - Other journey planning engines and routing services ::: tip Developer Note MOTIS's modular architecture is particularly valuable - you can deploy only the components you need (e.g., just the converter functionality or just the routing engine), making it suitable for both full-featured applications and specialized microservices. ::: ## Getting Started 1. Visit the [MOTIS GitHub repository](https://github.com/motis-project/motis) 2. Review documentation and deployment options 3. Configure modules based on your requirements 4. Deploy as a complete solution or specialized service 5. Try the live Transitous instance at [transitous.org](https://transitous.org/) ## Real-World Deployments - **Transitous**: Global community routing platform - **MOBIDROM**: Production mobility platform ## Support & Community - **Source Code & Issues**: [GitHub Repository](https://github.com/motis-project/motis) - **Transitous Community**: [transitous.org](https://transitous.org/) --- --- URL: "/tools/nplan.html" LLMS_URL: "/tools/nplan.md" document: "tool" title: "NPlan" description: "Open-source editor and backend system for creating and maintaining demand-responsive transport (DRT), flexible transport services, and timetable-based route planning" fullDescription: "NPlan is an open-source editor and backend system designed for small and medium-sized public transport operators and authorities to create and maintain demand-responsive transport (DRT), flexible transport services, and timetable-based route planning. It consists of the Enki web editor (frontend) and the Uttu backend services, forming a complete toolchain for planning, editing, and exporting transport data in NeTEx format." categories: - "reference-implementations" status: "active" endorsed: false license: "EUPL-1.2" repository: "https://github.com/entur/Transportdata-open-source-intro#nplan" website: null documentation: null demo: null developer: "Entur (Norway) & Fintraffic (Finland)" technology: "Java, TypeScript" language: "Java, TypeScript" type: "Editor" standards: - "netex" tags: - "NeTEx" - "DRT" - "Editor" - "Planning Tool" - "Public Transport" - "Flexible Services" lastUpdated: --- ## Overview NPlan is an open-source editor and backend system for creating and maintaining demand-responsive transport (DRT), flexible transport services, and timetable-based route planning. Designed primarily for small and medium-sized public transport operators and authorities, NPlan fills an important gap between complex enterprise planning systems and manual data preparation. The system consists of two main components: - **Enki**: Web-based editor (frontend) for planning and editing transport services - **Uttu**: Backend services for data management and NeTEx export Together, they form a complete toolchain for planning, editing, and exporting transport data in standard-compliant formats. ## Key Features - **Flexible service planning**: Support for demand-responsive transport, booking-based services, and scheduled routes - **NeTEx export**: Native support for exporting data in NeTEx format with Nordic profile compliance - **User-friendly interface**: Web-based editor designed for non-technical transport planners - **Small-scale optimization**: Tailored for operators managing up to 30 flexible or scheduled lines - **Complete workflow**: Integrated planning, editing, and export in a single system - **Open source**: Community-driven development with contributions from multiple countries - **Production-proven**: Active use across multiple Nordic countries with real-world validation ## Use Cases 1. **Demand-responsive transport planning**: Design and maintain DRT services that adapt to passenger demand 2. **Flexible service management**: Plan booking-based and on-demand transport services 3. **Small route network planning**: Manage scheduled services for small and medium-sized operators 4. **Data standardization**: Ensure transport data meets NeTEx requirements for National Access Points 5. **Gap filling**: Bridge the gap between manual planning and enterprise-scale systems 6. **Nordic profile compliance**: Create NeTEx data conforming to Nordic profile specifications ## Target Audience - Small and medium-sized public transport operators - Regional transport authorities managing flexible services - Demand-responsive transport service providers - National Access Points requiring NeTEx-compliant data from smaller operators - Transport planners working with flexible and on-demand services - Organizations transitioning from manual planning to standardized data formats ## Technical Details ### Technology Stack - **Frontend (Enki)**: TypeScript-based web editor - **Backend (Uttu)**: Java-based backend services - **Data Format**: NeTEx XML with Nordic profile support - **Deployment**: Can be self-hosted by organizations ### System Architecture NPlan consists of two integrated components: 1. **Enki (Frontend)**: Provides the user interface for transport planners to design routes, define service patterns, set operating hours, and configure flexible service parameters 2. **Uttu (Backend)**: Handles data persistence, validation, and export functionality, ensuring data consistency and NeTEx compliance ### Supported Service Types - Demand-responsive transport (DRT) - Booking-based services - Flexible routes with conditional stops - Traditional scheduled services - Mixed service patterns ## Production Deployment NPlan is actively used in production environments across the Nordic region: - **Norway**: 10–15 operators currently using the system - **Finland**: Approximately 20 operators managing flexible services - **Typical scale**: Operators manage up to 30 flexible or scheduled lines per deployment - **Joint development**: Maintained collaboratively by Entur (Norway) and Fintraffic (Finland) ## Why This Tool Matters ### Accessibility for Smaller Operators NPlan makes standardized transport data creation accessible to operators who cannot justify the cost and complexity of enterprise planning systems. ### Standards Compliance Made Easy The tool handles NeTEx complexity behind a user-friendly interface, enabling operators to publish high-quality, standard-compliant data without deep technical expertise. ### Filling a Critical Gap Many flexible and DRT services across Europe lack proper digital representation due to tool limitations. NPlan addresses this gap, enabling better integration into multi-modal journey planning and National Access Points. ### Open Governance Model As an open-source project with multi-country governance, NPlan benefits from shared development costs, diverse use cases, and community-driven improvements. ### Nordic Profile Leadership Norway and Finland have pioneered NeTEx implementation for flexible services. NPlan embodies this expertise, providing a reference implementation for other countries. ## Community & Contributions NPlan is developed under an open governance model: - **Joint maintenance**: Entur (Norway) and Fintraffic (Finland) - **Open participation**: Additional organizations welcome to contribute - **Community-driven**: Issues, features, and improvements guided by real-world operator needs - **Shared costs**: Development burden distributed across participating countries ::: info Open for Collaboration Organizations interested in contributing to NPlan development or adopting the system are encouraged to engage with the project maintainers through GitHub. ::: ## Getting Started ### Component Repositories - **Enki (Frontend)**: [github.com/entur/enki](https://github.com/entur/enki) - **Uttu (Backend)**: [github.com/entur/uttu](https://github.com/entur/uttu) - **Overview**: [Entur Transport Data Open Source Intro](https://github.com/entur/Transportdata-open-source-intro#nplan) ### Prerequisites - Java runtime environment (for Uttu backend) - Modern web browser (for Enki frontend) - Understanding of public transport planning concepts - Familiarity with NeTEx concepts (helpful but not required) ### Typical Deployment 1. Deploy Uttu backend services in your infrastructure 2. Configure Enki frontend to connect to Uttu 3. Set up user authentication and access controls 4. Train transport planners on the editor interface 5. Begin planning flexible services and export NeTEx data ## Related Tools NPlan complements other mobility data tools in the ecosystem: - **NeTEx validators**: For validating exported NeTEx data - **Journey planning systems**: Consuming NPlan's NeTEx output - **National Access Point platforms**: Publishing data generated by NPlan ## Support - **Source Code**: - [Enki Frontend](https://github.com/entur/enki) - [Uttu Backend](https://github.com/entur/uttu) - **Project Overview**: [Transportdata Open Source Intro](https://github.com/entur/Transportdata-open-source-intro#nplan) - **Issues**: Report issues in the respective GitHub repositories --- --- URL: "/tools/xsd-browser.html" LLMS_URL: "/tools/xsd-browser.md" document: "tool" title: "XSD-Browser" description: "Generates interactive, self-contained HTML documentation from XSD (XML Schema Definition)" fullDescription: null categories: - "converters" - "development" status: "active" endorsed: false license: "AGPL-3.0-or-later" repository: "https://github.com/tamtamresearch/xsd-browser" website: "https://tamtamresearch.github.io/xsd-browser/" documentation: "https://github.com/tamtamresearch/xsd-browser#readme" demo: null developer: "TamTam Research s.r.o." technology: "Python, CLI, HTML, WebAssembly, Pyodide" language: "Python, JavaScript, TypeScript" type: "CLI Tool, Web Application" standards: null tags: - "XML Schema" - "XSD" - "CLI" - "Web Application" lastUpdated: --- ## Overview A tool that generates interactive, self-contained HTML documentation from XSD (XML Schema Definition) files, enabling developers to visually explore and navigate complex schema hierarchies used in European mobility data standards. ## Key Features: - No install required: open the web app (e.g., from https://tamtamresearch.github.io/xsd-browser/), drag and drop a single XSD file, a folder of schema files, or a ZIP archive β€” the schema is rendered instantly in the browser - Download the result as a fully self-contained HTML file with no external dependencies, or browse it directly in the browser - Recursively resolves all / references with automatic namespace prefix handling - Cross-reference linking between elements, types, and groups, with "Used by" sections showing where each definition appears - Hash-based navigation (#element-Name, #type-Name, #group-Name) with collapsible, lazy-loaded views and persistent UI state - CLI (python based) conversion script is available too. ## Target Audience Developers and data modelers working with XSD-based European mobility data standards (DATEX II, NeTEx, SIRI) who need to understand, document, or onboard others to complex schema structures. ## Use Cases Exploring DATEX II, NeTEx, or SIRI schemas interactively without any setup; generating shareable offline documentation from a multi-file XSD set; onboarding new developers to an unfamiliar schema; producing single-file schema docs for distribution alongside a data product. ## Additional Information Processing runs entirely in the browser via WebAssembly (Pyodide) β€” no data is sent to any server. A command-line version is also available: uv tool install "git+https://github.com/tamtamresearch/xsd-browser.git". Developed by [TamTam Research s.r.o.](https://www.tamtamresearch.com) ---