ojp-rs 0.2.4

A library for interacting with Open Journey Planner (OJP) services
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

[![Crates.io](https://img.shields.io/crates/v/ojp-rs.svg)](https://crates.io/crates/ojp-rs)
[![Documentation](https://docs.rs/ojp-rs/badge.svg)](https://docs.rs/ojp-rs/)
[![Codecov](https://codecov.io/gh/urban-travel/ojp-rs/graph/badge.svg?token=IO4NWPBZHQ)](https://codecov.io/gh/urban-travel/ojp-rs)
[![Dependency status](https://deps.rs/repo/github/urban-travel/ojp-rs/status.svg)](https://deps.rs/repo/github/urban-travel/ojp-rs)

# OJP-RS

The `ojp-rs` crate is a Rust library for interacting with Open Journey Planner (OJP) services, a European 
standard for distributed, multimodal journey planning (see <https://opentransportdata.swiss/en/cookbook/open-journey-planner-ojp/>).

## Disclaimer

This crate is very early stage and used for testing purposes. It may or may not be extended in the future.


## Features

* Build and send OJP-compliant requests:
    * TripRequest: Plan journeys across multiple modes.
    * LocationInformationRequest: Search for stops and places.
* Parse XML responses into Rust types.
* Support for OJP v2.0 schema.
* Extensible design for additional OJP services (e.g., FareRequest, TripInfoRequest, StopEventRequest).
* Async support for HTTP requests.

## Use Cases

* Public transport apps
* Backend services for trip planning
* Research and analytics on multimodal transport

## Installation

Add to your `Cargo.toml`:

```console
cargo add ojp-rs
```
## Configuration

* Requires an API key from [opentransportdata.swiss](https://api-manager.opentransportdata.swiss/portal/catalogue-products/tedp_ojp20-1).
* By default the environment variable that must be set is `TOKEN` with the API key.

## Example

An example can be run with:

```console
cargo run --example find_journeys
```