EXHIBIT_D-Data_Aggregator_-_GTFS_Attachments.pdf

References of the Required existing data output

DocuSign Envelope ID: 7B1BA276-3779-42F6-9BE3-E0CE78D4A022

Data Dictionary Demographic Information

Row Description Field Note Row Description

Dataset Identfier Autopopulated by DFE GUID Unique identifier of the data set. This is generated programmatically in the DFE.

Dataset Name FDOT_ConsolidatedGTFS_V1 String/Text Name of the data set (example: Here_V3.1.2). Names should be descriptive of the data while remaining unique enough to accurately reflect version changes.

Dataset Short Name fdot_gtfs String/Text The short name for use in referencing the dataset. This will be the name which is used to represent the data for use in ingestion and API reference. This name should be lowercase and contain no spaces.

Last Update 2019‐07‐17 (GTFS‐RT v2.0) Date/Time

Last time (Date and Time) that the data set was updated. Date and Time represented in this field reflects the Date and Time of the underlying version or data creation. In the event of a dataset which is dynamic or continually updating, the date will reference the date and time of the first collection of the overall data for inclusion in the DFE.

Data Version 2.0 Numeric Version of the current data set. Datasets without a Version are populated with a value of 1 indicating it is the first version of the data in the DFE.

Dataset Revision Date 2019‐07‐17 (GTFS‐RT v2.0) Date/Time Date of the last dataset structural revision. Leave row blank for data which this does not apply.

Dataset Vendor Name String/Text

Name of the Vendor or Organization who is responsible for the creation of the data set. For versions of data which have been post processed, refined, or otherwise changed indicate the vendor, organization, or agency whom is providing the data for ingestion into the DFE Environment

Dataset POC String/Text Name of the Point of Contact for the dataset Vendor Email String/Text Email Address for the point of contact for the dataset Vendor Phone Number String/Text Phone number for the point of contact for the dataset Vendor Fax Number String/Text Fax Number for the point of contact for the dataset Vendor Address String/Text Postal address for the point of contact for the dataset

Original Dataset Source System Links to source data are referenced in the Additional Documents tab. String/Text Common name of the location where the data is being retrieved from. Examples include RCI, FDGL, UBR, HERE, or other common source names

Dataset Loading Method Access via APIs (see API Linkage tab) or download zip file of consolidated GTFS (URL TBD) String/Text What method is used to provide the data to the DFE Sandbox Environment. (Example: SQL Pull, Manual Download, XML feed, RSS Feed)

Dataset Loading Procedure Download at a configurable interval from an endpoint and load into DFE. String/Text Description, Instructions, or Links providing information on how the dataset is loaded into the DFE. This represents a short description/explanation of how the data is being loaded or made available to the DFE Environment.

Update Interval

The consolidated GTFS will be updated each time an agency updates its GTFS. Agency‐specific GTFS updates will be checked for once per day. String/Text

The frequency of update for the data. (Example: 30 second, 1 minute, 5 minute, Nightly, Weekly, Bi-Weekly, Monthly, Quarterly, etc.). If multiple update frequencies are available identify the update interval used for the DFE.

Volume About 1 million records String/Text Quantity of Records per Update Interval. This includes all rows in a table or feature per update interval timeframe that will be ingested in document. This value can be an estimate (ex. 50K per update interval).

Historical Period July 2019 onward. String/Text

Period of time in which the data is stored, represents the earliest data records included by timestamp date. If data is not continuously updated or not expected to be updated a date range should be included. For example (2013-2016). This can also represent data sets which have changed based on version changes in which the structure of the data was significantly altered and is no longer being collected at that version.

Data Size in DFE About 46 MB (unzipped file size) String/Text Estimated size input of data into DFE for each Update Interval. This value will be used in combination with the Update Interval to determine the overall Data Size of each update for the data.

Dataset Notes String/Text Additional Notes about the demographic portion of the dataset

Source Dataset Documentation

Links to source data are referenced in the Additional Documents tab. Additional resources, including from GitHub and gtfs.org are also referenced here. String/Text Links to source dataset documentation that may available via the data creator.

Access Policy Requires an API key. String/Text Description of any Access or Use Limitations

Data Dictionary Field Structure

Field Name Field Description Field Type Field Length agency_id Contains an ID that uniquely identifies a transit agency (optional for transit feeds that only contain data for a single agency). | GTFS files: agency

Varchar 255 agency_name Contains the full name of the transit agency (Google Maps will display this). | GTFS files: agency Varchar 255 agency_url Contains the URL of the transit agency. The value must be a fully qualified URL that includes http:// or https://, and any special characters in the URL must be correctly escaped. | GTFS files: agency

Varchar 255 agency_lang Contains a two‐letter ISO 639‐1 code for the primary language used by the transit agency. The language code is case‐insensitive (both en and EN are accepted). | GTFS files: agency

Varchar 2 agency_timezone Contains the timezone where the transit agency is located (cannot contain a space, but can contain an underscore). | GTFS files: agency

Varchar 255 agency_phone Contains a single voice telephone number for the specified agency. | GTFS files: agency Varchar 255 agency_fare_url Specifies the URL of a web page that allows a rider to purchase tickets or other fare instruments for that agency online. | GTFS files: agency

Varchar 255 service_id Contains an ID that uniquely identifies a set of dates when service is available for one or more routes.

| GTFS files: calendar, calendar_dates, trips

Varchar 255 monday Contains a binary value that indicates whether the service is valid for all Mondays (1 = service available for all Mondays in the date range, 0 = not). | GTFS files: calendar

Bit 1 tuesday Contains a binary value that indicates whether the service is valid for all Tuesdays (1 = service available for all Tuesdays in the date range, 0 = not). | GTFS files: calendar

