Real Time Transit Information System/System architecture

Architecture
The RTTIS uses a Service-oriented Architecture design, featuring loosely coupled services organized into application and data access layers.



Logical Models
SOA database abstractions housed in folder app/models/logical. Message formats are serialized into XML or YAML.

Bus Location
Real time vehicle position message payload routed between system services. Elements names are drawn from Google Transit Feed Specification (GTFS).

Notification
Message payload for broadcasting schedule deviations and other alerts/notification for specific route or system-wide. Uses OASIS Emergency Management Technical Committee's open standard Common Alerting Protocol (CAP) v1.1. This message includes core CAP elements, additional elements may be incorporated, depending on system requirements. Refer to CAP schema for element data types.