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

Relevant stops not included in alerts #108

Open
PasiSalenius opened this issue Jan 8, 2017 · 1 comment
Open

Relevant stops not included in alerts #108

PasiSalenius opened this issue Jan 8, 2017 · 1 comment

Comments

@PasiSalenius
Copy link

The following alert query returns an alert for tram 7B.

{
  alerts {
    id
    route {
      gtfsId
    }
    stop {
      gtfsId
    }
    alertDescriptionText
  }
}

But even though stops are listed as affected by the disruption alert, the stops property in the graphQL response is empty.

...
{
 "id": "QWxlcnQ6NTM3MDUgSFNMIDEwMDdCIHRydWUgMCAgbnVsbCAgIG51bGwg",
 "route": {
   "gtfsId": "HSL:1007B"
 },
 "stop": null,
 "alertDescriptionText": "Raitiolinjat 7A ja 7B poikkeusreitillä klo 16-24, ajetaan Rautatieaseman kautta. Seuraavat pysäkit jäävät ajamatta: Snellmaninkatu, Kansallisarkisto, Hallituskatu, Senaatintori, Aleksanterinkatu ja Ylioppilastalo. Syy: yleisötapahtuma. Lisätietoja: hsl.fi"
}
...
@tuukka
Copy link
Contributor

tuukka commented Jan 9, 2017

Although the GTFS-realtime specification and the Digitransit platform can list affected stops, the source systems at HSL don't yet provide this information in structured format.

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

No branches or pull requests

2 participants