Bit 1 wednesday Contains a binary value that indicates whether the service is valid for all Wednesdays (1 = service available for all Wednesdays in the date range, 0 = not). | GTFS files: calendar

Bit 1 thursday Contains a binary value that indicates whether the service is valid for all Thursdays (1 = service available for all Thursdays in the date range, 0 = not). | GTFS files: calendar

Bit 1 friday Contains a binary value that indicates whether the service is valid for all Fridays (1 = service available for all Fridays in the date range, 0 = not). | GTFS files: calendar

Bit 1 saturday Contains a binary value that indicates whether the service is valid for all Saturdays (1 = service available for all Saturdays in the date range, 0 = not). | GTFS files: calendar

Bit 1 sunday Contains a binary value that indicates whether the service is valid for all Sundays (1 = service available for all Sundays in the date range, 0 = not). | GTFS files: calendar

Bit 1 start_date Contains the start date for the service (YYYYMMDD format). | GTFS files: calendar Date 8 end_date Contains the end date for the service (YYYYMMDD format). | GTFS files: calendar Date 8 date Specifies a particular date when service availability is different than the norm, YYYYMMDD format. | GTFS files: calendar_dates

Date 8 exception_type Indicates whether service is available on the date specified in the date field (1 = service has been added for a specified date, 2 = service removed for the specified date) | GTFS files: calendar_dates

Integer 1 fare_id Contains an ID that uniquely identifies a fare class. | GTFS files: fare_attributes, fare_rules Integer 4 price Contains the fare price, in the unit specified by currency_type. | GTFS files: fare_attributes Float currency_type Defines the currency used to pay the fare, currency codes can be found at http://en.wikipedia.org/wiki/ISO_4217. | GTFS files: fare_attributes

Varchar 3 payment_method Indicates when the fare must be paid (0 = on board, 1 = before boarding). | GTFS files: fare_attributes Integer 1 transfers Specifies the number of transfers permitted on a fare (0 = no transfers, 1 = one transfer, 2 = two transfers, empty = unlimited). | GTFS files: fare_attributes

Integer 1 transfer_duration Specifies the length of time in seconds before a transfer expires (if transfer = 0, specifies how long the ticket is valid for). | GTFS files: fare_attributes

Integer route_id Contains an ID that uniquely identifies a route. | GTFS files: fare_rules, routes, trips Varchar 255 origin_id Associates the fare ID with an origin zone ID (defined in the stops.txt file). | GTFS files: fare_rules Varchar 255 destination_id Associates the fare ID with a destination zone ID (defined in the stops.txt file). | GTFS files: fare_rules Varchar 255 feed_publisher_name Contains the full name of the organization that publishes the feed. | GTFS files: feed_info Varchar 255 feed_publisher_url Contains the URL of the feed publishing organization's website. | GTFS files: feed_info Varchar 255 feed_lang Contains a IETF BCP 47 language code specifying the default language used for the text in this feed (helps GTFS consumers choose language‐specific settings). | GTFS files: feed_info

Varchar 255 feed_start_date The date from which the feed provides complete and reliable schedule information (YYYYMMDD format). | GTFS files: feed_info

Date 8 feed_end_date The date until which the feed provides complete and reliable schedule information (YYYYMMDD format). | GTFS files: feed_info

Date 8 feed_version Indicates the current version of the feed publisher's GTFS feed. | GTFS files: feed_info Varchar 255 feed_contact_email Indicates the email of the GTFS contact person at the organization that publishes the feed. | GTFS files: feed_info

Varchar 255 feed_contact_url Indicates the email of the GTFS contact person at the organization that publishes the feed as a web‐ address or a "mailto:". | GTFS files: feed_info

