Decision driving
Transport
Marine Department piers.
Marine Department berth, pier, port, terminal, navigation, and service-information context for Thai river, gulf, coastal, and border-water piers. The public berth registry is useful for official passenger-pier support, berth depth, berth length, and route-family context. It is not a verified national realtime ferry schedule, closure, queue, or seat-inventory API.
Public
Official public Marine Department dataset plus site pages; berth registry JSON/CSV is publicly reachable
Free public dataset and website
Weekly or monthly for berth metadata; operational notices as published
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
source health, observation ingest, signal compute, decision compute
pier name, route family, operator, lat/lon, address, first or last boat context where available, booking window, cancellation rule, weather sensitivity, port or pier owner, connected transfer, source ID
High for official context; validate endpoint availability before automation.
Runtime truth
Decision driving
Yes
route, station, airport, pier, destination, terminal, island
official_pier_support_score
where_to_go_today, where_to_stay, route_check, ferry_check
Feeds active observations and signals that currently influence traveler-facing decisions.
How this helps travel recommendations
Turns ferry planning into source-backed decisions about which pier matters, how fragile an island transfer is, where the last-boat risk sits, what should stay refundable, and whether a route needs a mainland or airport backup.
Endpoint and API notes
Marine Department berth, pier, port, terminal, navigation, and service-information context for Thai river, gulf, coastal, and border-water piers. The public berth registry is useful for official passenger-pier support, berth depth, berth length, and route-family context. It is not a verified national realtime ferry schedule, closure, queue, or seat-inventory API.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use Marine Department and PAT pages for official pier and port context, OSM for landing and pier geometry, Namtang static pier/station layers where useful, and commercial operator or booking feeds only when you need live schedules, fares, or availability.
Refresh every 15-60 minutes, with caching and backoff when the upstream fails.
Turns ferry planning into source-backed decisions about which pier matters, how fragile an island transfer is, where the last-boat risk sits, what should stay refundable, and whether a route needs a mainland or airport backup.
Marine Department, PAT, OSM piers, Namtang stop and pier downloads, official operator pages, and commercial ferry booking/search surfaces where authorized.
Example request
# Verify the documented ferry endpoint before production use.
curl -L "https://md.gdcatalog.go.th/dataset/1a58d2ed-4d9a-41db-b59c-1a2870c23e4b" -H "Accept: application/json"Failure modes
- There is no single public national Thailand ferry timetable API.
- Pier identity, operator schedule, and weather reality often come from different systems.
- Consumer booking sites can show routes or timings that need operator or marine confirmation.
- Last-boat timing, cancellation policy, and same-day sea-state risk can change faster than static pier pages.
- Dashboard markup or public-page layout can change without notice.
- 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.