Catalog only
Transport
OpenStreetMap Thailand taxi stands.
Best free geospatial layer for taxi ranks, pickup points, and some motorcycle-taxi stands where tagged. Coverage is incomplete and informal stands often need manual validation.
Public
OSM extracts and Overpass API using amenity=taxi, opening_hours, name, operator, and vehicle tags
Free open data under ODbL attribution/share-alike terms
Weekly nationally; daily/weekly for Bangkok and airports
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
page reference only
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
Medium-high for discovery and context; operational reliability depends on endpoint stability.
Runtime truth
Catalog only
Not yet
No runtime entity scope yet.
No live observation ingestion yet.
Not wired into active decisions yet.
Profiled in the atlas and public pages, but not yet connected to live graph computation.
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
Best free geospatial layer for taxi ranks, pickup points, and some motorcycle-taxi stands where tagged. Coverage is incomplete and informal stands often need manual validation.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
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.
Refresh daily, or more often only when the source publishes explicit current-status fields.
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.
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://wiki.openstreetmap.org/wiki/Tag:amenity%3Dtaxi" -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.
- Geospatial layers can be large, tiled, or projection-specific.
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.