Transport

DLT GPS passenger and complaint app.

Passenger-facing DLT GPS application for locating DLT-registered public vehicles, filing complaints, and searching passenger stations. Useful as evidence of regulated GPS-linked taxi oversight, not a verified public bulk API.

Public, automation terms unclear Official public mobile-app page and GPS management-center web surfaces Free public app and web access; bulk automation terms are unclear Operational / frequent Open source
Runtime role

Decision driving

Access class

Public, automation terms unclear

Access type

Official public mobile-app page and GPS management-center web surfaces

Free status

Free public app and web access; bulk automation terms are unclear

Cadence

Operational / frequent

Last verified

2026-05-11

Access class note

Publicly reachable, but automation, bulk reuse, or production SLA terms still need an operator or licensing review.

Used in layers

source health, observation ingest, signal compute, decision compute

Useful fields

period, complaint category, source or service type, vehicle or facility class, channel, location or jurisdiction, count, status, outcome, report file, source URL

Reliability rating

High for official context; validate endpoint availability before automation.

Runtime truth

Runtime role

Decision driving

Production ready

Yes

Entity scope

route, station, airport, pier, destination, terminal, district, service_area

Observation scope

official_taxi_oversight_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

Complaint data helps explain trust, nuisance patterns, escalation routes, and service-quality signals. It is strongest for trend analysis and complaint-channel guidance, not for live dispatch or personal-case tracking.

Endpoint and API notes

Passenger-facing DLT GPS application for locating DLT-registered public vehicles, filing complaints, and searching passenger stations. Useful as evidence of regulated GPS-linked taxi oversight, not a verified public bulk API.

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

Developer reference

Best endpoint

Use official complaint statistics, annual reports, or public intake pages; keep historical aggregates separate from live complaint channels and never imply private case detail is public.

Recommended refresh

Refresh weekly or when the catalog metadata changes; many agency catalogs update irregularly.

Travel scoring role

Complaint data helps explain trust, nuisance patterns, escalation routes, and service-quality signals. It is strongest for trend analysis and complaint-channel guidance, not for live dispatch or personal-case tracking.

Comparable / backup source

Official hotline pages, annual reports, regulator dashboards, public complaint portals, and adjacent operational or legal guidance pages.

Example request

# Source landing/download page; inspect linked resources before automation.
curl -L "https://gps.dlt.go.th/?page_id=145"

Failure modes

  • Complaint counts are not the same thing as true incidence.
  • Historical complaint files are often annual, PDF, or XLS/XLSX rather than stable APIs.
  • Live complaint intake and personal-case status are usually private.
  • Complaint categories and service classes can change between reporting periods.

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.