Scout Pins
Complete the cold-start discovery layer — seed defensible off-grid data while public platforms chase restaurants.
Summary
Complete the cold-start discovery layer. Scrape and enrich external data for dispersed camping, BLM, USFS, Crown Land, and Mexican overlanding corridors, then surface them as "Unverified Pins" that users convert into their own verified Scout Pins once they've actually been.
This is the data foundation that makes the map useful before a user's trusted network is large enough to matter. Also the feature most differentiated from Google / Yelp / Campendium — we seed defensible off-grid data while public platforms chase restaurants.
What's in scope
wp-scoutscraper cleanup and production readiness- Scrape and enrich data for US West Coast (CA, OR, WA, NV, AZ, UT, CO, ID, MT)
- Scrape and enrich Western Canada (BC, AB)
- Scrape and enrich Mexico (Baja, Pacific coast, popular overlanding corridors)
- Scout Pin elevation data population
- Scout Pin star/save button (after branch merge)
- Scout Pin → verified pin conversion flow (Scenario B)
- Photo rule enforcement (photo-free private OK, shared pins require photo)
- Android polish pass
Data enrichment model
Already built for Scout Pins and will extend to user pins in Release 2: display_name, named_land_unit, road_surface, county, nearest_town, nearest_feature, is_free, elevation_m, land_type, terrain, setting, sky_visibility.
Open questions
- Scout Pin conversion UX (Scenario B): What happens when a user taps "Create Pin" on a scout pin they've visited? PRD needed before this ships.
- Geographic expansion post-launch: East coast US, rest of Canada, interior Mexico. Scraper is region-configurable — adding regions is a data op, not a code change.