Catalog only
Transport
OSM Thailand piers.
Free pier and ferry map layer for amenity=ferry_terminal, man_made=pier, route=ferry, landings, and nearby boat-access context. Useful for coordinates, nearby transfers, and fallback mapping, not official route confirmation.
Public
OpenStreetMap Overpass API and ODbL geospatial data
Free open data under ODbL attribution/share-alike terms
Current community-edited data; daily or weekly refresh is typical
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
page reference only
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
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 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
Free pier and ferry map layer for amenity=ferry_terminal, man_made=pier, route=ferry, landings, and nearby boat-access context. Useful for coordinates, nearby transfers, and fallback mapping, not official route confirmation.
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 daily, or more often only when the source publishes explicit current-status fields.
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://overpass-turbo.eu/" -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.
- 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.