No generation. No approximation. Every contour in the Archive is traced from measured public-domain elevation and bathymetric data — USGS 3DEP for Earth, NASA MOLA and LRO for Mars and the Moon, and NOAA/GEBCO for the oceans — extracted in QGIS, cleaned by hand in Illustrator, and verified against the source. No AI generation at any stage.
Each Archive Entry has its own record. The product page surfaces the parts of that record that are ready. The Data page is where you can read it in full once verification is enabled.
Archive IDs appear on product pages and provenance cards. The format is HE-[WORLD]-[ENTRYNO]-[SLUG].
Type the Archive ID into the lookup above.
The record describes the terrain, the source dataset, the method, and any notice that applies. Fields populate as data is published.
Where a product page surfaces a field (for example contour interval), the Data record should agree. If they ever disagree, the Data record is authoritative.
Every product has an Archive ID printed on the packaging and shown on its product page. Enter it here to confirm its provenance.
Enter an Archive ID exactly as printed — for example HE-EA-26-001-HDM.
Each verification record can carry these fields. The set of fields that populate depends on the terrain, the source dataset, and the format. A real record is shown on the product page or in the lookup once published.
| Field | Value | Notes |
|---|---|---|
| Archive ID | When verification is published | Format HE-[WORLD]-[ENTRYNO]-[SLUG]. World codes EA, DP, SP. |
| Terrain | Where available | The name of the place behind the Archive Entry. |
| World | EA / DP / SP | One of the three locked world codes. |
| Subworld | Where applicable | An optional subdivision under a world (for example a planetary body inside Space). |
| Source dataset | When configured | The source of the underlying terrain data. Specific providers appear when published. |
| Dataset version | When configured | Identifies which version of the source data was used. |
| Method | Where available | How the data was extracted, interpreted, and edited. |
| Contour interval | Varies by terrain | The vertical step between adjacent contour lines. Only present where the visual system uses contours. |
| Verification status | Where available | Whether the record is verified, pending, or not yet published. |
| Last updated | When available | Date of the most recent change to the record. |
| Notices | Where required | Dataset-specific notices (for example, not for navigation) appear only where the source requires them. |
| Related products | Where configured | Tee, print, Complete Edition, Premiere, or Master Set links tied to this Archive Entry. |
| Per-plate records (Master Sets) | Where applicable | When a Master Set includes multiple terrains, each plate may carry its own Archive Entry. Set-level identifiers exist only when explicitly modeled. |
The table above describes the fields a record can contain. Enter an Archive ID above to see a real one.
The 3D Elevation Program is the authoritative elevation dataset for the United States. Derived from lidar and photogrammetry, it covers the contiguous US, Alaska, Hawaii, and US territories.
NOAA Coastal Relief Model for US waters, and GEBCO (General Bathymetric Chart of the Oceans) for global ocean and lake depths. Sonar-derived bathymetry at the highest available resolution per region.
Mars Orbiter Laser Altimeter for Martian terrain, and Lunar Reconnaissance Orbiter for the Moon. The same datasets used by planetary scientists and mission planners.
Raw elevation data is loaded into QGIS. The terrain is isolated, the contour interval is chosen based on the feature's vertical range, and contour lines are generated from the DEM.
Tool: QGIS · GDALContours are exported as SVG and opened in Illustrator. Every line is inspected: artifacts removed, index contours verified (every 5th interval), and the composition is set for the chosen template (V or S).
Tool: Adobe IllustratorThe finished contour set is cross-referenced against the source dataset. Elevation values are spot-checked. The Trophy Stat is verified against published records. The Archive ID is assigned.
Tool: QGIS + manualThe verified file is printed on 250gsm archival paper — matte, uncoated, acid-free, and FSC-certified — a museum-quality stock designed to resist yellowing and last for generations.
Output: 250gsm archival printThe method record describes how a terrain was read, what was kept, what was suppressed, and where the result was checked. Specifics live in the per-terrain record once published.
Source terrain data is extracted into a working representation before any visual decisions are made. The extraction step describes the operation, not the source provider.
Editing decisions are human. What stays, what goes, and how the place is framed are choices a person makes for that terrain.
The license field describes how the source data may be used and credited. Specifics appear in the per-terrain record.
Generative imagery is not used to invent terrain. Where operational tools are used elsewhere (for example, copy or QA), the record states what they are used for.
Verification covers cross-checking the extracted record against the source and confirming the editorial decisions. Status fields surface this for each Archive Entry.
Where a known issue exists with a specific record — for example, an upstream dataset correction — the record carries an issue note.
The provenance link surfaces the full record for that Archive Entry from the product page. The Data page is the destination of that link.
A verification record may include notices that apply to that specific terrain or dataset. Notices appear with the record, not universally across the catalog.
Where a source dataset requires a specific not-for-navigation notice, that notice appears with the verification record for that terrain. The page-level work is editorial.
When a source dataset has license or attribution terms, those terms appear with the record. Specifics live in the per-terrain field.
Where attribution is required by the source, the record carries the attribution text. The Data page does not assert a universal attribution string for the catalog.
If a source dataset is later corrected, the affected records may carry an issue note describing the correction and its effect on the Archive Entry.
Generative models can produce images that look like topographic maps. They cannot produce images that are topographic maps. The difference matters: a contour line either represents a measured elevation or it doesn't. There is no middle ground.
Every entry in the Archive is traceable to a specific dataset, at a specific resolution, processed through a documented pipeline. If you know the peak, you can verify the contours against the same public data we used. That is the product — not the aesthetic, but the accuracy.
We don't use generative models, style transfer, AI autocomplete, or automated contour simplification at any stage. A human chooses the interval. A human cleans the lines. A human checks the result.
No generative terrain · Documented process · Verifiable against source
Read the educational explainer, browse what's in the Archive today, or scan the FAQ for shorter answers.