Catalog only
Restaurants, nightlife, and wellness
OpenStreetMap Thailand spas and massage.
Best free spa and massage map spine for venue geometry, names, opening hours, and nearby fallback options. Coverage and tagging depth vary and should not be treated as treatment-quality proof.
Public
OSM extracts and Overpass API using shop=massage, leisure=spa, beauty=spa, opening_hours, and contact tags where mapped
Free open data under ODbL attribution/share-alike terms
Daily/weekly for major tourist cities and resort zones; weekly nationally
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
page reference only
venue name, venue type, cuisine or style, neighborhood or district, lat/lon, address, phone, website, opening hours, business status, ratings or review context where licensed, hotel-area fit, late-return note, 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 restaurants, nightlife, and spas into source-backed decisions about which named venues fit the route, how much return or rain friction exists, what kind of neighborhood the venue lives in, and which source is really proving location, hours, or commercial familiarity.
Endpoint and API notes
Best free spa and massage map spine for venue geometry, names, opening hours, and nearby fallback options. Coverage and tagging depth vary and should not be treated as treatment-quality proof.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use TAT and Thai SELECT for official context, OSM for free venue geometry, Google Places and other licensed POI layers for named venues and hours, and Wongnai-style local discovery only as clearly labeled commercial context.
Refresh daily, or more often only when the source publishes explicit current-status fields.
Turns restaurants, nightlife, and spas into source-backed decisions about which named venues fit the route, how much return or rain friction exists, what kind of neighborhood the venue lives in, and which source is really proving location, hours, or commercial familiarity.
TAT venue context, Thai SELECT, OSM, Google Places, Wongnai, destination food pages, accommodation pages, taxi and safety layers, and local correction notes once a venue workflow exists.
Example request
# Verify the documented venue endpoint before production use.
curl -L "https://wiki.openstreetmap.org/wiki/Tag:shop%3Dmassage" -H "Accept: application/json"Failure modes
- There is no single public all-venues Thailand API.
- Public tourism pages do not prove current hours, line length, or nightlife mood.
- Commercial POI and review sources have licensing, caching, and pricing limits.
- OpenStreetMap is strong for geometry and fallback logic, but coverage and recency vary by district.
- Nightlife and spa convenience depend heavily on hotel base, late transport, noise, and next-day plans, which pure venue APIs rarely answer.
- 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.