map transit incidents

[EddyIonescu]

While many agencies internally record incidents (which can often cause bunching and gaps down the line for hours), the TTC (Toronto Transit Commission) makes then publicly available here: https://www.toronto.ca/city-government/data-research-maps/open-data/open-data-catalogue/#bb967f18-8d90-defc-2946-db3543648bd6

This ticket only tracks putting them on the map (use fake hardcoded data when implementing this)

API endpoint creation tracked here: https://github.com/trynmaps/tryn-api/issues/30

[lukemccrae]

I'm looking into this. Should the frontend expect the location data to be geocoded into LatLng points?

[EddyIonescu]

@lukemccrae no, you should expect it to be a {lat: Number, lon: Number} object, from which you can make the LatLng point yourself.

[yubozhao]

@lukemccrae This will be fields available for each incident

    lat: Float
    lon: Float
    route: String
    type: String
    time: Int   // unix timestamp (in seconds)
    gap: Int  // in seconds
    delay: Int  // in seconds
    agency: String

It will be part of trynState Query

trynState(....) {
  ...
  routes: {...}
  incidents: {}
}

Let me know what you guys think and we can go from there. @EddyIonescu