The route shapes were built by sorting road nodes by distance. Where R274 has a
central reservation OSM draws each carriageway as its own way, so the sort
alternated between them: 216 of 1,715 points in 274-route.json lay on the second
carriageway, up to 38 m sideways, in the divided sections after 福山大橋 and
through 占冠. All three shapes are now traced back along the shortest-path tree,
so they follow one spine. Point spacing sums to exactly the km span and km
strictly increases in every file. No roster coordinate came from a dropped point.
274-route-west.json 54 pts 30.46 - 35.53 ends on the first main point
274-route.json 1499 pts 35.53 - 108.74
274-route-east.json 54 pts 108.56 - 113.99 overlaps main by 0.18 km
The stubs let the video bring the road in before 川端橋 and carry it on past
右左府 for 東に続く. The GeoJSON carries all three as separate lines.
Page and GeoJSON rebuilt, which also picks up the roster fixes. 274-dev.md
brought up to date: file table, current roster figures, and three new entries
under errors found and fixed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Eleven files were cluttering wip/ alongside an unrelated draft. They now
sit together in their own directory.
Checked against the pipeline in novoyuuparosk-auto-wiki before moving:
- discovery is source_dir.rglob("*.md"), so nested directories are found
- the skip test is `"wip" in rel.parts`, which still excludes wip/274/
while the song is in progress
- relative links resolve as (path.parent / rel_path), i.e. against the
file's own directory, so the three docs keep linking to each other
- the lrc field resolves as abs_path.parent / lrc_rel, so 274.lrc must
and does sit beside 274.md
Both scripts locate their inputs from __file__, so they needed no change;
verified after the move that --check is clean and the page rebuilds all
132 entries.
Non-Markdown files are never read by the pipeline at all.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S6MpcBisZYhX45oDGRRJoz
mikkeli