Skip to content
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.

Sign up for GitHub

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

Jump to bottom

GeoJSON API #41

Open
prhod opened this issue Jul 10, 2018 · 1 comment
Open

GeoJSON API #41

prhod opened this issue Jul 10, 2018 · 1 comment
Labels
api enhancement New feature or request

Comments

@prhod
Copy link
Collaborator

prhod commented Jul 10, 2018 •
edited
Loading

This issue sums up the discussion in #20.

The second endpoint should be a valid GeoJSON api, containing in one response all the details of a route (stops and stop_positions).
To avoid nesting geometries, the simplest solution seems to be a FeatureCollection containing:

  • a Feature describing the route
  • multiple Features describing the stops
  • multiple Features describing the stop_positions

If we provide this API, do we know someone interested ?
@prhod prhod mentioned this issue Jul 10, 2018
Closed
@frodrigo
Copy link
Collaborator

I'm OK with this.
But I still thinking #40 should also use this format. The route part should be provided as option.

@prhod prhod mentioned this issue Aug 26, 2018
Merged
@frodrigo frodrigo added enhancement New feature or request api labels Aug 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@frodrigo @prhod