Omnigraph
그래프 엔진으로 컨텍스트를 조립하고, 객체 저장소 기반에서 에이전트가 코드처럼 그래프 데이터를 분기·타입·검토·병합·감사·거버넌스합니다
Unofficial web viewer for the Roman Roads Research Association's Digital Britannia v1 dataset: Roman roads, forts, camps, settlements and milestones over LiDAR, historic OS maps and aerial imagery.
데이터PythonGitHub @adrianco온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Visualiser for the RRRA's roman road dataset
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Visualiser for the RRRA's Roman road dataset.
An unofficial web map viewer for Digital Britannia v1 from the Roman Roads Research Association. It shows the dataset's engineered Roman roads, forts, temporary camps, settlements, milestones and Hadrian's / Antonine Wall features over LiDAR hillshade, historic OS maps and aerial imagery.
Data: Digital Britannia v1, © Roman Roads Research Association / Mike Haken. CC BY-NC 4.0, non-commercial use only. This viewer is not endorsed by the RRRA.
The map is live at https://adrianco.github.io/romanroads/, served by
GitHub Pages from the docs/ folder of main. Each push to main redeploys
it within a minute or two.
The viewer fetches its GeoJSON over HTTP, so opening docs/index.html straight
from disk (file://) won't work. Serve the docs/ folder instead:
python3 -m http.server 8765 --directory docs
Then open http://localhost:8765.
Housesteads), a Roman
name (Vercovicium) or a road number (RR2, 2a). Road results zoom to the
whole route.#zoom/lat/lon), so you can share a link to
a specific spot.scripts/process.py). The GeoPackage's layers are
reprojected from British National Grid (EPSG:27700) to WGS84 (EPSG:4326) and
written as one GeoJSON file per layer.
Legionary Fortress / Legionary fortress), one garbled settlement
type, NULL text glued onto values (which broke some links), and padding
whitespace. The GeoPackage itself is never modified.layer_styles table. Roads are solid / dashed / dotted by
confidence; sites are coloured by type, as in the author's project.docs/index.html). A single page using MapLibre GL JS, with no
build step and no API keys. The full-fidelity data is 4.19 MiB in total,
under the 5 MB budget for a single page, so no vector-tile pipeline was
needed.docs/ERRATA.md). Every data issue found along the way, with
counts and examples, written up for the RRRA's next release.docs/adr/.Segment Confidence: solid = certain ±30 m,
dashed = probable ±200 m, dotted = conjectured. "No evidence" segments are
hidden by default. Margary RR number labels. Roads get a white halo so they
stay readable over the underlays.Why each source was chosen, and why others were rejected, is in ADR 0012.
data/digital-britannia_v1.gpkg source GeoPackage (EPSG:27700)
scripts/process.py GeoPackage -> per-layer GeoJSON (EPSG:4326)
requirements.txt pinned Python dependencies
docs/index.html the viewer (single page, MapLibre GL JS)
docs/data/*.geojson processed layers + manifest.json (itinere.geojson = Britain subset)
data/external/ third-party downloads (gitignored)
docs/ERRATA.md data issues to report back to the RRRA
docs/adr/ architecture decision records
python3 -m venv .venv
.venv/bin/pip install -r requirements.txt
.venv/bin/python scripts/process.py
The Itiner-e comparison layer comes from a 33.6 MB empire-wide file that isn't
committed. Only the Britain subset (docs/data/itinere.geojson) is. To rebuild
it, download itinere_roads.gpkg from
Zenodo record 17122148 into
data/external/ (gitignored) and rerun the script. Without the file, the
script keeps the committed subset.
Pleiades matching works the same way. Download pleiades-places-latest.csv.gz
and pleiades-names-latest.csv.gz from
the Pleiades dumps into
data/external/pleiades/, and the script re-matches and rewrites
data/pleiades_matches.csv and data/unmatched_pleiades.csv. Without
them, it reuses the committed match table.
A blog post records the development process over two days. Dev.to blog
data/unmatched_pleiades.csvVERCOVICIVMDurnovariaDVROVARIA