2022-09-21 13:06:04 +03:00
|
|
|
# PythonRMV
|
|
|
|
|
2022-09-22 19:31:12 +03:00
|
|
|
Small module that makes your journey with RMV REST API somehow easier. Based fully on official RMV API reference and HAFAS documentation.
|
2022-09-22 16:13:41 +03:00
|
|
|
|
2022-09-22 19:31:12 +03:00
|
|
|
# Requirements
|
2022-09-22 16:13:41 +03:00
|
|
|
|
2022-09-22 19:31:12 +03:00
|
|
|
* RMV API key (Get it [here](https://opendata.rmv.de/site/start.html))
|
|
|
|
* Python3 (Tested versions are 3.7.9 and 3.9.13)
|
|
|
|
* git (Only for installation from source)
|
2022-09-22 16:13:41 +03:00
|
|
|
|
|
|
|
# Installation
|
|
|
|
|
2022-09-22 19:31:12 +03:00
|
|
|
If you have everything listed in [requirements](#requirements), then let's begin.
|
2022-09-22 16:13:41 +03:00
|
|
|
|
2022-09-22 19:31:12 +03:00
|
|
|
### Variant 1:
|
|
|
|
1. `python -m pip install pyrmv`
|
2022-09-22 16:13:41 +03:00
|
|
|
|
2022-09-22 19:31:12 +03:00
|
|
|
### Variant 2:
|
2022-09-22 20:31:21 +03:00
|
|
|
1. `git clone https://git.end-play.xyz/profitroll/PythonRMV.git`
|
|
|
|
2. `cd PythonRMV`
|
2022-09-22 19:31:12 +03:00
|
|
|
3. `python setup.py install`
|
2022-09-22 16:13:41 +03:00
|
|
|
|
2022-09-23 16:01:00 +03:00
|
|
|
# Usage
|
|
|
|
|
|
|
|
```py
|
|
|
|
import pyrmv
|
|
|
|
|
2022-09-23 23:58:05 +03:00
|
|
|
# Set API key
|
2022-09-24 14:59:54 +03:00
|
|
|
access_id = "Something"
|
2022-09-23 16:01:00 +03:00
|
|
|
|
|
|
|
# Get origin's and destination's location
|
2022-09-24 14:59:54 +03:00
|
|
|
origin = pyrmv.stop_by_name(access_id, "Frankfurt Hauptbahnhof", max_number=3)[0]
|
|
|
|
destination = pyrmv.stop_by_coords(access_id, 50.099613, 8.685449, max_number=3)[0]
|
2022-09-23 16:01:00 +03:00
|
|
|
|
|
|
|
# Find a trip by locations got
|
2022-09-24 14:59:54 +03:00
|
|
|
trip = pyrmv.trip_find(access_id, origin_id=origin.id, dest_id=destination.id)
|
2022-09-23 16:01:00 +03:00
|
|
|
```
|
|
|
|
|
2022-09-22 16:13:41 +03:00
|
|
|
# Frequently Asked Questions
|
|
|
|
|
|
|
|
- [Why are there raw versions and formatted ones?](#why-are-there-raw-versions-and-formatted-ones)
|
|
|
|
- [Some methods work slightly different](#some-methods-work-slightly-different)
|
|
|
|
- [Documentation is not perfectly clear](#documentation-is-not-perfectly-clear)
|
|
|
|
|
|
|
|
## Why are there raw versions and formatted ones?
|
|
|
|
|
|
|
|
For the purposes of my projects I don't really need all the stuff RMV gives (even though it's not much).
|
2022-09-22 19:31:12 +03:00
|
|
|
I only need some specific things. However I do understand that in some cases other users may find
|
|
|
|
those methods quite useful so I implemented them as well.
|
2022-09-22 16:13:41 +03:00
|
|
|
|
|
|
|
|
|
|
|
## Some methods work slightly different
|
|
|
|
|
2022-09-22 19:31:12 +03:00
|
|
|
Can be. Not all function arguments written may work perfectly because I simply did not test each and
|
|
|
|
every request. Some of arguments may be irrelevant in my use-case and the others are used quite rare at all.
|
2022-09-22 16:13:41 +03:00
|
|
|
Just [make an issue](https://git.end-play.xyz/profitroll/PythonRMV/issues/new) and I'll implement it correct when I'll have some free time.
|
|
|
|
|
|
|
|
## Documentation is not perfectly clear
|
|
|
|
|
2022-09-22 19:31:12 +03:00
|
|
|
Of course docs cannot be perfect as a python docstring, especially if sometimes I don't
|
|
|
|
know how things should correctly work. That's why you get HAFAS API docs in addition to your
|
|
|
|
RMV API key. Just use my functions together with those docs, if you want to build something
|
|
|
|
really sophisticated. However I'm not sure whether RMV supports that many HAFAS features publicly.
|
2022-09-22 16:13:41 +03:00
|
|
|
|
|
|
|
# To-Do
|
2022-09-23 12:49:11 +03:00
|
|
|
- [ ] arrivalBoard (board_arrival)
|
|
|
|
- [ ] departureBoard (board_departure)
|
|
|
|
- [x] himsearch (him_search)
|
|
|
|
- [ ] journeyDetail (journey_detail)
|
|
|
|
- [x] location.nearbystops (stop_by_coords)
|
|
|
|
- [x] location.name (stop_by_name)
|
|
|
|
- [x] trip (trip_find)
|
|
|
|
- [ ] recon (trip_recon)
|