-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[question] How does one use rrrr #118
Comments
After you compile the code the commandline tool testerrrr can be used to test the journey planner itself. ./testerrrr -r makes a random request. The "webbased" API is compatible with OpenTripPlanner. Using "cherokee" in our repository in the handler_rrrr branch you will be able to start it. We don't have any installation guidelines yet, but they will be available shortly. |
Okay yes Monitoring ports 9292|9293 with tcpdump -A shows a bunch of JSON objects being passed around, but again, it's unclear what's what. Trying to use (Also, testerrrr apparently tests every transfer for symetry (all >200 millions of them) on every run, which makes it a little slow to use). If I could use testrrrr by sending it two stop ids and getting a readable JSON response, it would be enough for testing purposes; if I could then do the same via http I would be very happy... ;-) Thanks. |
If you want I can help you setting up cherokee with bliksem, like it is on https://1313.nl/ |
Start the program otp_api. It will listen on port 9393. Then use "curl" to send it a request. For instance, using the Netherlands DB referenced in README.md, $ curl 'http://127.0.0.1:9393/?to-idx=54864&from-idx=29164' which should return a JSON representation of the trip plan. Look in parse.c/parse_request_from_qstring for the various attributes you can send in the HTTP request. |
How does one query rrrr? I have it running with some GTFS data, but can't seem to figure out how to query it (sorry!)
Is it possible to query it via HTTP / does it need a webserver in front of it...?
Is there a doc for the API?
Thank you.
The text was updated successfully, but these errors were encountered: