Thailand Air Cargo Data.
Cargo schedule, shipment-workflow, e-booking, and ONE Record schema layers for Thailand air-cargo intelligence.
TAT dining, nightlife, and wellness context
Useful for official tourism framing around dining neighborhoods, nightlife districts, spa and wellness areas, and visitor-oriented route context. Not a canonical hours, licensing, or live-booking feed.
Public tourism website and destination pages for dining districts, nightlife areas, wellness, and spa context TransportAOT air transport statistics
Passenger, aircraft, cargo, and mail statistics for Airports of Thailand airports with current fiscal-year updates and long historical archives.
Investor/public statistics downloads and archive pages TransportCAAT air transport statistics
Official Thai aviation passenger, flight, cargo, mail, and aircraft-movement statistics reports. Useful for airport and industry trend pages, not live flight operations.
Official publication page and linked monthly, quarterly, and annual report files TransportIATA ONE Record
Air-cargo data-sharing standard with common data model and standardized secured web API concepts. Useful for cargo schema design, not a public feed of Thai cargo shipments.
Public standard documentation, API/data-model references, and implementation resources TransportPort Authority of Thailand Data Catalog
Official Port Authority catalog layer for Bangkok Port, Laem Chabang, and other PAT-managed port statistics and reference datasets. Useful for major-port identity, cargo, and logistics context. Low direct traveler value and not an island-ferry schedule, ticket, or berth-queue feed.
CKAN-style PAT Data Catalog with CSV/XLS/RDF/JPEG resources for port statistics, organization data, and official port datasets TransportTHAI Cargo e-services
THAI Cargo schedule search, e-booking, storage-charge, e-import, claim, and shipment-service surfaces. Useful for cargo service and shipment workflow context, but no open public bulk cargo API was verified.
Public cargo portal and e-service surfaces; deeper workflows require account or shipment context