enjoythai.land

Transport

OTP taxi GPS trip analytics.

Aggregate taxi passenger-trip analytics derived from DLT/OTP GPS data, including monthly average taxis, daily average trips, pickup trips, average trip distance, average speed, total distance, and total time. Good for mobility and demand analysis, not live taxi positions or raw trips.

Public MOT/OTP catalog resources in CSV/XLSX/PDF and API-backed catalog metadata where exposed Free public/open data where OTP resources are published Monthly Open source
Runtime role

Decision driving

Access class

Public

Access type

MOT/OTP catalog resources in CSV/XLSX/PDF and API-backed catalog metadata where exposed

Free status

Free public/open data where OTP resources are published

Cadence

Monthly

Last verified

2026-05-11

Access class note

Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.

Used in layers

source health, observation ingest, signal compute, decision compute

Useful fields

service or stand name, operator or provider, legal status or certification, vehicle or service category, fare rule where applicable, pickup point or stand, airport terminal/gate where relevant, lat/lon, complaint channel, aggregate trip metrics or demand zone where exposed, quote/ETA fields only when authorized, source ID

Reliability rating

Medium-high for discovery and context; operational reliability depends on endpoint stability.

Runtime truth

Runtime role

Decision driving

Production ready

Yes

Entity scope

route, station, airport, pier, destination, terminal, transport_zone

Observation scope

taxi_pickup_dropoff_support_score

Decision scope

where_to_go_today, where_to_stay, route_check

Runtime note

Feeds active observations and signals that currently influence traveler-facing decisions.

How this helps travel recommendations

Turns Thailand taxi and ride-hailing into source-backed decisions: whether a service is legal, what the fare rule actually is, where airport pickup happens, whether a stand or motorcycle-taxi win exists, which areas have strong taxi demand, and which app or complaint surface can actually support the claim.

Endpoint and API notes

Aggregate taxi passenger-trip analytics derived from DLT/OTP GPS data, including monthly average taxis, daily average trips, pickup trips, average trip distance, average speed, total distance, and total time. Good for mobility and demand analysis, not live taxi positions or raw trips.

Open the source endpoint or documentation. Return to the Thailand data atlas.

Developer reference

Best endpoint

Use DLT for legal registry, driver-license, operator-license, Taxi OK/VIP, complaints, and app-certification context; OTP/MOT for aggregate taxi GPS analytics and pickup/dropoff zones; AOT for airport taxi counters and surcharge rules; OSM/Google/Longdo/NOSTRA for stands and pickup points; and platform APIs only where explicit authorization exists.

Recommended refresh

Check weekly for change detection, but treat the official publication period as the real cadence.

Travel scoring role

Turns Thailand taxi and ride-hailing into source-backed decisions: whether a service is legal, what the fare rule actually is, where airport pickup happens, whether a stand or motorcycle-taxi win exists, which areas have strong taxi demand, and which app or complaint surface can actually support the claim.

Comparable / backup source

DLT, Thailand.go.th, MOT/OTP, AOT, DLT GPS, OSM/Overpass, Google Places, Longdo, NOSTRA, airport/operator pages, and partner-authorized ride-hailing or fleet integrations.

Example request

# Verify the documented taxi endpoint before production use.
curl -L "https://www.data.go.th/organization/otp" -H "Accept: application/json"

Failure modes

  • There is no single all-taxi Thailand API.
  • Public taxi data is usually aggregate, legal, or airport-specific rather than live dispatch.
  • OTP taxi GPS analytics do not expose raw GPS traces, live vehicle positions, driver identity, or passenger identity.
  • Ride-hailing apps show ETA, fare, and driver data to users, but that does not make it a public ingest API.
  • Airport taxi surcharge, baggage, and toll rules differ from street-hail or app pricing.
  • Motorcycle taxis, metered taxis, airport limousines, and app hire-cars need different service models.
  • Taxi stands and motorcycle-taxi wins are often under-mapped or informal.
  • Complaint datasets are useful for trends, not for realtime operational quality.
  • Batch files can change schema, naming, encoding, or publication cadence.

Last checked and source confidence

Last checked: 2026-05-11.

Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.