Course-Data Strategy

Source Tiers

• Public discovery data
  Course name, city, state, public website, and general location.
• OpenStreetMap-derived records
  Course boundaries, geographic features, and map references where OSM coverage exists.
• Licensed data
  Paid or permissioned datasets for hole layouts, hazards, tees, greens, and yardages.
• Venue or course supplied data
  Approved local notes, event info, league rules, and facility details.
• User notes
  Golfer-owned reminders, targets, misses, and bag decisions.

OpenStreetMap

Use OSM with visible attribution. Track any OSM-derived fields so Bay2Course can honor ODbL obligations if modified datasets are published or redistributed.

Attribution: © OpenStreetMap contributors

The live traveler course finder uses small Cloudflare-cached nearby OSM lookups as a launch bridge. The stable national database should come from imported OSM extracts stored in Bay2Course D1, not repeated public Overpass calls from every phone.

Stable National Coverage

• Download US or state OSM extracts from Geofabrik or an equivalent OSM extract source.
• Filter leisure=golf_course records into a normalized Bay2Course D1 table.
• Serve search from D1 with KV edge caches for popular travel areas.
• Keep OSM attribution, source URLs, correction flow, and data-register entries visible.
• Use Google, Mapbox, Geoapify, Foursquare, OpenGolfAPI, GolfCourseAPI, Golfbert, NGF, or USGA only after storage and redistribution terms are documented.

Product Boundary

• Do not claim official course yardages unless the course or licensed provider supplies them.
• Do not use scraped private member portals.
• Do not sell hole maps as complete until licensing is clear.
• Treat user notes as personal planning data, not official course records.

Best First Feature

Start with a course bag card: trusted tee club, safe layup number, wedge range, likely miss, equipment notes, and personal reminders. That creates value before Bay2Course needs expensive hole-level mapping.