lta-rs

🚍 Singapore LTA Datamall Rust async first client. lta-rs is used to interact with the lta-datamall

lta-rs in action

Cargo.toml setup

```toml [dependencies]

extra features available: blocking

lta = { version = "0.5.0" } ```

API key setup

You can get your API key from here

```rust use lta::{LTAResult, LTAClient, Client, Traffic, TrafficRequests};

[tokio::main]

async fn main() -> LTAResult<()> { let apikey = std::env::var("APIKEY").expect("APIKEY not found!"); let client = LTAClient::withapikey(apikey)?; let erprates = Traffic::geterprates(&client, None).await?; println!("{:?}", erprates); Ok(()) } ```

Examples

Getting bus timings

```rust use lta::{LTAResult, LTAClient, Client, Bus, BusRequests};

fn getbusarrival() -> LTAResult<()> { let apikey = std::env::var("APIKEY").expect("APIKEY not found!"); let client = LTAClient::withapikey(apikey); let arrivals = Bus::get_arrival(&client, 83139, None)?; println!("{:?}", arrivals); Ok(()) } ```

Getting other data

``rust // All the APIs in this library are designed to be used like this //lta::RequestType::getsomething` // All of them return lta::utils::LTAResult // The example below is Bus::getbusservices() // and Traffic::geterprates() // Do note that the API calling convention is similar across all the APIs except for // bus::getarrival // Most of the APIs returns only 500 record // If you want to get records 501 - 1000 take a look at get_erp() example use lta::{LTAResult, LTAClient, Client, Bus, Traffic, BusRequests, TrafficRequests};

async fn busservices() -> LTAResult<()> { let apikey = std::env::var("APIKEY").expect("APIKEY not found!"); let client = LTAClient::withapikey(apikey)?; let busservices= Bus::getbusservices(&client, None)?; println!("{:?}", bus_services); Ok(()) }

async fn geterp() -> LTAResult<()> { let apikey = std::env::var("APIKEY").expect("APIKEY not found!"); let client = LTAClient::withapikey(apikey)?; let erprates = Traffic:: geterprates(&client, Some(500))?; println!("{:?}", erp_rates); Ok(()) } ```

Custom Client

There are some instances where you might need to customise the reqwest client due to certain limitations.

```rust use lta::r#async::client::LTAClient; use lta::reqwest::ClientBuilder; use std::time::Duration; use lta::Client;

fn mycustomclient() -> LTAClient { let client = ClientBuilder::new() .nogzip() .connecttimeout(Duration::new(420, 0)) .build() .unwrap();

LTAClient::new("API_KEY", client)

} ```

General advice

Reuse LTAClient as it holds a connection pool internally
Reduce the number of times you call the API, take a look at Update Freq in the documentation and prevent yourself from getting blacklisted. Use a caching mechanism.

Getting help

You can get help via GitHub issues. I will try my best to respond to your queries :smile:

Design decisions

Made sure that Rust structs are as close to the original response as possible so that people can reference the original docs if there are any issues
Simple and no additional baggage. Only the client is included. E.g If anyone wants to add concurrency, they have to do it on their own
Predictable API usage

Changelog

Changelog can be found here

Requirements

Rust compiler 1.39

License

lta-rs is licensed under MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

Frequently Asked Questions

Is this library being actively developed?

Yes. However, development will slow down from mid August 2019 onwards due to my NS commitments.

What are the APIs available?

Take a look at the official LTA docs.

Where do I get the official docs from lta?

You can get them here