2a692021c0
The India ADM1 boundary is Creative Commons Attribution (CC BY 2.5 IN, sourced from DataMeet and the Election Commission of India), so the credit has to reach whoever receives the data. It did not: 6.1 MB of boundary GeoJSON shipped with no human-readable attribution, and a sidecar for one file of eight. data/boundaries/ATTRIBUTION now ships beside the data. Every licence value in it is verbatim from the geoBoundaries API, queried per boundary -- CC BY 2.5 IN for India, Public Domain for China. No licence wording is ours. ★ IT TOOK TWO ALLOWLIST EDITS, and the first one silently did nothing. The boundary staging is TWO-STAGE: a pair list gathers into the build pool, and a separate path list decides what reaches the tree. I added the file to the pair list, rebuilt, and it still did not ship. An entry in one stage of a two-stage pipeline is not an entry. WORLD-ADM0 IS CORRECTED, not closed. This register first guessed Natural Earth, public domain. It is geoBoundaries gbOpen assembled per country: its features carry geoBoundaries' own iso3/shapeGroup/shapeName, and the plugin's data/adm0/PROVENANCE.json names the source and endpoint. That file also states the real problem -- gbOpen passes each country's UPSTREAM licence through, so one file carries up to 162 licences and up to 162 attribution duties -- and its licences table is EMPTY. Which of the 162 are CC BY is unestablished. Stated in ATTRIBUTION as an undischarged duty rather than papered over. pplr's row is exp-shepherd's evidence: the PPLR ArcGIS org aggregating IMB, Joshua Project, ROP and WCD identifiers, publishing no licence at all, and WCD is a proprietary Brill database. |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| contributing | ||
| needs-eyes | ||
| readme-images | ||
| screenshots | ||
| CLOUD-DEVELOPMENT-ENVIRONMENT.md | ||
| CONTRIBUTING.md | ||
| develop-a-plugin-and-see-it-live.md | ||
| explanation.md | ||
| how-to.md | ||
| HOWTO-join-the-table.md | ||
| PRESET-PLUGIN-STANDARD.md | ||
| README-embed-example.md | ||
| README-embed-gospel-resources.md | ||
| README-SECTION-3-cli-commands.md | ||
| README.md | ||
| reference-capability-exemplars.md | ||
| reference-library-index.md | ||
| reference-universal-props.md | ||
| reference.md | ||
| THIRD-PARTY.md | ||
| tutorial.md | ||
| vendored-font-noto-serif-devanagari.md | ||
| vendored-fonts.md | ||
| why.md | ||
documentation/ — pick your path
"what is this?" "teach me" "how do I …?" "look it up" "all the detail"
│ │ │ │ │
why.md ──────────► tutorial.md ────► how-to.md ────► reference.md ───► architecture/
(2 min, 1 diagram) (first map) (task recipes) (tables) (contracts)
- why.md — the problem and the "map islands" idea. Start here.
- tutorial.md — build your first map, no jargon.
- how-to.md — recipes: embed, iframe, SPA, colors, CDN, mobile, tokens.
- reference.md — config fields, build scripts, the
profile-configcontract. - explanation.md — the model in 15 lines.
- architecture/ — the deep end: full contracts, the per-file catalog.
- README-embed-example.md — the drop-in README used when this bundler is embedded inside a host repo.
- README-embed-gospel-resources.md — the gospel map's URL contract for partner embeds: bring your own ISO 639-3 list, one country, one group, or the zero-access view.
Working on the repo:
- develop-a-plugin-and-see-it-live.md — ★ the golden path: zero to a plugin live, in 6 steps.
- README-SECTION-3-cli-commands.md — every command, per deployment method, with prerequisites.
- reference-capability-exemplars.md — which bundle is at which capability tier (generated).
- reference-library-index.md — the reusable
library/pieces you can import (generated). - CONTRIBUTING.md and contributing/ — how to contribute, and the bar for
library/.
Nothing on the simple path is longer than a few minutes; everything complex lives in
architecture/, linked from where you'd need it.