This feed has expired Service dates: 2017-05-31 - 2018-12-31

lampoon-pattana-transport - GTFS transit data for Thailand

Expired
transitfeeds Thailand May 31, 2017 — December 31, 2018

About This Feed

The lampoon-pattana-transport GTFS feed by transitfeeds provides structured public transit data for Thailand, covering 3 routes, 268 stops, and 2 transit agencies. Formatted according to the General Transit Feed Specification (GTFS), this dataset is ready for transit apps, routing engines, urban planning tools, and AI agents / LLM applications.

This feed was active from May 31, 2017 to December 31, 2018 and is no longer current. It remains available for historical analysis and research.

Data is automatically validated and corrected. View our quality pipeline →

Transit map showing lampoon-pattana-transport routes and stops in Thailand
Explore 3 routes, 268 stops, and 2 agencies

Browse routes, stops, and agencies from this feed. Public pages show merged data from all feeds. Sign in for per-feed details useful for GTFS integration and debugging.

Sign in to access →

Download this feed through the BusMaps API

Enhanced GTFS, source GTFS, GeoJSON, and validation reports are available through the API.

Use ?feedName=lampoon-pattana-transport to request this feed. View API documentation.

Enhanced & Validated Recommended

Updated 2026-08-01

Cleaned, corrected, and validated against GTFS specifications. View corrections.

ZIP GTFS Feed - Corrected & Enriched
0.06 MB
Available through API only The license for this work is not specified Content Hash: a30a0144df793484
ZIP Validation Report
0.01 MB
Available through API only
0Errors
14Warnings
1Info
Top Issues
stop too far from shape10
expired calendar1
feed expiration date7 days1
GeoJSON GeoJSON Data
0.02 MB
Available through API only

Original Source

Obtained 2018-02-20

Unmodified GTFS data from official sources. May contain errors or inconsistencies.

ZIP GTFS Source Data
0.05 MB
Available through API only The license for this work is not specified Content Hash: 6a2a23f3360f1927
ZIP Validation Report
0.01 MB
Available through API only
0Errors
33Warnings
1Info
Top Issues
mixed case recommended field14
stop too far from shape10
expired calendar7

Use This Feed from AI Agents

This feed is also served through the BusMaps MCP server: point Claude, ChatGPT, Gemini or any MCP client at https://mcp.busmaps.com/mcp and your agent can plan routes, read departures, and query this network in plain language.

About the MCP server →

Overlapping Feeds

Feeds that share stops or routes with this dataset.

Feed Stops Overlap Routes Overlap
coopthainctth 27 (10.07%)
coopthai-nct3 15 (5.6%)
Build real-time departures into your app Free API Access →

Frequently Asked Questions

What is GTFS data?

General Transit Feed Specification (GTFS) is an open data format for public transit schedules and geographic information. Created by Google and TriMet, it enables transit agencies to publish interoperable data for applications, trip planners, and mobility analytics tools.

What is the difference between enhanced and source data?

Source data is the original GTFS feed obtained from the transit agency or official provider. The enhanced version has been processed to fix errors, remove inconsistencies, and ensure compliance with GTFS specifications. We recommend the enhanced version for production applications.

Can I use this data in my application?

Data usage depends on the license specified by the original provider. Check the license information in the download section. Many GTFS feeds use open data licenses that allow free use with attribution. Always verify the license terms before integration.

How do I validate a GTFS feed?

Each feed includes a validation report documenting errors and warnings. You can also use the MobilityData GTFS Validator for independent validation. Enhanced feeds have already been processed to resolve the most critical validation issues.

All data on this site comes from publicly available sources. If a file was posted in error, has an incorrect license, or lacks correct source attribution, please contact us and we will correct it.