Varchar 255 route_short_name Contains the short name of a route (riders can identify but doesn't give information on places route servces). | GTFS files: routes

Varchar 255 route_long_name Contains the full name of a route. | GTFS files: routes Varchar 255 route_desc Contains a description of a route (must provide useful and quality information). | GTFS files: routes Varchar 255 route_type Describes the type of transportation used on a route (0 = tram/streetcar/light rail, 1 = subway/metro, 2 = rail, 3 = bus, 4 = ferry, 5 = cable car, 6 = gondola/cable car, 7 = funicular). | GTFS files: routes

Integer 1 route_url Contains the URL of a web page about that particular route (should be different from the agency_url).

| GTFS files: routes

Varchar 255 route_color Defines a color that corresponds to a route (for systems that have colors assigned to routes, six‐ character hexadecimal number). | GTFS files: routes

Varchar 6 route_text_color Specifies a legible color to use for text drawn against a background of route_color (six‐character hexadecimal number). | GTFS files: routes

Varchar 6 route_sort_order Orders the routes in a way which is ideal for presentation to customers. | GTFS files: routes Integer shape_id Contains an ID that uniquely identifies a shape. | GTFS files: shapes, trips Varchar 255 shape_pt_lat Associates a shape point's latitude with a shape ID (must be a valid WGS 84 latitude). | GTFS files:

shapes

Float shape_pt_lon Associates a shape point's longitude with a shape ID (must be a valid WGS 84 latitude from ‐180 to 180). | GTFS files: shapes

Float shape_pt_sequence Associates the latitude and longitude of a shape point with its sequence order along the shape (must increase along the trip). | GTFS files: shapes

Integer shape_dist_traveled Positions a shape point as a distance traveled along a shape from the first shape point (must increase along the shape_pt_sequence). | GTFS files: stop_times

Float trip_id Contains an ID that identifies a trip on which the specified frequency of service applies. | GTFS files:

stop_times, trips

Varchar 255 arrival_time

Specifies the arrival time at a specific stop for a specific trip on a route (measured from "noon minus 12 hours" (midnight except for days on which daylight savings time changes occur) at the beginning of the service day, if after midnight = a value greater than 24:00:00 local time for the day on which the trip schedule begins). | GTFS files: stop_times

Time departure_time

Specifies the departure time at a specific stop for a specific trip on a route (measured from "noon minus 12 hours" (midnight except for days on which daylight savings time changes occur) at the beginning of the service day, if after midnight = a value greater than 24:00:00 local time for the day on which the trip schedule begins). | GTFS files: stop_times

Time stop_id Contains an ID that uniquely identifies a stop. | GTFS files: stop_times, stops Integer stop_sequence Identifies the order of the stops for a particular trip (must increase along the trip). | GTFS files:

stop_times

Integer stop_headsign Contains the text that appears on a sign that identifies the trip's destination to passengers (can override the default trip_headsign when the headsign changes between stops). | GTFS files:

stop_times

Varchar 255 pickup_type Indicates whether passengers are picked up at a stop as part of the normal schedule or whether a pickup at the stop is not available (0 = regular, 1 = no pickup, 2 = must phone agency to arrange pickup, 3 = must coordinate with driver to arrange pickup). | GTFS files: stop_times

Integer drop_off_type Indicates whether passengers are dropped off at a stop as part of the normal schedule or whether a drop off at the stop is not available (0 = regular, 1 = no drop off, 2 = must phone agency to arrange drop off, 3 = must coordinate with driver to arrange drop off). | GTFS files: stop_times

Integer timepoint Indicates if the specified arrival and departure times for a stop are strictly adhered to by the transit vehicle or if they are instead approximate and/or interpolated times (empty/1 = exact, 0 = approximate). | GTFS files: stop_times

Integer stop_code Contains short text or a number that uniquely identifies the stop for passengers. | GTFS files: stops Varchar 255 stop_name Contains the name of a stop, station, or station entrance. | GTFS files: stops Varchar 255 stop_desc Contains a description of a stop (must provide useful and quality information). | GTFS files: stops Varchar 255 stop_lat Contains the latitude of a stop, station, or station entrance. | GTFS files: stops Float stop_lon Contains the longitude of a stop, station, or station entrance. | GTFS files: stops Float zone_id Defines the fare zone for a stop ID. | GTFS files: stops Varchar 255 stop_url Contains the URL of a web page about a particular stop (must be different from the agency_url and route_url fields). | GTFS files: stops

Varchar 255 location_type Identifies whether this stop ID represents a stop, station, or station entrance (empty/0 = stop, 1 = station, 2 = station entrance/exit). | GTFS files: stops

Integer 1 stop_timezone Contains the timezone in which the stop, station, or station entrance is located. | GTFS files: stops Varchar 255 wheelchair_boarding Identifies whether wheelchair boardings are possible from the specified stop, station, or station entrance (empty/0 = no info, 1 = at least some vehicles can be boarded by a wheelchair, 2 = not accessible). | GTFS files: stops

Bit 1 from_stop_id Contains a stop ID that identifies a stop or station where a connection between routes begins. | GTFS files: transfers

Integer to_stop_id Contains a stop ID that identifies a stop or station where a connection between routes ends. | GTFS files: transfers

Integer transfer_type Specifies the type of connection for the specified (from_stop_id, to_stop_id) pair (empty/0 = recommended transfer point, 1 = timed transfer between two routes, 2 = requires minimum amount of time to ensure successful connection, 3 = transfers not possible). | GTFS files: transfers

Integer trip_headsign Contains the text that appears on a sign that identifies the trip's destination to passengers. | GTFS files: trips

Varchar 255 trip_short_name Contains the text that appears in schedules and sign boards to identify the trip to passengers (should be left blank if riders do not commonly rely on trip names). | GTFS files: trips

Varchar 255 direction_id Contains a binary value that indicates the direction of travel for a trip. | GTFS files: trips Bit 1 block_id Identifies the block to which the trip belongs. | GTFS files: trips Bit 1 wheelchair_accessible Indicates whether wheelchair accessibility is available on a trip (empty/0 = no info, 1 = the trip vehicle Bit 1 bikes_allowed Indicates whether a bike is allowed on a trip (empty/0 = no info, 1 = the trip vehicle can accommodate at least one bike, 2 = not accessible). | GTFS files: trips

Varchar 255

Data Dictionary Additional Documentation

Document/Website Name Descriptions URL

GitHub.com A document that defines the format and structure of the filehttps://github.com/google/transit/blob/master/gtfs/spec/en/reference.md gtfs.org A document that explains the types of files that comprise a GTFS transit feed and defines the fields used in all of https://gtfs.org/reference/static gtfs.org A document of recommended practices for describing public transportation services in the General Transit Feed Specification (GTFS), synthesized from the experience of http://gtfs.org/best‐practices/ golynx.com Link to a downloadable GTFS file for LYNX. http://www.golynx.com/lynxmap/GoLYNX_data/google_transit.zip corporate.sunrail.com Link to a downloadable GTFS file for SunRail. https://corporate.sunrail.com/wp‐content/uploads/2016/05/google_transit.zip www.votran.org Link to a downloadable GTFS file for Votran. http://www.votran.org/core/fileparse.php/6120/urlt/google_transit.zip

Data Dictionary API

API Route Title Description HTTP Verb Route URL Parameters

Agencies Returns the agency ID and agency name of one or more FDOT agencies.

GET To Be Determined after award of contract

Optional parameter 'agencies': the agency id(s) for which data should be returned (type = string). If not included, the API will return data on all agencies in the consolidated FDOT GTFS. Valid values: 0, 411, 71, CFRTA, FDOT, LakeXpress (may include one or more separated by commas) | Example: agencies=0

Stops by Agency (Region) Returns all stops in the GTFS of one or more FDOT agencies, separated by agency.

GET To Be Determined after award of contract

Optional parameter 'agencies': the agency id(s) for which data should be returned (type = string). If not included, the API will return data on all agencies in the consolidated FDOT GTFS. Valid values: 0, 411, 71, CFRTA, FDOT, LakeXpress (may include one or more separated by commas) | Example: agencies=0

GTFS by Agency (Region) Returns all data from all files in the GTFS of one or more FDOT agencies, separated by agency.

GET To Be Determined after award of contract

Optional parameter 'agencies': the agency id(s) for which data should be returned (type = string). If not included, the API will return data on all agencies in the consolidated FDOT GTFS. Valid values: 0, 411, 71, CFRTA, FDOT, LakeXpress (may include one or more separated by commas) | Example: agencies=0

Routes Returns all routes for all agencies in the consolidated FDOT

GTFS.

GET To Be Determined after award of contract None

Stops by Route Returns all stops served by a specified route. GET To Be Determined after award of contract route: the route id for which stops should be returned (type = string)

Stops by Location Returns all stops near a specified latitude/longitude. Up to 15 stops may be returned within a one mile radius of the location.

GET To Be Determined after award of contract lat: the latitude near which stops should be returned (type = float) lon: the longitude near which stops should be returned (type = float)

Scheduled Arrivals and Departures by Stop

Returns all scheduled arrivals and departures for a direction and route for a particular stop.

GET To Be Determined after award of contract stop ‐ GTFS‐compatible stop_id value for which schedule should be returned. String. Example:

“7039” route (optional) ‐ GTFS‐compatible route_id value on the stop for which schedule should be returned. String. If not included then schedule for all routes serving the stop will be returned Example: “10350” direction (optional) ‐ GTFS‐compatible direction_id value on route of the stop for which schedule should be returned. Bit (0 or 1). If included then route must also be included If not included then schedule for all directions of the route serving the stop will be returned Example:

“0” datetime (optional) ‐ Epoch time after which schedule should be returned. Integer. If included then must be within the next seven (7) days If not included then schedule starting from the current datetime will be returned Example: “1563577735” max_time (optional) ‐ Defines maximum range of time (in minutes) within which trips will be returned. Integer between 1 and 1440 (24 hours). If not included defaults to 60. Example:

“120” max_trips (optional) ‐ Defines number of trips to return. Integer between 1 and 100. If not included defaults to 5. Example: “100”

Scheduled Arrivals and Deparatures by Route

Returns all scheduled arrivals and departures for a particular route or routes.

GET To Be Determined after award of contract route ‐ comma separated GTFS‐compatible route_id values on the stop for which schedule should be returned. Limit to 20 routes. String. Example: “10350” datetime (optional) ‐ Epoch time after which schedule should be returned. Integer. If included then must be within the next seven (7) days If not included then schedule starting from the current datetime will be returned Example: “1563577735” max_time (optional) ‐ Defines maximum range of time (in minutes) within which trips will be returned. Integer between 1 and 1440 (24 hours). If not included defaults to 60. Example:

“120” max_trips (optional) ‐ Defines number of trips to return. Integer between 1 and 100. If not included defaults to 5. Example: “100”

Scheduled Arrivals and Deparatures by Trip

Returns all scheduled arrivals and departures for a particular trip.

GET To Be Determined after award of contract trip ‐ GTFS‐compatible trip_id value for which schedule should be returned. String. Example:

“1335040” datetime (optional) ‐ Epoch time after which schedule should be returned. Integer. If included then must be within the next seven (7) days If not included then schedule starting from the current datetime will be returned Example: “1563577735”

Data Dictionary Demographic Information Fields to be Populated

Dataset Identfier Autopopulated by DFE GUID Unique identifier of the data set. This is generated programmatically in the DFE.

Dataset Name FDOT_ConsolidatedGTFSRT_V1 String/Text Name of the data set (example: Here_V3.1.2). Names should be descriptive of the data while remaining unique enough to accurately reflect version changes.

Dataset Short Name fdot_gtfsrt String/Text The short name for use in referencing the dataset. This will be the name which is used to represent the data for use in ingestion and API reference. This name should be lowercase and contain no spaces.

Last Update 2017‐09 (GTFS Version 2.0) Date/Time

Last time (Date and Time) that the data set was updated. Date and Time represented in this field reflects the Date and Time of the underlying version or data creation. In the event of a dataset which is dynamic or continually updating, the date will reference the date and time of the first collection of the overall data for inclusion in the DFE.

Data Version 2.0 Numeric Version of the current data set. Datasets without a Version are populated with a value of 1 indicating it is the first version of the data in the DFE.

Dataset Revision Date 2017‐09 (GTFS Version 2.0) Date/Time Date of the last dataset structural revision. Leave row blank for data which this does not apply.

Dataset Vendor Name String/Text

Name of the Vendor or Organization who is responsible for the creation of the data set. For versions of data which have been post processed, refined, or otherwise changed indicate the vendor, organization, or agency whom is providing the data for ingestion into the DFE Environment

Dataset POC String/Text Name of the Point of Contact for the dataset Vendor Email String/Text Email Address for the point of contact for the dataset Vendor Phone Number String/Text Phone number for the point of contact for the dataset Vendor Fax Number String/Text Fax Number for the point of contact for the dataset Vendor Address String/Text Postal address for the point of contact for the dataset

Original Dataset Source System Links to source data are referenced in the Additional Documents tab. String/Text Common name of the location where the data is being retrieved from. Examples include RCI, FDGL, UBR, HERE, or other common source names

Dataset Loading Method Access via APIs (see API Linkage tab) or direct download from an Amazon S3 bucket. String/Text What method is used to provide the data to the DFE Sandbox Environment. (Example: SQL Pull, Manual Download, XML feed, RSS Feed)

Dataset Loading Procedure Download at a configurable interval from an endpoint and load into DFE. String/Text

Description, Instructions, or Links providing information on how the dataset is loaded into the DFE. This represents a short description/explanation of how the data is being loaded or made available to the DFE Environment.

Update Interval 30 seconds String/Text

The frequency of update for the data. (Example: 30 second, 1 minute, 5 minute, Nightly, Weekly, Bi-Weekly, Monthly, Quarterly, etc.). If multiple update frequencies are available identify the update interval used for the

DFE.

Volume Live data, changes with each update. String/Text Quantity of Records per Update Interval. This includes all rows in a table or feature per update interval timeframe that will be ingested in document. This value can be an estimate (ex. 50K per update interval).

Historical Period

For realtime data, there may be predictions with timestamps in the near‐term past, but GTFS‐ realtime is not intended as a historical reporting format. Considering this, we are not reporting historical period here. String/Text

Period of time in which the data is stored, represents the earliest data records included by timestamp date. If data is not continuously updated or not expected to be updated a date range should be included. For example (2013-2016).

This can also represent data sets which have changed based on version changes in which the structure of the data was significantly altered and is no longer being collected at that version.

Data Size in DFE Variable; changes by day and time of day. String/Text Estimated size input of data into DFE for each Update Interval. This value will be used in combination with the Update Interval to determine the overall Data Size of each update for the data.

Dataset Notes String/Text Additional Notes about the demographic portion of the dataset source Dataset Documentation

Links to source data are referenced in the Additional Documents tab. Additional resources, including from GitHub and gtfs.org are also referenced here. String/Text Links to source dataset documentation that may available via the data creator.

Data Dictionary Field Structure Fields to be Populated

Field Name Field Description Field Type

Field

Length

Present in

Lynx VP

Feed

Present in

Sunrail VP

Feed

Present in

LYNX TU

Feed

Present in

Sunrail TU

Feed

FeedMessage Contains the content of the feed, all other fields are within the FeedMessage. | Present in Vehicle Positions and Trip Updates GTFS‐rt feeds FeedMessage No No No No header Contains metadata about the feed and feed message. | Part of FeedMessage object | Present in Vehicle Positions and Trip Updates GTFS‐rt feeds FeedHeader Yes Yes Yes Yes gtfs_realtime_version Version of the feed specification. The current version is 2.0. | Part of FeedHeader object | Present in Vehicle Positions and Trip Updates GTFS‐rt feeds string Yes Yes Yes Yes incrementality Determines whether the current fetch of data is incremental. | Part of FeedHeader object | Present in Vehicle Positions and Trip Updates GTFS‐rt feeds Incrementality Yes No Yes No timestamp

Identifies the moment when the feed content was created (POSIX time: number of seconds since January 1st 1970 00:00:00 UTC). | Part of FeedHeader object | Present in Vehicle Positions and Trip Updates GTFS‐rt feeds uint64 Yes Yes Yes Yes entity Contains the contents of the feed. | Part of FeedMessage object | Present in Vehicle Positions and Trip Updates GTFS‐rt feeds FeedEntity Yes Yes Yes Yes id Feed‐unique identifier for the entity (used only to provide incrementality support). | Part of FeedEntity object | Present in Vehicle Positions and Trip Updates GTFS‐rt feeds string Yes Yes Yes Yes vehicle Provides automatically generated information on the location of a vehicle. | Part of FeedEntity object | Present in Vehicle Positions GTFS‐rt feed VehiclePositions Yes Yes No No trip Identifies the trip that the vehicle is serving. | Part of VehiclePositions and TripUPdate objects | Present in Vehicle Positions and Trip Updates GTFS‐rt feeds TripDescriptor Yes Yes Yes Yes direction_id

Contains the direction of the trip, from the trips.txt file. | Part of TripDescriptor object | Present in Vehicle Positions (VehiclePositions/TripDescriptor) and Trip Updates (TripUpdate/TripDescriptor) GTFS‐rt feeds uint32 No Yes No Yes route_id

Contains an ID that uniquely identifies a route. | Part of TripDescriptor object | Present in Vehicle Positions (VehiclePositions/TripDescriptor) and Trip Updates (TripUpdate/TripDescriptor) GTFS‐rt feeds string Yes Yes Yes Yes start_date

Contains the date of the trip that the vehicle is serving. | Part of TripDescriptor object | Present in Vehicle Positions (VehiclePositions/TripDescriptor) and Trip Updates (TripUpdate/TripDescriptor) GTFS‐rt feeds string Yes, but noYes Yes Yes schedule_relationship

Contains the relation between the trip and the static schedule (scheduled, added, unscheduled, canceled // default = scheduled). | Part of TripDescriptor object | Present in Vehicle Positions (VehiclePositions/TripDescriptor) and Trip Updates (TripUpdate/TripDescriptor) GTFS‐rt feeds ScheduleRelationship Yes, but noNo Yes Yes position Identifies the current position of the vehicle. | Part of VehiclePositions object | Present in Vehicle Positions GTFS‐rt feed Position Yes Yes No No latitude Contains the latitude of the vehicle, degrees North, WGS‐84 coordinate system. | Part of Position object | Present in Vehicle Positions GTFS‐rt feed decimal Yes Yes No No longitude Contains the longitude of the vehicle, degrees East, WGS‐84 coordinate system. | Part of Position object | Present in Vehicle Positions GTFS‐rt feed decimal Yes Yes No No speed Momentary speed measured by the vehicle, in meters per second. | Part of Position object | Present in Vehicle Positions GTFS‐rt feed float No Yes No No bearing

Contains the compass direction that the vehicle is facing in degrees clockwise from North (i.e. north = 0, east = 90, south = 180, west = 270). | Part of Position object | Present in Vehicle Positions GTFS‐rt feed float Yes No No No vehicle

Gives additional information about the vehicle that is serving the trip. | Part of VehiclePositions and TripUpdate objects | Present in Vehicle Positions (VehiclePositions/VehicleDescriptor) and Trip Updates GTFS‐rt (TripUpdate/VehicleDescriptor) feed VehicleDescriptor No No Yes Yes id

Feed‐unique identifier for the entity (used only to provide incrementality support). | Part of VehicleDescriptor object | Present in Vehicle Positions (VehiclePositions/VehicleDescriptor) and Trip Updates (TripUpdate/VehicleDescriptor) GTFS‐rt feeds string Yes Yes Yes Yes label

Contains the internal system of identification of the vehicle, unique to the vehicle. | Part of VehicleDescriptor object | Present in Vehicle Positions (VehiclePositions/VehicleDescriptor) and Trip Updates (TripUpdate/VehicleDescriptor) GTFS‐rt feeds string No Yes No Yes current_stop_sequence Contains the stop sequence index of the current stop, determined by current status. | Part of VehiclePositions object | Present in Vehicle Positions GTFS‐rt feed uint32 Yes, but noYes, but noNo No stop_id Identifies the current stop. | Part of VehiclePositions object | Present in Vehicle Positions GTFS‐rt feed string Yes, but noYes, but noNo No current_status Contains the current status of the vehicle with respect to the current_stop_sequence. | Part of VehiclePositions object | Present in Vehicle Positions GTFS‐rt feed VehicleStopStatus No Yes, but noNo No timestamp Contains the moment at which the vehicle's position was measured. | Part of VehiclePositions object | Present in Vehicle Positions GTFS‐rt feed uint64 Yes, but noYes No No trip_update Represents fluctuations in the timetable, can give predicted arrival or departure times, cancellations, re‐schedules, re‐routes, etc. | Part of FeedEntity object | Present in Trip Updates GTFS‐rt feed TripUpdate No No Yes Yes stop_time_update Contains the realtime update for arrival and/or departure events for a given stop on a trip | Part of TripUpdate object | Present in Trip Updates GTFS‐rt feed StopTimeUpdate No No Yes Yes stop_sequence Provides the stop sequence that matches the one listed in stop_times.txt in the corresponding GTFS feed. | Part of StopTimeUpdate object | Present in Trip Updates GTFS‐rt feed uint32 No No Yes Yes arrival If schedule_relationship is empty or scheduled, must contain either arrival or departure information. | Part of StopTimeUpdate object | Present in Trip Updates GTFS‐rt feed StopTimeEvent No No Yes Yes departure If schedule_relationship is empty or scheduled, must contain either arrival or departure information. | Part of StopTimeUpdate object | Present Trip Updates GTFS‐rt feed StopTimeEvent No No Yes, but noYes time Absolute time of arrival or departure StopTimeEvents. | Part of StopTimeEvent object | Present in Trip Updates GTFS‐rt feed int64 No No Yes Yes stop_id Provides the stop ID that matches the one listed in stop_times.txt in the corresponding GTFS feed. | Part of StopTimeUpdate object | Present in Trip Updates GTFS‐rt feed string No No Yes Yes timestamp Contains the moment at which the vehicle's real‐time progress was mentioned. | Part of TripUpdate object | Present in Trip Updates GTFS‐rt feed uint64 No No Yes Yes

Data Dictionary API Fields to be Populated

GTFS‐RT Trip Updates

Returns the most recent trip updates feed for one or more agencies (all if no agency parameter included) after a specified time; if no time included then the most recent feed is returned

GET To Be Determined after award of contract agency (optional) ‐ GTFS‐compatible agency_id value for which data should be returned. String.

Example: “CFRTA” AfterDateTime (optional) ‐ Time after which the most recent trip updates should be returned. If no time is specified, then the most recent trip updates feed will be provided. If no trip updates feed is newer than the specified time, then an empty message will be returned. ISO 8601.

Example: 2020‐02‐21T10:52:47

GTFS‐RT Vehicle Positions

Returns the most recent vehicle positions feed for one or more agencies (all if no agency parameter included) after a specified time; if no time included then the most recent feed is returned

GET To Be Determined after award of contract agency (optional) ‐ GTFS‐compatible agency_id value for which data should be returned. String.

Example: “CFRTA” AfterDateTime (optional) ‐ Time after which the most recent vehicle positions should be returned. If no time is specified, then the most recent vp feed will be provided. If no vp feed is newer than the specified time, then an empty message will be returned. ISO 8601.

Example: 2020‐02‐21T10:52:47

GTFS‐RT Trip Updates Archived Returns a list of file names of all trip updates feeds for one or more agencies (all if no agency paramter included) generated in a time range

GET To Be Determined after award of contract agency (optional) ‐ GTFS‐compatible agency_id value for which data should be returned. String Example: “FDOT” FromDateTime ‐ Time after which file names of trip updates feeds should be returned. ISO 8601 Example: 2020‐02‐21T10:52:47 ToDateTime ‐ Time before which file names of trip updates feeds should be returned. ISO 8601 Example: 2020‐02‐21T10:57:47

GTFS‐RT Trip Updates From File Returns the trip updates feed for the specified trip updates file

GET To Be Determined after award of contract FileName ‐ File name of the trip updates feed. String Example: “trip_updates_1”

GTFS‐RT Vehicle Positions Archived Returns a list of file names of all vehicle positions feeds for one or more agencies (all if no agency paramter included) generated in a time range

GET To Be Determined after award of contract agency (optional) ‐ GTFS‐compatible agency_id value for which data should be returned. String Example: “FDOT” FromDateTime ‐ Time after which file names of vehicle positions feeds should be returned. ISO Example: 2020‐02‐21T10:52:47 ToDateTime ‐ Time before which file names of vehicle positions feeds should be returned. ISO Example: 2020‐02‐21T10:57:47

GTFS‐RT Vehicle Positions From File

Returns the vehicle positions feed for the specified vehicle positions file

GET To Be Determined after award of contract FileName ‐ File name of the vehicle positions feed. String Example: “vehicle_positions_1”

Dataset Identfier Autopopulated by DFE GUID Unique identifier of the data set. This is generated programmatically in the DFE.

Dataset Name FDOT_TripUpdates_V1 String/Text Name of the data set (example: Here_V3.1.2). Names should be descriptive of the data while remaining unique enough to accurately reflect version changes.

Dataset Short Name fdot_tu_v1 String/Text The short name for use in referencing the dataset. This will be the name which is used to represent the data for use in ingestion and API reference. This name should be lowercase and contain no spaces.

Last Update 2017‐09 (GTFS Version 2.0) Date/Time

Last time (Date and Time) that the data set was updated. Date and Time represented in this field reflects the Date and Time of the underlying version or data creation. In the event of a dataset which is dynamic or continually updating, the date will reference the date and time of the first collection of the overall data for inclusion in the

DFE.

Data Version 2.0 Numeric Version of the current data set. Datasets without a Version are populated with a value of 1 indicating it is the first version of the data in the DFE.

Dataset Revision Date 2017‐09 (GTFS Version 2.0) Date/Time Date of the last dataset structural revision. Leave row blank for data which this does not apply.

Dataset Vendor Name String/Text

Name of the Vendor or Organization who is responsible for the creation of the data set. For versions of data which have been post processed, refined, or otherwise changed indicate the vendor, organization, or agency whom is providing the data for ingestion into the DFE Environment

Dataset POC String/Text Name of the Point of Contact for the dataset Vendor Email String/Text Email Address for the point of contact for the dataset Vendor Phone Number String/Text Phone number for the point of contact for the dataset Vendor Fax Number String/Text Fax Number for the point of contact for the dataset Vendor Address String/Text Postal address for the point of contact for the dataset

Original Dataset Source System Links to source data are referenced in the Additional Documents tab. String/Text Common name of the location where the data is being retrieved from. Examples include RCI, FDGL, UBR, HERE, or other common source names

Dataset Loading Method Access via APIs (see API Linkage tab) or direct download from an Amazon S3 bucket. String/Text What method is used to provide the data to the DFE Sandbox Environment. (Example: SQL Pull, Manual Download, XML feed, RSS Feed)

Dataset Loading Procedure Download at a configurable interval from an endpoint and load into DFE. String/Text

Description, Instructions, or Links providing information on how the dataset is loaded into the DFE. This represents a short description/explanation of how the data is being loaded or made available to the DFE Environment.

Update Interval 30 seconds String/Text

The frequency of update for the data. (Example: 30 second, 1 minute, 5 minute, Nightly, Weekly, Bi-Weekly, Monthly, Quarterly, etc.). If multiple update frequencies are available identify the update interval used for the

DFE.

Volume Live data, changes with each update. String/Text Quantity of Records per Update Interval. This includes all rows in a table or feature per update interval timeframe that will be ingested in document. This value can be an estimate (ex. 50K per update interval).

Historical Period

For realtime data, there may be predictions with timestamps in the near‐term past, but GTFS‐ realtime is not intended as a historical reporting format. Considering this, we are not reporting historical period here. String/Text

Period of time in which the data is stored, represents the earliest data records included by timestamp date. If data is not continuously updated or not expected to be updated a date range should be included. For example (2013- 2016). This can also represent data sets which have changed based on version changes in which the structure of the data was significantly altered and is no longer being collected at that version.

Data Size in DFE Variable; changes by day and time of day. String/Text Estimated size input of data into DFE for each Update Interval. This value will be used in combination with the Update Interval to determine the overall Data Size of each update for the data.

Dataset Notes String/Text Additional Notes about the demographic portion of the dataset source Dataset Documentation

Links to source data are referenced in the Additional Documents tab. Additional resources, including from GitHub and gtfs.org are also referenced here. String/Text Links to source dataset documentation that may available via the data creator.

Field Name Field Description Field Type

Field

Length Part of SunRail GTFS‐rt Part of LYNX GTFS‐rt

FeedMessage Contains the content of the feed, all other fields are within the FeedMessage FeedMessage Yes Yes header Contains metadata about the feed and feed message | Part of FeedMessage object

FeedHeader Yes Yes gtfs_realtime_version Version of the feed specification; the current version is 2.0 | Part of FeedHeader object string Yes Yes incrementality Determines whether the current fetch of data is incremental | Part of FeedHeader object

Incrementality Yes Yes timestamp Identifies the moment when the feed content was created (POSIX time: number of seconds since January 1st 1970 00:00:00 UTC) | Part of FeedHeader object uint64 Yes Yes entity Contains the contents of the feed | Part of FeedMessage object FeedEntity Yes Yes id Feed‐unique identifier for the entity (used only to provide incrementality support) | Part of FeedEntity object string Yes Yes is_deleted Whether this entity is to be deleted | Part of FeedEntity object bool No No trip_update Represents fluctuations in the timetable, can give predicted arrival or departure times, cancellations, re‐schedules, re‐routes, etc | Part of FeedEntity object

TripUpdate Yes Yes trip Identifies the trip that the vehicle is serving | Part of TripUpdate object TripDescriptor Yes Yes vehicle Gives additional information about the vehicle that is serving the trip | Part of TripUpdate object

VehicleDescriptor Yes Yes stop_time_update Contains the realtime update for arrival and/or departure events for a given stop on a trip | Part of TripUpdate object

StopTimeUpdate Yes Yes timestamp Contains the moment at which the vehicle's real‐time progress was mentioned | Part of TripUpdate object uint64 Yes Yes delay The current schedule deviation for the trip; should only be specified when the prediction is given relative to some existing schedule in GTFS (experimental) | Part of TripUpdate object int32 No No trip_id Contains an ID that identifies the trip that a vehicle is serving | Part of TripDescriptor object string Yes Yes route_id Contains an ID that uniquely identifies a route | Part of TripDescriptor object string Yes Yes direction_id Contains the direction of the trip, from the tripstxt file | Part of TripDescriptor object uint32 Yes No start_time The initially scheduled start time of the trip instance | Part of TripDescriptor object string No No start_date Contains the date of the trip that the vehicle is serving | Part of TripDescriptor object string Yes Yes schedule_relationship Contains the relation between the trip and the static schedule (scheduled, added, unscheduled, canceled // default = scheduled) | Part of TripDescriptor object

ScheduleRelationship Yes Yes id Feed‐unique identifier for the entity (used only to provide incrementality support) | Part of VehicleDescriptor object string Yes Yes label Contains the internal system of identification of the vehicle, unique to the vehicle | Part of VehicleDescriptor object string Yes No license_plate The license plate of the vehicle | Part of VehicleDescriptor object string No No stop_sequence Provides the stop sequence that matches the one listed in stop_timestxt in the corresponding GTFS feed | Part of StopTimeUpdate object uint32 Yes Yes stop_id Provides the stop ID that matches the one listed in stop_timestxt in the corresponding GTFS feed | Part of StopTimeUpdate object string Yes Yes arrival If schedule_relationship is empty or scheduled, must contain either arrival or departure information | Part of StopTimeUpdate object

StopTimeEvent Yes Yes departure If schedule_relationship is empty or scheduled, must contain either arrival or departure information | Part of StopTimeUpdate object

StopTimeEvent Yes Yes schedule_relationship Contains the relation between the trip and the static schedule (scheduled, added, unscheduled, canceled // default = scheduled) | Part of TripDescriptor object

ScheduleRelationship Yes Yes delay Delay (in seconds) can be positive (vehicle is late) or negative (vehicle is ahead of schedule) | Part of StopTimeEvent object int32 No No time Absolute time of arrival or departure StopTimeEvents | Part of StopTimeEvent object int64 Yes Yes uncertainty If uncertainty is omitted, it is interpreted as unknown | Part of StopTimeEvent object int32 No No

Data Dictionary Additional Documentation Fields to be Populated gtfs.org A document that explains the types of files that comprise a GTFS transit feed and defines the fields used in all of those files. http://gtfs.org/realtime/

GTFS‐rt Structure

GTFS‐rt feeds are structured in a nested format. The Field Structure tab represents this by telling the viewer both the object that a field appears directly in, as well as the GTFS‐rt feed that the field is present in. All feeds contain a FeedMessage with a FeedHeader that contains the GTFS‐rt version, a timestamp, and the entity (which contains the body of the feed). Some objects and fields appear in multiple GTFS‐rt feeds but at a different position in the nested structure. For example, the TripDescriptor object is located within the VehiclePositions object in the Vehicle Positions feed, but is within the TripUpdate object in the Trip Updates feed. More information on this structure can be found at the link to the right.

http://gtfs.org/realtime/

GTFS‐RT Trip Updates

Returns the most recent trip updates feed for one or more agencies (all if no agency parameter included) after a specified time; if no time included then the most recent feed is returned

GET To Be Determined after award of contract agency (optional) ‐ GTFS‐compatible agency_id value for which data should be returned. String.

Example: “CFRTA” AfterDateTime (optional) ‐ Time after which the most recent trip updates should be returned. If no time is specified, then the most recent trip updates feed will be provided. If no trip updates feed is newer than the specified time, then an empty message will be returned. ISO 8601.

Example: 2020‐02‐21T10:52:47

GTFS‐RT Trip Updates Archived Returns a list of file names of all trip updates feeds for one or more agencies (all if no agency paramter included) generated in a time range

GET To Be Determined after award of contract agency (optional) ‐ GTFS‐compatible agency_id value for which data should be returned. String Example: “FDOT” FromDateTime ‐ Time after which file names of trip updates feeds should be returned. ISO 8601 Example: 2020‐02‐21T10:52:47 ToDateTime ‐ Time before which file names of trip updates feeds should be returned. ISO 8601 Example: 2020‐02‐21T10:57:47

GTFS‐RT Trip Updates From File Returns the trip updates feed for the specified trip updates file

GET To Be Determined after award of contract FileName ‐ File name of the trip updates feed. String Example: “trip_updates_1”

Dataset Identfier Autopopulated by DFE GUID Unique identifier of the data set. This is generated programmatically in the DFE.

Dataset Name FDOT_VehiclePositions_V1 String/Text Name of the data set (example: Here_V3.1.2). Names should be descriptive of the data while remaining unique enough to accurately reflect version changes.

Dataset Short Name fdot_vp_v1 String/Text

The short name for use in referencing the dataset. This will be the name which is used to represent the data for use in…