schedules page's rail routes

[albertkun]

hello @anithegregorian! for some reason the routes for the rail are showing the old non-regional connector routes:

Can you check to see if how you are generating those as it should be using the trip_shapes (for example https://api.metro.net/LACMTA_Rail/trip_shapes/801SB_RC_221121) looking like this:

[anithegregorian]

@albertkun I haven't implemented trip_shapes yet. I was looking forward to your reply on the other thread.

What I shared was on my local dev, If this API is ready then let me know. Would help immensely if I could gain some insight on how to use it, like how to get Trip ID etc.

[albertkun]

@anithegregorian ahh, ok i didn't know you were waiting for a reply! feel free to let me know what you need! for rail the trip_id is pretty straight forward since there is just one trip_id per rail route direction:, you should just pick one of the trip_id for each of the lines!

shape_id	route	direction
801NB_RC_221121	A Line	North
801SB_RC_221121	A Line	South
802EB_190513	B Line	East
802WB_190513	B Line	West
803EB_120215	C Line	East
803WB_120215	C Line	West
804EB_RC_221121	L Line	East
804WB_RC_221121	L Line	West
805EB_190513	D Line	East
805WB_190513	D Line	West
807NB_220810	K Line	North
807SB_220810	K Line	South

Let me know if you have any questions!

[anithegregorian]

Hi @albertkun ,

Is it possible to include the shape in the route overview or route stops grouped API's. It would not be a good practice to define this logic in the front end (Javascript). If there's any other possibility like creating a separate endpoint then I'm fine with it as long as the logic resides on server side.

Also, how can I use shapes for bus routes?

[albertkun]

@anithegregorian for rail that might be possible since there is only one route. As a temporary solution would you be able to hardcode the appropriate trip_shapes for the A line and E line?

In general, just selecting one trip_shape for busses is difficult because there are multiple routes per bus route. We are already working on a unique_route_stops endpoint, but I believe that was only for the stops and not trip_shapes. If we can include the trip_shapes in that endpoint then maybe that would simplify things.

I think @matikin9 is out of office today so I'll have to check in with her next week.

But in the meantime, I'll try to see what a simplified endpoint may look like.

[anithegregorian]

@albertkun @matikin9

I was able to get the hardcoded implementation working, do note, that it's purely for testing and demo.

While testing some route geometry doesn't match all the stops, for eg. if you check A-Line (801). And I didn't find anything for E-Line, you can check here:

https://lametro.wpengine.com/riding/schedules

On a different note if including the entire Feature/Geometry is not feasible then just the shape_id would also work in route overview or route stops.

Thanks, and have a great weekend!

[albertkun]

@anithegregorian Thank you for the reply! I don't think using the shape_id would make a difference as the trip_shapes is just a grouping off of the shape_id.

Which endpoint are you pulling the stops from?

Once you let me know, I'll go ahead and look into that!

I know it's getting late over there, so feel free to circle back with me on Monday! :)

[anithegregorian]

@albertkun

Before signing off, I'm using route overview and route stops grouped API, now with one additional API call to trip shapes for Rail routes for eg. https://api.metro.net/LACMTA_Rail/trip_shapes/801NB_RC_221121

What I was referring to was the shape_id in your response #435 (comment)

It's best to get the geometry or a reference to the geometry from the previous two API calls, I don't see avoiding a third API call for geometry :)

We're off on Monday BTW following Kite Festival and Pongal...

[albertkun]

@anithegregorian ohh, that makes sense! ok, i'll try to see what makes the most sense in terms of a general shape for a line! :)

I agree if we can reduce that one extra API call that would be great, so we'll see what we can do- though it might be unavoidable since different trips and directions will have different shapes 😢

No worries about Monday! Happy pongal and kite festival!!! 🪁 🥳

[anithegregorian]

@albertkun just checking if we can wrap this up during this week

[albertkun]

@anithegregorian yep,trying to decide what is the best way for the route_overview to reference the trip shape!

[albertkun]

@anithegregorian ok, we are going with the route_overview having a shape_direction_0 and shape_direction_1 column which will contain the general routes for the rail and bus! however, i'm having some issues getting the automation up and running. i will be working on it over the weekend and will keep you posted!

[anithegregorian]

@albertkun noted and thanks for the quick update

[albertkun]

thank you @anithegregorian ! i appreciate your patience! 🙏

[anithegregorian]

@albertkun I can tell you're slogging this one out if you need anything from me.