mikkeli
5ca0b871f8
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>
Northwich committee of magic researches songs repository
Just a collection of lyrics of songs. Probably will be managed into proper folders. Probably will have LRCs.
Publishing to the wiki
Song pages are auto-published to https://wiki.novoyuuparosk.org by the
songs pipeline in the companion repo novoyuuparosk-auto-wiki (the
"repo next door"). It triggers on push to master.
- Source-file contract (frontmatter fields, body conventions): see
pipelines/songs/SCHEMA.mdinnovoyuuparosk-auto-wiki. - Pipeline overview (branch convention, triggers, categories, LRC, etc.):
pipelines/songs/README.md.
In short: a file is published when its frontmatter has wiki.publish: true
and it isn't under wip/. The title field becomes the wiki page name.
Linking to another song page
Write an ordinary relative Markdown link. There is nothing to declare in the frontmatter:
For more behind-the-scene shenanigans, see [Dev gibberish](pulse_dev.md).
At publish time the .md target is swapped for the target file's own title,
giving a proper wikilink — so renaming a page means editing its title and
nothing else. The link keeps working in Gitea's blob view and in any editor
preview, because it is just a link.
Two things to know:
- The target must be published too (
wiki.publish: true, outsidewip/). Linking to a file does not publish it; an unresolvable link fails the CI run instead of quietly turning into plain text. - Links do not work inside a
```columnsfence — that block is verbatim by design. Put them in ordinary prose.
This replaces the old wiki.siblings frontmatter block and its ALL_CAPS
placeholders, which are gone.
Side-by-side lyrics (columns shorthand)
To lay two (or more) versions of a song next to each other — e.g. an original
and its translation — use a fenced code block tagged columns, with each
column separated by a line containing only ===:
```columns
**原題**
一行目
二行目
===
**Title**
first line
second line
```
Notes:
- Line breaks and blank lines are preserved verbatim (each column is rendered with line breaks intact).
Ncolumns ⇒N − 1===separators.- Use Markdown emphasis inside the block:
*italic*,**bold**,***bold-italic***. (No need for raw HTML.)
This is implemented entirely by the auto-wiki pipeline at publish time; the
authoritative description lives in
SCHEMA.md.
See kairo/kimito_en.md for a real example.