PRICES include / exclude VAT
Homepage>BS Standards>35 INFORMATION TECHNOLOGY. OFFICE MACHINES>35.240 Applications of information technology>35.240.60 IT applications in transport and trade>PD CEN/TS 17118:2024 Intelligent transport systems. Public transport. Open API for distributed journey planning
Sponsored link
immediate downloadReleased: 2024-12-18
PD CEN/TS 17118:2024 Intelligent transport systems. Public transport. Open API for distributed journey planning

PD CEN/TS 17118:2024

Intelligent transport systems. Public transport. Open API for distributed journey planning

Format
Availability
Price and currency
English Secure PDF
Immediate download
440.00 USD
You can read the standard for 1 hour. More information in the category: E-reading
Reading the standard
for 1 hour
44.00 USD
You can read the standard for 24 hours. More information in the category: E-reading
Reading the standard
for 24 hours
132.00 USD
English Hardcopy
In stock
440.00 USD
Standard number:PD CEN/TS 17118:2024
Pages:260
Released:2024-12-18
ISBN:978 0 539 30043 7
Status:Standard
PD CEN/TS 17118:2024 - Intelligent Transport Systems

PD CEN/TS 17118:2024 - Intelligent Transport Systems: Public Transport Open API for Distributed Journey Planning

Welcome to the future of public transport systems with the PD CEN/TS 17118:2024 standard. This comprehensive document is a must-have for professionals and organizations involved in the development and implementation of intelligent transport systems. It provides a detailed framework for an open API designed specifically for distributed journey planning, ensuring seamless integration and enhanced efficiency in public transport networks.

Key Features of the PD CEN/TS 17118:2024 Standard

This standard is a pivotal resource for anyone looking to innovate in the field of public transport. Here are some of the key features and benefits:

  • Comprehensive Coverage: With 260 pages of in-depth information, this standard covers all aspects of open API development for distributed journey planning.
  • Latest Release: Released on December 18, 2024, this document reflects the most current advancements and best practices in intelligent transport systems.
  • ISBN: 978 0 539 30043 7 - Easily reference and cite this standard in your work.
  • Standard Status: As a recognized standard, it provides authoritative guidance and is widely accepted in the industry.

Why Choose PD CEN/TS 17118:2024?

In the rapidly evolving world of public transport, staying ahead of the curve is crucial. The PD CEN/TS 17118:2024 standard offers numerous advantages:

Enhanced Interoperability

By adopting this standard, transport systems can achieve greater interoperability. The open API framework facilitates seamless communication between different systems and platforms, allowing for more efficient journey planning and management.

Improved User Experience

With distributed journey planning, users can enjoy a more streamlined and user-friendly experience. The standard ensures that data is accessible and usable across various devices and applications, enhancing the overall travel experience for passengers.

Future-Proof Your Systems

As technology continues to advance, having a robust and adaptable framework is essential. The PD CEN/TS 17118:2024 standard is designed to be future-proof, accommodating new technologies and methodologies as they emerge.

Who Should Use This Standard?

This standard is ideal for a wide range of stakeholders in the public transport sector, including:

  • Transport Authorities: Ensure your systems are up-to-date and compliant with the latest standards.
  • Software Developers: Create innovative solutions that integrate seamlessly with existing transport networks.
  • Urban Planners: Design smarter cities with efficient and interconnected transport systems.
  • Consultants: Provide expert advice and solutions to clients looking to enhance their transport infrastructure.

Conclusion

The PD CEN/TS 17118:2024 standard is an essential tool for anyone involved in the development and management of intelligent transport systems. By providing a comprehensive framework for an open API, it enables more efficient and effective journey planning, ultimately leading to better public transport services. Stay ahead in the industry by integrating this standard into your operations and projects.

Embrace the future of public transport with the PD CEN/TS 17118:2024 standard and ensure your systems are ready for the challenges and opportunities of tomorrow.

DESCRIPTION

PD CEN/TS 17118:2024


This standard PD CEN/TS 17118:2024 Intelligent transport systems. Public transport. Open API for distributed journey planning is classified in these ICS categories:
  • 35.240.60 IT applications in transport
The Technical Specification will be adapted in the following way: • OJP will be realigned with the latest Transmodel version and NeTEx issues, where appropriate (e.g. New Modes) • The integration of new modes especially the conceptual equivalency to major multi-modal standards shall be studied and if necessary, adaptions to OJP occur. The idea is to study OSDM, TOMP, TRIAS and GBFS/GOFS. The interactions should be smooth. Interaction between OJP and distribution features will be settled. • OJP is extended as far into the distribution area as it is considered a good idea. For the actual booking and purchase steps, OSDM, TOMP, TRIAS and/or GOFS are to be used. The line we think to draw is: booking. OJP should not transfer personalized information. This results in the following proposed adaptions to fit OJP into a full MaaS roaming environment: o An availability request (with response) o Token/id handling for trips and trip legs (for hand-over) and pushed information during trips. We will need to model bookable items on some level. o OJPFare needs to be extended/adapted. o TripInfoRequest and -Response need to be updated to reflect, information about trips and trip legs and not only vehicle and journey. • All work prepared under the heading OJP 1.1 will be finalised. • EPIAP (Accessibility) minimal profile will be used to verify that the trip planning can make use of it. • The provision of an OpenAPI and REST/JSON derived directly from the XSD shall be studied (eventually using a converter).