Closed mjtorn closed 6 years ago
Seems like the old API is closed since last tuesday. Any plans of changing the API to the new supported GraphQL version? (https://www.facebook.com/HSLdevcom)
As I read from the answer to your question on FB, updating to the new API doesn't seem to be a straightforward task, unfortunately. EDIT: however, in Github there are examples of Kalkati-to-GTFS converters, if that's what is needed
I might take a shot at this if help is welcome. No promises though :-)
Urgh, I didn't even notice it was a Facebook link I opened and all I saw was login nags :D
Anyway, I hope the new API gets in; if there's a site to escrow bounties or something, I'd pitch in some cash to get this done.
Took two seconds looking looking at the dev resources like https://github.com/HSLdevcom?utf8=%E2%9C%93&q=digitransit&type=&language= and https://digitransit.fi/en/developers/ but the closest to a reference implementation I could find is the actual site. It would be more helpful of HSL if they provided libraries for their APIs.
Does anyone know if there are libraries out there I couldn't find in the two seconds?
I believe @hsarkanen is working on this issue, he has updated the digitransit_api branch only three days ago?
It seems @otsaloma has been able to solve this API issue in helsinki-transit-live with fairly small changes. Let's hope it isn't too complicated here, could issue #13 also be repaired simultaneously?
helsinki-transit-live issue referenced here is related to vehicle positioning, which is quite simple change, but it's not related to route API which uses GraphQL. This could be solved by integrating the c++ library into the project or just mocking GraphQL by just parsing some JSON. Or integrating the nodejs library somehow.
Either way this would require some work and quite a lot of testing. I think queries are pretty much the same, but responses require so much more work.
I already tried to work on more sophisticated approach for the live positioning (essentially ditching polling and using mqtt, making it truely realtime). But data parsing would need some extra implementation and I would need to make some design choices (like do I read the whole Helsinki Live transit or just specified lines).
In the end, I didn't have the time to see it through.
The new version works again, thank you! Now if #13 could also be resolved...
Moro!
Noticed I'm not getting results for routes, or even resolving addresses. The addresses in this example are from my history. I uncommented some debuggy lines to get the output.
I got nothing on this. Is there something to be done?