aalises / barcelona-urban-mobility-graphql-api

GraphQL API that provides information about the different public transport / urban mobility services of Barcelona

Hi there 👋, I am Albert

• 🔭 I’m currently working as an Engineering Manager at Oliva Health where I was the founding engineer, previously Technical Lead at Kiwi.com
• 🔆 Currently living in Barcelona
• 🏥 MSc. in Computational Biomedical Engineering / BSc. in Telecommunications Engineering
• 🌱 Learning Golang and Rust
• 📫 How to reach me: add me on LinkedIn or send me an email or some kimchi 🍜
• 😄 Pronouns: He/him
• ⚡ Fun fact: I have played synths and bass in several bands, currently in The Zephyr Bones 🌊
• 👨‍🍳 Ah, and I cook a mean vindaloo curry!

BTW, Here's a Spotify playlist of all the songs I have been part of! 🎹 🎸

barcelona-urban-mobility-graphql-api's Issues

Setup deployment of the server on release

Setup deployment of the server (maybe using AWS Lambda with Serverless or Heroku), on tagging of the repository. Also, setup releases with tags and automatically generated changelogs

metroLines: Create Query with information about Metro Lines

Create metroLines query with information about Metro Lines (user can just get information about one line)

Endpoint

https://api.tmb.cat/v1/transit/linies/metro?app_id=XXX&app_key=XXX

metroStation: Create Query with information about a metro station

User can get a metro station by id or name

metroLine: Create query with information about a metro line

Setup Basic CI

Setup basic CI with Github Actions which runs linting and type checking.

busStops: Create Query with information about Bus Stops

Create busStops query with information about bus stops:

Endpoint

https://api.tmb.cat/v1/transit/parades?app_id=XXX&app_key=XXX

busStop: Create Query with information about a bus stop

User can get a bus stop by id or name

metroStations: Add filter by line name and code

Add an argument on the metroStations query that allows filtering by lineCode or lineName.

Generate CHANGELOG.md with each release

It should be automatically generated, as we are using conventional commits. Right now we can generate them after release using: https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-cli , but how cool would it be to place it in some action that automatically generated it after a release and committed it?

bikesStation: Create Query with information about a bike station

With the possibility of filtering by name and id

busLines: Create Query with information about Bus Lines

Create busLines query (user can just get one line if he wants):

Endpoint

https://api.tmb.cat/v1/transit/linies/bus?app_id=XXX&app_key=XXX

metroStation: add filtering by name

bikeStations: extend query with status of the station

By using https://api.bsmsa.eu/ext/api/bsm/gbfs/v2/en/station_status , we can extend the schema of the bikeStations query to also return information about the status of the station

queries: add findBy closest station parameter

You can provide some Coordinates and it will find the closest station.

bicingStations: Create Query with information about Bicing Stations

Create bikeStations query with information about Bicing Stations

Endpoint

https://api.bsmsa.eu/ext/api/bsm/gbfs/v2/en/station_information