TransitAlertServiceImpl Data Type

When an alert is added with more than one transit entity, e.g. a Stop and a Trip, both conditions must be met for the alert to be displayed. This is the case in both the Norwegian interpretation of SIRI, and the GTFS-RT alerts specification.

Implemented Interfaces
TransitAlertService
Properties
name data type description
allAlerts array of TransitAlert

Example

{
  "allAlerts" : [ {
    "alertHeaderText" : { },
    "alertDescriptionText" : { },
    "alertDetailText" : { },
    "alertAdviceText" : { },
    "alertUrl" : { },
    "alertType" : "...",
    "severity" : "UNDEFINED",
    "cause" : "POLICE_ACTIVITY",
    "effect" : "MODIFIED_SERVICE",
    "priority" : 12345,
    "id" : "...",
    "alertUrlList" : [ {
      "uri" : "...",
      "label" : "..."
    }, {
      "uri" : "...",
      "label" : "..."
    } ],
    "entities" : [ { }, { } ],
    "stopConditions" : [ "REQUEST_STOP", "START_POINT" ],
    "feedId" : "...",
    "effectiveStartDate" : 12345,
    "effectiveEndDate" : 12345
  }, {
    "alertHeaderText" : { },
    "alertDescriptionText" : { },
    "alertDetailText" : { },
    "alertAdviceText" : { },
    "alertUrl" : { },
    "alertType" : "...",
    "severity" : "WARNING",
    "cause" : "ACCIDENT",
    "effect" : "DETOUR",
    "priority" : 12345,
    "id" : "...",
    "alertUrlList" : [ {
      "uri" : "...",
      "label" : "..."
    }, {
      "uri" : "...",
      "label" : "..."
    } ],
    "entities" : [ { }, { } ],
    "stopConditions" : [ "DESTINATION", "REQUEST_STOP" ],
    "feedId" : "...",
    "effectiveStartDate" : 12345,
    "effectiveEndDate" : 12345
  } ]
}