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.

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

Add public transport information in waypoints (accesses) listing #1067

Closed
brunobesson opened this issue Apr 29, 2021 · 9 comments
Closed

Add public transport information in waypoints (accesses) listing #1067

brunobesson opened this issue Apr 29, 2021 · 9 comments

Comments

@brunobesson
Copy link
Member

brunobesson commented Apr 29, 2021

See #c2corg/c2c_ui#846

Field public_transportation_rating should be included. I assume we do not need the public_transportation_types field.

@AntoineMarnat
Copy link
Contributor

Any progress on this ?

@cbeauchesne
Copy link
Member

nope ...

@florentcadot
Copy link
Contributor

florentcadot commented Feb 29, 2024

Hey!
My understanding is that we should add a public_transportation_rating field in the Route table. It would make sense to also add a field in the Route create/update form front-end side, do you confirm ?

@eddy-geek
Copy link

mmm I'm discovering this, but I don't think new columns are needed, instead the existing public_transportation_rating data of the waypoints can be reused?

image

I'm guessing a route is accessible by public transport if at least one of its linked waypoints is accessible?

@florentcadot
Copy link
Contributor

florentcadot commented Mar 5, 2024

mmm I'm discovering this, but I don't think new columns are needed, instead the existing public_transportation_rating data of the waypoints can be reused?

image

I'm guessing a route is accessible by public transport if at least one of its linked waypoints is accessible?

Isola 2000 😍 (a bit of chauvinism, sorry)

@eddy-geek Understood, so does it mean GET /routes should return something like:

{
    "documents": [
        {
            "document_id": 1055792,
            "version": 1,
            "locales": [ ... ],
            "geometry": {...},
            .....
            "areas": [],
            "waypoints": [
            {
                        "document_id": 14274,
                        "version": 11,
                        "locales": [...],
                         "public_transportation_rating": "good service" 
                    },
                        {
                        "document_id": 14275,
                        "version": 11,
                        "locales": [...],
                         "public_transportation_rating": "no service" 
                    },
            ]

?

@Nayor
Copy link
Contributor

Nayor commented Mar 6, 2024

Hello !

From my point of view, the needs behind this feature are:

  • to know if a route is accessible by public transportation
    directly from the route information, without having to check any waypoints
  • to filter routes accessible by public transportation
    with a value comparison, with a slider for instance

I'm not sure giving back all the waypoints is a good way to fulfill these needs.
Moreover, it may increase a lot the response payload.

I've seen that waypoints have a computed value (routes_quantity), maybe routes can have something similar ?
It implies that all routes linked to a waypoint must be updated when the public transportation information is.

Some suggestions:

  • main_waypoint_public_transportation_rating (easy to compute, but this point is not necessarily the best for public transportation)
  • public_transportation_overall_rating : the best value of all the waypoints (cons: may not be the best start of the route, and can mix up the different transportation types)

@brunobesson
Copy link
Member Author

brunobesson commented Mar 7, 2024

Sorry, I missed this discussion before answering to the PR made for the frontend.

I made a mistake with the title of the issue. Indeed the idea is to have the public_transportation_rating info on access points, not routes. This is what is missing for c2corg/c2c_ui#846.

Having this information for routes could be interesting too, but it's another subject.

@brunobesson brunobesson changed the title Add public transport information in routes listing Add public transport information in waypoints (accesses) listing Mar 7, 2024
@Nayor
Copy link
Contributor

Nayor commented Mar 7, 2024

There is no other issue open about having this information into routes, I think that's a very nice feature to have 🙂

brunobesson added a commit that referenced this issue Mar 8, 2024
…fo-waypoints-listing

feat: #1067 add public transport information in waypoints listing
@eddy-geek
Copy link

@brunobesson the mistake has been made, now the whole discussion here is about routes, so can we reopen and keep original title?

I like @florentcadot's idea for the API extension, having basic waypoint information on routes (just location+rating, and only for access points) seems to add quite some flexibility, for example to enable better display of the results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants