@PetraOleum i think based on snooping with browser developer tools metlink is api driven. So all we need is frontend code to call metlink's api.
@pearofdoom There's the links in here that would be a good start: https://fyi.org.nz/request/14090-metlink-api-documentation
@PetraOleum well I think it must be mid development because the new site is only on beta.metlink.org.nz and the new api stuff doesn't really work.
I did manage to get a token and added a note on the fyi.org.nz thread.
@pearofdoom I've been playing with a proof of concept using the "secret" api mentioned in the first post of that thread, which works ok
@pearofdoom well it's midnight, but: rti.petras.space
I will have to redo the css for mobile though, but that can be tomorrow's problem
better late than never
I'm going to make a GIS dataset from the undocumented api
@pearofdoom @PetraOleum yes, the Metlink site looked API driven when I looked at doing something like this a few years ago. (I ended up just book marking the URLs for the stops I cared about onto my home screen instead. Then later switched to 100% WFH.)
From memory when I asked about getting a feed or timetable information they basically just suggested calling the API/scraping the webpages. So reversing enough of the API and calling it from JS is probably the most direct solution.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!