History

Doxa Maps 37edf77895 Two border peoples had no province, and my note blamed the wrong thing The table said Jing and Pana were "outside the twelve-province subset". Both provinces are IN that file — Guangxi and Yunnan. Measured: Jing sits 8.7 km outside Guangxi's outline and Pana 5.4 km outside Yunnan's. They are across the border, which is a fact about one coordinate standing for a whole people, not about a missing province. I shipped that wrong explanation twice, in the meta and in a commit message. Sourcing China's COMPLETE 34-unit ADM1 from geoBoundaries changes neither distance by a metre — same source geometry, 22 more provinces, none of them theirs. So better data is not the answer here, the downloaded file is deleted rather than staged for nothing, and the finding is written down so nobody repeats the experiment. A point within 15 km of exactly ONE province now joins it, carries near_border_km on its row, and is counted in meta as placed by nearest province. Two provinces inside the tolerance leave it unassigned: a near-miss is a hint, and a hint between two answers is not one. 1,007 assigned becomes 1,009 and unassigned 2 becomes 0 — with the two exceptions visible per row rather than dissolved into the total, because gospel-internet reads this file and should be able to tell a point inside a province from one 9 km out.	2026-09-27 04:23:09 +00:00
..
dx-maps	Two border peoples had no province, and my note blamed the wrong thing	2026-09-27 04:23:09 +00:00
README.md	Rename the output folder to dx-maps	2026-09-25 19:26:14 +00:00

Doxa Maps 37edf77895 Two border peoples had no province, and my note blamed the wrong thing

The table said Jing and Pana were "outside the twelve-province subset". Both provinces
are IN that file — Guangxi and Yunnan. Measured: Jing sits 8.7 km outside Guangxi's
outline and Pana 5.4 km outside Yunnan's. They are across the border, which is a fact
about one coordinate standing for a whole people, not about a missing province. I shipped
that wrong explanation twice, in the meta and in a commit message.

Sourcing China's COMPLETE 34-unit ADM1 from geoBoundaries changes neither distance by a
metre — same source geometry, 22 more provinces, none of them theirs. So better data is
not the answer here, the downloaded file is deleted rather than staged for nothing, and
the finding is written down so nobody repeats the experiment.

A point within 15 km of exactly ONE province now joins it, carries near_border_km on its
row, and is counted in meta as placed by nearest province. Two provinces inside the
tolerance leave it unassigned: a near-miss is a hint, and a hint between two answers is
not one. 1,007 assigned becomes 1,009 and unassigned 2 becomes 0 — with the two
exceptions visible per row rather than dissolved into the total, because gospel-internet
reads this file and should be able to tell a point inside a province from one 9 km out.

2026-09-27 04:23:09 +00:00

dx-maps

Two border peoples had no province, and my note blamed the wrong thing

2026-09-27 04:23:09 +00:00

README.md

Rename the output folder to dx-maps

2026-09-25 19:26:14 +00:00

README.md

public/ — the built output

This folder is GENERATED by bun run build; do not edit it by hand. It holds exactly one thing:

dx-maps/ — the output folder: 23 plugin bundles and 35 pages, self-contained. Copy this one folder to any web host (or open it from disk) and it works.
- dx-maps/index.html — the front page: the Plugin Studio, every plugin in one place.
- dx-maps/<plugin>/<plugin>.js — a plugin's bundle (a custom element; load it with a <script> tag).
- dx-maps/<plugin>/<page>/index.html — a ready-made page for one plugin view (embed it in an <iframe>).
- dx-maps/manifest.json — every plugin, page and embed snippet, machine-readable.
- dx-maps/assets/ — the data, fonts and images the plugins fetch at runtime.

The folder's name comes from name in vite.doxa-maps-build-config.json. Sources live in plugin-designs/, library/ and data/; rm -rf public/ && bun run build recreates all of this.