TransitEntity Data Type

All OTP Transit entities should extend this class. The purpose of the class is to enforce a common implementation of the identity:

  1. id - All entities should have an id. The id should be unique within the context the entity live. For aggregates which live in a global space the id must be unique. This apply to all entities listed in the index service.
  2. The hashCode()/equals() method is consistent and based on the id (identity). We frequently use this to index and lookup entities.

Abstract Type
Subtypes
GroupOfStations, FlexStopLocation, Pathway, Trip, Entrance, TripPattern, FareAttribute, MultiModalStation, Notice, Route, FlexTrip, StopTimeKey, FareZone, Stop, StationElement, BoardingArea, PathwayNode, FlexLocationGroup, Agency, Operator, Station, Branding
Implemented Interfaces
Serializable
Properties
name data type description
id FeedScopedId

Example

This data type is abstract. The example below may be incomplete. More accurate examples can be found in subtypes pages.
{
  "id" : {
    "feedId" : "...",
    "id" : "..."
  }
}