[codex] Add Bend landmarks, bike resources, and trails#91
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Populate the Bend MTB pane with 169 curated trails. Trails are matched to OSM ways by geometry (scripts/align_bend_geometry.py decodes the bendbikerides reference polylines and map-matches them to cached Overpass ways), then length + per-point elevation are sampled from Mapbox Terrain-RGB (scripts/build_bend_trails.py). Rendering reuses the shared nationwide OSM trails tileset matched by OSM_ID (CuratedTrailLayerConfig.matchBy='osmId'), with a base filter restricting the curated layer to the matched ids and a deterministic per-way owner so a shared way's color and a click's resolved trail always agree. The nationwide layer excludes curated ids to avoid double-stroking. Auto-detect + map-click resolve OSM_ID to the curated trail name. Includes per-trail elevation profiles, the bendbikerides reference dataset, and the OSM geometry match table.
kwiens
changed the title
The scraper, geometry aligner, and dataset generator for the Bend MTB trails, plus the bendbikerides reference data and OSM geometry match table. (These were dropped from the prior commit by the lint-staged hook, which doesn't match .py/.csv globs.) Hardening: the aligner now resolves flexible-polyline axis order by validating each trail's geometry against its scraped flag point (with a decode quality gate) instead of a magnitude heuristic; the scraper anchors elevation stats to the elevation object, allows negative elevations, and separates network retries from parse errors. Output is byte-identical on current Bend data.
kwiens
marked this pull request as ready for review
June 21, 2026 19:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Bend-specific sidebar/map data so the Bend layer is closer to feature parity with Chattanooga:
Data scope
The PR includes only runtime app data needed by the map:
srccity data and public elevation JSON files. Raw scrape/matching inputs, helper scripts, and onX/MTB Project validation docs/scripts are intentionally not included.Impact
When
NEXT_PUBLIC_CITY_ID=bendis active, the Attractions, Bike Resources, and MTB Trails layers can render Bend-specific markers/trails instead of empty lists. Trail selection and ride auto-detection dispatch curated Bend trail names rather than raw OSM IDs.Validation
pnpm test:runpnpm lint