HSLdevcom / HSLdevcom/digitransit-ui
Make an easy doc to properly configure a working digitransit-ui with a standard OTP instance
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 267
- Forks
- 145
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 75
Description
It would be great to provide an easy way to configure a working digitransit-ui based on an already set up standard OTP instance (latest master, supporting GraphQL).
Currently I'm not able to get it working, whereas I use a working OTP instance (http://paris.acolytesanonymes.org), and tried to set up geocoding using mapzen. Geocoding doesn't seem to work, and map display neither.
Thanks for your help.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the issue. Start by locating the current digitransit-ui setup documentation and reproducing the configuration with a standard OTP instance, GraphQL, Mapzen geocoding, and map display; done means a newcomer can follow the documented steps to get a working UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100