Two things: record where our forebears’ graves are, so later generations can still find them; and divide the visiting work clearly, so none is missed.
What this page covers
The live part is built — it lives in the clan area, behind a sign-in.
The public layer does two things, and does them well:
- A grave coordinate register with multi-format export — each forebear’s resting place recorded permanently, importable into phones and watches for navigation.
- Group assignment and route planning — which group covers which graves, in what order, over what distance, settled in advance so nothing is missed.
The third — watching clansmen’s movements live after signing in — sits in the clan members’ area (sign-in required), not on this public page.
Preventing omissions really rests on assigning graves in advance and exporting GPX — each group’s graves settled beforehand and loaded into phone and watch, so the responsibility sits on paper and in the watch. Live reporting lets those in the same party see where each other has got to: a supplement, not a substitute.
Coordinate systems: the single biggest cause of lost graves
Please read this section before recording any coordinate. A latitude and longitude captured by a phone in the village, if it comes from an Amap or Tencent base map, is GCJ-02 (the “Mars coordinates”). Baidu uses BD-09. But the datum required by GPX and KML is WGS84.
Use the converter below to bring a raw reading back to WGS84 before recording it. The conversion runs on your own machine: no network, no submission.
Conversion runs locally: no network, no submission, no logging.
What to record about a grave
Coordinates alone are not enough. Three graves stand in a row on one ridge; GPS tells you only that you are “nearby” — which one is your ancestor’s? So record these as well:
| Item | Why it is essential |
|---|---|
| Latitude and longitude (WGS84) | Basic fixing. Normalise the datum first — see above. |
| Elevation | Two points on a hillside may be tens of metres apart horizontally and a hundred vertically. Elevation is what rules out “the wrong tier of the hill”. |
| Fix accuracy (m) | A phone gives 5–15 m, a dedicated handheld 3–5 m, RTK down to centimetres. A point accurate to 50 m will send people to the wrong place — worse than no point at all. |
| Orientation (坐X向Y) | The traditional geomantic notation, using the twenty-four mountains. 向 is the direction the tombstone faces. No hiking app has this field, and it is the most effective way to tell neighbouring graves apart. |
| Condition | Intact / weathered / illegible / lost (record only). “Illegible” is the one to record earliest — once the strokes wear away, no amount of searching brings them back. |
| Inscription extract | Lineage, dates, the year the stone was raised. the “filial sons and grandsons” are transcribed as they stand; lacunae are written 囗, never guessed. |
| How to walk in | From which village, by which path, how many minutes on foot. Coordinates bring you near; the route brings you there. |
Dividing the work so that nothing is missed
What ruins a visiting day is not the walking — it is assuming someone else went. The remedy is simple and old: assign every grave to a specific group beforehand, in writing.
The planner below divides by geography, not by equal headcount — because a visiting party walks one hill and finishes it. Splitting by headcount puts the same hill in two groups’ lists, and both waste the trip. Once the split is settled you can export a GPX per group for phone or watch.
- Every grave assigned to a group appears in the GPX as a waypoint, so the watch announces the arrival — this is the “navigate to our forebear’s home” part.
- Each group also carries a route, which is what most sports watches use for turn-by-turn navigation.
- Planning and export happen entirely on your own machine: the browser generates the file, no server is involved, and this site cannot learn which graves you chose.
The distribution map: seeing at a glance whether anything is missed
The map below is drawn by this site itself: base map and coordinates are handled inside this site, and it sends no request to any online map service — which graves you look up never travel to someone else’s server.
It is the same set of coordinates: team splitting, routes, the exported GPX and this map all come from one function on one set of data — what is on the map cannot differ from what is on the watch. The grid and the scale bar are true distances.
There are no graves that may be drawn on the public layer.
This is not an omission — the gate is working. Registered graves: 0. Public-layer precision: “undefined”.
Publishing exact coordinates together with inscription photographs amounts to handing looters a numbered treasure map.
Exact positions are shown only in the clan area (after signing in), or distributed offline by the clan association.
Importing into phones and watches: formats and how-to
You are right that standard formats exist. The de facto standard for outdoor navigation is GPX, with KML second. This site produces three; pick by device.
| Format | Who accepts it | Notes |
|---|---|---|
| GPX 1.1 | Garmin, Suunto, Coros, Amazfit, 两步路, 六只脚, OsmAnd, Locus, Komoot | The common standard for hiking and watch navigation. First choice. Datum must be WGS84. |
| KML 2.2 | Google Earth, Google My Maps, 奥维互动地图 | Looks good; ideal for checking positions on a computer first. Weaker for navigation than GPX. |
| GeoJSON | QGIS, web maps | For people making maps. Not for device navigation. |
| FIT | Garmin devices (courses/activities) | Binary, lighter on battery, more fields. Most people do not need it; GPX is fine. |
One easy trap: in GPX, <wpt> (waypoints) and <rte> (routes) are different things. Watches navigate routes, but only waypoints show up as a marker labelled “our forebear’s home”. Supply one and you either cannot import it or arrive with no marker. This site supplies both.
- On a phone, 两步路 or 六只脚: Mine → Import track/waypoints → choose the GPX file. These two are what Chinese hill walkers mostly use.
- Garmin watch: Garmin Connect on the web → Training & Planning → Courses → Import GPX; or copy the GPX into
GARMIN/NewFiles/. - Suunto: Suunto App → Routes → Import GPX.
- Coros: Coros App → Me → Routes → Import.
- Apple Watch: does not ingest GPX itself. Use an app such as WorkOutDoors or Footpath to import the GPX, then sync to the watch.
- 奥维互动地图: import the KML to review positions and orientations on a computer first.
Files are downloadable under “Published waypoints” below. If your graves are marked clan-only (and so do not appear there), generate the file locally with the planner above, or ask the clan association for the offline file.
Downloads (import straight into phone and watch apps)
No files available yet
Reason: there are no publishable grave coordinates yet. Exact coordinates stay out of the public layer by default (looting risk).
Exact grave coordinates stay off the public page
The distribution map on the public page goes only as far as “which hillside, roughly how many graves”. Exact coordinates are distributed by the clan association as offline files — never posted here.
- Pick the graves you need in your own browser: GPX / KML / CSV are generated on the spot and land straight on your computer — the server never learns which graves you chose.
- “Finding them” depends on the file being in your hands, not on anything being posted publicly.
Live reporting: how to watch it, how to stop it
Inside the clan members’ area (sign-in required): one map carries the forebears’ positions and the positions of clansmen currently reporting — who has reached where, and which graves nobody has visited yet, at a glance.
The system flags anyone worth calling: someone with no fresh position for a long while has that row highlighted; someone far from the nearest companion is marked “detached”. Nobody has to press anything.
